Escalation Policy

An escalation policy is a set of rules describing how an alert moves through people and channels if it is not acknowledged. Typically it names a first responder, a timeout, then a backup person, then a manager or a wider team.

Why it matters

Individuals miss alerts: phones are on silent, networks fail, people are asleep or ill. Without escalation, one missed notification can turn a short incident into a long outage. A written policy also removes ambiguity during stress, since nobody has to decide whom to call.

Example

Step 1  immediately   primary on-call (push + SMS)
Step 2  after 10 min  primary again (phone call)
Step 3  after 20 min  secondary on-call
Step 4  after 40 min  engineering manager

Severity can change the policy. A critical outage may notify two levels at once, while a low-severity warning only posts to a chat channel.

Common mistakes

• Escalation delays that are longer than the target response time.
• Not testing the policy, so outdated phone numbers are found during a real incident.
• Escalating forever to the same person with no final fallback.
• Failing to stop escalation once someone acknowledges the alert.

Related

• On-call
• Alert
• Severity levels
• MTTA

यह पेज सामान्य जानकारी है, जिसे हमारी संपादकीय टीम ने लिखा है और दस्तावेज़ीकरण बदलने पर अपडेट किया जाता है। सर्वर और प्रदाता अलग-अलग होते हैं, इसलिए बदलाव पहले सुरक्षित तरीके से जाँचें। देखें: संपादकीय नीति और अस्वीकरण.