How to Design an On-Call Schedule That People Can Sustain
A sustainable on-call schedule balances coverage with rest. Common patterns are weekly rotations with a primary and secondary responder, or follow-the-sun schedules across time zones that avoid night shifts. Aim for enough people that each is on call infrequently, hold structured handoffs, compensate on-call time, and measure page load so the schedule is fixed when it becomes unsustainable.
Start with rotation size
The number of people in a rotation determines how often each person is on call, which matters more than any scheduling pattern. With a weekly rotation, four people means one week in four, which many engineers find wearing over time. Six to eight people spreads the load considerably. If a team is too small for a sustainable rotation, options include combining rotations across related services, sharing secondary coverage with another team, or reducing what requires out-of-hours response.
Common schedule patterns
Each pattern trades handoff overhead against fatigue. Pick the one that matches your page volume and team distribution, then adjust based on measured load.
Weekly rotation
One person is primary for a week, often handing over on a weekday morning so the handoff happens during working hours. Simple, with few handoffs, but a noisy week is exhausting.
Split weekday and weekend
Different people cover weekdays and weekends, spreading the disruption of weekend coverage more evenly.
Daily or shorter shifts
Reduce continuous exposure per person, at the cost of more handoffs. Useful when page volume is high.
Follow-the-sun
Teams in different time zones each cover their own working hours, so nobody is paged at night. Requires enough engineers in each region with the context to respond, and disciplined handoffs between regions.
Primary and secondary
A primary responder receives pages first; a secondary is paged if the primary does not acknowledge within a set time, or is pulled in to help during larger incidents. The secondary role provides resilience against missed pages and gives newer engineers a way to learn on call with support. Rotate people through both roles, and consider pairing a new engineer as secondary with an experienced primary.
Handoffs
Hold handoffs at a consistent time during working hours. Cover open incidents, ongoing risks such as planned changes or degraded components, noisy alerts, and anything the incoming person should watch. A short written handoff note in a consistent place preserves context and builds a record of what on-call weeks are actually like.
Keeping it sustainable
- Measure load. Track pages per shift, pages outside working hours, and time spent on incidents. Review them regularly.
- Fix noisy alerts. Every page should be actionable. Treat non-actionable pages as bugs.
- Rest after bad nights. Let people start late or take time back after significant out-of-hours incidents.
- Compensate on-call time in line with company policy and local law, whether through pay, time off, or both.
- Allow swaps easily, with a simple process and schedule tooling that reflects them.
- Set an escalation path so nobody is left alone with an incident beyond their knowledge.
A sample weekly rotation
For a team of seven with a weekly rotation: each engineer is primary one week in seven and secondary the week before, so they start their primary week already familiar with current issues. Handoff happens on a weekday morning, with a written note and a short call. The secondary takes pages the primary misses after a set interval, and joins any major incident. Engineers who handle significant out-of-hours incidents take time back the following day. Page load is reviewed monthly, and any shift with more than a handful of out-of-hours pages triggers an alert review.
Tooling
Use scheduling and paging tools that support rotations, overrides, escalation policies, and time zones, and that integrate with your monitoring and incident tracking. The schedule should be visible to everyone, and it should be obvious at any moment who is on call for each service. Link incidents to the on-call shift in which they occurred, so load can be measured per person and per rotation.
Frequently asked questions
- What is the best on-call rotation schedule?
- The one your team can sustain. For many teams, a weekly rotation with primary and secondary roles and six or more participants works well. Teams across time zones can use follow-the-sun coverage to avoid night pages. High page volumes favour shorter shifts. Measure load and adjust rather than picking a pattern once.
- How many people should be in an on-call rotation?
- Enough that each person is on call infrequently and can recover between shifts. Six to eight is a common target for weekly rotations. Very small rotations, such as two or three people, are rarely sustainable for long, so consider combining rotations across services or reducing out-of-hours response requirements.
- Should on-call engineers be paid extra?
- Many organisations compensate on-call time with extra pay, time off in lieu, or both, and some jurisdictions have legal requirements about on-call work and rest. Compensation recognises the disruption of being available and responding out of hours. Check company policy and local employment law when designing a rotation.
- What is follow-the-sun on-call?
- It is a model in which teams in different time zones each cover on-call during their own working hours, handing over to the next region as the day ends. It removes most night pages but requires sufficiently staffed, well-informed teams in each region and disciplined handoffs between them.
- How long should an on-call shift be?
- Weekly shifts are common because they minimise handoffs, but they can be exhausting when page volume is high. Shorter shifts, such as daily or split weekday and weekend coverage, reduce continuous exposure at the cost of more handoffs. Choose based on measured page load and adjust when the load changes.