You have been asked to set up on-call, or to fix a rotation that wears people out. This guide covers the setup steps, rotation examples including follow-the-sun and 4-3-3-4, a handoff checklist and a copyable template. The goal is one owner per alert, a quiet handover, and everyone else off duty.
What is an on-call schedule?
An on-call schedule defines who responds to alerts at any moment and who backs them up. It covers responsibility outside and inside working hours.
A rotation hands that responsibility from one person to the next at a fixed handoff time. For example, the shift changes weekly at 10:00 on a Monday in a specific timezone.
The primary person is notified first when an alert fires. The secondary person acts as the backup if the primary does not acknowledge. An escalation policy decides who is notified next and after how long.
How to set up an on-call schedule
1. Decide what needs covering
List the services and alerts that require immediate human response. Not every alert needs a person. Some can be fixed by automated runbooks or resolved by the next business day.
Determine the hours of coverage. Some services need a person around the clock; others only during working hours. Be explicit about which hours apply to each service.
2. Pick a rotation length and handoff time
Choose a rotation length that matches your team size. Weekly rotations are common. One person owns the week. Daily rotations spread the load more evenly but require more frequent handoffs.
Set a fixed handoff time. A weekly rotation might hand off at 10:00 on Monday. A daily rotation might hand off at 09:00 every morning. The key is consistency. Everyone knows exactly when responsibility shifts.
Hand off during working hours. Both the outgoing and incoming engineers should be awake and available. A midnight handoff makes a proper transfer of context impossible. Keep the handoff time in a single timezone.
Keep the rotation large enough. Each person should be on call for a minority of the total time. If the rotation is too small, people burn out.
3. Add a backup and an escalation policy
Never rely on a single person. Always have a secondary or a next level in the escalation policy. The primary is notified first. If the primary does not acknowledge within a set wait time, the alert escalates to the secondary.
Define the escalation policy clearly. Specify the wait time for each level.
4. Plan for holidays and swaps
Plan for time off in advance. Do not wait until the last minute to find a replacement.
Use overrides or substitutions to handle time off. A substitution temporarily replaces the primary for a specific date range. The original rotation resumes automatically after the substitution ends. This keeps the schedule predictable.
Communicate planned time off early. Update the schedule so everyone knows who is covering during those days. This prevents gaps in coverage.
On-call rotation examples
Teams choose rotation shapes based on alert volume, team size, and timezone coverage. The following patterns cover the most common needs.
Weekly rotation
A weekly rotation assigns one person as primary for seven days. The responsibility passes to the next person at a fixed handoff time, for example Monday at 10:00. This is the simplest model to set up. Everyone knows their week in advance.
A week is a long time to be responsible for alerts. If pages are frequent, a single person can burn out before the handoff. If pages are rare, a week is fine.
Weekday and weekend split
This pattern separates weekdays from weekends. One person covers Monday through Friday. Another person covers Saturday and Sunday.
The weekend becomes its own turn, so weekend duty rotates separately from the week.
Follow-the-sun rotation
Follow-the-sun assigns shifts based on timezone. People in different regions cover their own daytime hours. When one region's workday ends, the next region's workday begins. This ensures nobody is on call at night.
This model requires people in at least two regions. It also requires a handoff at the end of each region's day. The handoff must be smooth so that no incident is lost between regions.
Follow-the-sun respects local time and reduces late-night pages. It does not reduce the total number of pages, but it distributes them across the day.
What is a 4-3-3-4 rotating schedule?
The 4-3-3-4 pattern comes from industrial shift work, such as 12-hour shifts in manufacturing or healthcare. In this model, someone works 4 days, has 3 days off, works 3 days, then has 4 days off. Over two weeks, people alternate between long and short blocks.
For software on-call, this is less common than weekly handoffs. Software incidents do not always follow a 12-hour shift rhythm. However, the alternating block structure has an advantage: it spreads weekends fairly.
If your team prefers longer blocks of time off, 4-3-3-4 can work. A weekly rotation or a weekday/weekend split is simpler to manage. Use 4-3-3-4 only if your team specifically wants alternating block lengths.
On-call handoff checklist
A clear handoff transfers context so the incoming engineer can respond immediately. Hold the handoff when both people are at work, not at midnight.
- Open incidents and their current state.
- Anything noisy, snoozed, or silenced.
- Planned changes and maintenance in the next shift.
- Known risks and fragile services.
- Anything promised to someone else.
On-call schedule template
A simple table keeps the rotation visible and predictable. Copy this four-week structure and adjust the names.
| Week | Primary | Secondary | Handoff |
|---|---|---|---|
| 1 | Person A | Person B | Monday 10:00 |
| 2 | Person B | Person C | Monday 10:00 |
| 3 | Person C | Person D | Monday 10:00 |
| 4 | Person D | Person A | Monday 10:00 |
Each person acts as secondary the week before they are primary. This gives them time to see what is happening and prepare for the handoff.
To extend this for a rotation of 5 or 6 people, add rows and keep the pattern of the next person as secondary. The handoff time stays fixed.
On-call rotation best practices
- Hand off during working hours. Both people are at work to discuss open incidents and known risks.
- Keep the rotation large enough that on-call is a minority of each person's time. This prevents burnout.
- Always have a backup. A secondary or escalation policy ensures alerts are acknowledged even if the primary is unavailable.
- Review noisy alerts after each shift. Fix or delete them so the next person does not inherit them.
- Make the schedule visible to everyone. Transparency helps the team plan holidays and understand coverage gaps.
- Plan holidays early. Book time off in the schedule before it is taken so the rotation remains balanced and predictable.
Building the schedule in OnCallAlerting
OnCallAlerting maps each rotation shape to a specific roster configuration. A weekly rotation is a simple rotation every 7 days with a handover time and a timezone. For a weekday and weekend split, use layers with weekly time restrictions. Later layers win where they overlap.
Holidays are handled with substitutions. The original rotation resumes by itself after the substitution ends. Follow-the-sun uses shifts per region. The awake shift is notified first. The primary is the fallback after 1-60 minutes. Backup is an escalation policy with 1-10 levels. Notifications are Slack and in-app.
Read the rosters docs, follow-the-sun docs, escalation policies docs, and start a 30-day trial.