If you have spent any time researching process documentation, you have probably seen the terms SOP and work instruction used interchangeably. They are not the same thing. Understanding the difference helps you create the right type of documentation for each situation, so your team finds what they need without wading through the wrong format.
Quick Answer
A standard operating procedure (SOP) describes a complete process from trigger to outcome. It covers every step, every decision point, and every handoff involved in getting from A to Z.
A work instruction zooms into a single task within that process and provides the granular, technical detail needed to execute it correctly.
Example: An SOP titled "How to Process a Customer Return" covers the full flow: receiving the item, inspecting it, issuing the refund, and restocking. A work instruction titled "How to Issue a Refund in Shopify" covers just the refund step in exact detail: which buttons to click, what amounts to enter, what confirmation to look for.
What Is a Standard Operating Procedure
A standard operating procedure is a documented set of steps for completing an entire process. SOPs are written for a process-level audience: someone who needs to understand the full workflow and their role in it.
SOPs typically include:
- The purpose and scope of the process
- Who is responsible for each part
- Sequential steps from beginning to end
- Decision points and branching logic
- Expected outcomes and verification criteria
SOPs answer the question: "How do we do this process?"
For a deeper look at writing them, see our guide on how to write a standard operating procedure.
What Is a Work Instruction
A work instruction is a detailed, task-level document that explains how to perform one specific activity. Work instructions are written for an operator-level audience: someone standing at a machine, sitting at a screen, or handling a specific piece of equipment.
Work instructions typically include:
- The specific task being performed
- Exact tool settings, field values, or measurements
- Safety warnings relevant to this task
- Visual aids (photos, annotated screenshots, diagrams)
- Quality checkpoints for this task
Work instructions answer the question: "How exactly do I do this one task?"
Key Differences at a Glance
| SOP | Work Instruction | |
|---|---|---|
| Scope | Entire process (multiple steps) | Single task (one step in detail) |
| Audience | Anyone involved in the process | Person performing a specific task |
| Detail level | Moderate. Enough to follow the flow. | High. Exact values, settings, clicks. |
| Typical length | 5 to 20 steps | 3 to 15 micro-steps per task |
| Decision points | Yes, branches and handoffs | Rarely. Usually linear. |
| Visual aids | Optional | Almost always necessary |
| Update frequency | When the process changes | When the task or tool changes |
When to Use an SOP
Write an SOP when:
- Multiple steps involve multiple people. A process that crosses departments or roles needs one document showing the full picture.
- Onboarding new team members. SOPs give newcomers the overview they need to understand where their work fits in the bigger process.
- Standardizing across locations. If the same process runs in different offices, stores, or facilities, an SOP keeps everyone aligned.
- Meeting compliance requirements. Regulations often require documented procedures at the process level (ISO, HACCP, GMP, SOC 2).
When to Use a Work Instruction
Write a work instruction when:
- A single task is technically complex. Setting up a CNC machine, configuring an API integration, or calibrating laboratory equipment all warrant detailed instructions.
- Errors in one task have serious consequences. If getting a task wrong means safety hazards, data loss, or expensive rework, the detail of a work instruction is justified.
- Multiple people perform the same task differently. A work instruction eliminates variation by specifying the exact method.
- Training requires hands-on precision. When someone needs to learn a task by following instructions at their workstation, a work instruction is the right format.
When You Need Both
For many processes, you need both. Here is how they connect in practice.
Example: Employee Onboarding
The SOP covers the full process:
- Create the employee record in HR software
- Set up their email account
- Provision access to internal tools
- Schedule orientation sessions
- Assign a buddy
- Conduct the first-week check-in
Step 2 ("Set up their email account") might be straightforward for a cloud-based email provider. One click in the admin panel. No work instruction needed.
But step 3 ("Provision access to internal tools") could involve five different systems, each with different admin panels, permission levels, and naming conventions. That step gets its own work instruction with screenshots for each system.
The SOP links to the work instruction at step 3. The work instruction links back to the SOP for context. The reader moves between them as needed.
How They Work Together
Think of documentation as a hierarchy:
- Process: The end-to-end flow (documented as an SOP)
- Task: A single activity within the process (documented as a work instruction when needed)
- Verification: A confirmation that a step or group of steps was done correctly (documented as a checklist)
Not every task needs its own work instruction. A good rule of thumb: if the SOP step is clear enough that the target reader can execute it without extra detail, leave it as a step. If the step needs more than two or three sentences to explain properly, create a separate work instruction.
This hierarchy keeps your documentation manageable. SOPs stay concise because complex tasks are documented separately. Work instructions stay focused because they don't need to explain the broader process.
Managing Both in One Platform
The challenge with maintaining both SOPs and work instructions is keeping them connected. If they live in different folders, different drives, or different tools, the links break and people lose trust in the documentation.
Credia solves this by storing everything in one knowledge base. SOPs and work instructions live side by side, linked together, searchable, and accessible to the right people. When a work instruction changes, anyone following the parent SOP sees the updated version immediately.
Start with your most critical processes. Write the SOP first, then create work instructions for the steps that need them. Browse our SOP templates for ready-made starting points across different industries. For detailed instructions on writing each type, see how to write work instructions and our getting started with SOPs guide.