Templates

School Emergency Notification Scripts: Call and Text

An emergency notification is not an announcement. It is a timed sequence, and the district that has thought about T+15 and T+45 in advance sends better messages at T+0. This page ships the sequence, sixteen scripts, and the one script every district needs and nobody publishes: the retraction of an alert that was sent in error.

Last reviewed 2026-08-04 ยท Kastr is pre-launch; we publish dated status rather than logos.

Message sequencing — who hears what, and when
TimeAudienceChannelContentWhat it must not contain
T+0 to T+15All families and staff at the affected siteSMS first, voice failoverWhat protocol is active, that students are secure, do not come, do not callCause, names, numbers, reassurance
T+15Staff district-wideEmail + SMSOperational instruction for other sites, media routing, phone-line disciplineAnything not yet verified by the incident commander
T+30 to T+45All families at the siteSMS + voiceStatus, whether dismissal changes, when the next update comes"There is no danger" before an all-clear
T+45 to T+90Families, if reunification is activatedVoice + SMS + emailSite address, ID requirement, entrance, release authorityAny instruction that conflicts with law enforcement
On verificationAll families and staffSMS + voiceAll-clear, accounting, dismissal plan, counselling availabilityCasualty detail, suspect detail, student names
Same day, before dismissalAll families district-wideEmailFull letter: what happened, what was done, what happens tomorrowSpeculation about motive or investigation
T+24 hoursFamilies and staffEmailSupport resources, schedule changes, how questions are being answeredAnything that pre-empts an active investigation

Your emergency operations plan, your superintendent and the law-enforcement public information officer of record outrank everything on this page. The value of a sequence written in advance is that the argument about who is told what happens in a planning meeting rather than at T+4.

The first message, and the four things it must never contain

Lockdown, SMS, 142 characters. [DIST] EMERGENCY: [SCHOOL] is in lockdown. Students and staff are secure. Police on site. DO NOT come to school. DO NOT call. Update to follow.

Lockdown, voice, 34 seconds. This is an emergency message from [DISTRICT]. [SCHOOL] is in lockdown. Students and staff are secure inside the building and law enforcement is on site. Do not come to the school. Do not call the school office — the lines must stay open for emergency use. We will send another message as soon as we have verified information. Again, do not come to the school.

Spanish, SMS. [DISTRITO] EMERGENCIA: [ESCUELA] está en cierre de seguridad. Los estudiantes están seguros. La policía está presente. NO venga. NO llame.

Four things the first alert must never contain, each with the safe alternative:

  • A student's name, or any detail that identifies one child. "A student was taken to hospital" identifies a specific child in a small school as effectively as a name. Say "we are not releasing details about individuals" and mean it.
  • A suspect description. You will be wrong, and a wrong description sent to twelve thousand households produces vigilantism and a defamation exposure. Law enforcement issues descriptions, not the district.
  • An unverified casualty count. Numbers in a first alert are almost always wrong and are quoted forever. Say "we will confirm what we know once law enforcement has confirmed it to us."
  • "There is no danger." Before the building is cleared you do not know that. The safe alternative is a statement of fact about the protocol: "students and staff are secure and law enforcement is on site."

Sixteen scripts across the arc

  • Initial alert, cause unknown. Protocol name, secure statement, two instructions, promise of an update. Nothing else.
  • Hold in place. Explain it, because families do not know the word: students remain in classrooms, instruction continues, hallways are clear for a medical or operational reason.
  • Lockdown, internal threat. The script above.
  • Secure or shelter, external threat. Exterior doors locked, instruction continues inside, this is precautionary and driven by an incident in the neighbourhood.
  • Shelter for weather. Different instruction entirely. Say when the shelter is expected to lift and whether dismissal will move.
  • Evacuation, on-site assembly. Students are out of the building and at the assembly point, do not come yet, next update in [N] minutes.
  • Off-site relocation. The address is the message. Say it first, say it three times, spell the street.
  • Reunification activation. Site, entrance, ID requirement, and the sentence that students are released only to adults listed on the emergency card. Cross-reference the reunification templates.
  • Reunification, wait instruction. For families already queueing. Expected wait, why it takes time, and that every student is accounted for.
  • Medical emergency on campus, no threat. Sent because families will hear the sirens. Say there is no threat to the school, that emergency services are attending an individual, and that no details about that person will be shared.
  • Threat received, school operating normally. The one families most want detail on and the one where speculation does most damage.
  • All-clear. Protocol lifted, building cleared, all accounted for, dismissal plan, counselling availability, letter to follow.
  • Dismissal change following an incident. Time, doors, bus status, who may collect.
  • Next-morning message. What school will look like today, extra staff present, and what a family should do if their child does not want to come in.
  • Staff-only operational message. Media routing, phone-line discipline, and what staff may and may not say to a parent in the car line.
  • Correction of an alert sent in error. Below.

