The Incident Commander Handover Pattern

Long incidents need fresh leadership. The handover protocol that prevents context loss.

When to handover

IC handover is rule-driven, not vibes-driven. Time on shift, fatigue, or scope shift each trigger the handover protocol. The named successor list per rotation prevents the "no one to hand to" trapped-shift failure mode.

• Every 4 hours during active incident. Time-bound rotation by default. Long shifts degrade decision quality more than ICs realise mid-shift.
• Fatigue trigger. IC too tired for sound decisions hands off; teammates flag the IC if the IC does not. Self-awareness varies.
• Scope shift to different expertise. Database incident becomes networking incident; right IC follows the scope. Match expertise to current shape.
• Named successor list. Per-rotation IC bench listed in writing. Catches the "no one to hand to" trap before it traps the on-call.

How

The handover is structured. Five-minute briefing covers timeline, current hypothesis, in-flight actions, key people. New IC plays the picture back to confirm; outgoing stays available 30 minutes for clarification questions.

• 5-minute briefing. Timeline, current hypothesis, in-flight actions, key people. Bounded so the handover does not itself become an incident-extending event.
• Verify understanding. New IC plays back the picture; outgoing IC confirms or corrects. Catches transfer errors before they propagate.
• 30-minute availability. Outgoing IC stays on standby for clarification questions. Hands off authority without disappearing.
• Channel announcement. Explicit "X is now IC" post in the incident channel. Catches dual-IC confusion before anyone acts on stale authority.

Avoid

Two failure modes turn the handover into a problem. Silent handovers leave the team unsure who is in charge; multiple simultaneous ICs cost minutes to coordinate. Both are caught by the explicit announcement and single-IC rule.

• Silent handover. The team needs to know who is in charge. No-quiet rule is non-negotiable.
• Multiple simultaneous ICs. Strict single-IC rule. Confusion costs minutes that compound during a live incident.
• Documented audit log. Handover history captured per incident. Supports postmortem timeline reconstruction.
• No-mid-decision rule. Handovers wait for stable state. Catches handovers in the middle of risky decisions where the new IC inherits exposure they did not choose.