Digital work instructions vs SOPs: what's actually different
Share article
Quick answer: An SOP defines the standard for a whole process and is maintained as a controlled document. A work instruction is the task-level version an operator follows at one station, and it leaves behind a record of what was done. ISO 9001 draws the same line in different words: procedures are maintained, evidence is retained.
Ask two people in the same plant to explain work instructions vs SOPs and you'll usually get two answers, both partly right. The terms get swapped in job ads, in audits and in software demos, and the confusion has a cost: it's why plants buy a document viewer and expect an execution system.
The distinction that holds up is about altitude and output. An SOP describes how a process is meant to run and stays under document control. A digital work instruction guides one task at one station and produces evidence that the task happened. ISO, OSHA and IATF all draw that line, each in its own language, and none of them uses the two words the way a shopfloor does.
What's the difference between a work instruction and an SOP?
An SOP is process-level. It defines scope, responsibilities, the overall sequence, and the documents the process depends on. A work instruction is task-level: what one person does at one station, in order, with the checks and inputs belonging to each step. The SOP is the reference a plant maintains. The work instruction is the sequence a person executes and confirms.
| SOP | Work instruction | |
|---|---|---|
| Question it answers | How is this process meant to run? | What do I do at this station, now? |
| Altitude | One process, often crossing departments | One task at one station |
| Audience | Anyone who has to understand or audit the process | The person doing the work |
| Typical size | Several pages of prose, tables and references | The steps of one job |
| What it produces | An approved, revision-controlled document | An execution record: who, when, which revision, what was measured, what deviated |
| Who owns it | Document control, quality, or PLM | The process owner for that station |
| Cost of it being out of date | An audit finding | A wrong part fitted on a running line |
The two nest rather than compete. A policy sets the intent, a process describes the flow, an SOP fixes the standard for one process, and work instructions are what that SOP points to for the individual jobs inside it. A plant with good digital SOPs and no work instructions has documented its standard without reaching the station.
Does ISO 9001 treat SOPs and work instructions differently?
ISO 9001:2015 uses neither term. Clause 7.5 splits documented information two ways instead, and the split maps onto the distinction almost exactly: information the organisation shall maintain, meaning the statement of how work is to be done, and information it shall retain, meaning evidence that the work was done.
Read that way, an SOP is maintained information and an execution record is retained information. They have different owners and different failure modes: a maintained document goes wrong by drifting out of date, and a retained record goes wrong by never existing.
ISO 9001:2015 is in its final months as the edition in force: ISO has the sixth edition, ISO 9001:2026, scheduled for publication on 16 September 2026, with a three-year transition running to September 2029. Plants scoping documentation work before that date are deciding, whether they frame it that way or not, which of their documented information gets maintained and which gets generated as a record.
Regulation makes the same split explicit. OSHA's lockout/tagout standard requires under 1910.147(c)(4)(i) that energy control procedures be developed, documented and used, which is the SOP. Under 1910.147(c)(6)(ii) it separately requires the employer to certify the periodic inspection, identifying the machine, the date, the employees included, and the person who performed it. That certification is a record, and no amount of procedure quality produces one.
Which one has to be accessible at the workstation?
The work instruction. IATF 16949, the automotive quality standard, requires standardised work documents to be communicated to and understood by the people performing the work, legible, presented in a language those people understand, and accessible for use at the designated work area. An SOP filed in a document management system three screens away satisfies none of those four conditions, which is a large part of why the printed binder at the end of the line survived every digitalisation programme aimed at it.
Quality managers push back here, and the objection is fair: the auditor asks for the controlled document, so the controlled document is what belongs in front of the operator. An audit asks for two separate artefacts, though. It wants the approved standard, and it wants evidence the work followed that standard. A controlled PDF on a tablet delivers the first and leaves the second to whatever someone writes on a sheet afterwards.
If we digitise our SOPs, do we have digital work instructions?
No. Moving a PDF onto a tablet changes where the document is stored and leaves the work itself untouched. The operator still reads prose, still judges which revision applies, and still finishes the job without the system knowing anything happened. What separates digital work instructions from a digitised SOP is what exists after the operator closes the screen.
Three instruction states are worth separating when you audit your own library, because each one asks something different of a platform:
- Reference instruction. Operational knowledge somebody consults: a cleaning procedure, an OEM machine manual, a troubleshooting guide. No process instance is running, and the whole job is finding the right content for the machine in front of you.
- Executed instruction. A person works through it and the system records who did it, when, against which revision, what they confirmed, what they measured, and where they deviated.
- Process-bound instruction. The instruction is selected and triggered by live process state. The order, the variant, the machine condition or the qualification of who's on shift decide which instruction appears and when.
Most of a plant's library should stay in state one, and this is where conversion projects go wrong. A 40-page OEM manual has no business being restructured into confirmable steps; it needs to be findable and answerable at the asset, and nothing more. Restructuring the whole library is why conversion quotes come back measured in quarters instead of weeks. The subset worth converting into executed instructions is the task-level work with a fixed sequence, a check that matters, and a real consequence when a step gets skipped.
Once that subset is identified, the mechanics are the cheap part. Creating the digital work instruction from existing content with AI drafts the step breakdown from the document you already have, and a process owner approves it before anything reaches a station.
What changes on the floor when the work instruction is the digital artefact?
The evidence stops being a separate job. At Dantherm, an HVAC manufacturer, paper processes were eliminated across production, with full traceability from workstation to ERP and significant quality improvement through automated quality checkpoints. The mechanism behind that last point is the split above: the check is a confirmable step inside the instruction rather than a clause in a procedure nobody opens at the station.
Two numbers set expectations for scope. Go-live on one production line takes 2 weeks, and 85% of configuration is handled by ops teams without IT involvement. Neither figure describes converting a library. They describe one station, one job, one sequence, which is the unit of work this distinction implies.
Common mistakes when separating SOPs from work instructions
- Converting everything. The reference material stays reference material. Only the task-level work with a sequence and a check earns the conversion effort.
- Retiring the SOP. Document control, PLM or the QMS remains the system of record for the standard itself. The work instruction points at it rather than replacing it.
- Writing work instructions at SOP altitude. Paragraphs of prose numbered 1 to 14 are still prose. A step is one action a person can confirm.
- Leaving the routing rules unwritten. Which station, which variant, which trigger, which qualification: in most plants these live in a supervisor's head and appear in no document at all. They surface the moment you try to make the instruction reach the right place.
- Treating a checklist as a work instruction. Digital checklists capture confirmations against a standard. A work instruction also carries the content the operator needs to perform each step. The two are often combined in one screen, and a checklist on its own leaves the operator to find the content elsewhere.
Frequently asked questions
Is a work instruction the same thing as an SOP?
No. An SOP is the process-level standard: scope, responsibilities, sequence and references, maintained as a controlled document. A work instruction is the task-level detail for one job at one station, and in a digital system it also produces the record of what was done. An SOP usually references several work instructions. In casual use the terms get swapped, which is why audits and software evaluations so often talk past each other.
Does ISO 9001 require work instructions?
ISO 9001:2015 doesn't name work instructions or SOPs. Clause 7.5 requires the documented information the organisation determines is necessary for the effectiveness of its quality management system, which leaves the format to you. It does distinguish information you maintain from information you retain, so both a standard and evidence of conformance are expected. Sector standards are stricter: IATF 16949 requires standardised work documents accessible at the designated work area.
How many work instructions does one SOP produce?
There's no fixed ratio. A useful first pass counts the stations and distinct jobs the SOP covers rather than its pages. A twelve-page assembly SOP spanning four stations with two variants can yield eight work instructions, or one instruction with variant logic, depending on how much of the difference is genuine. Deciding that is process work rather than documentation work, and it's where the real effort sits.
Who should write work instructions?
The process owner for that station, working from the existing SOP and from whoever currently does the job well. Document control owns the SOP; the process owner owns the sequence. Instructions written centrally, away from the station, tend to describe the standard accurately while missing how the work actually runs, which is the most common reason operators go back to the binder.
Where do digital SOPs fit if the work instruction is what reaches the operator?
They stay the governing standard, and digitising them is worth doing on its own terms: revision control, searchability and a single current version instead of six printed copies of different vintages. Digital SOPs solve findability and currency. Work instructions solve execution and evidence. Plants that only do the first get a tidier library and the same shopfloor.
Do we have to move our SOPs out of SharePoint before we can start?
No. Content can be linked from the systems it already lives in, so the SOP library can stay where document control wants it while the task-level instructions are built and executed elsewhere. A migration project as a precondition is the single most common reason this work never starts. If you want to see what the split looks like on one of your own procedures, you can walk one SOP through it with us.
Pick the one station where a skipped step costs the most, and separate its SOP into the reference content, the confirmable sequence, and the rules deciding which version applies. The rest of the library can wait until that one runs. The complete guide to digital work instructions covers implementation and integration in more depth.