At 10:00 on a Thursday, three hours into an outage of the trust's central systems, the chair of trustees asks the chief operating officer three questions. Which of the twelve schools are open? Which are on paper registers? Which have told parents? The answers are spread across twelve WhatsApp groups.
Seeing the status of every school during an incident takes a fixed set of questions, one named reporter in each school, a deadline, and one place where the answers land.
A trust can only see how every school is coping with an incident if it asks in a set form. Each school answers the same five questions by a stated time, a named person is chased when an answer is missing, and every answer lands in one shared view.
What Is Trust-Wide Incident Status?
Trust-wide incident status is a single, current answer to a short list of questions about every school in the trust: whether it is open, what it has moved to paper, whether parents have been told, whether safeguarding cover is in place and what help it needs. It is a summary for decisions, separate from the technical recovery log.
Each school already knows its own answers. The headteacher at school seven knows the registers are on paper and the text to parents went at 08:20. The gap is one level up, where nobody holds all twelve answers at once. That makes seeing the status of every school during an incident a job for the trust.
Why Does Seeing The Status Of Every School During An Incident Matter?
Seeing the status of every school during an incident matters because the trust is accountable for all of them and makes decisions that depend on the whole picture: where to send IT staff first, what to tell trustees, and whether the incident has crossed a reporting threshold such as the closure of more than one school.
As at October 2026, the Department for Education (DfE) cyber security standard for schools and colleges lists the National Cyber Security Centre (NCSC) among the bodies to report to where an attack causes long-term school closure, the closure of more than one school or serious financial damage. A trust that can't count its closed schools can't tell whether that applies.
The Academy Trust Handbook 2026, effective from 1 October 2026, says the board of trustees holds collective accountability and responsibility for the trust (paragraph 1.10). A board can't discharge that from twelve separate phone calls.
What Does Multi-School Incident Visibility Have To Show?
Multi-school incident visibility has to show five things for every school, each with the time it was last confirmed: open, part-open or closed; which procedures are on paper; whether parents and staff have been told; whether a designated safeguarding lead (DSL) is on site; and what the school needs from the central team.
The table lists the five status items, what the trust needs to know about each one and who in the school reports it.
| Status Item | What The Trust Needs To Know | Who Reports It |
|---|---|---|
| Open, part-open or closed | The position now and any change planned for tomorrow | Headteacher |
| Paper procedures | Whether registers, sign-in and medication records are on paper | School business manager |
| Parents and staff told | Which message went, by which channel and at what time | Headteacher or office manager |
| Safeguarding cover | That a designated safeguarding lead or deputy is on site | Designated safeguarding lead |
| Help needed | Staff, devices, printing or a decision from the trust | Headteacher |
Five items is deliberate. Every extra question lowers the number of schools that answer on time. And each answer needs a time beside it, because "open" at 08:15 says little about 11:00.
The DfE's emergency planning guidance says settings should do their best to minimise the amount and length of any disruption to education, and that schools should have a trained DSL or deputy available on site. The five items let a trust check both. The guidance applies to England, schools elsewhere should check their own, and this article is orientation, not legal advice.
Will Headteachers Report Their Status When They Have A Moment?
Most won't, and the reason is sensible. A headteacher in the first hours of an outage is at the gate, in the office and on the phone to parents, and an update to the central team comes last. Status that depends on spare time arrives late, and it arrives first from the schools with the fewest problems.
That last point is the trap. The quiet schools report, the struggling ones don't, and the view the board sees is better than the truth. Without a rule for silence, seeing the status of every school during an incident becomes seeing the schools that are coping. Treat no answer as a status of its own: not confirmed.
Seeing the status of every school during an incident can't depend on goodwill, so the trust has to ask. A request with a deadline, sent to a named person and a deputy, turns a favour into a two-minute task. It also tells the headteacher that nobody from the central team will phone for the same information ten minutes later.
How Do You Collect Status Without Phoning Every Headteacher?
Collect status with one structured request per school in place of twelve phone calls. Send every school the same five questions at the same moment, name the person who answers and a deputy, set a deadline, chase only the schools that miss it, and repeat the request at fixed times through the day.
Take the trust from the opening scene, with that routine in place.
- 07:30. The incident lead declares a trust-wide incident and sends the first status request to twelve headteachers and their deputies.
- 08:00. Nine schools have answered. The request for the other three passes to their deputies.
- 08:20. Eleven answers are in. The operations lead phones the twelfth school, where the headteacher is dealing with a first-aid incident.
- 09:30. The second round goes out. Two schools have moved from open to part-open.
- 10:00. The chair of trustees asks the three questions. The chief operating officer reads the answers from one screen, with a time against each.
Each round leaves a record. The DfE's guidance on record keeping in an incident asks for detailed time references to build a timeline, and for a decision log that gives the rationale for key decisions and who made them.
How Does Crises Control Give A Trust One View Of A Live Incident?
Crises Control gives a trust one view by keeping the status request, the chasing and the answers in the same platform. The trust sets up one task per school, each with an owner, a deadline and an escalation rule, and task status feeds the live operational view in the Control Centre while the incident is running.
The request goes out through Ping by SMS, voice call, email, push notification and Microsoft Teams, and the platform tracks who has acknowledged. Task Manager holds the task for each school and escalates one that isn't accepted or completed in time, in stages the trust configures. The incident dashboard shows status, acknowledgements, response teams and task progress in one place.
This is the part of Business Continuity Software that a written plan doesn't cover. The plan says each school will report. The platform shows which ones have, and records each notification, task and decision as the incident runs.
The view shows what people have reported. It can't see into a building, so a headteacher who marks a task complete without checking makes the view wrong. The five questions, the named reporters and the reporting times have to be agreed by the trust beforehand. The platform makes seeing the status of every school during an incident quicker, and the decision about a school that is close to closing stays with the incident lead.
The School Emergency Management Software page describes the shared operational picture for central and site-based teams, and Incident Manager is where the incident itself is declared and recorded.
Trust-Wide Status Checklist
This checklist covers what has to be in place before seeing the status of every school during an incident is possible.
- The trust has agreed five status questions, and every school answers the same ones.
- Each school has a named reporter and a deputy.
- Status requests go by a channel that works when the trust's email is down.
- Every request has a deadline, and missed deadlines are chased by name.
- A school that hasn't answered is shown as "not confirmed", never as "open".
- Each answer carries the time it was given.
- Requests repeat at fixed times, and schools know the times in advance.
- The answers sit in one place that the incident lead and trustees can both see.
Twelve Schools, One Answer
Go back to 10:00 and the chair's three questions. With twelve WhatsApp groups, the honest answer is "I'll find out", followed by a long round of phone calls to headteachers who have better things to do.
With a status round at 09:30, the answer takes a minute. Ten schools open, two part-open, all on paper registers, parents told at eleven of them, and the twelfth being chased.
Seeing the status of every school during an incident is mostly a matter of agreement made on a calm day: which questions, who answers, by when. A trust can test it on any ordinary morning by sending the five questions and timing how long twelve answers take.
For the next step, read how schools reach parents when the MIS and email are down, what governors should ask before the next emergency, or how Crises Control supports business continuity during a live incident.
Frequently Asked Questions
What does seeing the status of every school during an incident involve?
Seeing the status of every school during an incident involves asking each school the same short set of questions, by a deadline, and collecting the answers in one place. The five things to track are whether the school is open, what is on paper, whether parents have been told, whether safeguarding cover is in place and what help is needed. Each answer should carry the time it was given.
What is trust-wide incident status?
Trust-wide incident status is one current summary of how every school in a trust is affected by an incident. It is built from the same questions, answered by a named person in each school at fixed times. The central team and trustees use it to decide where to send help and what to report.
Is a WhatsApp group enough for multi-school incident visibility?
A WhatsApp group is quick for conversation but weak for multi-school incident visibility. Messages arrive in the order people type them, so nobody can see at a glance which schools have answered and which have not. A structured request with a deadline gives every school the same questions and shows the gaps. A trust can keep the group for discussion and use a separate tool for status.
How often should a trust ask schools for a status update during an incident?
A trust should ask at fixed times that schools know in advance, with shorter gaps early in the incident. One workable pattern is a first request when the incident is declared, a second within two hours and another before the end of the school day. The right interval depends on how fast the situation is changing, and it should be written into the plan.
What is business continuity software?
Business continuity software helps an organisation carry out its continuity plan during a disruption by coordinating incidents, communications and response tasks in one platform. It replaces static documents and manual phone trees with alerts, assigned actions and live tracking of progress. Crises Control's business continuity software records each notification, task and decision as the incident runs.
This article was drafted with AI assistance and reviewed by the Crises Control team. Featured image: AI-generated.
