On this page3 sections
Before filling the calendar, decide what happens when it rings. Which services need coverage, during which hours, for what severity and with what response expectation? A business-hours question and an urgent service failure do not create the same staffing need. Without that distinction, on-call can become the place every unresolved problem is sent.
Equal primary shifts are only one part of distributing the promise. An apparently balanced rota may still rely on the same specialists whenever an incident becomes difficult. Designing the rotation means accounting for that supporting work as well as the visible schedule, then giving responders the access, practice and recovery time required to fulfill it.
What happens after the primary receives a page?
Each shift needs a primary, an active backup and reachable specialist routes. Describe how the assignment changes when someone cannot acknowledge, lacks the required permission or needs relief. A name in the backup field is useful only if that person knows about the assignment and is available to take it.
Follow a real practice page into the dashboards, incident record and recovery tools. Can the assigned person receive it, inspect the service and find help? Then remove the usual chat system and try the alternate route. The point is to discover what breaks between the name on the calendar and a useful response.
An exercise may show that the primary can recognize the problem but needs a particular expert to proceed. That is useful information for staffing: the escalation route requires an available person with the necessary expertise, not simply a contact entry. The primary schedule alone will not reveal how often this support is needed.
Read diagram description
Illustrative route: the primary responder uses backup support when unavailable, overloaded or unable to act. Specialists supply service expertise; test real delivery, access and an alternative communication path. Diagram labels: Urgent page: Service scope and severity are defined; Primary responder: Acknowledges, investigates or requests help; Active backup: Accepts coverage, relief or escalation; Specialist support: Reachable expertise and required authority.
A primary responder need not possess every specialist’s depth, but the rota must provide a reachable route to it. The hours spent helping the primary are part of coverage even when the specialist never appears in a scheduled shift. Count that support alongside incident response, recovery and ordinary absence when planning engineering work; otherwise an evenly divided calendar can still depend on the same people being available for two jobs.
Shadow shifts reveal access and knowledge gaps
Shadow shifts and bounded exercises let new responders learn common failures with help available. They should be able to interpret the usual alerts, locate the runbook and reach the right escalation route without guessing who might agree to assist. The exercise tests the service's support arrangements as well as the individual.
A stuck shadow responder can reveal three very different problems. They may lack access to the dashboard, need help choosing the recovery branch, or need a specialist who is not available. The fixes are access, supported practice and coverage respectively. Sending the person back to training for all three leaves two parts of the system unchanged.
Absence and recovery change the available capacity
Ordinary absence is part of the workload model. If the calendar works only with everyone present, it has already spent the capacity needed for leave, sickness and training. Cross-region coverage can move some work out of the night, but the outgoing responder still needs time to transfer the unfinished incident. A boundary on the calendar is not a boundary on the customer’s problem.
Agree how recovery after disrupted nights or long incidents changes the next day's plan. Which work moves, and who arranges coverage? Follow applicable organizational policies and agreements for scheduling and compensation. Reflecting lost project capacity in the plan makes recovery time usable instead of leaving the responder to reconcile two simultaneous commitments.
After launch, compare pages, overnight interruptions, active incident time and repeated specialist calls, alongside private feedback. These reveal burdens that shift counts conceal and give the team grounds to change scope, staffing or recurring page sources. The on-call load measurement guide develops that measurement in more detail.
Suppose merging two rotations halves the primary assignments but still wakes the same two specialists for every difficult incident. The visible calendar improved; their supporting workload did not. Include those calls, follow-up and recovery needs before deciding what the combined rota can cover. A useful calendar describes work the organization can provide, not work it hopes someone will absorb.
Source context
This article does not include external reference links. Read it as the author’s perspective and evaluate the guidance against your environment.
Report an error or outdated detail