Build a schedule#
- An organization administrator opens On Call and creates an active schedule for the owning team.
- Set an IANA timezone and select primary or secondary tier.
- Add a rotation layer with start time, optional end time, rotation interval, and ordered active participants.
- Use distinct layer priorities when multiple layers overlap. Higher-priority active layers take precedence.
- Save and inspect the current on-call result. Then connect the schedule to an escalation policy and verify a test incident.
Rotation intervals and local time#
Intervals are durations in seconds, not a promise of a fixed local-clock handoff across daylight-saving changes. Explicitly check the intended handoff times, timezone, end date, and participant order. Choose intervals that fit your team's operating model and test DST boundaries if applicable.
Temporary overrides#
- Choose the schedule and create an override for a specific active user, time window, and reason.
- Review the displayed boundaries in the intended timezone. Check that the override covers the full shift.
- Verify the effective on-call responder during the override. Remove an obsolete override through the supported action rather than changing historical event data.
Avoid coverage gaps#
- Keep the team, schedule, and participants active.
- Rotation and override participants are paged only while they are an acting member (responder, team admin or organization admin) of the schedule's team. Organization viewers are never paged. If a schedule shows nobody on call, check team membership first.
- Ensure at least one rotation is effective now and at future handoff boundaries.
- Review primary and secondary coverage independently.
- Do not rely on sampled UI previews to prove every minute of future coverage. Continuous coverage certification is not yet an exhaustive timeline feature.
- Re-test after deactivating a user or changing a schedule referenced by policies.