Operations
Standard operating procedure (SOP)
A standard operating procedure (SOP) is a written, step-by-step description of how a recurring task is done, who does it and what good looks like, so it is done the same way each time.
How it works in practice
SOPs keep work consistent when people change and make training faster. A useful SOP names the trigger, the steps, the systems used, the person responsible and the checks at the end. Most companies have a few, often out of date, and much of the real procedure lives in people’s heads.
SOPs and automation go together. Writing the SOP is often the first step of an automation build, because a process nobody has written down is hard to automate. After the build, the SOP is updated to say which steps the system does and which a person still owns, and it becomes part of the handover.
A worked example
A recruitment agency wrote an SOP for onboarding a new placement: 14 steps across five systems. Nine of them are now automated from the signed offer, and the SOP lists the five a consultant still does, with links to each screen.
Examples in this glossary describe typical builds for companies of 1 to 1,000 people. They are not named client results.















