Playbook vs runbook is a distinction of level, not of format. A runbook is one situation and the numbered steps to handle it, written to be followed by whoever is on duty. A playbook is the collection of runbooks for a domain with the judgement on top: which situation this is, which runbook applies, who decides, and what to do when none of them fits. A small business needs runbooks first and a playbook once it has several. The standard operating procedure template on this site sizes a runbook from its steps.
The runbook: steps for one situation
Symptoms to recognise it by, who to tell first, the numbered steps with the exact system and contact named, decision points as steps, when to escalate, what to record. Written to be read under pressure by someone who may never have done it, so it is short and literal. The template prints its reading time, which should be minutes.
The playbook: the judgement above them
A playbook opens with how to tell which situation you are in and which runbook to open, names who has the authority to decide and to escalate, and says what to do when the situation is none of the runbooks. It is read on a quiet day, by the people who will decide, not at the moment of the incident. It is shorter than the runbooks it indexes.
Which a small business needs first
Runbooks. A payment system outage, a supplier failure and a key absence each need their own steps before any playbook can index them. A playbook written before its runbooks is a list of good intentions. Once there are four or five runbooks in a domain, the playbook is the page that says which to open.
Keeping both current
Runbooks go stale with every changed contact or system; playbooks go stale when a new situation arrives that none covers. Both have an owner, a version and a review date, and a rehearsal is how the gaps are found before the real run. RunbookDesk Pro keeps runbooks and the playbooks that index them with the same version history and review reminders as every other procedure.
Questions people ask about playbook vs runbook
Is an SOP a runbook?
An SOP is for a routine task the business triggers; a runbook is for a situation it does not. Same shape, different reader and moment.
Can a playbook contain steps?
Only the steps for choosing a runbook. Steps for handling the situation belong in the runbook, or the playbook becomes one.
Is the template free?
Yes: the standard operating procedure template sizes either from its steps, without an account.