Emergency Notification Checklist

The principal or designated incident commander confirms the report directly with the staff member who witnessed it — front-office secretary, teacher, SRO, or custodian. Do not push a notification on a secondhand report; rumors of lockdowns have closed buildings unnecessarily and damaged trust with families.

The classification drives template choice, channel mix, and who gets paged. Match to your Comprehensive School Safety Plan / EOP categories — most sites use Lockdown, Secure, Shelter-in-Place, Evacuate, Hold, and Reunification per the Standard Response Protocol.

Notification of families never precedes notification of law enforcement or EMS. Confirm dispatch has the building address, gate code, and the entrance officers should use. Stay on the line until told to disconnect.

Use the pre-approved templates inside SchoolMessenger, ParentSquare, Blackboard Connect, or Remind — whichever the district has standardized on. Templates exist for a reason: they are legally vetted, translated, and avoid the ambiguity that ad-hoc drafts produce under stress.

State what is known, what families should do, and when the next update will arrive. Do not name a suspect, describe a weapon, or speculate on motive — those details belong to law enforcement's public information officer, not the school. FERPA also restricts naming any student involved.

Title VI requires meaningful access for limited-English-proficient families. Verify Spanish and any other top home-language translations are attached or auto-translated by the platform. ELL coordinator can confirm the home-language list in the SIS.

Pull the audience from PowerSchool, Infinite Campus, Skyward, or Aeries — single school, grade band, bus route, or full district. Verify the list reflects today's enrollment, not a stale export. Include staff and substitutes; they often get forgotten when the alert is parent-focused.

Safety-critical messages go on every channel — voice call, SMS, email, app push, and the website banner. Families without smartphones or English fluency are the equity gap; SMS-only is not enough for a lockdown notice.

Press send. Capture the platform's send confirmation — message ID, recipient count, scheduled vs. immediate. The audit trail matters during an after-action review or an OCR / Clery inquiry.

Run the platform's delivery report — sent, delivered, failed, opted-out. Bounce rates above 5% usually point to stale contact data in the SIS, not a platform issue.

Office staff work the failed-delivery list by phone using the alternate contacts in the SIS. For lockdown or evacuation events, every family must be reached — not just the ones whose phones are current. Document each call with timestamp and outcome.

Families need a defined cadence — most districts commit to updates every 30–60 minutes during an active incident, plus an explicit all-clear. Silence after the initial alert is the single biggest driver of parent rumors and unauthorized pickup attempts.

Export the final message text, recipient list, delivery report, and approval record into the incident file. State retention rules typically require 3–7 years; check your district records officer's schedule. This is the file an auditor or OCR investigator will ask for.

Principal, SRO, communications, and any responding district staff walk through what worked and what didn't — message timing, classification accuracy, channel performance, translation gaps. Capture concrete fixes; vague resolutions like 'communicate better' don't survive the next event.