DailyWF / Templates
Runbook Template
Document how to operate, recover, or support a system.
Template intent
A runbook must help someone act correctly while attention is limited. It should lead with symptoms, safe checks, commands or actions, validation, rollback, and escalation.
Recommended fields
- Purpose and supported scenario.
- Prerequisites, access, tools, and safety checks.
- Step-by-step actions with expected results.
- Validation, rollback, and escalation path.
- Last tested date and owner.
Expected output
A reusable template that produces consistent records without forcing unnecessary approval language.
Common failure mode
Creating a document that looks complete but cannot be followed under real conditions.
Use notes
| Copy style | Keep headings stable but allow local names, tools, and examples to change. |
|---|---|
| Avoid | Do not include fields that nobody will use or review. |
| Review point | Revise after the template produces unclear or inconsistent records. |
Related pages
- Postmortem TemplateAnalyze an incident or failed outcome without losing practical lessons.
- Runbook DrillTest whether a documented procedure works before an emergency requires it.
- Acceptance Criteria TemplateDefine what must be true before work is considered complete.
- Checklist TemplateA structured list for work that must be completed consistently.
- Communication Plan TemplatePlan who needs to know what, when, and by which channel.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.