On-Call Without Burning Out the Team
On-call is where reliability and retention collide. Done badly it burns out your best engineer and trains everyone to ignore alerts. Four levers — a real rotation, alert quality, a severity ladder, and recovery — make it sustainable.
On-call rotation + escalation policy
Copy as markdown to paste into your repo, or download a branded PDF for sharing with non-technical stakeholders.
Frequently asked questions
How many people do you need for an on-call rotation?
A humane rotation needs at least three or four people who can hold the pager — fewer than that and the rest between shifts is too short to matter. If only two or three engineers can safely respond, that's your real problem: spread the operational knowledge before you spread the rotation.
What should actually trigger a 2 a.m. page?
A page that wakes someone has to pass two tests, both required: the problem is user-facing (a customer is being hurt right now) and actionable (there's something the responder can do immediately). Anything that fails either test gets demoted to a dashboard, a daily digest, or a business-hours channel.
How many pages per week is too many?
Track pages per person per week. Sustained above two or three, your alerts are too loud and your team is being trained to ignore them. The work of on-call between incidents is tuning that number down.
How many severity levels does an on-call policy need?
Three is enough. Sev1 is a customer-facing outage (page immediately, all hands if needed), Sev2 is degraded-but-working (page during hours, next morning otherwise), and Sev3 is a ticket. Write the definitions down so the 2 a.m. judgment is already made.
How do you keep on-call from burning people out?
Make it a system with recovery built in: compensate real off-hours work with time back or a late start, keep every postmortem blameless, and feed incidents back into alert tuning. The number that predicts burnout is off-hours pages per person — the 2 a.m. wakeups specifically — so fix it before someone quits.
What if we don't have enough people to staff a rotation?
That's the signal that too few people can safely hold production, not that on-call is broken. The fix is spreading operational knowledge — pairing on incidents, writing the runbooks, running game-day drills — so you build the bench before the hero burns out.
Get the next one.
New operating guides as we publish them — practical, infrequent, unsubscribe in one click.
The pager is a system. The Assessment checks whether yours is.
Kaan Systems does platform engineering and Terraform for funded SaaS, health-tech, and fintech. Compliance evidence is the by-product of that work. The Assessment looks at paging, severity, and whether the rotation survives one person being out. The 7-day Assessment is read-only. Book a call.