Routing Critical Incident Escalation for Directors

When something goes wrong in a public school, the first phone call is almost always to the Director.

Not the Department. Not the Minister. Not the media line. The Director.

This is how the system is supposed to work. The Director is the first escalation point for incidents that rise above the site. It is the design. It is just also a design that depends entirely on the Principal picking up the phone.

And the Principal is not always in a position to pick up the phone.

What Escalation Actually Looks Like in Practice

Ask a Director to describe a critical incident in their portfolio, and the story usually starts the same way. They got a call. Sometimes at 2am. Sometimes from a Principal in tears. Sometimes from a police officer who got to the site before the Principal did. Sometimes from a parent who went directly to the Minister's office.

By the time the Director is on the phone, the incident is already at least an hour old. The Principal has been making decisions, under pressure, alone. The Deputy may or may not have been reached. The staff may or may not have been briefed. The evidence trail is forming in real time, mostly in text messages and incomplete file notes.

The Director's job in that moment is triple. Support the Principal. Surface what the Department needs to know. Make sure the incident is documented in a way that will stand up later.

None of those three things have infrastructure supporting them. All of them depend on the Director's personal capacity in that moment.

Why the Phone Call Model Fails

The phone call model fails in three directions.

First, it fails upward. The Director hears the version of events the Principal gives them. The Principal, under stress, may leave things out. Not through evasion, through the simple cognitive reality of being mid-incident.

Second, it fails sideways. The Director's peers, other Directors in the same system, never hear about the incident unless it bubbles up through Departmental channels. Patterns across a system stay invisible.

Third, it fails downward. The Deputy Principal who is actually running the response on the ground is often not on the call. The Administrator who is gathering the evidence is not on the call. The people who need the information are two steps removed from the conversation.

Every one of these failures is a design problem. None of them are caused by insufficient effort.

What Routed Escalation Looks Like

In a designed system, escalation is routed, not called.

When an incident is logged at a site, the relevant Director sees it within the same minute. Not as a phone call. As a live signal on their portfolio view, with a timestamp, an initial classification, and a pointer to who is running the response.

The Director sees what the Principal is carrying, in real time, without the Principal having to explain it.

If the incident meets Departmental thresholds, the escalation routes further. The right people at the Department see a notification. Not a summary. The source record. The same one the Principal, the Deputy, and the Director are all looking at.

Meanwhile, the response on the ground continues. The Deputy and the Administrator are logging against the incident in the moment. Every file note, every decision, every call made, becomes part of the record as it happens.

By the time the crisis is stabilised, the documentation is already complete.

The Coroner's Question

The test for any public-school incident record is not whether the Department is satisfied. It is whether, in the worst case, a Coroner would be.

A Coroner asks very specific questions. What was the first signal? Who decided what, when? Who was told, and when were they told? What evidence exists to support those claims?

In the phone call model, most of that information is reconstructed after the fact, from text messages, notebooks, and people's memories. Reconstruction is always partial. Reconstruction under legal scrutiny is always fragile.

In the routed model, the record is contemporaneous. It was written as the incident unfolded. It carries timestamps, identities, and a chain of custody that was never assembled, because it was produced by the work itself.

That difference is not academic. It is what makes the record defensible.

The Response Lives in Improve, the Archive Lives in Assure

One subtle piece of the EthosGov design sits here. Critical incident response, the live, in-the-moment work, lives in Improve. Not in Assure.

The reason is that an incident is, structurally, the beginning of an improvement cycle. Something went wrong. Something needs to be done now. Something needs to be learned so it does not happen the same way again.

Improve is where the response runs, the decisions get captured, and the post-incident review closes the loop back into the risk register and training plan.

The archive, the Coroner-ready historical record, lives in Assure. Immutable. Time-stamped. Auditable.

Response is dynamic. Archive is permanent. The two sit next to each other by design.

What This Changes for the Director

When escalation is routed, the Director's role in an incident shifts.

They stop being the information collector. The information is already in front of them.

They become the judgement caller. What does this need? Who else should know? Is this a portfolio pattern or a one-off? What support does this Principal need in the next forty-eight hours?

Those questions are the work. The work the Director is actually paid to do. Everything that happens before those questions, the phone call at 2am, the ring-around to figure out what happened, the reconstructing of the timeline, all of it gets taken off the Director's plate.

The result is not fewer incidents. Incidents will still happen. The result is that incidents stop consuming the Director's bandwidth in the way they used to.

The System Benefit

When escalation is routed across every Director portfolio in a state, a new capability becomes available to the Department.

Patterns. Not in aggregate, quarterly, retrospective form. In real time.

If three incidents of the same type occur across three different portfolios in a week, the Department sees it the week it is happening. Not in the next quarterly report. Not after a media cycle forces an inquiry. In the moment.

This is the capability the public system has been trying to build internally for a decade. Every attempt has failed because the data at the site has never been structured enough to roll up without distortion.

When the site-level data is clean, the system-level picture becomes composable. That is the Department dividend of the Oversee design.

Take the Next Step

If this article speaks to your situation, two routes from here.

Go deeper on the verb. Read the Oversee cornerstone. It is the deep page that sits underneath every article in this category.

See it on your site. Book a Governance Review. 45 minutes. No deck. We measure what the friction is costing you and whether EthosGov reduces it measurably.

---

Part of the EthosGov resources library. Governance infrastructure for public school systems. Lead. Improve. Assure. Oversee.