A runbook helps someone complete a known task safely, often under time pressure. It should be written for a teammate who does not already know the hidden assumptions behind the process.
Write the procedure in executable order
- State when to use the runbook and what permissions or prerequisites are required.
- List the steps with expected output and a way to verify each important change.
- Explain how to stop, roll back, or escalate if the result differs from expectations.
Keep the instructions maintainable
Link to the authoritative dashboard or system rather than copying fast-changing values into prose. Never put passwords, tokens, or private customer information in the runbook.
Ask someone unfamiliar with the task to follow the instructions in a safe environment. Update the runbook when the process changes and identify an owner for future corrections.