Overview

Nine common on-call patterns, each with the requirement, a week view and the exact layers to enter. Pick the one closest to your team and adjust it.

Examples
9
Each has
Week view and layer table
Start with
Create a schedule

Pick an example

Example Best for
1. Regional coverage by time zones Three regions cover weekdays, one person covers the weekend
2. Follow the sun Global teams, 12-hour weekend shifts
3. Weekday shifts and rotating weekend duty Three 8-hour weekday shifts, one weekend person
4. Split regional shifts Unequal regional shifts, 8-hour weekend shifts
5. Primary and backup Two schedules and a two-level escalation policy
6. Customer time zones One schedule per customer region
7. Two-shift pager rotation Small team, day and night shifts
8. Small team, 24/7 One person on call at a time
9. Overlap for critical hours Two people on call during a handover window

Before you start

Good to know for every example:

  • Lower layers win. Where two layers cover the same time, the lower layer decides who is on call, and an override beats every layer. One schedule always has exactly one on-call person at a time.
  • Same person all weekend. When a weekend is split over several layers (Saturday, Sunday, Monday morning), give them the same start date, the same users in the same order and the same Weekly rotation, so one person covers the whole weekend.
  • Pick a city time zone (for example Europe/London rather than a fixed offset) so shifts follow daylight saving time.
  • Shifts that cross midnight are split in two layers: the evening part ends at 23:59 and the night part starts at 00:00 on the next day's list of days (Tuesday to Saturday for a Monday to Friday night shift).