The Five-Minute On-Call Handoff Pattern

Most on-call handoffs are ‘everything was quiet, you’re up.’ Five minutes of structure prevents the next incident from rediscovering yesterday’s context.

Why handoffs lose context

Outgoing on-call has live context. Incoming has none. Without transfer, every recurring incident gets re-investigated.

Five minutes of structured transfer prevents days of repeated work.

Five-minute template

• 1. Active incidents (1 min).
• 2. Recent alerts that fired (last 24h) (1 min).
• 3. Open mitigations / temporary changes (1 min).
• 4. Heads-up on planned changes (1 min).
• 5. Questions (1 min).

Sync vs async

Sync handoff (5 min call) for high-context periods. Async handoff (written doc) for quiet periods.

Default: written doc + optional 5-min call if any item is unusual.

The handoff doc

Doc lives in one durable place; not Slack DM.

Linked from on-call rotation system; survives team turnover.

Antipatterns

• No handoff at all. Context lost.
• Handoff in chat. Lost in scrollback.
• 30-minute handoff. Wastes time; signal degrades.

What to do this week

Three moves. (1) Apply this practice to your next on-call rotation. (2) Survey the team after one cycle. (3) Iterate based on feedback; the discipline is the cadence.