Governance decides how it goes.The review proves how it went.
Command authority, escalation and decision frameworks built before an incident. Independent, evidence-based reviews after it.
The gap most organisations carry
Plans get approved and debriefs get held. Whether either one works is rarely tested.
What usually exists
- Emergency management plan approved and current
- Crisis management team names listed
- Escalation chart on file
- Regulatory compliance boxes ticked
- A debrief held after the incident
- Actions recorded in a spreadsheet
What's missing
- Command authority tested under realistic pressure
- Decision frameworks that function in chaos
- Escalation protocols proven to work
- Independent validation for board assurance
- A review that investigates, not reassures
- Corrective actions closed and verified
Twelve months later, a similar incident exposes the same gaps. Lessons identified are worthless until they are lessons embedded.
One loop. Build it, test it, fix it.
Governance sets the rules before an incident. The review shows whether they held. The findings go straight back into the governance.
Governance that holds
Who decides, on what authority, and when it escalates. Settled before the incident, not during it.
Command Authority Validation
Decision rights, delegations and conditions, tested in exercises with a traceable decision record.
Decision Assurance
Controls for the moments where executive judgement matters, so the call can be defended later.
Crisis Management Framework
Escalation pathways, notification and reporting that work under pressure.
How a Crisis Management Team works with the IMTPlan Review and Regulatory Alignment
Independent review against your regulator and your ground truth. Gaps named, not glossed.
Reviews that tell the truth
Did it hold? An independent, evidence-based account of what worked, what failed and why.
Post-Incident Review
Timeline reconstruction, decision-point mapping and the information flows that shaped the outcome.
Facilitated Debriefs and AARs
Hot debriefs and after action reviews run by practitioners. Honest input, no blame.
Contributing Factor Analysis
Incidents rarely have one root cause. We find the system conditions that combined to produce one.
Corrective Actions That Close
Prioritised actions with owners, dates and completion criteria, fed straight back into governance.
Officers carry a personal WHS duty.
Due diligence can't be delegated. Tested governance and honest reviews help show it is being met.
Regulatory and legal scrutiny
Regulators, coroners and courts examine what you decided and what you did afterwards. Exercised frameworks and a robust review are stronger evidence than filed paperwork.
Board assurance
Boards expect evidence that governance has been tested, and that findings were closed, not shelved.
Preventing recurrence
Without embedded corrective actions, the same system conditions produce the same incident.
Workforce confidence
Your people watch what changes after an incident. Visible fixes build trust. A superficial review does the opposite.
How we work
No generic templates. Start at any step: a governance build, or a review after an incident.
Assess
2-4 weeks
- Governance framework and document review
- Command authority and decision structure audit
- Regulatory alignment assessment
- Executive briefing on governance maturity
Build
6-12 weeks
- Governance framework and escalation pathways
- Command authority documentation
- Decision assurance and recovery governance
- Integration with existing operational systems
Test
4-8 weeks
- Desktop and functional governance exercises
- Recovery pathway testing
- Independent assurance assessment
- Board and regulator reporting
Review
After any incident or exercise
- Hot debriefs while detail is fresh
- Interviews, logs and timeline reconstruction
- Contributing factor analysis
- Corrective actions fed back into governance
Built to be acted on, not filed.
Governance Framework
- Command authority and delegations
- Escalation and notification pathways
- Decision assurance controls
Board and Regulator Reporting
- Capability, gaps and residual risk
- Exercise evidence and assurance findings
- Regulatory readiness documentation
Post-Incident Review Report
- Timeline and decision-point analysis
- Contributing factors
- Executive summary for board and regulator
Corrective Action Register
- Actions prioritised by consequence
- Named owners and agreed dates
- Tracking to verified closure
General information only, not legal advice.
Governance and review, answered.
What does emergency governance cover?
Who decides, under what authority, when decisions escalate, and how they are recorded so they can be defended afterwards.
What is a post-incident review?
A structured analysis, after an emergency, of what worked, what failed and what needs to change, across decisions, response actions, communication and governance.
How is it different from an after action review?
An after action review is a rapid team debrief soon after the event. A post-incident review goes deeper, examining system conditions, governance and decision-making. We run both.
Are your reviews independent?
Yes. Our reviews are independent, evidence-based and built to stand up to regulatory scrutiny.
Your board needs assurance. Your regulator wants evidence.
Building governance from scratch, testing what you have, or reviewing a recent incident. Start where you are.