Incident runbook template
By Kivrelune Studio

Incident runbook
Give the person on call a short path from a reported symptom to a verified recovery.
Recognise the incident
[Service] recovery
Owner: [team]
Last rehearsal: [date]
Start this procedure when [observable symptom] lasts [duration]. Check [dashboard] for [signal]. Escalate to [role] immediately if [condition].
Restore service
- Record the time and observed impact in [incident log].
- Use [approved reversible action]. Expected result: [signal].
- If the signal stays outside [range], call [on-call role] and share [diagnostic context].
- Announce recovery in [channel] after [verification checks] pass.
Close the loop
- Capture the first and last affected timestamps.
- Attach the dashboard view used to confirm recovery.
- Assign an owner and due date to the follow-up.
- Replace any instruction that was hard to execute during the incident.
Using this template
Rehearse the runbook with an operator who did not write it and verify that the starting symptom and recovery check are observable. Record the rehearsal date, escalation contact and service signal that permits the incident owner to declare recovery.
Questions & answers
Looking for more help? Visit the Help center.
How do we choose a reliable recovery check?
Pick a signal tied to the user's affected task and a verification window appropriate to the service. Confirm the operator can observe it with their normal access.
What is included in this template?
Recognise the incident · Restore service · Close the loop. Each section includes prompts you can adapt to your team.
When should the owner revisit this document?
Tie the next review to a change in service, access or ownership. Record who checked the evidence and which instruction they updated.
How do I use my own copy?
Choose “Start with this doc” to open an editable copy on this device. You can also copy the Markdown or download the file and use it in your own editor.

