A standard operating procedure, or SOP, is a written procedure for one repeated task, detailed enough that a person doing it for the first time gets the same result as the person who has done it for years. It names the task, says who owns it, says when it applies, lists the steps in order, and says what to do when a step fails.
Standard operating procedure. Three words worth reading one at a time.
Standard means one agreed way, not each person's own way. Operating means it is about doing the work, not about intent or values. Procedure means a sequence: this, then this, then this. A document that misses any of the three is something else. A list of principles with no order is a policy. A diagram of who hands what to whom is a process map.
Five parts. Anything past these five is optional, and most SOPs that nobody reads are long because the optional part ate the document.
A policy says what must be true. A process says how work moves between people. An SOP says how one person does one task. They sit at three different zoom levels, and the confusion between them costs real time in audits.
A worked comparison of all four terms, with an example of each, is in SOP vs policy vs procedure vs process.
The person who does the task writes the draft. Nobody else can: the detail that matters is invisible from a desk. The manager who owns the outcome reviews it. If the task carries a legal or safety obligation, the person accountable for that obligation signs it.
Two signatures are the practical minimum: the author and the owner. A document with no named owner ages badly, because nobody is responsible for the day the tools change and the procedure quietly stops matching reality.
Long enough that a new person needs no second source, short enough that they read it before doing the work rather than after. For most single tasks that lands between one and three pages.
If a draft runs past that, the usual cause is that two tasks are living in one document. Split it. Two three-page SOPs get followed; one nine-page SOP gets skimmed once and then remembered wrong.
Three failures, in the order we see them.
It is written for the auditor, not the operator. The document proves a procedure exists. It does not help anyone do the task, so it is opened once a year and never at the dock.
It is stored where the work is not. A procedure in a shared drive folder three clicks deep, while the task happens in a warehouse, in a kitchen, on a site. Distance is a failure mode.
It is text where the task is physical. Some steps are hard to write and easy to show: which lever, in which order, how far. Those are the steps people get wrong from a written document no matter how careful the wording is.
Getting a procedure written is most of the work, and most of the value is still locked up: written procedures get read once, at induction, and then remembered approximately.
Teams solve that by making the procedure watchable. A two minute video of the same five steps gets played the morning somebody actually does the task, and a new hire will watch it twice without being asked.
If you already have a filled-in procedure, turning it into a video takes a script and a style, and the script is already written: it is your SOP. If you are starting from nothing, the standard operating procedure template is a filled example, not an empty form, and downloads without an email address.