Incident handover records
Own the handover process before the incident starts
Agree on the record, roles and transfer procedure in advance. During an outage, responders should not have to invent how responsibility changes hands.
In this article
Define a small common record
Choose one place for current impact, active changes, next decisions and ownership. Keep the detailed timeline and restricted evidence linked rather than forcing everything into the summary.
Provide a lightweight template with guidance on facts, hypotheses and observation times. Avoid so many mandatory fields that responders postpone writing anything until they can complete the form.
Assign ownership for the template and tools so broken links, access problems and confusing fields can be corrected between incidents.
Establish the transfer ritual
The outgoing lead refreshes the current state, the incoming lead reads it back and both record the transfer time. Name any specialist tasks that remain with other owners.
Set expectations for stakeholder updates and escalation. These responsibilities should not disappear during a shift change because everyone assumes someone else retained them.
Use clear time-zone notation in shared records. Teams across Brisbane, Sydney and other locations may not always be working under the same offset.
Rehearse with a realistic unresolved state
Practise a scenario where service is stable but a mitigation remains active and several records need reconciliation. The receiver should identify what can resume and what must wait.
Test tool access and a fallback communication path. An incident involving the primary collaboration service should not eliminate the team's only way to coordinate.
Capture lessons from the rehearsal as changes to the process, not as criticism of the participant who exposed an ambiguous instruction.
Connect response to ordinary ownership
After an incident, transfer cleanup, data correction and preventative work into the normal tracking system with named owners. Retain links from the incident record.
Review whether handover failures contributed to repeated work, missed updates or lingering temporary access. Improve the specific mechanism rather than adding generic process overhead.
The process is established when a new on-call team can use it without relying on the original designer. Clear state and accepted responsibility should remain the same principles even as tools and team size change.
Primary sources
Google SRE: incident responseReferences checked 11 September 2026.