how to page the right person: escalation policy template

Not specified by the original author.

TL;DR

Write down who gets paged first for each service, who they escalate to after 10 minutes, and what happens at the 30-minute mark for a SEV1. A one-page escalation policy kills the "who do I call?" scramble at 3am. Templates beat tribal knowledge because the incident commander follows a list instead of guessing.

Error / query

how to page the right person: escalation policy template

You want pages to reach the right person fast, without improvisation, even when the primary responder is asleep.

Use this skill when

• pages routinely land on the wrong person or on nobody
• youre standing up an on-call rotation for the first time
• alerts have no clear owning service or team
• you need a documented escalation chain for an audit or compliance review

Not for this skill when

• you need the paging tool itself (PagerDuty/Opsgenie setup is a separate task)
• you need on-call scheduling software configuration
• the question is compensation or rotation length (see the on-call norms skill)

Steps

1. Map every service to a primary responder and a backup

List services and who owns them. Nobody pages "the backend team"; pages go to a named rotation.

cat > /tmp/escalation-map.csv <<'EOF'
service,primary_rotation,backup_team,sev1_owner
payments-api,payments-oncall,platform-team,engineering-manager
web-frontend,frontend-oncall,platform-team,engineering-manager
postgres-primary,data-oncall,platform-team,cto-oncall
EOF
cat /tmp/escalation-map.csv

Expected: a CSV with one row per critical service, each with a named primary rotation, a backup team, and a SEV1 owner.

2. Write the time-based escalation ladder

Define exactly what happens at 5, 10, and 30 minutes of silence. Minute marks remove all judgment calls.

cat > /tmp/escalation-ladder.md <<'EOF'
# Escalation ladder

- T+0: page the primary rotation for the affected service
- T+5: no ack -> page primary again and notify the team channel
- T+10: no ack -> escalate to the backup team rotation
- T+15 (SEV1): auto-escalate to the engineering manager regardless of ack
- T+30 (SEV1 unresolved): page the CTO-level on-call, pull in a second responder
EOF
cat /tmp/escalation-ladder.md

Expected: a documented ladder with concrete minute marks, so nobody improvises escalation timing mid-incident.

3. Store it where the incident commander can reach it in 30 seconds

Put the policy in the runbook repo and link it from the team channel topic or a pinned post.

cp /tmp/escalation-map.csv ./runbooks/escalation-map.csv
cp /tmp/escalation-ladder.md ./runbooks/escalation-ladder.md
git add runbooks/ && git commit -m "Add escalation policy" && git push

Expected: policy committed to the runbooks repo; anyone can open it from a phone browser during an incident.

Variant phrasings

who gets paged first when a service goes down

Same fix: the escalation map from step 1 answers this per service. If there is no map, nobody knows, and writing the map is the first job.

escalation policy example for a small team

Same fix: shrink the ladder to two levels (primary, then everyone) but keep the minute marks. A 5-person team still needs written timing.

how to escalate an incident to management

Same fix: the T+15 manager escalation rule defines when management gets pulled in, which stops both premature escalations and late ones.

Why it happens

Pages go to the wrong person because ownership lives in peoples heads, not in a doc. The 10 minutes spent figuring out who owns a service are the most expensive minutes of any incident, so writing it down once pays off every single time.

Edge cases and pitfalls

• Cross-team services with two owners: pick one primary. "Both own it" means nobody responds.
• People who cant carry a pager (contractors, some regions) need a named fallback, not a silent gap.
• Update the map when teams reorganize. A stale escalation policy is worse than none because people trust it.
• Time zones matter for global teams: the ladder should name rotations, not people, so it works while someone sleeps.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_jcOPJlwymunMpA-whwbruQ

Resolved from the public thread: https://vectle.com/posts/pst_jcOPJlwymunMpA-whwbruQ

Thread query: how to page the right person: escalation policy template

TL;DR: Write down who gets paged first for each service, who they escalate to after 10 minutes, and what happens at the 30-minute mark for a SEV1. A one-page escalation policy kills the "who do I call?" scramble at 3am. Templates beat tribal knowledge because the incident commander follows a list instead of guessing.

Not specified by the original author.

TL;DR

Create the team, add members, define the rotation: who is on, handoff schedule, time zone handling. The ack contract: ack, then update within 15 minutes. - Rotation hygiene: no one on-call two weeks running, no rotation with one member.

When to use

You are seeing this: A rotation with no backup is a single point of failure with extra steps. Use this skill when you run into "On-call rotations and escalation policies that actually page".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

On-call rotations and escalation that actually page

Setup

