What is an escalation policy
An escalation policy is a set of rules that decides who gets alerted when an incident triggers and what happens if they don’t respond. If the first person doesn’t acknowledge within a set time, the incident moves to the next person and keeps moving until someone picks it up.
Why every team needs an escalation policy
Every team that responds to incidents needs an escalation policy. It’s what makes sure an incident reaches someone who can act on it. Without one, an incident can trigger and simply stop there with no follow-through and no clear owner.
Also, it doesn’t matter how big or small the team is. From a small startup to a large organization, everyone faces the same fundamental problem: when something goes wrong, who is on it? An escalation policy answers that clearly.
What an escalation policy looks like
Say your payment service goes down at 11pm. A simple escalation policy for that might look like:
- Step 1: Alert the on-call responder via phone call
If not acknowledged in 5 minutes, move to step 2 - Step 2: Alert Alex (Senior Engineer) via phone call
If not acknowledged in 5 minutes, move to step 3 - Step 3: Alert Bilal (Engineering Manager) via phone call
The example has three steps but there’s no fixed limit. In Spike, you can add as many escalation steps as your team needs.
Not sure where to start? Spike provides ready-made escalation templates so you don’t have to build from scratch.
How escalation policies and on-call schedules work together
These two are often mentioned together but they do different things.
An on-call schedule answers the question: who is responsible for the incidents now? It’s a roster. It tells you that Alex covers this week and Bilal takes over next week. It manages on-call rotation and shift ownership.
An escalation policy answers a different question: what happens when an incident triggers? It decides who gets alerted and what happens if they don’t respond.
The two connect naturally. Your escalation policy will often point to whoever is currently on-call as the first step. But the on-call schedule doesn’t decide what happens if that person doesn’t respond. The escalation policy does.
A small team can start with just an escalation policy that alerts a few people. An on-call schedule becomes useful later once the team grows and rotating responsibility starts to make sense. But an escalation policy is something every team needs from day one.
FAQs
Is an escalation policy the same as an alert policy?
Yes, the two terms are often used interchangeably. Some tools call it an alert policy. The idea is the same: a set of rules that decides who gets alerted when an incident triggers and what happens next.
What happens if an incident resolves itself before anyone acknowledges it?
Most tools stop the escalation as soon as the incident is resolved or acknowledged. The policy only runs as long as the incident is active.
Can an escalation policy alert a whole team rather than an individual?
Yes. Some policies are set to alert an entire team rather than a specific person. This is common for critical incidents where you want everyone to be aware and ready to act.