/Aristotl
Language
Demo

What is an SOP?

Updated

Short answer

A standard operating procedure (SOP) 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 whoever is on shift, and so that an auditor, inspector or client has something concrete to test against.

What the document is 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 they are not 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 a multi-site operation there is a fourth job nobody names: the SOP is how head office knows what a site is supposed to be doing.

One SOP card for cleaning a filler, with a version tag v4 in front of an older v3 card, three numbered steps, and an empty checkbox asking whether it is followed on the floor; notes point to the version, the task and order, the checks and the one field the document cannot fill.
Everything on the card is written down; whether it is followed is not.

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.

A Dutch production site revises the cleaning procedure for a filler after a contamination finding. The new SOP is published in the quality system on a Wednesday. The weekend crew, three of them agency workers, clean the machine the way they were shown in March. Nothing in the quality system is wrong. The revision never became an instruction.

Codex art. I.2-21 names the moments at which training must be given: on entering service, on a change of function, and on the introduction of new work equipment or new technology, repeated and adapted as risks evolve. Arbowet art. 8 requires instruction adapted to each task and supervision of compliance. Read together, an updated SOP nobody was instructed on is a live exposure: the revision proves something changed, and the missing instruction records prove 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". The multi-location SOP rollout playbook works through that per version rather than per topic.

Sources

  1. Codex over het welzijn op het werk, art. I.2-21 (FOD Werkgelegenheid)
  2. Arbeidsomstandighedenwet, artikel 8

Read next