The On-Call Handoff Checklist That Saves Incidents

The 60-second handoff that prevents an incident from being inherited blindly. Six items, in order, with examples of what each catches.

The six items

The six items cover the surface where handoff failures happen most. Active incidents and their owner; recent deploys in the 4-hour window; open changes in flight; known flapping alerts that can be ignored; people who should not be paged; anything weird that hasn’t become an incident but might. Each is a known cause of next-shift surprise.

• Active incidents and owner. The on-call coming on must know what is in flight before any ticket lands.
• Recent deploys (4-hour window). Yesterday’s deploy is today’s regression; visibility prevents repeated investigation.
• Open changes in flight plus flapping alerts. Feature flags rolling, scheduled maintenance, partial rollouts; flapping alerts that can be ignored.
• People not to page plus latent weird stuff. Vacation, sick, unavailable; latent signals the previous on-call has fresh intuition for.

When to do the handoff

The handoff timing matters. 5 minutes before the shift change is long enough to cover the items and short enough to fit the calendar; synchronously in the on-call channel because async handoff loses the urgency of flapping alerts and weird stuff; outgoing on-call is on the hook until the handoff is acknowledged with no “I emailed you” shortcuts.

• 5 minutes before shift change. Long enough for the items, short enough for the calendar.
• Synchronous in on-call channel. Async loses the urgency of flapping alerts and weird stuff.
• Outgoing responsible until ack. No “I emailed you” shortcuts; explicit transition.
• Per-shift handoff record. The handoff captured in chat; supports later review.

Make it a ritual

Ritual is what makes handoff stick. The same six items, the same order, every shift, predictable, no deviation based on who is on-call; if the channel doesn’t have an outgoing handoff message, page the outgoing on-call because the ritual is mandatory. Ritual catches cases where someone is too tired to remember; cognitive offload is the point.

• Same six items, same order. Predictable; no deviation based on who is on-call.
• Mandatory ritual. If no handoff message, page the outgoing on-call; the ritual is non-optional.
• Cognitive offload. Catches cases where someone is too tired to remember; the checklist holds the memory.
• Per-rotation ritual adoption. The discipline lives at the rotation level; supports cross-team consistency.