incident handoff runbook kit · handoff lane
cross-team incident turnover

Incident turnovers stay tied to explicit next owners.

The handoff lane keeps bridge state, blockers, evidence readiness, and next action on one route so accountability does not drift between teams.

IH-204 · platform-reliability → revenue-systems

checkout-degradation

SLA 2.0h elapsed 3.1h, blockers 2, evidence complete: no.

Complete the handoff packet, assign revenue-systems, and keep the bridge active until acknowledgment.

IH-211 · security-operations → support-operations

identity-incident

SLA 4.0h elapsed 2.5h, blockers 1, evidence complete: yes.

Transfer to support-operations with a named owner and close remaining evidence gaps in the next cycle.

IH-223 · webops → content-systems

schema-drift

SLA 6.0h elapsed 5.4h, blockers 1, evidence complete: no.

Transfer to content-systems with a named owner and close remaining evidence gaps in the next cycle.

IH-230 · data-platform → revops

crm-backfill

SLA 8.0h elapsed 4.2h, blockers 0, evidence complete: yes.

Maintain the handoff into revops and archive the packet as clean proof.