SOP vs Work Instruction in Manufacturing: When a Procedure Is Not Enough

What to take away

Where the two documents sit in the hierarchy

Most US plants run four levels of paperwork: policy, SOP, work instruction, record. The SOP carries the process view, from inputs through approvals to the records that prove a step happened. A work instruction carries task detail: settings, sequence, acceptance criteria and the point where the operator stops and checks.

Numbering follows the hierarchy. A typical US scheme gives the procedure a number such as SOP-1140 and the instruction under it a tied number, WI-1140-03. The instruction names its parent SOP on its face, so a revision to one prompts a check of the other.

A standard operating procedure is a process document by definition, and most published definitions stop there. On a plant floor the useful question is narrower: which document is in the operator's hand while the machine runs?

The FDA entry point for drug makers is 21 CFR 211.100, which requires written procedures for production and process control and requires deviations to be recorded. A procedure that says "mix until uniform" can pass a desk review and fail on the line.

Process safety sites face a heavier version of the same demand. The PSM standard lists 14 elements, and its operating procedures element asks for steps for each operating phase, operating limits, and the consequences of deviation. Refresher training is required at least every three years. OSHA also publishes a plain-language guide to the standard.

Paperwork reviews fail for the same reason management reviews do, which is why the discipline behind management foundations checks applies: a review that changes no decision is a ritual.

The criteria that matter

Both columns rest on a written record, and the test in the performance management case study applies just as well: what must the record prove six months later, to someone who was never on the line?

The SOP alone, and the SOP plus a work instruction

An SOP on its own is enough when a process has few decision points, the operators are experienced, and the variation that matters lands in a batch record anyway. Cleaning schedules, calibration rounds and supplier approval share that shape. Adding a work instruction there produces a document nobody reads.

A work instruction earns its place when a step can be done two ways and only one of them passes. It also earns it when a hazard requires a fixed order of operations, or when the same step keeps turning up in internal audit findings. The SOP keeps the process view and the instruction holds the detail.

What belongs in the work instruction:

Example: die change on a tablet press

A press SOP covers setup, running, in-process checks and cleaning. It states that tooling must be seated correctly and that the first tablets are checked against specification. That is process language, and it is accurate at the level it is written.

The die change work instruction lists the torque for the retaining screws, the turret gap setting, the order the press is brought up to speed, and the weight and hardness limits for the first ten tablets. Those results usually land in an electronic system.

FDA data integrity guidance expects a reviewable audit trail behind such records, so the instruction has to say when the trail is reviewed and by whom.

Where each one wins

One test settles it: a procedure alone where a record catches the variation, a work instruction where a skilled operator can be wrong in a way the record will not show. Torque, alignment, sequencing, sampling location and line clearance are instruction territory.

Neither wins when the real constraint is equipment condition, staffing or an unrealistic rate. Whether a change helped is a measurement question, and the opening move in team management metrics applies: name the failure first, then pick the number.

What neither document fixes

Every document in the hierarchy describes the intended process, not the performed one. If the work instruction says the line is cleared before changeover and the crew clears it afterward, no revision corrects that. Only observation on the floor, plus a record showing who checked, closes the gap.

A document that cannot be found at the machine is not a control.

Revision control is the other shared weak point. A superseded card still taped to a machine defeats both documents at once, and it is the finding most likely to open an inspection. Adoption of a revision is a change problem, and change management covers what usually decides it.

Training records sit beside both documents, not inside them. The record names the person, the document number and revision they were trained against, and the date. A signature filed against a superseded revision proves nothing.

Common questions