What is an SOP? Standard Operating Procedures, explained
Plain-English definition, what an SOP actually contains, and how it differs from work instructions, playbooks, and meeting notes.
Published · by The Sendabrief Team
A Standard Operating Procedure (SOP) is a written document describing how to perform a repeatable business process, step by step, in a way that produces a consistent outcome regardless of who runs it. This article defines the term precisely, explains what an SOP must contain to be useful, and clarifies how it differs from adjacent artifacts like work instructions and playbooks.
The plain-English definition
An SOP is a written procedure that any reasonably trained team member could follow to produce the same result. It is not a meeting summary, not a project plan, and not a description of how the founder happens to do something. It is the canonical version of a process.
The test is simple: if a new hire could read the SOP and execute the process correctly on their first day, it is an SOP. If they would need to ask a coworker for context, it is not yet.
What every SOP contains
A complete SOP has five elements. First, a title naming the process. Second, a trigger — the event that causes someone to execute the procedure. Third, an ordered list of numbered steps written in plain, executable language. Fourth, role assignments — who does what. Fifth, decision points and exceptions for the cases where the standard path branches.
Optional but useful: linked artifacts (templates, forms, dashboards), success criteria, and the date the SOP was last reviewed.
SOP vs work instruction vs playbook
A work instruction is narrower. It describes how to perform a single task — often at the keystroke or click level. An SOP describes an end-to-end process composed of multiple tasks.
A playbook is broader. It is a collection of SOPs, talk tracks, decision trees, and reference material organized around a function (sales playbook, customer success playbook). Each individual procedure inside a playbook is, structurally, an SOP.
A meeting summary is a record of one conversation. It expires. An SOP is a reusable artifact that persists until the process changes.
Who needs SOPs
Any team that is growing, training, or delegating. The cost of not having SOPs scales with headcount: every new hire pays the tribal-knowledge tax, every handover loses information, every operator becomes a bottleneck.
Agencies, operations teams, customer success, and franchised businesses are the heaviest users. Engineering teams call them runbooks and treat them slightly differently, but the structural shape is identical.
Why most SOPs never get written
Writing an SOP from a blank page is uniquely painful: the writer has to translate fluent in-head knowledge into pedagogical step-by-step prose for a reader who may not exist yet. This is why SOPs sit at the bottom of every operations backlog.
The shortcut is to generate the first draft from any source where the process already lives — a recording, a chat thread, a typed brain-dump, or a 90-second voice memo describing how the work happens — then edit. That moves the task from authoring (slow, blocked) to editing (fast, unblocked).
Frequently asked
What does SOP stand for?
Standard Operating Procedure. The term originated in manufacturing and military operations and is now standard across business operations more broadly.
What's the difference between an SOP and a process map?
A process map is a visual diagram of the process flow. An SOP is the written procedure. They are complementary — large processes often have both.
How long should an SOP be?
As long as the process requires and no longer. Most useful SOPs are between 5 and 25 steps. If you're past 30 steps, the procedure is probably actually two SOPs.
How often should SOPs be updated?
Every time the underlying process changes. As a backstop, review quarterly. Stale SOPs are worse than no SOPs because they erode trust in the documentation system.