Blog
Copy-ready escalation chains for a small team: who gets paged first, how long to wait before the next level, what acknowledgement means and how nights differ from days.
A practical escalation policy example for a small team has three levels. The primary on-call engineer is paged first. If nobody acknowledges within 5 minutes, the secondary is paged. If there is still no acknowledgement after another 10 minutes, the engineering lead or founder is paged and the page repeats until someone owns it. Run one policy for business hours and a separate, stricter one for nights that only fires on critical alerts and allows a little more time to wake up.
This article gives you concrete chains you can copy, explains how to choose the timeouts between levels, defines what acknowledgement should actually mean and shows how to adapt the policy to teams of two to six people. Who is on call in a given week is a separate question, covered in our guide to on-call rotation models for small teams. Here we focus on what happens after the first page goes unanswered.
An escalation policy is a set of rules that decides who gets notified next when an alert is not handled. It is different from a schedule: the schedule says who is primary this week, the policy says what happens when that person does not respond.
Every usable policy answers six questions:
If any of these is missing, the policy has a gap that will show up at 3 a.m.
The following is pseudo-configuration, not the syntax of a specific tool. It describes a business-hours policy for a team of three engineers plus a lead.
policy: prod-critical-business-hours
applies: Mon-Fri 09:00-18:00 (team timezone)
severity: critical, high
levels:
- level: 1
target: schedule:primary
channels: [push, slack-dm]
escalate_if_not_acked_after: 5m
- level: 2
target: schedule:secondary
channels: [push, sms]
escalate_if_not_acked_after: 10m
- level: 3
target: user:engineering-lead
channels: [sms, push]
repeat_every: 10m
max_repeats: 3
then: notify channel:#incidentsLevel 1 uses push and a direct message because during the day the primary is at a desk. Level 2 adds SMS because the secondary is not expecting to be paged and may be in a meeting. Level 3 goes to a named person, not a schedule, because the lead is the person who can reassign work or pull someone out of a meeting.
The final step posts to a shared incident channel. At that point the alert has been ignored by three people for roughly 25 minutes, and visibility matters more than noise.
14:02 API health check fails from 3 regions, alert fires
14:02 Level 1: primary (Anna) gets push + Slack DM
14:07 No ack. Level 2: secondary (Ben) gets push + SMS
14:09 Ben acknowledges. Escalation stops.
14:09 Anna is informed that Ben owns the alert
14:31 Monitor recovers, alert resolves automaticallyNote the last two lines. The person who missed the page should be told that someone else took over, otherwise two people may start working on the same problem in parallel once Anna returns to her phone.
Timeouts are a trade-off between giving people enough time to respond and keeping total time to engagement acceptable. Work backwards from your reliability target: if a critical outage must have someone actively working on it within 15 minutes, the sum of your level 1 and level 2 timeouts must stay below that.
Reasonable starting values for a small team:
Avoid timeouts under 3 minutes. They do not give anyone a realistic chance to respond and effectively turn a sequential policy into paging everyone at once. Also avoid timeouts above 15 minutes for critical alerts, because a single missed page then costs more downtime than most small SaaS products can afford.
Acknowledgement is the action that stops escalation. Teams often treat it as a reflex, tapping the button to silence the phone. That makes the policy useless, because the alert is now owned by someone who is not working on it.
An acknowledgement should mean exactly one thing: I own this alert and I am looking at it now. Write that sentence into your on-call guidelines.
Some rules that keep acknowledgement honest:
A single policy for all hours either pages too loudly during the day or too softly at night. Split it.
policy: prod-critical-night
applies: Mon-Fri 18:00-09:00, Sat-Sun all day
severity: critical only
levels:
- level: 1
target: schedule:primary
channels: [sms, push-critical]
escalate_if_not_acked_after: 10m
- level: 2
target: schedule:secondary
channels: [sms, push-critical]
escalate_if_not_acked_after: 10m
- level: 3
target: user:engineering-lead
channels: [sms, push-critical]
repeat_every: 10m
max_repeats: 4The differences from the daytime policy are deliberate:
Deciding which alerts are critical enough for nights is the hard part. If your night policy fires more than occasionally, the problem is usually alert quality, not the escalation chain. Our article on cutting alert fatigue with actionable pages covers how to filter that list.
The three-level example assumes enough people to have a distinct primary, secondary and lead. Smaller and larger teams need small adjustments.
Level 1 is the primary, level 2 is the other engineer, level 3 is the founder or whoever owns the business risk. Accept that the secondary is effectively always on call and keep the night policy very strict so that this does not burn people out.
Keep primary and secondary as schedules, and make level 3 a small schedule of leads instead of one named person, so a single manager is not the fallback for every night of the year. Consider separate policies per service if teams own different systems.
The engineering lead belongs at level 3, not level 2. Putting a manager directly after the primary turns every missed page into a management event and discourages honest reporting of missed alerts. At level 3, the manager's job is not to fix the outage but to find someone who can.
Step 7 is the one most teams skip. A policy that has never been tested end to end usually fails at the last level, because a phone number is outdated or a notification is filtered.
In m0nitor, on-call schedules define rotations, temporary overrides for holidays and swaps, and do-not-disturb hours, and alerts are routed to whoever is on call. Alert workflows automate reactions to monitor events, such as notifying a channel, creating an incident or calling a webhook, which covers the routing of business-hours and night alerts to different targets.
Alerts can go to email, Slack, Discord, Microsoft Teams, Mattermost, Telegram, Pushover, SMS, PagerDuty and ilert, as listed on the alert channels and integrations page. If your team already runs timed multi-level escalation with acknowledgement in a dedicated paging tool, forwarding alerts there is one option. The policy design in this article applies regardless of which tool executes it.
An escalation policy is an ordered set of rules that decides who is notified when an alert is not acknowledged in time. It defines the levels, the people or schedules at each level, the notification channels and the timeouts before moving to the next level.
For small teams, three levels are enough: primary on-call, secondary on-call and a final fallback such as the engineering lead or founder, with repeated notifications at the last level. More levels mostly add delay without adding people who can actually respond.
The schedule determines who holds the primary and secondary role at a given time. The escalation policy determines what happens when the person currently on call does not respond. Policies should reference schedules rather than names so they stay correct when the rotation changes.
Start with 5 minutes from level 1 to level 2 during business hours, 10 minutes at night, and 10 minutes from level 2 to level 3. Adjust so that the total time until someone is actively working on a critical alert stays within what your reliability target allows.