Skip to content

How do you write SOPs that people actually follow?

The short answer

Write SOPs with the people who do the job, keep them short, and describe the task the way it really happens on the floor. Then triage your document set by risk, fixing the critical few first instead of rewriting everything.

Ask any operator why they don't follow an SOP exactly and you'll usually hear the same answers. It's too long. It doesn't match how the job is done. It was written for the auditor, not for them. Each of those is a design problem, and each can be fixed.

Why SOPs get ignored

Most procedures drift away from reality for predictable reasons. They are written by Quality at a desk. They try to serve as training material, regulatory justification and work instruction all at once. They grow with every CAPA that adds another step. And they are reviewed on a schedule, not when the process changes.

The result is a document that passes audit and fails on the shift. That gap is a risk in its own right, because an inspector who watches the task and reads the SOP will spot the difference.

“An SOP nobody follows isn't a control. It's a finding waiting to happen.”

Craig Jacobs, Founder and Chief Momentum Officer, Affirm8

Six rules for SOPs that get followed

  1. Write it with the people who do it. Ask an experienced operator to walk you through the task. Write the steps in the order they happen, in their words.
  2. One action per step. Start each step with a verb: open, check, record, sign. If a step contains "and", it is probably two steps.
  3. Show, don't tell. Use photos, simple flowcharts and labelled diagrams wherever they make a step clearer.
  4. Separate the why from the how. Move background, rationale and regulatory references into a short introduction or into training material. Keep the working steps clean.
  5. Make critical steps stand out. Flag the steps that affect product quality or safety so people know where they cannot deviate.
  6. Test it before you issue it. Ask someone unfamiliar with the task to follow the draft. Wherever they hesitate, the SOP needs work.

What to do with hundreds of documents

Rewriting every document is rarely realistic. Triage instead:

  • Rank by risk and use. Put the documents that affect product quality and are used daily at the top.
  • Fix the critical few first. Rewrite the top ten to twenty using the rules above.
  • Merge duplicates. Many sites have several procedures describing the same activity in slightly different ways.
  • Retire what nobody uses. Every obsolete document still needs reviewing, training and controlling.

A smaller, simpler document set is easier to train, easier to audit and much harder to deviate from. It also shrinks your review backlog and your training matrix at the same time.

Keep them alive

An SOP starts to drift the day it is issued. Build in a simple feedback route so operators can flag steps that no longer match the job. Review a procedure when the process changes, not only when the review date arrives. And when a deviation points to a procedure, fix the procedure rather than adding a warning note.

Where to start this week

  1. Pick the three procedures linked to the most deviations over the last year.
  2. Watch each task being done on the shift and note every point where practice and procedure differ.
  3. Rewrite one of them with the operator who knows it best, test it with someone new, and measure the deviations over the next quarter.

That single before-and-after comparison is often enough to win support for tackling the rest of the document set. It also gives you a template and a style guide your team can reuse for every procedure that follows.

Frequently asked questions

How long should an SOP be?

As short as the task allows. Many good work instructions fit on one or two pages. If an SOP runs past ten pages, check whether it is really several procedures combined.

Should SOPs include the reason for each step?

Keep the reasons out of the working steps. Put a short purpose statement at the start, and cover the detailed reasoning in training.

How Affirm8 can help

Affirm8 helps quality teams in pharmaceuticals, supplements, medical devices and cosmetics triage their documents, co-write priority SOPs with frontline staff and build lean processes that perform. Find out where your processes stand with the free Always Audit-Ready Diagnostic at affirm8.co.uk.

Related reading

Life Sciences teams we have worked with