Work Instructions vs SOPs: The Difference, and How to Write Both

The short answer

An SOP describes a process from end to end: what it covers, who is responsible, what has to be recorded, what happens when something goes wrong. A work instruction describes one task at one place, in enough detail that a person can do it correctly without asking anybody.

The SOP is written for the person who owns the process. The work instruction is written for the person doing the job at the machine.

That distinction matters on the floor. Nobody reads a nine page SOP at a Haas with a part half set up. They need the setup sheet. But your quality system still needs the SOP, because it is where the process boundaries, the responsibilities, and the records live.

Where the confusion comes from

Most small shops write one document and call it either name, depending on who wrote it. That is not automatically wrong. ISO 9001 and AS9100 do not require a document called an SOP or a document called a work instruction. They require that the information needed to control the process is available at the point of use, at the correct revision, and that people are competent to do the work.

So the real question is not which word to use. It is whether the information a person needs is in front of them where the work happens, and whether the process controls are written down somewhere an auditor can find them.

The practical differences

Scope

An SOP covers a process: receiving inspection, first article, nonconforming material, calibration. A work instruction covers a task: how to run job 4471 on Mill 3, how to zero this CMM fixture, how to change the coolant on the Okuma.

Audience

SOPs get read by supervisors, quality staff, and auditors. Work instructions get read by whoever is standing at the machine, often a new hire, often on second shift, often at 11pm with nobody to ask.

Level of detail

An SOP says "the operator verifies first piece dimensions against the drawing and records results." A work instruction says which gage, which feature, which sample frequency, and where the numbers go.

Change frequency

SOPs change rarely. Work instructions change whenever a fixture moves, a tool is substituted, or an operator finds a better sequence. This is why revision control hurts more on work instructions than it does on SOPs.

Length

An SOP can run several pages and survive it. A work instruction that runs several pages will not be read. Split it.

Where they overlap

Both need an owner, a revision number, an approval, and a controlled release. Both need to be reachable by the people they govern. Both should reference each other: the SOP names the work instructions that sit under it, and each work instruction points back up to its parent SOP so an auditor can walk the chain.

Both also fail the same way. They get written once, printed, and then quietly diverge from what the shop actually does.

How to write an SOP

1. 1Define the boundary first. Where does the process start and where does it hand off?
2. 2Name the owner by role, not by person.
3. 3List the inputs, the outputs, and the records generated.
4. 4State the responsibilities: who approves, who inspects, who signs.
5. 5Cover the exceptions. What happens when the part fails, when the gage is out of cal, when the customer changes the drawing mid run.
6. 6Reference the work instructions underneath it rather than absorbing them.

Keep it in the language a supervisor would use in a meeting. If a sentence exists only to satisfy a clause number, it will not be read and it will not be followed.

How to write a work instruction

Different job entirely. One task, one place, short numbered steps, one action per step, photos of the actual setup rather than CAD renderings. Written for the phone screen the operator is holding.

We already have a full guide to this: How to write step by step training instructions that operators use. It covers step structure, photos, what to leave out, and sign-off. Rather than repeat it here, start there once you have the SOP boundary settled. If you want a document to type into rather than a blank page, you can build one and download it as Word or PDF with the numbered steps, revision block, and approval line already laid out. === /EDIT ===

Do you need both?

If the process has one task, one operator, and one output, write one document. Call it a work instruction and reference it from whatever manual holds your process descriptions.

If the process has multiple tasks, handoffs, or roles, write the SOP once and let the work instructions live under it. That way a fixture change updates one page instead of forcing you to re-approve and re-issue the whole process document.

Keeping both at the current revision

This is where the walk starts. You approve a revision, print controlled copies, and go around the shop pulling the old ones out of binders and sleeves. Then somebody photocopies a sheet for convenience and you have an uncontrolled copy in the wild that you will find during an audit rather than before it.

ScanToRun puts a tag where the work happens. Scan it, and the current revision of that work instruction opens on a phone. When you approve a change, the next scan gets the new version. There is no old copy to retrieve because there was never a copy to begin with.

SOPs can live behind the same system, linked from the work instructions they govern, so an auditor following the chain from the machine upward finds everything at the right revision.

See ScanToRun for machine shops for how this works at the machine, including the training register that records who signed for which revision. Plan options are on the pricing section.