Escalation Paths
You'll learn how to systematically escalate incidents when your team's expertise or authority isn't sufficient to resolve them quickly.
What Is an Escalation Path?
An escalation path is a predefined chain of communication and responsibility transfer that activates when an incident exceeds the initial responder's ability to handle it. Think of it like a hospital emergency room: triage nurses handle minor issues, but they know exactly when and how to escalate to specialists or trauma surgeons for cases beyond their scope.
Not every incident can or should be resolved by the on-call engineer alone. Escalation paths ensure critical decisions reach the right people without delay.
When to Escalate
Escalate based on severity, expertise, or authority gaps:
- Severity thresholds: Your runbook might say "SEV-1 incidents lasting >30 minutes require director notification"
- Knowledge boundaries: You've exhausted your troubleshooting steps and need a database specialist
- Decision authority: Fixing the issue requires taking a major service offline, which needs management approval
- Resource needs: You need additional engineers to investigate multiple systems simultaneously
How to Escalate Effectively
Your escalation should be informative and actionable:
- State the current situation clearly: "Payment processing is down for 45 minutes, affecting all regions"
- Summarize what you've tried: "Restarted services, verified database connectivity, checked recent deploys"
- Explain why you're escalating: "Need assistance from payments team to investigate transaction queue backlog"
- Provide context links: Include your incident channel, dashboard, and relevant logs
Document your escalation policy in runbooks so responders don't hesitate when needed. Escalation isn't failure—it's smart incident management.
Key Takeaway: Escalation paths define who to contact, when, and with what information when an incident exceeds your current capabilities—ensuring expertise and authority arrive where needed without costly delays.