Build an incident escalation matrix
Prepared 22 October 2026 by NightMarshal

An escalation matrix pairs each incident condition with a permitted action, primary owner, backup and no-answer path. Record acknowledgement separately from an attempted call so an unanswered message cannot look like an owned incident.

Instructions
1. Define incident categories and allowed actions.
2. Assign primary, backup and no-answer handling.
3. Test acknowledgement without contacting emergency services.

Open the blank CSV in a spreadsheet app; add one row per item. Use Pending for unknowns and N/A only where a field truly does not apply. Review the separate example CSV; all example values are fictional. Keep completed sheets private. Do not include passwords, access codes, personal contacts, footage links or camera stream URLs. No input is collected by these downloads.

Fields
Condition
Permitted action
Primary role
Backup role
No-answer path
Acknowledgement evidence

Fictional example
Fictional depot: an uncertain gate event goes to the duty manager. If the test call is unanswered, the deputy acknowledges through the agreed channel and owns the next decision.

Limits
The matrix does not guarantee police dispatch, attendance or response time. Actual actions require a site-specific agreement.