Incident handover records
Hand the incident to someone who did not watch it happen
A rehearsal reveals missing context quickly. Give the incoming responder only the record and ask them to explain the next safe action.
In this article
Prepare a synthetic incident with unfinished work
Use a scenario where the primary API has recovered but a queue remains paused and several business commands have uncertain outcomes. Include one disproved hypothesis and one temporary configuration change.
Write the handover as the team would during an incident, with links to safe test evidence. Do not add a verbal explanation before the receiving person reads it.
Ask them to identify current customer impact, the active mitigation and the person authorised to make the next change.
Test the dangerous misunderstanding
Present a proposed action such as resuming all consumers. The record should explain why uncertain commands need reconciliation first and which workers can resume safely.
If the incoming responder cannot distinguish those groups, the handover lacks operational scope. Add the missing state or link, not a longer general history.
Then ask them to reverse the temporary configuration in the test environment. They should find the exact change and its reversal condition without guessing the previous value.
Challenge evidence and time
Include an old healthy dashboard screenshot and a newer unresolved-impact note. The receiver should recognise their observation times and seek current evidence rather than treating the screenshot as final proof.
Use timestamps from different zones with explicit offsets. Confirm that the sequence remains understandable to a team in another location.
Ask which statements are facts and which are hypotheses. An unlabelled causal claim should be corrected before it becomes the basis for the next experiment.
Verify responsibility transfer
Have the incoming lead restate the state and accept ownership in the record. Confirm who sends the next stakeholder update and when.
Remove access to one optional supporting tool in the rehearsal. The critical summary should remain usable, and the team should know the fallback path for essential evidence.
Finish by identifying the incident-closure conditions and any remaining reconciliation owner. A passing handover lets the receiver continue without repeating failed work or mistaking service stability for complete business recovery.
Primary sources
Google SRE: incident responseReferences checked 11 September 2026.