The correction script, and why it exists

Every district that has run mass notification for more than a few years has sent something in error — a drill message that went to the live audience, a template with the wrong school in it, a test that was not a test. Nobody publishes the retraction, so it gets written in a panic by the person who made the mistake.

SMS, 138 characters. [DIST]: The alert sent at [TIME] was sent in ERROR. There is no emergency at [SCHOOL]. Students are safe and classes are normal. [PHONE]

Voice, 36 seconds. This is [NAME], [TITLE] at [DISTRICT]. The message you received at [TIME] was sent in error. There is no emergency at [SCHOOL]. Students are in class and the school day is running normally. The message was sent because of [ONE-CLAUSE FACTUAL CAUSE], and we have taken steps to prevent it recurring. We are sorry for the alarm this caused. If you have questions, please call [PHONE]. Again, there is no emergency.

Four rules for the correction:

  • Send it within ten minutes. Every minute after that is a parent driving to the school.
  • Send it on every channel the error used, plus voice. A text correcting a voice call does not reach the household that only answers the phone.
  • Lead with the correction, not the apology. The first eight words must contain "sent in error" and "no emergency".
  • Give the cause in one clause, factually. "A drill template was sent to the live audience" is a fact. "Human error" is an evasion that invites a records request. Do not name the individual.

Reunification card, and what the platform does and does not give you

The instruction card for the receiving site, short enough to be read by a parent in a queue:

[DISTRICT] FAMILY REUNIFICATION — [SITE NAME], [ADDRESS]
1. Park in [LOT] and enter through [ENTRANCE]. Do not queue in the roadway.
2. Bring government-issued photo ID. Every adult must show ID, including staff.
3. Students are released only to an adult listed on the student's emergency card. If you are not listed, you cannot be given the student today, whatever the relationship. Speak to a staff member at the [DESK].
4. Expect to wait. Every release is checked against a record before the student is brought forward.
5. Do not go to [SCHOOL]. Nobody is being released from the school site.
6. Water and restrooms are at [LOCATION]. Staff in [COLOUR] vests can answer questions.

The limitation that matters most in an emergency. Kastr resolves two audience shapes: specific people, and everyone in the district. There is no school-level, grade-level or route-level targeting. For a single-school lockdown that means either sending district-wide — which alarms eleven thousand families who are not affected — or selecting that school's families as an explicit audience, which works, can be saved as a reusable preset and driven through the API, and takes preparation you must do before the incident rather than during it. If your emergency plan depends on picking one school from a dropdown at T+2, Kastr does not do that today. Build and save the audience presets now, or weight this heavily in your evaluation.

What the platform does contribute at T+0: an emergency flag that genuinely bypasses per-family channel preferences and quiet hours, gated on a capability rather than available to everyone; SMS-to-voice failover on terminal failure with the two records linked; row-level idempotency keyed on broadcast, person and channel, so a double-press or a crashed worker does not send the lockdown alert twice; and a per-district append-only audit log, hash-chained with SHA-256 and append-only at both the database role and the row-security policy, so the after-action question — what went out, when, to whom, authorised by whom — has an answer that is tamper-evident rather than merely stored.

Questions people actually ask

What should the first message to parents say during a school lockdown?

Four things and nothing else: which protocol is active, that students and staff are secure, do not come to the school, do not call the office. Add that another message is coming. No cause, no names, no numbers, and no reassurance you cannot yet support.

Do quiet hours apply to a school emergency alert?

An emergency notification is the clearest case for the emergency-purpose reasoning, and platforms including Kastr allow an explicitly emergency-flagged send to bypass quiet hours and per-family channel preferences. The discipline is keeping that flag genuinely rare: a district that flags event reminders as emergencies has spent the exemption and, more practically, has trained families to ignore the flag.

Should a school text parents before the facts are confirmed?

Yes, and this is the most common error in the other direction. Families will know something is happening within minutes from their own children's phones. A message that says what protocol is active and that students are secure is accurate at T+3 without knowing the cause. Waiting for a complete picture means the district is the last source families hear from.

What should the all-clear message say, and when?

Only after law enforcement or the incident commander has cleared the building and students are accounted for. It should say the protocol is lifted, that the building was cleared and everyone is accounted for, what the dismissal plan is, that counsellors are available, and that a fuller letter follows the same day. Do not send an all-clear to beat a news cycle.

How do you correct an emergency alert that was sent in error?

Within ten minutes, on every channel the error used plus voice, leading with "sent in error" and "there is no emergency" in the first sentence. Give the cause in one factual clause without naming an individual, say what has been done to prevent recurrence, and apologise for the alarm. The full script is on this page.

One price. Every feature. Locked for three years.

$3.50 per student per year under 5,000 students. No tiers, no add-on modules, no per-message fees. Published on the site because you should not have to book a call to learn a price.