Overview
A primary and a backup on call at the same time, in two schedules, with an escalation policy that pages the backup if the primary does not acknowledge. This page shows the requirement, a week view of who is on call, and the exact layers to enter in SQIBS.
The requirement
All times GMT. Build this twice: a Primary schedule and a Backup schedule.
Schedule layers
| Layer | Shift Type: Week | Time based on-call | Users | Rotation Type |
|---|---|---|---|---|
| 1 | Monday to Friday | 08:00 to 23:59 | Weekday members | Daily (primary) / Weekly (backup) |
| 2 | Tuesday to Saturday | 00:00 to 08:00 | Weekday members | Daily (primary) / Weekly (backup) |
| 3 | Saturday | 08:00 to 23:59 | Weekend team | Weekly |
| 4 | Sunday | 00:00 to 23:59 | Weekend team | Weekly |
| 5 | Monday | 00:00 to 08:00 | Weekend team | Weekly |
Make sure primary and backup differ
List the users in a different order in the backup schedule (or start its layers one rotation later), so the same person is never primary and backup at once. Check both final previews side by side.
The escalation policy
- In Escalation, click New Escalation Policy.
- Level 1: the Primary schedule. Set how many minutes it waits before escalating.
- Level 2: the Backup schedule.
- Optionally tick If no one acknowledges, repeat this policy, and save. See create an escalation policy.
How to build it
In Schedules, click Create new schedule, choose the team, name and Timezone, then add one layer per row below with Add New Layer. For each layer set the start date and time, choose Shift Type > Week and the days, add the users, choose the Rotation Type, and turn on Time based on-call with the times shown. Check the Final preview chart, then click Save new schedule.
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).