What Is a Work Instruction?
A work instruction is a document that tells a person exactly how to carry out a specific task, step by step. It is more detailed than a procedure, more focused than a policy, and more practical than a process map. In the context of ISO standards, a work instruction is the ground-level document that bridges the gap between what your management system says should happen and what actually happens on the floor, at the desk, or in the field.
On this page
If you have ever handed a new employee a checklist for closing down a piece of equipment, written out the exact steps for calibrating a measuring device, or documented how to handle a customer complaint call from start to finish, you have already created something that functions as a work instruction, whether you called it that or not.
Work instructions are referenced across many ISO standards including ISO 9001 for quality management, ISO 45001 for occupational health and safety, ISO 14001 for environmental management, and ISO 27001 for information security. They are not always mandatory as a named document type, but they are almost always necessary in practice if you want your system to actually work.
Work Instructions vs Procedures vs Policies: What Is the Difference?
This is one of the most common points of confusion for businesses going through ISO certification for the first time. People use these terms interchangeably, and auditors see it constantly. Let me break it down clearly.
Policy
A policy states the intent and direction of your organisation. It answers the question: what do we stand for and what are we committed to? It does not tell anyone how to do anything. An example is an Occupational Health and Safety Policy that states your organisation is committed to providing a safe working environment and preventing work-related injury.
Procedure
A procedure describes a process at a higher level. It answers the question: what needs to happen and who is responsible? It often covers multiple steps across multiple roles or departments. An example is a Corrective Action Procedure that outlines the stages from identifying a nonconformance through to root cause analysis, corrective action, and verification of effectiveness.
Work Instruction
A work instruction gets down to the task level. It answers the question: how exactly do I do this specific thing? It is typically written for one person doing one task. An example is a work instruction for how to complete a goods receipt inspection, including which measurements to take, what tolerances are acceptable, how to record the result, and what to do if the item fails.
Think of it this way. The policy sets the direction, the procedure maps the route, and the work instruction tells you exactly how to drive. All three serve different purposes and all three are needed in a functioning management system.
Get 3 ISO Quotes. 24 Hours Response
Tell us what you need and compare vetted ISO consultants or certification bodies within 24 hours. Free, no obligation.
Trusted by 400+ businesses like yours
Where Do Work Instructions Fit in ISO Standards?
ISO standards do not always use the term “work instruction” explicitly, but the concept is embedded throughout. ISO terminology refers to documented information as the broader category, and work instructions fall squarely within that definition.
In ISO 9001:2015, Clause 8 on Operation is where work instructions become most relevant. When you are planning and controlling your operational processes, you need to define the criteria for carrying out those processes. That is where work instructions live. If your process for manufacturing a product has specific steps that must be followed in a specific order to ensure quality, those steps need to be documented and accessible to the people doing the work.
In ISO 45001, work instructions often appear as safe work method statements or task-specific safety instructions. They tell workers how to perform a hazardous task safely, what personal protective equipment to use, and what to do if something goes wrong.
In ISO 27001, work instructions might cover how to handle a data access request, how to back up a server, or how to respond to a security incident in the first hour.
The common thread across all these standards is this: if a task has a significant impact on quality, safety, environment, or security, and if doing it wrong would cause a problem, then there should be a work instruction for it.
What Should a Work Instruction Include?
There is no single mandatory format for a work instruction under ISO standards. The standard gives you flexibility in how you document things, which is actually a good thing because it means you can write instructions that suit your people and your work environment. That said, a useful work instruction typically includes the following elements.
Title and Identification
Every work instruction needs a clear title that tells the reader exactly what task it covers. It should also have a document number, version number, and date so you can control it properly as part of your controlled document system.
Scope and Applicability
Who is this instruction for? Which tasks, equipment, locations, or products does it apply to? Being specific here prevents confusion and ensures the right people are using the right instructions.
Responsibilities
Who is responsible for carrying out the task? Who reviews the result? This does not need to be a full RACI matrix, but it should be clear enough that there is no ambiguity about ownership.
Required Resources
What tools, equipment, materials, or software does the person need before they start? Listing these upfront saves time and prevents people from getting halfway through a task and realising they are missing something critical.
Step-by-Step Instructions
This is the core of the document. Each step should be written in plain language, in the order it needs to be performed. Use numbered lists rather than paragraphs. Avoid jargon unless you define it. If a step requires a specific measurement or tolerance, state it explicitly. If a step has a decision point, explain what to do in each scenario.
Safety and Quality Checks
Where relevant, include checkpoints within the steps. For example, after completing step four, check that the reading is within a certain range before proceeding. This builds quality and safety into the task itself rather than relying on someone to remember.
References and Related Documents
If the work instruction references a form, a specification, a drawing, or another procedure, list those references so the person can find them easily.
Review and Approval
Document who approved the instruction and when. This is important for audit purposes and for maintaining document control.
Real-World Examples of Work Instructions
Abstract definitions only go so far. Here are some concrete examples across different industries to show what a work instruction looks like in practice.
Manufacturing: Machine Setup Instruction
A metal fabrication company has a CNC milling machine. The work instruction for setting up this machine before a production run includes the exact steps for loading the correct program, setting the work offsets, checking the tool lengths, running a dry cycle, and inspecting the first piece before approving full production. Without this instruction, two different operators might set up the machine differently, leading to inconsistent output and potential scrap.
Healthcare: Hand Hygiene Procedure
A medical clinic has a work instruction for clinical hand hygiene that follows the six-step technique recommended by the World Health Organisation. It specifies when to use soap and water versus alcohol-based hand rub, how long each step should take, and when hand hygiene is required during patient care. This is not left to individual interpretation because the consequences of getting it wrong are serious.
IT Services: User Account Provisioning
A managed service provider has a work instruction for setting up a new user account. It covers the exact steps in the identity management system, which security groups to assign based on the user role, how to verify the setup before handing over credentials, and how to document the action in the service log. This ensures every new account is configured consistently and that there is an audit trail.
Food Production: Cleaning and Sanitation
A food manufacturer has a work instruction for cleaning a mixing vessel between production runs. It specifies the cleaning agents to use, the concentrations, the contact times, the rinsing steps, and the verification check (such as a swab test or visual inspection) before the vessel is cleared for the next use. Under ISO 22000, this kind of documented control is essential for food safety.
Construction: Pre-Start Equipment Check
A civil construction company has a work instruction for the daily pre-start inspection of an excavator. It lists each item to check (fluid levels, lights, horn, tracks, bucket teeth, safety devices), the acceptable condition for each item, and what to do if a defect is found. This supports the requirements of ISO 45001 by ensuring hazards are identified before work begins.
When Are Work Instructions Required vs Optional?
This is a question that comes up a lot, and the honest answer is: it depends on the risk and the complexity of the task.
ISO 9001:2015 does not give you a list of work instructions you must have. Instead, it asks you to maintain documented information to the extent necessary to have confidence that processes are being carried out as planned. That means you need to use your judgement. A good rule of thumb is to write a work instruction when any of the following conditions apply.
- The task has a direct impact on product or service quality.
- Doing the task incorrectly would create a safety, environmental, or security risk.
- The task involves specialised knowledge that is not obvious to a competent person in the role.
- There is more than one way to do the task and consistency matters.
- The task is performed infrequently enough that people might forget the correct method.
- Regulatory or customer requirements specify how the task must be done.
On the other hand, you do not need a work instruction for every single thing your business does. Writing instructions for tasks that are straightforward, low-risk, and obvious to any competent employee creates unnecessary documentation burden without adding value. The goal is a right-sized system, not a bloated one.
Common Mistakes Businesses Make With Work Instructions
Having helped many organisations through ISO certification, I have seen the same mistakes come up repeatedly. Here are the ones that cause the most problems.
Writing Instructions That Nobody Reads
This is the most common problem. Businesses write lengthy, text-heavy documents that sit in a folder nobody opens. Work instructions need to be accessible, readable, and practical. Consider using photos, diagrams, flowcharts, or even short videos for complex tasks. The format should match the environment. A laminated one-page visual guide on the factory floor is often more effective than a ten-page Word document on a shared drive.
Writing Instructions That Do Not Match Reality
If your work instruction describes how a task should be done in theory but everyone on the floor does it differently in practice, you have a problem. An auditor will identify this as a nonconformance because your documented system does not reflect your actual system. Work instructions need to be written by or with the people who actually do the work, and they need to be updated when the process changes.
No Version Control
If you have multiple versions of a work instruction floating around, people will inevitably follow the wrong one. Every work instruction needs to be version-controlled, with obsolete versions removed from circulation. This is a basic requirement of maintaining a master document register.
Too Much Detail or Not Enough
Work instructions that try to cover every possible scenario become unmanageable. Instructions that are too vague leave too much to interpretation. The right level of detail is enough that a competent person new to the task could follow the instruction and produce the correct result.
No Review Cycle
Businesses write work instructions during their initial ISO implementation and then never touch them again. Processes change, equipment changes, regulations change. Work instructions need to be reviewed regularly and updated when changes occur. Build a review cycle into your document control procedure.
How Work Instructions Support Your ISO Audit
When an auditor visits your site, work instructions are one of the key pieces of evidence they look for. They will typically ask to see the instruction for a task being performed, then observe whether the task is actually being carried out in accordance with that instruction. This is called checking for conformance between documented information and actual practice.
Having clear, current, and accessible work instructions makes an auditor's job easier and gives them confidence that your system is real and functioning. Conversely, missing instructions, outdated instructions, or instructions that bear no resemblance to what is actually happening are reliable ways to collect nonconformances.
Work instructions also support your internal audit programme. When your internal auditors are checking processes, they use work instructions as the reference point for what should be happening. Without them, internal audits become vague conversations rather than structured conformance checks.
Beyond audits, work instructions are a practical business tool. They reduce training time for new staff, reduce errors, support consistent output, and protect you when something goes wrong by demonstrating that you had a defined and documented process in place.
Getting Started: How to Write Your First Work Instruction
If you are starting from scratch, do not try to document everything at once. Start with the tasks that carry the highest risk or have the most impact on quality, safety, or compliance. Talk to the people who actually perform those tasks. Watch them do it. Ask them to explain each step as they go. Then write the instruction in plain language that reflects what they actually do.
Once you have a draft, test it. Give it to someone who is competent but unfamiliar with the specific task and ask them to follow it. If they get confused or ask questions, revise the instruction until it is clear. Get it approved by the relevant supervisor or manager, assign it a document number, and add it to your document register.
Then make sure people can actually find it. A work instruction that exists on a shared drive but nobody knows about is worthless. Train your team on where to find instructions, how to use them, and what to do if they think an instruction is incorrect or out of date.
If you are working toward ISO certification and are unsure whether your documentation is at the right level, this is exactly the kind of thing a good ISO consultant can help you assess. At CertBetter, you can submit one form and receive up to three competing quotes from verified ISO consultants who can review your existing documentation, identify gaps, and help you build a right-sized system that will hold up under audit. The service is completely free for businesses seeking certification help.
