A runbook that's a paragraph of prose is the wrong format for 3 a.m., half-awake, pager-screaming incident response. What works is a numbered sequence with a screenshot of exactly which dashboard, which button, which log query — so a half-asleep on-call engineer can match what's on their screen to what's on the page without translating words into clicks. Guidyy captures the runbook the same way it captures any workflow: record yourself resolving the incident once, and the click-by-click reference is done.
Incident Response Documentation
Incident Runbooks Your On-Call Engineer Can Actually Follow at 3 A.M.
Build step-by-step incident runbooks with real screenshots of your dashboards — not a wall of text nobody can parse under pressure.
Quick checklist
- List your top 10 recurring incident types from the last quarter
- Record yourself resolving one, narrating each check as you go
- Add the escalation trigger and contact at the bottom
- Link the runbook from your alert/pager tool description
- Review and re-record after any incident that revealed a gap
01
What belongs in a runbook vs a postmortem
A runbook is forward-looking: what to check, in what order, to resolve a known failure mode. A postmortem is backward-looking: what happened this time and why. Keep them separate — a runbook bloated with incident history becomes unreadable during the next incident.
02
Structure that works under pressure
Symptom at the top (what the alert says), diagnosis steps in order of likelihood, the fix for each branch, and an escalation trigger if none of it resolves the issue in a set time window.
- Symptom: what the alert or report says
- Check 1, 2, 3 — in order of most-likely cause first
- Fix per branch, with exact commands or dashboard screenshots
- Escalate if unresolved after [X] minutes — name the contact
FAQ
Frequently asked questions
Should runbooks include actual production URLs and server names?+
Only for the internal version. Use AI Smart Redact to auto-blur sensitive details before sharing a runbook outside the on-call rotation.
How do I keep runbooks in sync with a changing architecture?+
Re-record the affected runbook whenever the underlying dashboard or tool changes — a 60-second update instead of rewriting a doc from memory.
Guidyy
Ship the documentation in 60 seconds.
Record once with Guidyy. Get a step-by-step guide, a clickable interactive demo, and a branded PDF — automatically.
Get Guidyy freeRelated reads