Work Instruction vs SOP: What's the Difference?

An SOP (standard operating procedure) describes the whole process for a task: the steps, the order, and who does what. A work instruction sits one level below and spells out exactly how to carry out a single step. The SOP tells you what happens and in what sequence. The work instruction shows an operator how to do one part of it, in detail.

If you only remember one thing: an SOP is the process, a work instruction is the how-to for a step inside that process.

The quick comparison

	SOP	Work instruction
Scope	A whole process or procedure	A single task or step
Audience	Anyone involved in the process, often across roles	The operator doing the specific job
Detail	Moderate: what to do and in what order	High: exactly how to do it, settings and all
Example	"How we process a customer return"	"How to recalibrate the torque wrench on Line 3"
Changes	When the process changes	When the method or equipment for one step changes

Where each one sits

Most quality systems stack their documents in three layers. At the top is policy, which sets the rules and the intent. Below that are SOPs, which turn policy into a repeatable process. At the bottom are work instructions, which take one step of an SOP and break it down far enough that someone can do it without asking.

A single SOP usually points to several work instructions. The SOP for assembling a gearbox might reference a work instruction for the press setup, another for the torque sequence, and another for the final inspection. The SOP holds them together. The work instructions do the close-up work.

A shop-floor example

Say you run an SOP called "Assemble the Line 3 gearbox." It lists the stages in order: stage the parts, press the bearings, fit the housing, torque the bolts, inspect, sign off. It names who owns each stage and what gets recorded. That is the process.

Now look at one stage: torque the bolts. The work instruction for that stage gives the bolt pattern, the torque value, the order to tighten in, what a correct reading looks like, and what to do if it reads high. It is specific enough that a new starter can pick it up and get it right. That is the how-to.

Both matter. The SOP keeps the whole job consistent across shifts. The work instruction keeps each step correct in the hands of whoever is doing it that day.

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

Write an SOP when you need people to agree on a process: the sequence, the handoffs, the records, the responsibilities. Write a work instruction when one step is detailed enough, or risky enough, that getting it wrong causes scrap, rework, or a safety problem.

A useful test: if a step makes a new operator hesitate, it probably needs its own work instruction. If different people do the same job differently, the process needs an SOP.

What about "standard work"?

If you run Lean, you will hear "standard work" used near these terms. Standard work is the current best way to do a job at the pace customer demand sets, covering the sequence, the timing, and the work in progress. It overlaps with a work instruction, but its job is to drive out variation and feed continuous improvement, not just to document a method. Treat it as a close cousin rather than the same thing.

The problem neither document solves on its own

Here is what actually goes wrong in most factories. The SOP and the work instructions are written once, filed in a folder, and then the process moves on. Someone improves the torque step. The equipment changes. A supplier swaps a part. The documents do not keep up, so the operator on the floor is reading last year's method while the line has already changed.

The hierarchy is only useful if it stays true. When it drifts, people stop trusting the written version and start asking the experienced operator instead. That works until the experienced operator is on holiday, or leaves for good and takes the knowledge with them.

This is the gap Promptable is built to close. It reads the SOPs and work instructions you already have, so an operator can ask a plain question ("what torque on the Line 3 bolts?") and get the answer with a citation back to the exact document. When a step changes, it flags where your documents have fallen out of step with each other, so the SOP and its work instructions stay in agreement instead of quietly drifting apart.

If your procedures are scattered across SharePoint, drives, and people's heads, see what Promptable does with the documents you already have.

Frequently asked questions

Is a work instruction part of an SOP?

Usually, yes. A work instruction expands one step of an SOP into detailed how-to guidance. One SOP can reference several work instructions.

Which comes first, the SOP or the work instruction?

The SOP. You define the process first, then write work instructions for the steps that need them. Not every step needs one.

Do small manufacturers need both?

Not always. If a process is simple and everyone does it the same way, an SOP may be enough. Add work instructions for the steps that are detailed, risky, or commonly done wrong.

What is the difference between a work instruction and an SOP in ISO 9001?

ISO 9001 does not mandate the labels. It asks you to control "documented information." In practice most firms use SOPs for processes and work instructions for task-level detail, then control both the same way: current version available, old versions withdrawn.