A trust with four schools is replacing a system that nobody liked. The brief says “something that works in a lockdown”. Three suppliers demonstrate, all three look fine, and the difference between them does not show up in a demonstration.
It shows up eighteen months later, when a deputy head tries to send to one building at 08:40 and cannot work out how, or when nobody can say which parents were told.
Mass notification systems for schools are sold on the lockdown scenario and bought on everything else: the wet Tuesday, the coach running late, the boiler failure that closes one building. The lockdown is why a trust starts looking. The ordinary weeks are what decides whether the system is still used in year three.
Choosing is not the same as alerting. How to reach parents, students and staff in the moment is a separate article. This one is about what to buy, and what to insist on seeing before you do.
What Mass Notification Systems For Schools Have To Do
Mass notification systems for schools send urgent messages to staff, students and parents across several channels at once and record who received them. For a school the selection question comes down to four capabilities, because almost every supplier can send a message.
- Targeting. Can it address one building, one year group, one shift of site staff, without anybody editing a list on the day
- Separation of audiences. Can one event produce different messages for staff, students and parents, sent together
- Proof. Does it produce a named list of who acknowledged and who did not, exportable afterwards
- Data flow. Does it stay current from the school information system on its own
Mass notification systems for schools that do the first and not the third are mailing lists with a better interface. The third is what a governing body asks for after the event, and it is the one capability nobody thinks to test during a demonstration. Published standards treat it the same way: the US National Fire Protection Association’s NFPA 72 covers emergency communications systems alongside fire alarm and signalling, putting the ability to communicate and record inside the system rather than beside it.
Two things are deliberately not on that list. Message templates matter enormously, but every supplier has them. Number of channels matters less than schools expect, because four channels that all arrive on one parent’s phone are one channel.
Six Checks Before You Commit
Mass notification systems for schools should be judged on these six, run as a scripted demonstration with the supplier driving and somebody from the school timing it. Ask for each to be done live rather than described. A supplier who will not demonstrate on their own system, with your structure loaded, is telling you something.
| # | Check | Ask to see it done live |
|---|---|---|
| 1 | Targeting | A message sent to one building, one year group, in under a minute, with nobody editing a list |
| 2 | Audience separation | One trigger producing three different messages to staff, students and parents |
| 3 | Proof of receipt | A named list of who acknowledged and who did not, exported afterwards |
| 4 | Data flow | A joiner and a leaver flowing from the school information system without manual work |
| 5 | Offline and fallback | The same alert sent with the main school network disabled |
| 6 | Day-to-day operation | A member of office staff sending a real alert, unaided, first time |
What A Weak Answer Sounds Like
Suppliers rarely say no. They say “that is on the roadmap”, “that can be configured”, or they answer a different question. The test for each row above is whether you watched it happen, not whether somebody said it could.
Staff, Students And Parents Need Different Messages
This is a selection criterion rather than a communications plan, and it is where mass notification systems for schools are weakest.
One event should produce three messages at once: an instruction for staff, a plain repeated instruction for students, and a holding message for parents that says the incident is managed and when the next update will come. A system that sends one message to three lists forces somebody to write three messages during the incident, which is the moment there is least time.
Ask the supplier to show one trigger producing three different messages to three audiences. Writing those messages, and deciding what each audience is told, is covered in emergency alerts for schools.
Lockdown, Evacuation And Roll Call
Lockdown and evacuation are the scenarios every school asks about, and the ones mass notification systems for schools handle least convincingly in a demonstration.
For a lockdown the system has to reach adults in rooms quickly and quietly, repeat the instruction, and let staff confirm without leaving a door. For an evacuation the hard part arrives afterwards: student accountability. Schools need to know, at a muster point, which students are present and which are not, and that answer has to be assembled from people standing outside in the cold.
Student accountability is where school emergency software is most often found wanting. Ask how roll call is taken, whether it works offline if the building network is down, and whether the result is a list a school can act on rather than a percentage. In England, the Department for Education’s emergency planning and response guidance for education settings sets out what settings are expected to plan for, and is worth reading before a requirements list is written rather than after.
Integrating With The Systems A School Already Runs
The integration that matters is the school information system, because it holds the groups. If classes, year groups and staff roles have to be maintained by hand in a second system, they will drift, and the drift shows up during an incident.
Three questions separate real integration from a file upload:
- Which named systems are supported, not “we have an API”
- Is synchronisation automatic and scheduled, or does somebody export a file
- What happens to a leaver, removed automatically or only flagged
Attendance and registration data is the related question. A school communication platform that can see attendance can tell you who was expected on site today, which is the starting point for roll call. Ask whether that link exists or whether it is manual.
Comparing Options: What To Ask A Supplier
When you compare k-12 crisis messaging software, the differences that survive contact with a real incident are not the ones on the feature matrix.
- Ask for the price of the thing you will actually use, including parent contacts, not a per-pupil headline
- Ask what happens when the main school network is down, since that is a scenario rather than an edge case
- Ask who administers it day to day, and what happens when that person is absent
- Ask to speak to a school of similar size and structure, and ask them what went wrong first
The best crisis communication tools for schools tend to be the ones a school business manager can operate without a manual at 08:40 on a Monday. Ease of use under pressure is a selection criterion, not a nicety, and it is the one that predicts whether the system is still in daily use two years later.
It is worth separating the trust-level question from the school-level one. A multi-academy trust buying centrally needs to know whether each school can send independently, whether one school’s administrator can reach another school’s parents by accident, and whether reporting rolls up. Those questions rarely appear on a shortlist and they decide how the system behaves once it is live.
From Pilot To Drill: Putting It In
Implementation is where mass notification systems for schools quietly fail, usually because the data was loaded once and never again.
A workable sequence: start with staff only, on one site, with real groups fed from the information system. Run one unannounced send and measure how many acknowledged inside five minutes. Add parents once staff acknowledgement is reliable. Only then add the scenarios that matter, lockdown and evacuation, and run them as drills rather than as tests of the software.
Review the contact data on a schedule that matches how fast it actually moves, which in most schools means parents more often than staff. Once a term is a reasonable starting point rather than a rule.
Budget for the part nobody quotes for: the time to build the groups properly the first time. Mass notification systems for schools usually disappoint because the data behind them was loaded once in a hurry, not because the software could not do what was asked of it.
What Goes Wrong After The First Year
The pattern is consistent enough that it is worth planning against. A system is bought, configured carefully, used twice, and then slowly stops being trusted.
Three things cause it. The contact data drifts, so a send that reaches 94% of parents reaches 71% a year later and nobody notices until it matters. The person who configured it moves on, taking the knowledge of how groups were built with them. And the system gets used for routine notices, which trains parents to treat its messages as ordinary post.
The counter to all three is mundane. Put the data refresh on a calendar with a named owner. Write down how the groups are structured, in one page, where the next person will find it. And keep a hard line between urgent sends and routine ones, ideally on different channels.
Mass notification systems for schools are not really bought once. They are maintained, and the schools that get value from them are the ones that budgeted for that from the start rather than discovering it in year two.
Multi-Academy Trusts: Buying For Four Schools At Once
Buying centrally changes the questions, and trust-level requirements are where most shortlists are silent.
Mass notification systems for schools are usually demonstrated to one school and bought for several. Four things decide whether that works:
- Can each school send independently, without waiting for a central administrator who is in a different building
- Can one school reach another school’s parents by accident, which is the failure nobody tests for and everybody remembers
- Does reporting roll up, so the trust can see acknowledgement rates across all sites without logging into each one separately
- Who owns the contact data, when each school runs its own information system and the trust runs none
A system that treats a trust as one large school will frustrate every school in it. One that treats each school as entirely separate gives the trust no view at all. Ask to see both the school view and the trust view in the same demonstration.
Procurement adds its own constraint. A trust buying under a framework has a shorter list than it realises, and the practical question becomes which of the available suppliers can do the six checks rather than which supplier is best in the abstract.
What It Costs To Run, Beyond The Licence
The licence is rarely the expensive part. Three costs appear afterwards and none of them appears on a quotation.
Message volume. Some suppliers price SMS separately from the platform. A school that discovers this during its first real incident will ration messages, which defeats the purpose. Establish whether urgent sends are metered before you sign.
Data maintenance. If the integration is a file upload rather than a synchronisation, somebody runs that upload. That is a recurring hour of someone’s week, and when that person leaves the upload stops.
Training turnover. Office staff change. Mass notification systems for schools that only one person can operate become unusable the week that person leaves, which is why “a member of office staff sending a real alert, unaided, first time” is on the six checks rather than being left to training.
A sensible way to compare is total cost over three years including message volume at a realistic incident rate, not the first-year licence.
One more cost is worth naming because it is almost always underestimated: the time to build the groups properly the first time. Year groups, forms, departments, site roles and parent contacts all have to be mapped from whatever the school already holds, and that mapping is the thing the system depends on for the rest of its life. Schools that rush it spend the next three years working around it.
Where Crises Control Fits
Crises Control’s Ping module reaches people through SMS, voice calls, email, push notifications, Microsoft Teams and web alerts, and recipients acknowledge with one tap. Alerts can be targeted at a single site, a department or an on-call rota, which is the targeting layer the first check asks about.
Automatic escalation continues until the right people respond. Every delivery, acknowledgement and response is recorded, creating a communication history that can be exported, which answers the proof check.
For the data question, the platform connects with Microsoft Entra ID, Google Workspace, Okta and any SCIM-compatible application for single sign-on and automated user provisioning, and supports secure imports by SFTP and CSV. The school emergency management software page sets out how this works across schools, colleges and universities, and Crises Control's alerting platform covers the sending side in detail.
What it does not do is make the selection for you, or decide what a school tells its parents. Those stay with the school, as they should.
Frequently Asked Questions
What should a school mass notification system be able to do?
Target one building, one year group or one staff role without editing a list on the day; produce different messages for staff, students and parents from one event; return a named list of who acknowledged and who did not; and stay current from the school information system automatically. Most suppliers do the first. Fewer do all four.
How do schools alert during a lockdown?
Quietly and repeatedly, to adults in rooms, with a way for staff to confirm without leaving a door. The harder part is afterwards: knowing which students are accounted for at a muster point. Ask how roll call is taken and whether it works when the building network is down.
How do schools reach parents and staff with different messages?
Through a system that treats them as separate audiences rather than separate lists, so one event produces a staff instruction and a parent holding message at the same moment. Writing those messages is a separate exercise from choosing the system, and is covered in the companion article on emergency alerts for schools.
How much do mass notification systems for schools cost?
The licence is the predictable part. The costs that surprise schools are metered message volume, the recurring staff time to maintain contact data where the integration is a file upload rather than a synchronisation, and retraining when the one person who can operate the system leaves. Compare total cost over three years at a realistic incident rate.
What should a multi-academy trust ask that a single school would not?
Whether each school can send independently, whether one school can reach another’s parents by mistake, whether reporting rolls up to a trust view, and who owns the contact data when each school runs its own information system. Ask to see the school view and the trust view in one demonstration.
This article was drafted with AI assistance and reviewed by the Crises Control team. Featured image: AI-generated.
