SOP vs work instruction: what's the difference?

Updated 2026-07-11 · reading time ~4 min

Definition An SOP describes how a whole process is carried out across the roles involved. A work instruction is a narrower document that details how to perform one specific task or step within that process. The SOP is the map; the work instruction is the close-up.

People use the terms interchangeably, but in a documented quality system they sit at different levels of detail. Getting the distinction right keeps your documents the right length and stops them from duplicating each other.

Side by side

	SOP	Work instruction
Scope	An end-to-end process, often across several roles	A single task or step, usually one role
Detail	Numbered steps, with owner and time per step	Fine-grained detail: exact settings, clicks, torque values
Audience	Everyone who touches the process	The person doing that one task
Example	"New customer onboarding"	"How to configure the welcome email template"

The documentation hierarchy

Most quality systems stack their documents like this, broad to narrow:

Policy — what must be true and why.
Process — the high-level flow of how work moves.
SOP — how a specific process is executed, step by step.
Work instruction — how to perform one detailed task inside an SOP.

A single SOP can reference several work instructions. You do not always need work instructions — add one only when a step is complex or error-prone enough that a new person could get it wrong.

Which should you write first?

Start with the SOP. Once the end-to-end procedure is clear, you will see which one or two steps are detailed enough to deserve their own work instruction. Writing work instructions first tends to produce fragments with no map to connect them.

Write your SOP first — from a plain-text description →Preview free · one-time from $19 · no subscription