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

说明与用途

为小型工程团队提供的实用指南，建立可靠的值班系统：明确轮班规则、自动化升级、跨时区协作和补偿政策。

问题

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

结果

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

工作流

• 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

证据

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.

来源

PagerDuty: Best overall, but expensive for small teams

来源

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

来源