How to set up on-call rotations for a small team

Small teams get on-call wrong the same way most of the time. They hand the pager to whoever built the service and call it done. That burns someone out inside a quarter. Here is a setup that holds when you only have four to six responders.

Work through these:

• A weekly rotation instead of daily. Daily handoffs mean nobody ever fully switches off. One person owns primary for a week, then rotates out.
• A named secondary. If primary misses a page, it escalates to secondary in 5 minutes, then to a lead. Write the escalation policy down so it fires automatically, not when someone remembers to text.
• One-click overrides. Swapping a shift should need no manager approval. Life happens, and a rigid schedule just gets ignored.
• Coverage math. Four responders on weekly rotation is one week on, three off. Drop below four and you are one vacation away from a single person holding the pager alone.
• A load cap. Around 4 incidents per person per month is healthy, 15 or more is a resignation risk. Track it per person, because a rotation that looks fair on the calendar can be wildly unfair in real pages.

Rootly handles the schedule, escalation, and overrides, and flags when one person's load drifts high. What it cannot fix is being understaffed. If three people cover a 24/7 service, the tool will just show you that plainly.