They are not the same thing. A work instruction, an SOP, and a process map are three different documents with three different purposes, three different audiences, and three different levels of detail — and the most common documentation mistake in engineering and manufacturing businesses is using them interchangeably, or creating all three for every process when one would do.
The confusion is understandable. All three describe how work gets done. All three are referenced in quality management discussions. And the terminology is genuinely inconsistent — some organisations call their task-level documents SOPs when they are technically work instructions; others call their process-level maps SOPs when they are technically procedures. The words have been used loosely enough for long enough that the distinction has been blurred for many practitioners.
This article gives you a clear definition of each document type, a concrete engineering example of each, and a simple three-question decision framework for choosing the right one for any given process. After reading it, you will never have to guess which document to create.
At a glance — the three document types compared
| Dimension | Work Instruction | SOP | Process Map |
|---|---|---|---|
| Scope | One specific task | A complete process — start to finish | An entire value stream or cross-functional workflow |
| Audience | The operator performing the task | The person responsible for the process | Management, improvement teams, cross-functional stakeholders |
| Detail level | Highest — step-by-step operator instructions | Medium — sequence, responsibilities, decision points | Lowest — flow and sequence, not operational instructions |
| Format | Numbered steps, one action per line, specific measurements, visual aids | Numbered procedure with sub-tasks, responsibility table, decision branches, scope statement | Swimlane or flowchart — process boxes, decision diamonds, hand-off arrows |
| Engineering example | How to set up a CNC turning operation; how to perform a weld bead inspection | The incoming material inspection process from goods receipt to floor release | The customer order fulfilment flow from order receipt to invoice |
| ISO 9001 clause | Clause 7.5 (documented information); clause 8.5 (production and service provision) | Clause 7.5 (documented information); clause 8.4 (supplier control); clause 8.6 (product release) | Clause 4.4 (QMS processes and their interaction); supports management review |
The most specific document in the hierarchy
A work instruction is a document that describes how to perform one specific task. It is written for the operator who performs the task, at a level of detail where they can complete the task correctly on their first attempt without verbal guidance from anyone. It does not describe a complete process or a system of processes — it describes a single task within a process.
Numbered steps in the order they are performed; one action per step with no bundling; specific measurements, tolerances, and tool specifications; visual aids (photographs, diagrams) at every critical checkpoint; and a defined completion trigger — the point at which the operator knows the task is done correctly.
How to set up a CNC turning operation from drawing receipt to first-article sign-off; how to perform a weld bead inspection on a carbon steel joint; how to apply a zinc-rich primer coat to a prepared steel surface; how to load and zero a CMM probe for a specific component inspection routine.
When task-level variation between operators is causing defects or inconsistency; when you are onboarding new operators who need to perform the task correctly without supervision; when a task has safety-critical or quality-critical checkpoints that must be verified in a specific sequence; when an existing SOP references ‘perform inspection per WI-XXX’ and the task needs a separate, more detailed document.
Clause 7.5 (documented information required for the operation of its processes), clause 8.5 (control of production and service provision — work instructions are one of the primary mechanisms for ensuring consistent execution).
A work instruction answers one question and one question only: exactly how do I perform this specific task? If the document answers a broader question than that, it is probably an SOP.
The process-level document
An SOP is a document that describes how a complete process operates — the sequence of activities from start to finish, who is responsible for each activity, what the decision points are, and what the expected output is. It is written for the person responsible for the process, not the operator performing each individual task.
A scope statement defining what the SOP covers and what it does not; a responsibility table mapping roles to activities; a numbered procedure sequence with sub-tasks and decision branches where the process diverges; document control fields (revision number, approval date, review date, owner); and a revision history table. An SOP may reference work instructions for individual tasks — it does not reproduce them.
The incoming material inspection process from goods receipt to floor release; the customer complaint management process from receipt to close-out; the corrective action process from non-conformance identification to root cause elimination; the new supplier qualification process from initial assessment to approved vendor list entry.
For any repeatable process that spans multiple steps or involves multiple roles; when ISO 9001 certification requires documented evidence of how the process operates; when the process has been improved (through a Lean workshop, for example) and the new method needs to be standardised; when inconsistency in process-level execution — not task-level execution — is causing problems.
Clause 7.5 (documented information), clause 8.4 (control of externally provided processes and services — supplier qualification SOPs), clause 8.6 (release of products and services — inspection and release SOPs). Most of the documented information that ISO 9001 auditors ask to see is in SOP format.
An SOP answers the question: how does this process work, and who does what? It does not tell the operator how to perform a specific task — it tells the process owner how the sequence of activities fits together.
The system view that shows how everything connects
A process map is a visual diagram that shows the flow of activities across an entire value stream or cross-functional workflow. It does not describe how to do any individual activity — it shows how they connect, who owns each section of the flow, and where hand-offs occur between functions or departments.
Swimlane or flowchart format with clearly delineated responsibility lanes; process boxes for activities, decision diamonds for branch points, and arrows showing the direction of flow; inputs and outputs at the start and end of the flow; typically covers end-to-end — from trigger event (customer order, complaint received, design request) to final output (product dispatched, issue resolved, design approved). Process maps do not include step-by-step instructions — those belong in SOPs and work instructions.
The customer order fulfilment flow from enquiry to invoice; the new product development process from concept approval to production release; the supplier qualification flow from initial contact to approved vendor registration; the quality management flow from non-conformance identification to corrective action close-out.
For system-level visibility — when you need to show management or a cross-functional team how processes connect; as the starting point for a Lean or VSM improvement exercise (a process map shows you where to look; a value stream map adds the data that tells you what to fix); for management review and strategic planning; for onboarding new managers or leaders who need to understand how the business operates at a process level.
Clause 4.4 (‘the organisation shall determine the processes needed for the QMS and their interaction’) explicitly requires organisations to understand and document how their processes connect. A process map is the most natural and readable way to satisfy this requirement.
A process map shows you the system. It does not tell anyone how to do anything — that is what SOPs and work instructions are for. Confusing the two produces process maps that are too detailed to be useful as system views and not detailed enough to guide anyone performing a task.
One important distinction worth noting: a process map shows the sequence and ownership of activities. A value stream map adds timing data, queue times, inventory, and information flows — making it a diagnostic tool for waste identification as well as a visualisation tool. VSM is process mapping with data.
How they relate — the documentation hierarchy
The three document types form a hierarchy by level of detail and intended audience. Each level serves a different purpose and should not be expected to serve the purpose of the levels above or below it.
An SOP may reference multiple work instructions (‘perform weld inspection per WI-027’) without reproducing them. A process map shows the sequence of SOPs in a value stream without describing what any of them contain. The relationship is hierarchical, not redundant — each level adds specificity for the audience that needs it.
The most important practical point: not every process requires all three levels. Most Australian engineering SMEs need SOPs and work instructions. Process maps are most valuable for improvement projects, management review, and cross-functional training — not for day-to-day operational guidance. The default starting point for most businesses building their first documentation system is SOPs, with work instructions added for tasks where operator-level variation is causing measurable problems.
Which one do you need? A simple decision framework
Three questions. Answer them in order.
The two most common wrong choices
The process map shows the flow beautifully but does not tell anyone what to do at each step or who is responsible for the decision points. The team sees the diagram and has no more operational guidance than before it was drawn.
The SOP describes the sequence correctly but does not go to the operator-level detail that would allow a new team member to perform the critical task without supervision. The variation continues because the task-level method is still in people’s heads, not on paper.
Start with the document your team is most likely to use.
For most engineering and manufacturing SMEs: SOPs first, work instructions where operator-level variation is causing problems, process maps when you need a system view for improvement or management review.
Download Our Free SOP Template →