On this page5 sections
The on-call calendar looks better after two rotations merge. Each engineer takes fewer primary shifts. Then a difficult incident arrives, and the same specialist gets called in again. The calendar has changed; the person answering the second phone has not.
That hypothetical comparison is why page counts and shift counts are only a beginning. Two rotations can receive the same number of pages while one handles short daytime incidents and the other interrupts several nights, calls in extra help and leaves repairs for tomorrow.
Follow the work until it stops occupying people's time. Who helped after the page arrived? What still needs doing? Which delivery commitment will move to make room for recovery? “Get some rest” is much easier to offer than a calendar with room to take it.
Thirty minutes on the clock, an hour of work
A page is a notification. It does not tell you how much effort followed. In an illustrative thirty-minute investigation, two fully engaged responders contribute one person-hour: half an hour from each person. The elapsed time is still thirty minutes. If both were off duty, the interruption also reaches two people's nights. Those are separate measures, not competing descriptions of the same cost.
Then the incident ends, but the work does not. Someone writes the handoff. Someone replaces the temporary repair. The specialist answers another question while trying to return to planned work. A record containing only the primary responder's time leaves those hours out.
A team average can conceal the same problem in another way. Most people may have a manageable week while one expert handles the hardest cases. Keep the distribution visible as well as the total.
Google's discussion of on-call connects operational work with the engineering time needed to improve a service. The local decision is whether this team can carry its service commitment alongside its other work. A staffing ratio from another organization is useful only when its assumptions fit this one.
Read diagram description
A conceptual map, not measured results. Follow the interruption, investigation, specialist help and unfinished work separately: a lighter primary schedule can still leave someone else carrying the hours. Diagram labels: Page arrives: Timing and interruption matter; Primary response: Investigation and recovery; Specialist assistance: Work outside the scheduled shift; After the incident: Cleanup, handoff and recovery time; Capacity plan: Change commitments to reflect the work.
Fewer shifts, but who still gets the call?
Return to the merged rotations. Fewer primary shifts are a real benefit. Yet the primary now has more systems to understand, and the same specialists support both families of services. The schedule alone cannot tell us whether the total workload fell or moved.
Trace a difficult incident through the primary responder, the backup, the specialist and the cleanup the following day. Do the available skills and recovery time fit the combined service? If not, the review needs to change an allocation: defer a delivery commitment, adjust coverage or make engineering time for recurring problems.
This is where a workload review becomes useful to the people doing the work. Recording the extra hours is not the same as making room for them. Somebody with authority over the plan must decide what those hours displace.
Look for the change people were promised
If alert cleanup was supposed to help, look for fewer unnecessary night interruptions while failure detection remains intact. If training was the remedy, look for the primary finishing more investigations without waking the specialist. If staffing increased, look for recovery time becoming possible and unfinished work getting smaller.
Compare periods with similar work, and note changes in service scope, incident mix and reporting. A quiet week is welcome, but it may be luck rather than proof that the new arrangement worked. Ask responders about help that never made it into the incident record, too.
Keep voluntary wellbeing information separate from performance scoring. This review is about fixing the operating plan, not diagnosing anyone's health. Calls, hours, coverage gaps and displaced commitments can support an allocation decision without turning personal disclosures into a score.
Put an end date on “just for now”
A rare incident may call for extra coverage. Name who will arrange relief, which commitments move, when the arrangement gets reviewed and what conditions permit ordinary coverage to resume. If that return keeps moving away, revisit the service commitment rather than renew the word “temporary.”
Not every repair needs a large sample first. An unstaffed dependency, a known permission gap or repeated calls to an off-duty specialist is already something to address. Limited observations should make claims of improvement cautious; they need not prevent action on a demand the team can identify.
The rotation design guide covers staffing and qualification, and the overload response guide addresses immediate relief. If alert cleanup is the chosen remedy, the alert acceptance method keeps failure coverage in view. This review supplies the connection to what the organization will fund, defer or stop.
Give the hours a place in the plan
A compact decision record keeps the review from ending at “the team seems busy.” Record the service promise, the work it creates and the choice that follows.
| Part of the decision | What belongs in the record |
|---|---|
| Service commitment | The covered services, expected response and known dependencies on particular skills. |
| Observed demand | Interruptions, disturbed nights, elapsed duration, combined effort and follow-up, recorded separately. |
| Work transferred | What backup responders, specialists or the next shift absorbed. |
| Conflicting commitments | The delivery or recovery commitment displaced by that demand. |
| Decision | Fund a repair, change coverage, defer work, narrow scope or accept a time-bounded surge through the proper owner. |
| How to judge the change | What should decrease, and which independent service signal must stay acceptable. |
| When to reverse it | The workload or coverage observations that would invalidate the change. |
| Accountable owner | Who can change the plan and when they will revisit it. |
If the merged rotation improves the primary calendar but leaves the specialist's nights unchanged, report both. Bring the calls, hours and unfinished repairs into the plan, then make room through training, repair work, coverage changes or recovery time. At the next review, follow those same pieces of work again. The person who was never listed as primary should be able to feel the benefit, not just see a better-looking calendar.
Sources & context
Sources linked in this article. Read alongside the author’s analysis; a citation does not independently verify a publisher’s claims.
- Google’s discussion of on-callsre.google
