The difference between work instructions vs SOPs is scope. A standard operating procedure (SOP) describes a process: what happens, in what order, who is responsible, and which controls apply. A work instruction describes how to do one task inside that process, step by step, at the machine, the panel, or the sample point.
People confuse the two because the boundary moves from plant to plant. EPA's own guidance on how to write SOPs says that a good SOP should give detailed work instructions. Plenty of sites call every controlled document an SOP. That is workable. The name on the document causes little trouble. Trouble comes from a system where nobody can say which document governs the process, and which one tells a new operator where to put the torque wrench.
This guide gives working definitions and the document hierarchy that most quality systems use. It gives a decision rule for which document to write. It also gives examples from a machine shop, a process plant, and a wastewater utility.
SOP vs work instruction at a glance
If you only need the short version of SOP vs work instruction, this is it. The rows show typical practice. Your quality system decides the exact split.
| Criterion | SOP (procedure) | Work instruction |
|---|---|---|
| Question it answers | What happens, who does it, when, and under which controls | How to do this one task, correctly, every time |
| Scope | A whole process, often across roles or departments | A single task, usually one role at one station |
| Primary reader | Supervisors, process owners, auditors, and the people who do the work | The operator, technician, or inspector at the point of work |
| Level of detail | Sequence, responsibilities, limits, references | Individual steps, settings, tools, acceptance criteria, photos |
| Typical format | Controlled text document with a flow chart | Numbered steps with images or video, often posted at the station |
| Changes when | The process, the organization, or a regulation changes | A machine, part, tool, or method changes |
| Level in the ISO 9001 hierarchy | Level 2 | Level 3 |
| Manufacturing example | Machine changeover and first-piece approval | Loading and touching off tools on one CNC model |
| Utility example | Wastewater compliance sample collection | Calibration of the field meter before a sampling run |
What is an SOP?
A standard operating procedure is a set of written instructions that documents a routine or repetitive activity that an organization follows. That is the definition in the US Environmental Protection Agency's Guidance for Preparing Standard Operating Procedures (EPA QA/G-6). It is one of the clearest public references on the subject. The purpose of an SOP is consistency. The process runs the same way when people change, and an inspector can check the work against it.
A typical SOP holds more than steps. EPA's recommended structure includes:
- Scope and applicability: which process, which sites, which equipment.
- Responsibilities and qualifications: who does, reviews, and approves the work, and the minimum experience necessary.
- Health and safety, cautions, and interferences: what can go wrong and what to watch for.
- The procedure itself: the ordered sequence, with a reference to each checklist and form at the step where people use it.
- Quality control and references: how to check the output, and which standards or methods apply.
The same guidance says to review SOPs whenever the process changes, and systematically every one to two years. It says to withdraw an SOP when nobody follows the process any more. An SOP that describes last year's process is worse than none, because people trust it.
What is a work instruction?
A work instruction is a task-level document that describes exactly how to do one job. It gives the sequence of steps, the key points for quality and safety, and the reasons for those key points. That framing comes from the job instruction tradition, and most teams forget the reasons. Under time pressure, people skip the step with no reason first.
Work instructions are specific to a machine, a part, or a variant. An SOP might say "prepare the machine per the setup sheet and obtain first-piece approval." The work instruction names the fixture, the clamping order, the torque value, the gauge, and what an acceptable first piece looks like. That is why work instructions are usually visual and posted at the station. Teams also revise them far more often than the procedure above them.
Is a work instruction a procedure?
In the loose sense, yes: both specify how to do work. In a document system they are different levels. The procedure or SOP governs a process across roles. The work instruction sits below it and covers a single task.
ISO 9001:2015 deliberately does not settle the question. ISO's own frequently asked questions on the 2015 revision say that the standard no longer mentions specific documented procedures. Procedures, work instructions, and records are now all "documented information." What matters is which verb applies. Information that changes, such as procedures and work instructions, must be maintained up to date. Information that should not change, such as records, must be retained.
The ISO 9001 document hierarchy: policy to procedure to work instruction to record
Most quality systems arrange documents in four levels. Each level is narrower and more specific than the one above it:
- Level 1, policy and objectives: the quality policy, the quality objectives, and the scope of the management system. Why the system exists and what it commits to.
- Level 2, processes and procedures (SOPs): process maps and procedures that say what happens, in what order, and who is responsible.
- Level 3, work instructions: task-level detail for the steps where execution matters.
- Level 4, forms and records: blank forms and checklists are controlled documents. When people complete them, they become records: the evidence that the work happened as planned.
The pyramid diagrams usually omit two points. First, the hierarchy is a convention, and the standard does not require it. ISO's guidance on documented information stresses that the standard asks for a documented quality management system. It does not ask for a system of documents. It lists procedures, work instructions, and even quality manuals only as examples of documents that can add value. Second, the right amount of documentation depends on the organization. It depends on the organization's size and activities, the complexity of its processes, and the competence of its people. A shop full of journeyman machinists needs fewer work instructions than a line staffed by new hires, and ISO says so.
The same guidance adds a line to pin above every document control desk. Analysis of the processes should drive the documentation. The documentation should not drive the processes.
When to write an SOP and when to write a work instruction
The practical test is where the risk sits. Suppose things go wrong because people disagree about who does what, or in what order. Then you need a procedure. Suppose things go wrong because a competent person did a step slightly differently. Then you need a work instruction.
Write an SOP when
- The work crosses roles, shifts, or departments, and it fails at the handoffs.
- The process needs an owner, approvals, or defined responsibilities.
- A regulation or customer requires a written procedure, such as operating procedures under OSHA's process safety management standard.
- You must define operating limits, and the response to a deviation, in one place.
Write a work instruction when
- One person at one station does the task, and the detail of execution decides quality or safety.
- The task varies by machine, part number, or product variant.
- New or rotating staff do it, or people do it so rarely that nobody remembers the sequence.
- An audit finding or a defect traced to how someone did a step.
Write neither when
Sometimes the task is simple, and the people who do it are trained and competent. Then a document can add maintenance burden and no control. Duplication is the other trap. When an SOP and a work instruction both describe the same steps, one of them will become out of date first. Put each fact in one place, and refer to it from the other.
Work instruction vs SOP examples from manufacturing and utilities
CNC machining: changeover
SOP: Machine changeover and first-piece approval. It covers every CNC cell. It gives the setter, operator, and quality inspector their parts. It sets the sequence (teardown, setup, first-piece run, inspection, release) and refers to the setup sheet and inspection form.
Work instruction: Loading and touching off tools on one specific machining center. Photos of the tool holders, the touch-off routine, where to enter offsets, and what to check before cycle start.
Form and record: the blank setup sheet is a controlled form. The completed first-piece inspection report is the record. A machinist brings judgement to offsets when a job goes strange, and that judgement is in none of the three.
Quality inspection: marginal parts
SOP: Control of nonconforming product. How to tag, segregate, review, and disposition a suspect part, and who has the authority to decide.
Work instruction: Measurement of a bore diameter with a specific bore gauge, including how to set the gauge to the master and how many readings to take. The nonconformance record captures the decision and who authorized it. The quality inspector's reasoning on a part just outside tolerance rarely reaches the form.
Process plants: operating procedures under OSHA PSM
In facilities covered by OSHA's process safety management standard, written operating procedures are a legal requirement. 29 CFR 1910.119(f) says what they must address. They must give the steps for each operating phase. The phases are initial startup, normal operations, temporary operations, emergency shutdown, emergency operations, normal shutdown, and startup after a turnaround or emergency shutdown. They must give operating limits, with the consequences of deviation and the steps to correct it. They must also cover safety and health considerations, and safety systems. The procedures must be readily accessible to the people who work in or maintain the process. Teams must review them as often as necessary to reflect current practice, and certify them annually as current and accurate.
That is SOP-level content. The valve line-up to bring one specific pump online, with tag numbers and the order of operation, is the work instruction below it. A control-room operator who runs a startup uses both.
Wastewater utilities: compliance sampling
SOP: Wastewater sample collection. EPA's QA/G-6 guidance uses this as a worked example: scope, definitions, health and safety warnings, personnel qualifications, equipment, the collection procedure, and quality control.
Work instruction: Calibration of the field meter before a sampling run, or preparation of the composite sampler at one particular outfall. A water treatment operator who comes from another plant can follow both. But that operator can still lack the knowledge of how this plant behaves after a dose change.
What neither document records
SOPs and work instructions describe the work as people should do it. Records show that they did it. None of them hold the judgement behind the work. Why did the setter slow the feed when the sound changed? Why did the operator run a different dose than the jar test suggested? Which of two identical-looking valves actually matters? A procedure records what people did. It never recorded why.
Better writing does not fix this. A good work instruction gives reasons for its key points, but only the reasons that its author anticipated. Judgement is a response to conditions that were absent when someone wrote the document. EPA advises that the people who do the work should write the SOPs. That advice is correct, but it is still a reconstruction at a desk, after the fact.
Bob closes that gap from the other end. Bob is a wearable (head or chest mount) that an experienced worker wears through a real job. It records first-person video, audio narration, and spatial data (location and orientation) while the worker says what they do and why. There is no staged demonstration and no authoring step. With Record (AutoSOP), the worker does the job once and gets the SOP, for example as a PDF. Bob encrypts each recording on the device. The decryption computer moves the recordings into your own cloud tenancy, and nothing goes to Mission Control. A version with a volumetric spatial sensor in place of a camera is available. The expert opts in: it is their knowledge, recorded on their terms, for the next person in the job.
Keep your controlled documents. Capture is the layer that they cannot hold. See how it works on Bob for Manufacturing and Bob for Energy. Are you choosing software to author and deliver work instructions? Start with the best digital work instructions software, how Bob handles digital work instructions, and what a connected worker platform is.
References
- US EPA, Guidance for Preparing Standard Operating Procedures (SOPs), EPA QA/G-6, EPA/600/B-07/001, April 2007
- ISO/TC 176/SC 2, Guidance on the requirements for Documented Information of ISO 9001:2015
- ISO/TC 176/SC 2, ISO 9001:2015 Frequently Asked Questions
- 29 CFR 1910.119, Process safety management of highly hazardous chemicals, paragraph (f) Operating procedures (GovInfo, 7-1-24 edition)