The three terms get used interchangeably, which is how teams end up with a “runbook” that’s actually a policy statement and an “SOP” nobody can follow. They’re different documents with different jobs. Here’s the field guide.
SOP: the how, step by step
A standard operating procedure answers one question: how exactly do I perform this task? It’s numbered steps, one action per step, ideally with a screenshot for each. The test of a good SOP is brutal and simple: can someone who has never done the task complete it correctly using only the document?
Use SOPs for repeatable, hands-on-keyboard tasks — processing a refund, publishing a release, setting up a new client account. If the reader needs judgment or context to follow it, it’s not an SOP yet; it’s a draft.
Process doc: the what and why
A process document operates one level up. It describes how work flows across people and systems: who owns each stage, what triggers a handoff, where approvals happen. Swimlanes and flowcharts live here; step-by-step clicks don’t.
Use process docs when the audience is a manager, a new team member getting oriented, or an auditor — anyone who needs to understand the shape of the work rather than execute it. A good process doc links out to the SOPs that implement each stage.
Runbook: the break-glass manual
A runbook is operational documentation for a specific scenario, usually a bad one: the database failover, the payment provider outage, the 3 a.m. alert. It assumes a competent operator under time pressure, so it front-loads diagnostics (“check X first”), decision points (“if Y, escalate”), and exact commands.
The defining feature of a runbook is that you write it before you need it and pray you never do. If it gets used weekly, it’s probably just an SOP with a dramatic name.
Which one does your team need?
Start where the pain is:
- Repeated “how do I…?” questions → SOPs
- Work falling through the cracks between people → process doc
- Incidents handled from memory by whoever’s on call → runbooks
For most teams the honest answer is “SOPs, first and mostly.” They’re the document type with the highest ratio of usefulness to effort — especially now that a screen recording and a few minutes of AI processing can produce one. Nail the how, and the what-and-why documents get much easier to write.