# Escalation Policy

> The rule for who gets the page next when no one answers.

**Field:** Infrastructure  
**Category:** Reliability  
**Also known as:** On-Call Escalation, Escalation Chain, Paging Policy

## Think of it like

Think of it like a phone tree. If the first person does not answer, the call goes to the next.

## Definition

An escalation policy says who gets an alert, and who gets it next if nobody answers. It is a list of steps, each with a wait time. The first on-call person is paged. If they do not answer in time, such as 10 minutes, the next person is paged, and so on. It makes sure no alert is left with nobody.

## Example

Lucy's policy pages the main on-call engineer first. After 10 minutes with no answer it pages the backup, and after 20 it pages the team lead.

## Why it matters

People sleep through phones and lose signal. The policy makes sure a real alert still reaches someone.

## Common mistake

Setting it up and never checking it. People leave, phone numbers change, and the chain ends at someone who is gone.

## Three principles

- **Who first.** The main on-call person.
- **Then who.** The next step after a wait.
- **Nobody left out.** Every alert reaches someone.

## Related terms

- [On-Call](https://learn.benibix.com/term/infrastructure/on-call)
- [Alerting](https://learn.benibix.com/term/infrastructure/alerting)
- [Mean Time to Acknowledge (MTTA)](https://learn.benibix.com/term/infrastructure/mean-time-to-acknowledge)
- [Incident Severity Level](https://learn.benibix.com/term/infrastructure/incident-severity-level)
- [Escalation](https://learn.benibix.com/term/business/escalation)

![An incident card labelled SEV1 at the top. Below it, an incident commander in the middle hands jobs to a fixer and to a communicator, who posts to a public status page. On the left, an escalation ladder pages the main on-call, then the backup after 10 minutes, then the lead after 20.](https://learn.benibix.com/diagrams/inf4-incident-roles.svg)

---

Source: https://learn.benibix.com/term/infrastructure/escalation-policy
Author: Behnia Zarei (a developer in Vienna, Austria, who builds and teaches data, AI and business intelligence at BENIBIX)
Publisher: BENIBIX Learn (https://learn.benibix.com/)
Last updated: 2026-11-19
Licence: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Quote freely with attribution.
