Landing page
Your next post-incident review, held by the tool. 30 days.
A critical incident is the start of an improvement loop. EthosGov runs the post-incident review, writes back to the risk register, updates the training plan, and routes to the Director. 30 days to ready.
A critical incident is, at its core, the start of an improvement loop. EthosGov runs the review, writes back to the risk register, updates the training plan, surfaces to the Council pack, and routes to the Director. One review. Four audiences informed. No rekeying.
The Promise
In 30 days, your site is ready to run its next post-incident review inside EthosGov. When the next serious incident happens, the immediate response, the communication, the timeline and the review all happen in one surface. The archive is coroner-ready from day one.
What You Get
- Critical incident workflow configured to your site and your state's reporting obligations.
- Timeline, communication log and response actions captured in structured fields.
- Post-incident review template that writes back to the risk register and training plan.
- Council-scoped view of incidents within Council's oversight scope.
- Routed escalation to your Education Director.
- Immutable archive. Coroner-ready. Audit-ready.
What We Do
- Day 1-5. Governance Review. We walk through your last critical incident and the review process that followed. We identify the rekeying, the missing write-backs, and the places the learning evaporated.
- Day 6-15. Incident workflow configured to your site. Your risk register and training plan are linked as write-back targets.
- Day 16-25. Tabletop exercise. We run a simulated post-incident review through the workflow with your leadership team. Refinements made.
- Day 26-30. Live ready. Documentation handover. Director escalation path tested.
What You Are Not Being Asked to Do
You are not waiting for an incident to happen. The workflow is ready. The next incident, whenever it comes, runs in the surface.
You are not re-running your last incident review. You are making the next one better than the last one was.
Why This Works
Incidents are where the governance stack gets tested. A site that is incident-ready is a site whose Lead, Improve and Assure layers are working together. Getting the incident workflow live is a direct test of whether the platform reduces friction at the hardest moment.
Go Deeper Before You Book
- Public School Improvement - the cornerstone.
- Routing Critical Incident Escalation for Directors - the architecture.
- Improvement Cycles That Carry Through - the chain.
Ready?
Book the 30-Day Incident Readiness Pilot
Not sure yet? Book a Governance Review instead. 45 minutes. No commitment.
What you will see
The surfaces you ship with this wedge.
These are the working views Principal, Council and Director read from once the wedge goes live. Not marketing mock-ups: screens from the live product.
Why this wedge matters
The people this wedge is for are carrying this work right now.
We built it because the leaders we have been listening to for two years said they would pay almost anything to stop rebuilding your next post-incident review, held by the tool. 30 days. from three systems every cycle.
Your next post-incident review, held by the tool. 30 days.
A critical incident is the start of an improvement loop. EthosGov runs the post-incident review, writes back to the risk register, updates the training plan, and routes to the Director. 30 days to ready.