[object Object]

The point of on-call is not “page the right person.” The point is “the right team, with full context, takes the right action fast.” ServiceNow’s On-Call Scheduling module gives you the first half. The second half is design work nobody does.

The handoff is the failure mode

A P1 incident opens at 23:55. The pager fires. The on-call from Western US shift accepts. Five minutes later, shift changes to EMEA. The new on-call gets paged on the same incident with no context. Now there are two responders, both with half the picture.

Design the schedule for handoff windows

Build schedules with a 15-minute overlap between shifts, not a hard cutover. Use the Schedule’s Span properties:

Western US: 16:00-00:15 PT
EMEA: 23:45 PT - 08:15 PT
APAC: 08:00 PT - 16:15 PT

The 15-minute overlap is the warm handoff window. Active responders complete their action; new responders read the incident before their shift goes live.

Make handoff a recorded event

Every shift transition fires an event. Build a handoff log:

Table: u_oncall_handoff_log
Columns:
  group
  shift_outgoing
  shift_incoming
  active_incidents (list)
  handoff_notes (text)
  acknowledged_by (user)
  acknowledged_at

The outgoing on-call is responsible for filling handoff_notes for any active P1 or P2. The incoming on-call must acknowledge before the alert routing flips. No acknowledgment, the outgoing on-call stays primary for an extra hour.

Escalation policies are not a substitute for design

A common mistake: try to fix handoff with three escalation tiers. All you have built is “page everyone, hope someone responds.” Escalation is the safety net, not the workflow.

Test the schedule with a tabletop

Once a quarter, run a synthetic P1 at the worst possible time — exactly at shift boundary. Time to acknowledge, time to first action. Both should drop below 10 minutes. If they do not, the schedule design is wrong.

Integrate handoff into incident timeline

Every handoff during an active incident appends an entry to incident.work_notes with the outgoing and incoming responder names and the handoff notes. Postmortems then have the full provenance trail.

What to do this week

Map your current on-call schedules. Confirm overlap windows exist on every shift transition. If you have hard cutovers, build a 15-minute overlap and the handoff log this sprint. The first late-night incident will pay back the investment.

[object Object]
Share