SOP vs Work Instructions vs Process Documentation
Last updated: January 2026
Process documentation describes what happens across a whole workflow, end to end. A standard operating procedure (SOP) describes how one team performs a single procedure within it. A work instruction describes exactly how one person completes one task inside that procedure. They are the same subject at three zoom levels: process, procedure, task.
These three terms get used interchangeably, and the confusion is understandable. They all describe how work gets done. But they are not synonyms; they are three levels of zoom on the same subject. Getting the distinction right stops you from writing a fifty-page “SOP” that is really a process map, or a “process document” nobody can act on because it is actually a pile of click-by-click steps.
Below, each term gets a plain definition, then the scope, audience, and detail that separate it from its neighbours, followed by a side-by-side table, a worked example that flows through all three, and a short decision guide. If you are ready to write one, our guide to writing an SOP goes step by step, the SOP template gives you a starting format, and the SOP software page covers the tools that create and maintain these documents. The full field is on the comparison hub.
What is process documentation?
Process documentation is a record of an entire workflow from start to finish: every stage, decision, hand-off, and role involved in getting from trigger to outcome.
Its job is to show the whole picture: what happens, in what order, who owns each step, and where work passes from one team or system to the next. Because it operates at the workflow level, process documentation is usually the most abstract of the three: think flowcharts, swimlane diagrams, and stage-by-stage narratives rather than button-level detail.
Scope: an end-to-end process, often spanning multiple teams. Audience: managers, process owners, auditors, and new joiners getting oriented. Granularity: high-level stages and hand-offs, not individual clicks. Example: the complete employee onboarding process, from signed offer to a fully productive first week.
What is a standard operating procedure (SOP)?
A standard operating procedure is a set of ordered steps that defines how one team carries out a single, repeatable procedure the same way every time.
An SOP sits one level below process documentation. Where a process map shows that “IT provisions the new hire” as one box, the SOP is the contents of that box: the actual steps, the person responsible for each, the standard the output must meet, and how to handle common exceptions. It is detailed enough to act on but stops short of narrating every keystroke. That is a work instruction's job.
Scope: one repeatable procedure owned by a single team. Audience: the team accountable for the procedure. Granularity: ordered steps, responsibilities, standards, and exceptions. Example: the IT team's SOP for provisioning a new hire's accounts and hardware.
What is a work instruction?
A work instruction is a granular, step-by-step description of exactly how one person performs one specific task, down to the individual clicks, fields, and settings.
A work instruction is the deepest zoom. It takes a single step of an SOP that is too intricate to describe in a line (often a software task) and spells it out completely, so that someone who has never done it can complete it correctly on the first try. This is the level where screenshots earn their place: one action per step, the exact field values, and a clear success state at the end.
Scope: one specific task at one screen or workstation. Audience: the individual doing the task, often new or occasional. Granularity: literal click-by-click steps, usually with screenshots. Example: how to create a user in the admin console, field by field.
Side by side
The clearest way to hold the three apart is to line up the dimensions where they differ: scope, audience, level of detail, owner, update cadence, and a concrete example.
| Dimension | Process documentation | SOP | Work instruction |
|---|---|---|---|
| Scope | An entire end-to-end process, often across teams and systems | One repeatable procedure owned by a single team | One specific task performed at one workstation or screen |
| Question it answers | What happens, in what order, and who owns each hand-off? | How does our team consistently carry out this procedure? | Exactly which buttons, fields, and clicks complete this task? |
| Audience | Managers, process owners, auditors, new joiners orienting | The team responsible for the procedure | The individual doing the task, often a new or occasional operator |
| Level of detail | High-level: stages, decisions, hand-offs, roles | Medium: ordered steps, responsibilities, standards, exceptions | Granular: literal click-by-click steps with screenshots |
| Typical owner | Operations lead or process owner | Team lead or subject-matter expert | The practitioner who performs the task |
| Update frequency | Rarely, only when the workflow itself is redesigned | Occasionally, when the procedure or standard changes | Often, whenever the underlying tool or screen changes |
| Example | The full employee onboarding process | The IT team's SOP for provisioning a new hire's accounts | How to create a user in the admin console, step by step |
The hierarchy: one example through all three
The three levels nest: a process contains several SOPs, and an SOP contains several work instructions.
Employee onboarding makes the nesting concrete. Follow one thread from the widest zoom to the narrowest.
Level 1: Process documentation
The employee onboarding process
A workflow spanning HR, IT, and the hiring manager: offer accepted → paperwork and payroll set up (HR) → accounts and hardware provisioned (IT) → first-week plan and introductions (manager) → new hire productive. It shows the stages and hand-offs; it does not say how any one team does its part.
Level 2: SOP (zoom into the IT box)
SOP: Provisioning a new hire's accounts and hardware
The IT team's procedure: create the user in the identity provider, assign the correct group and licenses, order and image a laptop to the standard build, grant access to the team's core apps, and confirm first-day login works. Each step names a responsible person and the standard to meet, but it does not narrate every click of creating the user.
Level 3: Work instruction (zoom into one SOP step)
Work instruction: Create a user in the admin console
The click-by-click for that one step: open the admin console, go to Directory → Users, click Add user, fill in the naming-convention email and department fields, assign the “All Staff” group, set “require password change on first login,” and click Create. A screenshot per screen, one action per step, ending at the confirmation that the user exists.
Which one do you need?
Work backwards from what is actually going wrong. A quick decision tree:
Do things break at the hand-offs between teams?
→ You need process documentation. The problem is the seams, not the steps. Map the whole workflow and make ownership of each hand-off explicit.
Does one team do the same procedure inconsistently, or does it live only in one person's head?
→ You need an SOP. Capture the ordered steps, responsibilities, and standard so anyone on the team can follow it the same way.
Do people get stuck on one intricate, click-heavy task, usually in software?
→ You need a work instruction. Document that single task step by step with screenshots so a first-timer can complete it unaided.
Most teams end up with all three over time, linked together. If you are starting from nothing, begin with the SOP for your most error-prone procedure (it is the most useful single document), and add the level above or below only when the SOP alone stops being enough.
Where a capture tool fits
Work instructions are the level most painful to write by hand, because they demand a current screenshot for nearly every step. This is where automatic-capture tools help: Dubble watches you perform a task once and turns it into a step-by-step guide with screenshots and video, so a work instruction is produced as a byproduct of doing the work rather than as a separate documentation chore. Because those captured guides paste cleanly into Notion, Confluence, or Google Docs, you can compose several of them into an SOP and reference that SOP from a higher-level process map, building the hierarchy from the bottom up. It does not replace the judgement of writing a good SOP or mapping a process; it removes the manual screenshot work at the task level where most documentation efforts stall.
Frequently asked questions
Keep reading
- How to write an SOP: a step-by-step method once you know you need one.
- SOP template: copyable formats to start from.
- SOP software: the tools that create and maintain these documents.
- The comparison hub: every documentation tool, head to head.
Turn a task you just did into a work instruction
Dubble captures your screen while you work and produces a step-by-step guide with screenshots and video, free to start, and it pastes straight into your SOPs and knowledge base.