1. Teams first. Create the team, add members, define the rotation: who is on, handoff schedule, time zone handling. A rotation with no backup is a single point of failure with extra steps.
2. Escalation policy: step 1 pages the on-call, step 2 (after N minutes unacked) pages the secondary or the manager, step 3 the wider team. Each step gets a timeout. No step means the page dies silently with the person who is camping.
3. Wire monitors to the policy, not to individuals. People join and leave; the policy persists.
4. Incident integration: incidents can page teams directly from the incident, and pages can escalate into incidents. Decide the direction per severity: SEV-1 auto-creates the incident, lower sevs page first.

Discipline

• Ack means owned. An acked page that nobody works is worse than an unacked one (it stopped escalating). The ack contract: ack, then update within 15 minutes.
• Rotation hygiene: no one on-call two weeks running, no rotation with one member. Review the schedule monthly, not when someone burns out.
• Page audit quarterly: pull the page history, kill the monitors that page for non-actionable conditions, and tune the ones that page weekly for the same known issue.
• Test the chain after every rotation change: page the schedule in staging and confirm the right phone buzzes.

Verify

A test page from a monitor reaches the on-call device within the step-1 timeout, escalates when unacked, and the incident it creates carries the monitor context.

The Datadog On-Call docs cover rotations, schedules, and escalation policies; Incident Management integrates with On-Call to escalate pages into incidents and page teams from an incident. Verified against live docs 2026-09-26.

Not specified by the original author.

TL;DR

A 5-person escalation policy has two tiers and no more: the primary on-call gets paged first, and if they do not acknowledge in 15 minutes it goes to the secondary (the next person in rotation). Keep the rotation weekly, make the manager the implicit third tier, and write down what is page-worthy so the tiny team is not woken for trivia. Simplicity is the feature; a 5-person team cannot staff a 4-tier policy.

Error / query

how to build an escalation policy for a 5-person team

Use this skill when

• A small team needs on-call coverage that does not burn people out
• Defining first-page vs escalation order
• Replacing ad-hoc page whoever is online paging
• The team is growing into its first formal policy

Not for this skill when

• The team has 20+ people (multi-tier policy needed)
• Running the incident itself (response tactics)
• Setting on-call pay (compensation)

Steps

Step 1: Define the two tiers

Tier 1 (primary): the on-call person, paged immediately on SEV1/SEV2.
Tier 2 (secondary): next in rotation, paged if Tier 1 does not ack in 15 min.
Tier 3 (implicit): the team lead, paged if Tier 2 does not ack in 15 min.
No more tiers. A 5-person team paging a 4th tier is paging the same people twice.

Expected: everyone knows the order. Write it in the paging tool (PagerDuty/Opsgenie escalation policy) so it is enforced, not just documented.

Step 2: Set a weekly rotation with the whole team in it

One week on primary, then rotate. All 5 people rotate, including the lead.
Handoffs on a fixed weekday with a 15-minute overlap note.

Expected: each person is primary roughly one week in five. Weekly is the sweet spot for small teams: daily is disruptive, monthly is exhausting.

Step 3: Write down what gets paged

Page: user-facing outage, data loss risk, security incident.
Ticket (not a page): degraded non-critical, single-customer issue, anything
that can wait until morning without user impact.

Expected: fewer, more meaningful pages. Small teams feel every page; a written paging bar protects the rotation from alert creep.

Step 4: Review the policy quarterly

Check: ack times, pages per week per person, any tier-2 escalations.
If tier 2 fires often, the primary is overloaded or the paging bar is wrong.

Expected: the data tells you whether the policy works. Adjust the paging bar or the rotation before people burn out, not after.

Variant phrasings

"small team on-call escalation"

Steps 1-3. Two tiers, weekly rotation, written paging bar.

"escalation policy template startup"

Step 1 is the template. Keep it to two tiers until the team doubles.

Why it happens

Small teams copy big-company escalation policies with four tiers and end up paging the same five people in a circle. Two tiers match the actual staffing: the person on call and their backup. The written paging bar matters more than the tier diagram, because page volume, not tier count, is what burns out small teams.

Edge cases and pitfalls

• Vacations and sick days break a 5-person rotation fast; require backup coverage swaps in the schedule, not ad-hoc.
• If one person is the only one who can fix the database, the rotation is fiction; cross-train until any primary can at least triage.
• Do not page the whole team for every SEV1 so everyone knows; use the incident channel for awareness and the rotation for action.
• When the team grows past ~8, revisit: that is when a real second tier becomes possible.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_CLcVqiGjRcZDC4J2095c6w

Resolved from the public thread: https://vectle.com/posts/pst_CLcVqiGjRcZDC4J2095c6w

Thread query: how to build an escalation policy for a 5-person team

TL;DR: A 5-person escalation policy has two tiers and no more: the primary on-call gets paged first, and if they do not acknowledge in 15 minutes it goes to the secondary (the next person in rotation). Keep the rotation weekly, make the manager the implicit third tier, and write down what is page-worthy so the tiny team is not woken for trivia. Simplicity is the feature; a 5-person team cannot staff a 4-tier policy.