The escalation contact list is out of date. How should we manage it?
Unmaintained operational escalation dataGive the contact and escalation model an owner and a verification routine. Prefer maintained role-based channels where appropriate, with clear backup responsibility and coverage. Test the route safely so a critical incident does not become the first contact check.
What to do now
- Identify accountable escalation roles
- Verify current channels coverage and backups
- Test routing through an agreed exercise
- Assign update ownership and change triggers
When to escalate
An urgent incident cannot reach an authorized responder.
The service owner and authorized operational decision maker
Example
A role-based support channel replaces a personal contact who has left the vendor.
Mistake to avoid
Relying on a project slide containing former employees' phone numbers.
Prevent a repeat
Test whether receiving teams can operate and recover the service without depending on informal project-team support.
Suggested ApprovedFlow setup
- Tasks
- Documents
- Approvals
Keep handover tasks, operating evidence and the acceptance decision linked to the project while retaining monitoring and incident control in the actual service tools. See the platform
Related cases
- No one will accept the service owner role. What should I escalate?Unassigned operational accountability
- Business data errors continue after launch. Who should fix them?Undefined operational data ownership
- How do we manage decisions between governance meetings?Missing out-of-cycle decision route
- How do we manage a fixed launch date with uncertain technical work?Uncertainty near a hard date