Work Instructions vs SOPs: What Is the Difference?

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 perform one task inside that process, step by step, at the machine, the panel, or the sample point.

The two get confused because the boundary moves from plant to plant. EPA's own guidance on writing SOPs says a good SOP should provide detailed work instructions, and plenty of sites call every controlled document an SOP. That is workable. What causes trouble is not the name on the document. It is 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, the document hierarchy most quality systems use, a decision rule for which to write, and 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 are typical, not rules; your quality system decides the exact split.

What is an SOP?

A standard operating procedure is a set of written instructions that documents a routine or repetitive activity an organization follows. That is the definition in the US Environmental Protection Agency's Guidance for Preparing Standard Operating Procedures (EPA QA/G-6), one of the clearest public references on the subject. Its purpose is consistency: the process runs the same way when people change, and an inspector can check the work against it.

A typical SOP carries more than steps. EPA's recommended structure includes:

• Scope and applicability: which process, which sites, which equipment.
• Responsibilities and qualifications: who performs, reviews, and approves, and the minimum experience required.
• Health and safety, cautions, and interferences: what can go wrong and what to watch for.
• The procedure itself: the ordered sequence, with the checklists and forms referenced at the step where they are used.
• Quality control and references: how the output is checked and which standards or methods apply.

The same guidance says SOPs should be reviewed whenever the process changes and systematically every one to two years, and withdrawn when the process is no longer followed. 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 perform one job: 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 the reasons are the part most teams forget. A step with no reason attached is the first one skipped under time pressure.

Work instructions are specific to a machine, a part, or a variant. Where an SOP might say "set up 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 they are usually visual, posted at the station, and revised far more often than the procedure above them.

Is a work instruction a procedure?

In the loose sense, yes: both specify how work is done. In a document system they are different levels. The procedure or SOP governs a process across roles; the work instruction sits beneath it and covers a single task.

ISO 9001:2015 deliberately avoids settling the question. ISO's own frequently asked questions on the 2015 revision say specific documented procedures are no longer mentioned in the standard. 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, and 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 gets 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; once filled in, they become records, the evidence that the work was done as planned.

Two points the pyramid diagrams usually leave out. First, the hierarchy is a convention, not a requirement. ISO's guidance on documented information stresses that the standard asks for a documented quality management system, not a system of documents, and 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: its 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 worth pinning above every document control desk: analysis of the processes should drive the documentation, not the other way round.

When to write an SOP and when to write a work instruction

The practical test is where the risk sits. If things go wrong because people disagree about who does what, or in what order, you need a procedure. If things go wrong because a competent person did a step slightly differently, you need a work instruction.

Write an SOP when

• The work crosses roles, shifts, or departments, and handoffs are where it fails.
• 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.
• Operating limits and the response to a deviation have to be defined in one place.

Write a work instruction when

• One person at one station performs 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 perform it, or it is done rarely enough that nobody remembers the sequence.
• An audit finding or a defect traced back to how a step was performed.

Write neither when

If the task is simple and the people doing it are trained and competent, a document can add maintenance burden without adding control. Duplication is the other trap: when an SOP and a work instruction both describe the same steps, one of them will fall out of date first. Put each fact in one place and reference it from the other.

Work instruction vs SOP examples from manufacturing and utilities

CNC machining: changeover

SOP: Machine changeover and first-piece approval. Covers every CNC cell, assigns the setter, operator, and quality inspector their parts, sets the sequence (tear down, set up, run first piece, inspect, release), and references 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 offsets are entered, 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. The judgement a machinist brings to offsets when a job goes strange sits in none of the three.

Quality inspection: marginal parts

SOP: Control of nonconforming product. How a suspect part is tagged, segregated, reviewed, and dispositioned, and who has the authority to decide.

Work instruction: Measuring a bore diameter with a specific bore gauge, including setting the gauge to the master and the number of readings to take. The nonconformance record captures the decision and who authorized it; the quality inspector's reasoning on a part that is just outside tolerance rarely makes it onto 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) requires them to address the steps for each operating phase (initial startup, normal operations, temporary operations, emergency shutdown, emergency operations, normal shutdown, and startup after a turnaround or emergency shutdown), operating limits with the consequences of deviation and the steps to correct it, safety and health considerations, and safety systems. They must be readily accessible to the people who work in or maintain the process, reviewed as often as necessary to reflect current practice, and certified annually as current and accurate.

That is SOP-level content. The valve line-up for bringing one specific pump online, with tag numbers and the order of operation, is the work instruction beneath it. A control-room operator running 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: Calibrating the field meter before a sampling run, or setting up the composite sampler at one particular outfall. A water treatment operator arriving from another plant can follow both and still not know how this plant behaves after a dose change.

What neither document records

SOPs and work instructions describe the work as it should be done. Records show that it was done. None of them hold the judgement behind the work: why the setter slowed the feed when the sound changed, why the operator ran a different dose than the jar test suggested, which of two identical-looking valves actually matters. A procedure records what was done. It has never recorded why.

This is not a failure of writing. A good work instruction carries reasons for its key points, but only the reasons its author anticipated. Judgement is a response to conditions that were not present when the document was written. EPA's advice that SOPs be written by the people who do the work is correct, and still a reconstruction at a desk, after the fact.

Bob closes that gap from the other end. Bob is a chest-mounted device an experienced worker wears through a real job. It records first-person video, audio narration, and spatial data (location and orientation) while they talk through what they are doing and why. There is no staged demonstration and no authoring step. Recordings land in your own cloud tenancy, and 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 whoever holds the job next.

Keep your controlled documents. Capture is the layer they cannot carry. See how it works on Bob for Manufacturing and Bob for Energy. If you are 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)

Related reading

• Bob for Manufacturing: manufacturing knowledge transfer
• Bob for Energy: utility knowledge transfer
• Best Digital Work Instructions Software
• What Is a Connected Worker Platform?
• All posts on the blog