The Incident Debrief Template
Your RCA logs what the system did. This logs what it cost the operator.Sleep lost, decision-quality the next day, the same service dragging you out of bed for the third time this quarter — that's operational data, and most teams never write it down. So the human cost of on-call stays invisible until someone quits. This pack is the instrument: paste-in templates to capture it, spot the pattern across incidents, and turn "on-call is rough" into a documented, arguable number.Four templates, each delivered in two ready-to-use formats — plain text (paste into any doc, ticket, or terminal) and a formatted, fillable Word .docx: Night-of five-line debrief — two minutes before you try to sleep. Captures the raw state before you rationalize it in the morning. Structured personal debrief — run it 24–48h later; surfaces patterns across incidents when you keep a running document. Blameless team debrief (human-cost edition) — runs alongside your technical RCA to put operator load on the record. Not to process feelings — to log a cost. Running incident log — the spreadsheet that turns "your salary already covers on-call" from an argument-from-memory into a documented pattern with a business cost attached. Plus a readable PDF overview of the whole pack.Who it's for: on-call SREs, platform, and DevOps engineers. Fill-in-the-blank; paste into a doc, ticket, or spreadsheet. An operational instrument, not a wellness quiz.How it's made: drafted with AI assistance, reviewed and edited by a human. Full provenance at steadystate.engineer.Instant download (readable PDF + 8 template files). 30-day, no-questions refund.CompanionThe free On-Call Hygiene Checklist is the two-minute self-audit; its Section 03 (DEBRIEF) is exactly this — the ready-to-paste instrument behind it. Pairs with The On-Call Survival Field Guide ($19), where these templates are Section 5 expanded into the full pack.
Get it → steadystateengineer.gumroad.com