Crisis Communication Team Roles and Responsibilities
Every district has a crisis communication team on paper. The question that decides whether it works is narrower: at 7:42am, with a police vehicle on campus and no confirmed facts, which named human writes the first sentence, which named human approves it, and which named human presses send. This page is nine role cards, two staffing models, and a succession rule.
| Role | Usually held by | First 15 minutes | Hands off to | Cut order when short-staffed |
|---|---|---|---|---|
| Incident commander liaison | Assistant superintendent or safety director | Stands next to the IC, relays confirmed facts only, times the first update commitment | PIO, continuously | Never cut |
| PIO / spokesperson | Communications director | Owns the public record, takes the first press call, sets the staging area | Superintendent for on-camera | Never cut |
| Message writer | Comms specialist or exec assistant | Drafts the holding statement from the template, plain language, sixth-grade reading level | Approver | Never cut |
| Approver | Superintendent or standing designee | Says yes or edits within 3 minutes; silence is not approval | Sender | Never cut — delegate instead |
| Sender / operator | Whoever is fluent in the notification tool | Selects audience, checks channel mix, sends test-to-me, sends | Logs the send time | Merge into writer |
| Front-office phone lead | Building secretary or registrar | Reads the approved script verbatim, logs every caller question | PIO, every 20 minutes | Merge into building admin |
| Social monitor | Anyone under 40 with a laptop | Watches parent groups and local pages, escalates by threshold, never replies unprompted | PIO | Merge into PIO after hour two |
| Translation lead | Bilingual staff member or EL coordinator | Reviews machine output before it goes, flags anything ambiguous | Sender | Machine-only with a review-later flag |
| Staff liaison | Principal or HR designee | Gets staff the message 5–10 minutes before families, and the reason why | Building admin | Cut first — but never skip the staff-first send |
"Cut order" is the question nobody asks until August, when three of these nine people are on holiday and a bus rolls over. Fill the column in during a calm week. The roles marked never-cut are the ones where a vacancy stops the whole chain rather than slowing it.
The three roles that decide everything, and the six that support them
Writer, approver, sender. If those three seats are filled by named people with named backups, a district can communicate through almost anything. If any one of them is ambiguous, the first message is late, and every subsequent problem is downstream of that.
The specific failure is worth naming because it is nearly universal. A district lists "Superintendent" as approver and nobody else. At 7:42am the superintendent is driving, or already at the scene, or on the phone to the county. The draft sits. Fourteen minutes pass. In those fourteen minutes a student posts a video, a parent group chat reaches 400 people, and the district's first message is now a correction rather than a statement. The fix costs nothing: write down a designee, write down the designee's designee, and write down the interval you wait before moving down the list. Three minutes is the interval most districts settle on.
The six supporting roles are not optional so much as compressible. A small district merges them. What cannot be merged is the duty: somebody is watching social media, somebody is answering the front-office phone with an approved script rather than improvising, and somebody is making sure staff hear it before parents do. Staff learning about a lockdown from a parent email is a morale injury that outlasts the incident by years.
Two staffing models, side by side
The 2,000-student district. Three people cover nine roles. The superintendent is approver and, if it comes to it, spokesperson. The communications-and-everything-else person is writer, sender and social monitor. The building principal is incident commander liaison and staff liaison, with the school secretary on the phone script. Translation is machine output with a bilingual staff member reviewing afterwards rather than before, which is a compromise you should make consciously and write down rather than discover.
The thing a small district gets right that a large one often does not: the three people know each other's mobile numbers by heart and can reach a decision in ninety seconds. Do not build process that destroys that advantage.
The 40,000-student district. Nine roles, nine or more people, plus a joint information centre once a county or municipal agency is involved. Here the risk inverts. Nobody is missing; everybody is present, and the message goes through four hands before it reaches a family. Measure your approval-chain latency in a tabletop exercise and treat any chain longer than two approvals as a defect. Add a standing rule that holding statements pre-approved in writing need no fresh approval at all — that is the entire point of having them written in advance.
Large districts also need a second sender. One person fluent in the notification tool is a single point of failure with a commute.
Succession, call-down and the after-hours card
Write a call-down tree that fits on an index card in a lanyard, and give every person on it the card. It contains, in order: role, primary name and mobile, backup name and mobile, second backup, and the wait interval before escalating. Nothing else. A tree that lives only in a shared drive is a tree nobody can open from a car park at 5:50am.
Three succession rules worth adopting verbatim:
- Silence is not approval. If the approver does not respond within the stated interval, authority moves to the next name automatically. Say this out loud in the plan so nobody has to decide it under pressure.
- The person at the scene does not write. Whoever is standing on the campus is a source of facts, not an author. Their attention belongs to the incident.
- One voice out. Everyone else, including board members, refers to the PIO. Put that sentence in the board handbook, not just the crisis plan, because a board member freelancing to a reporter is a predictable event. See media relations during a school crisis.
Counselling routing is a role duty, not an afterthought: whoever holds the staff liaison seat should have the district's mental-health lead and the counselling-resource paragraph to hand from minute one. Our post-crisis follow-up letter carries the standard block, including the 988 Suicide & Crisis Lifeline. The National Association of School Psychologists PREPaRE framework and the National Center for School Crisis and Bereavement both publish role guidance for the mental-health side of the team; where their guidance and this page differ, follow theirs, and follow your district's own crisis plan and counsel above both.
Wiring roles into the sending tool, honestly
Roles on paper have to survive contact with software, and this is where most districts discover a mismatch at the worst moment.
Kastr models one person with many effective-dated roles rather than one account per hat. A building secretary who is also a parent at a different school is one identity, so a role granted in August and ending in June is a dated row rather than a second login that outlives its purpose. Permission to send an emergency-flagged message — the flag that bypasses quiet hours and per-family channel preferences — is gated on a specific capability rather than on general admin rights, so the sender seat can be granted narrowly.
Two gaps you should plan around rather than be surprised by. There is no SSO and no MFA. Magic link is the only authentication Kastr has, for staff and families alike, which means the sender's email account is the security boundary and should be treated accordingly. Audience targeting resolves two shapes today: everyone, and an explicitly selected set of people. Grade, school and route presets do not resolve. For a multi-building district that means a tier 1 send is district-wide or hand-selected, and your plan should say which. Kastr is pre-launch and has no customer references; verify this behaviour by watching it happen, with us and with anyone else.
What does help the sender seat: cost-and-reach preview before sending, send-test-to-me, translation preview across languages before anything leaves, and an append-only audit log with a SHA-256 hash chain so the record of who sent what at which minute survives a records request months later.
Questions people actually ask
Who should be on a school district crisis communication team?
At minimum a writer, an approver and a sender, each with a named backup. Beyond that: an incident commander liaison who stands with operations, a PIO who owns the public record, a front-office phone lead working from an approved script, a social monitor, a translation lead and a staff liaison. Small districts merge these into three people; the duties still have to be assigned rather than assumed.
Who is authorised to speak to the media during a school crisis?
One person, named in advance, normally the communications director acting as PIO, with the superintendent taking on-camera moments where the district needs a decision-maker's face. Everyone else — principals, teachers, board members, coaches — refers reporters to the PIO. Put that instruction in the board handbook and the staff handbook, not only in the crisis plan, because board members freelancing to a reporter is a predictable failure rather than an unlucky one.
How does a small district staff a crisis comms team?
Three people covering nine duties. The superintendent approves and, if needed, speaks. The communications generalist writes, sends and monitors social. The principal covers scene liaison and staff notification, with the school secretary on the phone script. The compromise you accept is that translation gets machine output with human review afterwards rather than before, and you should write that down as a known limitation rather than let it surface during an incident.
What happens if the designated approver cannot be reached?
Authority moves to the next name on the list after a stated interval, usually three minutes, and the plan should say that silence is not approval. Districts that skip this rule find the first message delayed by ten to fifteen minutes, which is long enough for a student video and a parent group chat to become the primary source. Pre-approved holding statements sidestep the problem entirely for the first message, because they were approved in advance.
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.