Writing a useful runbook
Document triggers, prerequisites, checks, actions and recovery steps so that a runbook can be used in practice.
Practice & Orientation
Describe the purpose, prerequisites, required role, and expected initial state. Name situations in which the flow should not be executed.
Record steps in a clear order. After each significant action, describe how the person performing the action recognizes the expected outcome.
Name a drop-off point and the responsible contact. Explicitly include fallback path, final functional test and necessary documentation.
Focus of this page: Runbooks at SYNEDAT.