A standard operating procedure is a written instruction that fixes how a specific task is performed, by whom, in what order, and with which checks. It exists so that the same task produces the same result regardless of who is on shift.
What the document is really for
An SOP has three jobs. It makes a task repeatable across people and locations. It captures the decisions someone made about safety, quality and sequence, so that they do not have to be re-made under time pressure. And it gives an inspector, an auditor or a client something concrete to test against, which is why SOPs sit under HACCP plans, quality systems and client site rules alike.
In multi-site operations there is a fourth job that goes unnamed: the SOP is the only mechanism by which head office knows what a site is supposed to be doing.
The gap between written and followed
Almost no organisation has an SOP problem in the sense of not having them. What they have is a distribution problem. The procedure lives in a document management system, a binder, or a shared drive that half the workforce cannot reach from the floor.
Consider a Dutch production site that revises the cleaning procedure for a filler after a contamination finding. The new SOP is approved on a Wednesday and published in the quality system. The weekend crew, three of whom are agency workers, clean the machine the way they were shown in March. Nothing in the system is wrong. The revision never became an instruction.
New equipment is a legal trigger, not an internal milestone
This is where an out-of-date instruction stops being a housekeeping issue. Codex art. I.2-21 names the moments at which training must be given: on entering service, on a change of function, and explicitly on the introduction of new work equipment and new technology. Instruction is repeated and adapted as risks evolve. In the Netherlands, Arbowet art. 8 requires instruction adapted to distinct tasks, and lid 4 requires the employer to supervise compliance with the instructions given.
Read together, an updated SOP that nobody was instructed on is a live exposure. The revision is the evidence that something changed, and the absence of instruction records is the evidence that nothing followed it.
Why version is the field that matters
The useful question is never "do we have a procedure". It is "which version does each site have, and who has confirmed the current one". Our multi-location SOP rollout playbook covers how to run that per version rather than per topic.
Bring the SOP you revised most recently to a demo and we will turn it into a module with a knowledge check.