How to write an SOP, from first walk to approved document

A working method for producing a Standard Operating Procedure that people actually follow. Not the section list, the process of getting from an undocumented task to a controlled document.

Set the boundary before you write a word

The most common reason an SOP becomes unusable is that it covers too much. Someone sets out to document "receiving" and ends up with fourteen pages spanning unloading, inspection, put-away and the ERP transaction, none of which the person doing any one of those jobs will read.

Fix the boundary first, in one sentence, and be specific about both ends: where the process starts, and what condition the output is in when it ends. "Starts when the pallet is on the dock, ends when the material is in a bin with a printed label" is a boundary. "Receiving" is a topic.

Then find the process owner, meaning the person accountable for the outcome, not the person who happens to perform the task. You will need them twice: once for facts you cannot determine yourself, and once for approval. Identifying them at the start prevents a finished draft sitting unapproved for a month.

Watch the process actually happen

This is the step almost everyone skips, and skipping it is why so many procedures describe a process nobody recognizes.

Go and watch the task performed, start to finish, without interrupting. Take notes on what happens, not on what should happen. Pay particular attention to three things:

• The steps nobody mentions. Experienced operators stop noticing the things they do automatically. Wiping a surface, checking a light, waiting for a beep. These are the steps a new hire fails on.
• Where they pause or check something. Every hesitation is a decision point, and decision points need to be written as explicit branches rather than left to judgment.
• What they do when something is wrong. Watch long enough to see one exception if you can. The failure path is the part of the procedure that matters most and is documented least.

If the process is too slow to observe end to end, watch the parts with the most handoffs. Handoffs are where consistency breaks.

Interview the person who does it

After watching, ask. Two questions produce more useful material than any structured interview:

1. "What do new people get wrong?" The answer is a ready-made list of the steps that need the most detail, verification, or a warning. Someone who has trained three people can tell you exactly where each one stumbled.
2. "When does this go wrong, and what do you do?" This gets you the exception handling, which is the material you cannot invent and which turns a description into a procedure.

One rule while you draft: never invent a value. Torque specs, tolerances, temperatures, dwell times and cure times either come from a released document or from the process owner in writing. If you do not have the number, leave a visible placeholder rather than a plausible guess. A wrong tolerance in a controlled document is worse than a missing one, because the missing one gets questioned and the wrong one gets followed.

Draft in this order, not top to bottom

Writing an SOP from the first section to the last is slow, because purpose and scope are much easier to write once you know what the procedure actually contains. Work in this order instead:

1. Procedure first. The numbered steps, from your observation notes. This is the bulk of the work and everything else is shaped by it.
2. Records. As you write steps, note every point where something is written down or signed. Those are your records.
3. Materials and equipment. Read back through your steps and list everything they reference. This catches the gauge you forgot.
4. Responsibilities. Now that the steps exist, assigning roles is a matter of reading who does what.
5. Safety and PPE. Written after the steps, so hazards are attached to real actions.
6. Purpose and scope last. Both are now easy, because you know exactly what is in the document and what is not.
7. Document control block. Number, revision, effective date, approvals.

Write steps that survive the floor

A procedure lives or dies on its numbered steps. Four habits do most of the work:

Start every step with a verb. "Measure the bore at three positions" is an instruction. "The bore should be measured" is a description, and descriptions are read as optional.

One action per step. If a step contains "and", check whether it is two steps. Combined steps are the ones that get half done, and they cannot be cited cleanly when something goes wrong.

Put the acceptance criteria in the step. Not in an appendix, not in a specification stored somewhere else. If the tolerance is plus or minus 0.05 mm, it belongs on the same line as the measurement, because that is where the person is looking.

Write the failure path immediately after the check. Every verification step needs a companion step stating what happens when it fails and who is told. A procedure that only covers the good outcome is abandoned the first time the outcome is bad.

Pilot it before you approve it

Hand the draft to someone who does not perform the task and ask them to follow it while the regular operator watches. Every place they stop, ask a question, or do the wrong thing is a defect in the document, not in the person.

This takes about an hour and it is the highest-value hour in the whole exercise. It is also the step that reveals the assumed knowledge you could not see yourself, because you learned the process by watching an expert.

Then route it for approval. At minimum the process owner, who is accountable for the content, and one approver independent of the author, usually quality. Record both names and dates in the document control block. Approval evidence is the first thing an auditor checks, and an unapproved procedure is not a controlled document at all.

Train, control, and set the review trigger

Issuing a procedure is not the same as implementing one. Three things finish the job:

Train against it and record that you did. The training record is what connects the document to the people expected to follow it. Without it, an auditor has a procedure and no evidence anyone knows it exists.

Control the copies. Put the document number and revision in the footer of every page, and mark printed copies as uncontrolled. The copy taped to a machine is the one that will still be at revision 1 in two years.

Set a review trigger, not just an interval. An annual review is a floor. The triggers that matter are a process change, a nonconformance the procedure failed to prevent, and any corrective action that changes the method. A document only ever revised on its anniversary is usually a document nobody is using.

Common questions