On-Call Done Right: A Practical Guide for Small Engineering Teams

Description and use

A practical guide for small engineering teams to set up a reliable on‑call system with clear rotation rules, automated escalation, follow‑the‑sun coverage, and compensation policies.

Problem

Manual on‑call scheduling leads to coverage gaps, burnout, lack of escalation paths, and holiday blindness.

Outcome

Teams adopting the described workflow experience fewer missed incidents, balanced on‑call load, clear escalation paths, and improved morale.

Workflow

• Define primary and secondary on‑call roles and rotate weekly
• Set rotation limits (no more than 2 consecutive weeks per engineer)
• Schedule consistent handoff time (e.g., Monday 10am local)
• Implement escalation policy: primary 5min, secondary 10min, manager 15min, CTO 30min
• Track escalation automatically
• Plan follow‑the‑sun coverage for global teams
• Provide on‑call bonus and recovery days
• Use tools (PagerDuty, Opsgenie, Slack cron, or custom script) to automate scheduling and escalation
• Create and maintain a template for the schedule and escalation policy
• Avoid common mistakes: avoid newest engineer as primary, skip handoff, ignore holidays, make on‑call optional

Evidence

On-call rotations are the backbone of any reliable service. But most teams I have worked with treat scheduling as an afterthought — a spreadsheet someone updates manually, forgotten until 2am when the wrong person gets paged.

Source

PagerDuty: Best overall, but expensive for small teams

Source

Simple cron + Slack: For teams under 5 people, this works fine

Source