Maintain the incident contact tree
Keep current primary, alternate, supplier, property, emergency, legal, and leadership contacts with roles, availability assumptions, secure access, and tested escalation routes.
| Field | Value |
|---|---|
| Business area | security-continuity |
| Primary role | general-manager |
| Frequency | monthly |
| Privacy sensitivity | high |
| Security sensitivity | high |
| Compliance review | needed |
Trigger and handoff
Trigger: Scheduled review, staff or supplier change, or failed escalation attempt.
Inputs
- Current role ownership
- Contact and availability confirmation
- Incident scenario requirements
Outputs
- Approved current contact tree
- Identified coverage gaps
- Tested escalation evidence
Current manual methods
- Printed phone list
- Personal contacts
- Old incident-plan appendix
Human judgment and approvals
-
Assess whether coverage and authority are sufficient
-
Decide safe distribution and offline availability
-
Approval: General manager approves business contacts; security owner approves storage and access
Failure modes
- Departed person remains primary contact
- Contact list exists only in an unavailable system
Success metrics
- Critical roles have confirmed primary and alternate contacts
- Contact path is usable during a representative outage