Skip to main content
Ionhour
On-call

Writing on-call escalation policies people actually follow

An escalation policy only works if the people in it trust it. Keep the levels few, the timeouts honest, and the ownership obvious.

K

Kareem Arafa

September 1, 2026 · 1 min read

Most escalation policies are written once, during a quiet week, and then ignored during the incident they were meant for. The fix is to design them around how people really respond at night.

Fewer levels, clearer owners

Two or three levels cover almost every team:

  1. The on-call engineer for the service that alerted.
  2. A secondary who can step in if the first person is unreachable.
  3. A lead who can make decisions and pull in other teams.

Timeouts that match reality

If acknowledging an alert usually takes eight minutes, a five-minute timeout wakes the secondary for no reason and teaches everyone to ignore the policy. Review real acknowledgement times every quarter and adjust.

ShareXLinkedIn

Kareem Arafa

Founder, Ionhour

Kareem builds Ionhour and writes about the unglamorous work of keeping scheduled jobs, APIs and websites running.

Know the moment a job doesn’t run.

Cron jobs, websites, and APIs — watched 24/7, with alerts in Slack, SMS, or email.