DailyWF / Operations
Runbook Drill
Test whether a documented procedure works before an emergency requires it.
Operating review
Runbook Drill should be run as a practical control, not as a ceremonial meeting. The review should produce decisions, assigned follow-up, and evidence that the checked condition is still healthy or being corrected.
- Open the current operating record and confirm the review period.
- Check facts against systems of record instead of relying on memory.
- Record findings, decisions, exceptions, and assigned follow-up.
- Escalate items that exceed threshold, authority, risk, or due date.
- Close the review with a next date and evidence location.
Expected output
A dated operating review record showing findings, decisions, exceptions, owners, and next review point.
Common failure mode
Creating a document that looks complete but cannot be followed under real conditions.
Use notes
| Best trigger | Use when the work repeats, affects others, creates risk, or needs a defensible handoff. |
|---|---|
| Evidence | Keep the shortest record that proves the decision, action, owner, and result. |
| Review point | Review after incidents, repeated confusion, tool changes, ownership changes, or missed expectations. |
Related pages
- Postmortem TemplateAnalyze an incident or failed outcome without losing practical lessons.
- Runbook TemplateDocument how to operate, recover, or support a system.
- Decision LogRecord important decisions so future work does not re-litigate context.
- Issue LogTrack problems that are real but not yet formal incidents or projects.
- Weekly ReviewSummarize active work, blockers, decisions, and next priorities.
Use this with a tool
Find related documents, copy a checklist, or request a missing workflow.