Standard Operating Procedure
A documented repeatable procedure for performing a task consistently.
The written way a task always gets done.
What It Is
Standard Operating Procedure belongs to Execution, specifically the Systems part of it. In practice it means this: a documented repeatable procedure for performing a task consistently.
It is a repeatable structure, which means it only pays off when it is actually followed through instead of quoted. Used with that meaning, it stays a working tool rather than a talking point.
How It's Used
You will usually meet Standard Operating Procedure in project delivery, scheduling and the handover between people doing the work. In real work it sits close to Documentation, Workflow and Checklist. The practical test is whether anyone can follow it without the person who wrote it in the room.
Why It Matters
Standard Operating Procedure is cheap to get right early and awkward to fix late. When it is unclear, work still happens — it just happens twice. Deciding it deliberately costs one conversation. Leaving it undecided costs several.
Think of a checklist that stops you skipping the important part. The written way a task always gets done.
Termshift™
How the meaning shifts depending on who is using it, and where.
Inside the industry, Standard Operating Procedure is used tightly and assumed to be understood: a documented repeatable procedure for performing a task consistently.
Away from the jargon, it is the written way a task always gets done.
The Bottom Line
The practical takeaway on Standard Operating Procedure: the written way a task always gets done. Judge it by that, not by how it sounds.