Runbook

A runbook is a documented set of step-by-step procedures for operating, maintaining, and troubleshooting a software system or infrastructure component.

The term originates from mainframe operations, where teams literally kept books of procedures to run. In modern software operations and [DevOps] and [SRE] contexts, a runbook transforms complex or infrequently performed procedures into standardized, repeatable processes that any team member can execute consistently — reducing reliance on individual expertise, minimizing errors, and accelerating response times during incidents.

A typical runbook includes a purpose statement, prerequisites (access credentials, tools, environment requirements), sequential instructions with expected outcomes at each step, verification checks, and escalation paths if something goes wrong.

Runbooks are commonly categorized by their purpose: general operational runbooks cover routine day-to-day tasks such as deployments, backups, and certificate renewals; emergency runbooks guide teams through incident response and recovery scenarios, where clear procedures are especially valuable under pressure.

A third category, automated runbooks, replaces or supplements manual steps with scripts or orchestration tooling, requiring minimal human intervention.

The term "playbook" is closely related and often used interchangeably, though some teams draw a distinction. A runbook describes the specific steps for a specific task, while a playbook provides broader strategic guidance for handling a category of situations.