SOP vs Work Instruction: Key Differences and When to Use Each

An SOP describes the full process: what needs to happen, in what order, and who is responsible. A work instruction zooms in on one specific task inside that process and gives exact, detailed directions for doing it. Think of the SOP as the chapter and the work instruction as the fine print underneath it.

By Julian Vance

The One-Sentence Difference

If you only remember one line from this guide, make it this: the SOP tells you what to do and who does it; the work instruction tells you exactly how to do one piece of it.

Both are written documents. Both aim for consistency. The difference is scope and detail. An SOP covers a whole process from start to finish. A work instruction covers a single task within that process at a level of detail where nothing is left to interpretation.

Side-by-Side Comparison

	SOP (Standard Operating Procedure)	Work Instruction
Scope	A complete process, end to end	One task or operation inside a process
Detail level	Steps plus roles, purpose, and scope	Exact actions, settings, and measurements
Audience	Team members, supervisors, auditors	The person performing the task, often at the workstation
Length	Usually several pages	Often one page, sometimes a single card
Answers	What, who, when, and in what order	Exactly how, with what settings and tolerances
Example	"Customer complaint handling"	"How to calibrate the torque wrench to 25 Nm"
Changes when	The process or responsibilities change	The tool, settings, or technique change

Read the table top to bottom and the relationship becomes clear. The SOP sits above. It references or links to work instructions where a step needs deeper detail.

The Document Hierarchy

SOPs and work instructions live inside a family of documents, each with its own altitude. Picture it as a pyramid:

Level 1: Policy

The rule. Short, high-level, no steps. Example: "All customer complaints must be resolved within 48 hours." Policies say what must be true.

Level 2: Process

The flow. It maps the stages of work at a high level. Example: complaint received, then investigated, then resolved, then followed up. Processes say what happens in what order, without the fine detail.

Level 3: SOP

The procedure. It takes one process and spells out the steps, roles, and responsibilities. Example: the complaint-handling SOP names who logs the complaint, who investigates, what the response templates say, and when to escalate. SOPs say who does what, step by step.

Level 4: Work Instruction

The exact how. It covers one task from the SOP in precise detail. Example: the work instruction for logging a complaint shows each field in the ticketing system, what to type, and which category codes to use. Work instructions leave nothing to guesswork.

Level 5: Records

The proof. Forms, logs, and checklists filled in while doing the work. Example: the completed complaint log. Records show the procedure was actually followed.

You do not always need all five levels. A simple task might need only a work instruction. A regulated process might need the full stack. The hierarchy is a menu, not a mandate.

Example: Same Task, Two Documents

Concrete examples make the difference obvious. Take a commercial kitchen's dish station.

The SOP: "Dishwashing and Sanitizing Procedure." It covers the whole flow: scrape and pre-rinse, load the machine, run the cycle, air-dry, inspect, stack in the clean zone. It names who is responsible each shift, states the sanitizer concentration to verify, lists what to do when the machine breaks down, and sets the logging requirement. A health inspector reads this document.

The work instruction: "Loading the Dish Machine." It shows exactly how to rack plates (soiled side facing the spray arms), where glasses go, the maximum stack height, which cycle button to press for which load, and what the temperature gauge must read before unloading. It might include a photo of a correctly loaded rack. The new dishwasher reads this at the station.

Notice how they connect. The SOP's step "load the machine" points to the work instruction for the exact method. The SOP stays readable because the fine detail lives one level down.

When to Use an SOP

Write an SOP when:

• A process has multiple steps and multiple people. Handoffs between people are where work breaks down. The SOP defines each handoff.
• Order and responsibility matter. If doing things out of sequence or by the wrong person causes problems, you need the SOP level.
• You need to show auditors or customers how work is controlled. SOPs are the documents inspectors ask for first.
• You are training people on a whole job, not just one motion. New hires learn roles and flow from SOPs.
• The process crosses departments. When work moves from sales to operations to finance, the SOP keeps everyone aligned on the shared flow.

If you are starting from zero, begin with the SOP. It gives you the map. You can add work instructions later wherever the map needs more detail.

When to Use a Work Instruction

Write a work instruction when:

• A single task needs exact detail. Settings, measurements, sequences, safety positions. Anything where "close enough" is not good enough.
• The worker is at the point of work. Work instructions live at the workstation, on the machine, or in the app where the task happens.
• The task is done by rotating or temporary staff. Precise instructions let someone competent but unfamiliar do the job safely on day one.
• Errors come from technique, not from skipping steps. If people do every step but do step four wrong, the fix is a work instruction for step four.
• Safety depends on exact method. Lockout procedures, chemical handling, machine setup. These deserve their own detailed sheets.

A good test: if the SOP step says "calibrate the sensor" and three technicians do it three different ways, that step needs a work instruction.

Can One Document Do Both Jobs?

Often, yes. Small businesses rarely maintain a strict five-level hierarchy, and they do not need to. A single document can carry SOP-level structure (purpose, scope, roles, steps) with work-instruction-level detail embedded where it counts (exact settings, photos, measurements).

The combined approach works when the process is short and the team is small. It starts to strain when the same detailed task appears inside several different processes. Then it is cleaner to write the work instruction once and reference it from each SOP. One source of truth, many pointers to it.

Whatever structure you choose, keep the logic straight: broad flow up top, exact detail down below, and clear links between the two. Readers should always know whether they are looking at the map or the magnifying glass.

Writing Either One Well

The writing rules are the same for both documents:

• One action per step. Never combine two actions in one numbered step.
• Use verbs at the start: "Open," "Enter," "Verify," "Record."
• Put warnings before the risky step, not in a section at the end.
• Add photos or diagrams where words get clumsy. A picture of the correct setup beats three paragraphs describing it.
• Test with a real user. If a new person cannot follow it, rewrite it.

Start with a standard operating procedure template for the SOP level and a work instruction template for the detail level. For the full method behind both, see our pillar guide on how to write an SOP. And if you are still building your foundations, what is an SOP covers the complete definition.

Frequently Asked Questions

What is the main difference between an SOP and a work instruction?

Scope and detail. An SOP covers a complete process: steps, roles, and order. A work instruction covers one task inside that process with exact, step-level directions.

Is a work instruction part of an SOP?

It can be. Many organizations keep work instructions as separate documents that SOPs reference, so one detailed instruction can serve several SOPs. Others embed the detail directly in the SOP for short processes.

Which should I write first?

The SOP. Map the whole process first, then add work instructions wherever a step needs exact detail. Writing detail before you understand the full flow leads to precise instructions for the wrong process.

Do small businesses need both?

Not always. A small team can often combine both levels in one document: SOP structure up top, exact detail where it matters. Split them when the same detailed task appears in multiple processes.

What is a SWI?

SWI stands for Safe Work Instruction: a work instruction focused on performing a task without injury. It covers hazards, protective equipment, and safe methods for one specific job.