ISO 9001 Work Instruction Template: How to Write Instructions That Actually Get Used
Published 5 April 2026 · Last reviewed 23 February 2026
Most ISO 9001 work instructions fail for one of two reasons: they are so detailed that nobody reads them, or so vague that an auditor rejects them on the spot. Getting the balance right matters because work instructions are the documents your operators actually touch every day. A good ISO 9001 work instruction template gives you a repeatable structure that satisfies Clause 8.1 requirements while being short enough that staff follow it without prompting.
This guide covers the template structure, a worked example, the difference between procedures and work instructions, how many you actually need, and the mistakes that generate audit findings.
What is a work instruction (and how is it different from a procedure)?
Before writing anything, get the terminology straight. ISO 9001 does not use the term "work instruction" explicitly — it refers to "documented information" needed to support process operation (Clause 8.1). In practice, most UK certification bodies and UKAS auditors recognise a three-tier documentation hierarchy:
Procedures describe what happens and who is responsible. They cover a whole process — for example, your purchasing procedure might explain how suppliers are selected, orders placed, and goods received. Procedures answer the question: what are the steps in this process and who owns each one?
Work instructions describe how to perform a specific task within a procedure. They are the step-by-step detail an operator needs to do one job correctly. Using the same example, a work instruction might cover how to inspect incoming goods against a purchase order. Work instructions answer: how exactly do I do this task?
Forms and records capture evidence that a task was done. The completed goods receiving inspection form is the record; the blank form is the template. Records answer: did this happen, and what was the result?
Here is a practical way to think about it:
| Level | Document type | Answers | Example |
|---|---|---|---|
| 1 | Procedure | What happens, who does it | Purchasing procedure |
| 2 | Work instruction | How to do a specific task | Goods receiving inspection |
| 3 | Form / record | What was the result | Goods receiving inspection checklist (completed) |
Your quality manual sits above all three, describing the overall QMS. Procedures reference work instructions; work instructions reference forms. Each layer adds detail without repeating the layer above.
ISO 9001 work instruction template: the 8-field structure
Every work instruction needs the same core fields. This structure satisfies auditor expectations, keeps the document navigable, and ensures revision control works properly.
1. Title
Clear, specific, and matching how staff refer to the task. "Goods Receiving Inspection" works. "WI-PUR-003" does not — that is a document ID, not a title. Use both: the title tells staff what the document covers; the ID tells the document control system where it lives.
2. Document ID
Follow whatever numbering convention your QMS uses. A common pattern for small businesses: WI-[process code]-[sequence number]. Example: WI-PUR-003 (third work instruction in the purchasing process). Keep the system simple — if you need a manual to understand the numbering, it is too complex.
3. Revision number and date
Essential for document control. Use sequential revision numbers (Rev 1, Rev 2, Rev 3) and include the date of last revision. Some businesses add a brief revision history table at the bottom. At minimum, the current revision number and date must be visible on the first page.
4. Purpose
One or two sentences explaining why this work instruction exists. "To ensure incoming goods are inspected against purchase order specifications before being accepted into stock." This prevents scope creep and helps new staff understand what the instruction is for.
5. Scope
What tasks does this instruction cover, and what does it not cover? Define the boundaries. "Applies to all physical goods received at the Swindon warehouse. Does not cover digital deliveries or services." Scope prevents confusion when multiple work instructions sit in the same process area.
6. Step-by-step instructions
The core of the document. Write each step as a numbered action, starting with a verb. Be specific enough that a competent person can follow the steps without asking questions, but do not write a training manual. Assume the reader has the baseline competence for their role.
Good step: "Compare the delivery note quantities against the purchase order. Record any discrepancies on the Goods Receiving Form (F-PUR-003)."
Weak step: "Check the delivery."
Over-engineered step: "Pick up the delivery note from the driver's hand. Walk to the computer terminal located in the warehouse office (Room 1.04). Open the ERP system by double-clicking the icon on the desktop. Navigate to Purchasing > Purchase Orders > Open Orders..."
The middle ground is what you are aiming for. Write for a trained operator, not a complete beginner and not an auditor.
7. Records generated
List every form, log, or record that this instruction produces. Example: "Goods Receiving Form (F-PUR-003), Nonconformance Report (F-QMS-008) if applicable." This links the work instruction to your records and gives auditors a clear trail.
8. Approval
Who approved this version, and when. For small businesses, this is typically the process owner or quality manager. Some companies use a two-signature system (prepared by / approved by). Keep it proportionate — a 25-person company does not need a three-tier approval chain.
Worked example: goods receiving inspection
Here is what this template looks like filled in for a small manufacturer receiving raw materials at a single UK site.
Title: Goods Receiving Inspection
Document ID: WI-PUR-003 | Revision: Rev 2 | Date: 14 March 2026
Purpose: To ensure all incoming goods are inspected against purchase order specifications and supplier conformance requirements before acceptance into stock.
Scope: Applies to all physical goods and raw materials received at the Swindon warehouse. Does not apply to consumables under £50 per order or to digital deliveries.
Steps:
- Collect the delivery note from the driver and check the supplier name, PO number, and delivery address match our records.
- Conduct a visual inspection of packaging for damage. Photograph any damage before signing the driver's delivery note — note damage on the driver's copy as well.
- Open the purchase order in the ERP system using the PO number from the delivery note.
- Compare delivered items against the PO: verify part numbers, quantities, and any specified material certifications or test reports.
- For items requiring dimensional inspection, measure a sample per the inspection plan (minimum 10% of batch or 5 units, whichever is greater). Record measurements on the Goods Receiving Form (F-PUR-003).
- If all items conform: sign the Goods Receiving Form, update stock in the ERP system, and move goods to the designated storage location.
- If any items do not conform: quarantine the nonconforming items in the red-tagged area, complete a Nonconformance Report (F-QMS-008), and notify the Purchasing Manager within 2 hours.
- File the completed Goods Receiving Form in the monthly inspection folder (physical) and scan to the QMS shared drive within 24 hours.
Records generated: Goods Receiving Form (F-PUR-003), Nonconformance Report (F-QMS-008) if applicable, damage photographs if applicable.
Approved by: Warehouse Manager | Date: 14 March 2026
Notice what is in this instruction and what is not. It tells a trained warehouse operative exactly what to do at each step. It does not explain how to use the ERP system (that is a training matter), how to operate a micrometer (that is a competence requirement), or why the company inspects incoming goods (that is in the purchasing procedure). Each layer of documentation does its own job.
How many work instructions does a small business need?
This is where most UK SMBs go wrong — usually in the direction of too many. A 20-person manufacturer does not need 150 work instructions. The standard does not prescribe a number. Clause 8.1 says you need documented information "to the extent necessary" to have confidence that processes are carried out as planned.
In practice, most small businesses with 5 to 100 employees need between 10 and 30 work instructions. The number depends on:
- Process complexity. A CNC machining shop with tight tolerances needs more work instructions than an IT consultancy delivering standard service packages.
- Staff turnover. High-turnover roles benefit from more documented instructions because you are training new people more frequently.
- Risk. Tasks where errors cause safety issues, significant financial loss, or customer complaints deserve a work instruction. Routine admin tasks usually do not.
- Regulatory requirements. Some sectors (medical devices, aerospace supply chain, food manufacturing) have regulatory obligations that drive additional documentation.
A useful test: if a trained person can do the task correctly without referring to a document, and the consequences of doing it slightly differently are low, you probably do not need a work instruction for it. Write instructions for the tasks that matter — the ones where consistency, traceability, or risk justify the documentation effort.
If you have already done a gap analysis, your findings will tell you which processes lack documented controls. Start there rather than trying to document everything.
Common mistakes that generate audit findings
Copying manufacturer instructions verbatim
Pasting the machine manufacturer's operating manual into your QMS and calling it a work instruction is a common shortcut. Auditors see through it immediately. The manufacturer's manual describes how their equipment works in general. Your work instruction should describe how your operators use that equipment in your process, with your acceptance criteria, generating your records.
Reference the manufacturer's manual by all means — "Refer to ABC Machine Operating Manual, Section 4.2 for setup parameters" — but do not replace your own instruction with it.
Writing for auditors instead of operators
If your work instructions read like they were written to impress an auditor, your staff will not use them. And if staff do not use them, the auditor will find out during interviews. "Can you show me the work instruction for this task?" followed by "Do you actually follow these steps?" is a standard audit trail. Blank looks and improvised answers generate nonconformities.
Write for the person doing the job. Use the language your team uses. If the shop floor calls it a "goods-in check," do not title the document "Incoming Material Conformity Verification Procedure." The auditor cares that the instruction exists, covers the right controls, and gets followed — not that it uses formal vocabulary.
No revision control
A work instruction without a revision number and date is a document control failure (Clause 7.5). Worse, having multiple versions in circulation — one pinned to the warehouse wall from 2022, a different one on the shared drive from 2024 — is a near-guaranteed nonconformity.
Every work instruction must be part of your document control system. Current versions accessible to people who need them. Obsolete versions removed or clearly marked. Revision history maintained. This is basic QMS hygiene, but auditors find revision control failures in roughly one-third of UK SMB surveillance audits.
Documenting everything
Writing work instructions for every conceivable task is a trap. It creates a documentation burden that nobody can maintain, and outdated instructions are worse than no instructions — they actively mislead. If your QMS contains 200 work instructions and half of them have not been reviewed in three years, you have a systemic document control problem.
Be selective. Document the tasks that need documenting. Leave the rest to training and competence.
Skipping the "records generated" field
If your work instruction does not specify what records it produces, auditors cannot trace the evidence chain. They will ask: "How do I know this task was done?" If the answer is "there is no record," they will ask: "Then how do you verify the process is being followed?" This quickly becomes a Clause 8.1 finding.
Every work instruction that involves a quality-critical task should produce at least one record.
ISO 9001 work instruction template: fitting it into your QMS
Work instructions do not exist in isolation. They are part of a documentation hierarchy that includes your quality manual, procedures, and records. Getting the connections right matters:
- Your quality manual references the procedures that govern each process area.
- Each procedure references the work instructions that provide step-by-step detail for specific tasks within that process.
- Each work instruction references the forms and records it generates.
- Your document control system tracks revision status across all three levels.
When an auditor examines your Clause 8 operational controls, they follow this chain. They read your procedure to understand the process, check whether work instructions exist for critical tasks, pick a recent record to verify the instruction was followed, and interview the operator to confirm they know the instruction exists and use it. If any link in that chain breaks, you have a finding.
For businesses going through certification for the first time, start by writing procedures first, then identify which tasks within each procedure need a work instruction. Do not write work instructions before you have mapped your processes — you will end up with instructions that do not connect to anything.
Keeping work instructions current
A work instruction is only useful if it reflects what actually happens today. The most common trigger for updating a work instruction is a process change — new equipment, revised acceptance criteria, a corrective action that changes how a task is done. Build work instruction review into your existing change management and corrective action processes.
As a minimum, review each work instruction annually as part of your management review cycle. If you have not changed a process in two years, the instruction may still be current — but confirm it, date the review, and record that no changes were needed. "Reviewed, no changes" is a valid outcome. No review at all is a gap.
For businesses preparing for the ISO 9001:2026 revision, now is a sensible time to audit your work instruction library. Check which instructions are still current, which need updating, and which can be retired. The clause comparison tool shows what has changed in the operational planning clauses.
Practical takeaway checklist
Use this when writing or reviewing your work instructions:
- Use the 8-field template structure: title, document ID, revision, purpose, scope, steps, records, approval
- Write steps as numbered actions starting with a verb — specific enough for a trained operator, not a training manual
- Target 10 to 30 work instructions for a typical SMB — document what matters, not everything
- Write for operators, not auditors — use the language your team actually uses
- Include the "records generated" field in every work instruction so auditors can trace the evidence chain
- Never copy manufacturer manuals verbatim — reference them, then write your own process-specific instruction
- Apply revision control to every work instruction and remove obsolete versions from circulation
- Review work instructions at least annually and after every process change or corrective action
- Connect each work instruction to its parent procedure and to the forms it generates
- Test the instruction: give it to someone who does the task and ask if it matches what they actually do — if it does not, rewrite it
Get this right and you end up with a lean set of work instructions that staff actually use and auditors accept without extended questioning. That is the standard your QMS documentation should meet — useful on the shop floor and defensible in an audit.
If you are not sure how your overall documentation stacks up, the ISO 9001 readiness quiz gives you a clause-by-clause assessment in under five minutes. For a full picture of what certification will cost, including the documentation effort, try the ISO 9001 cost estimator.
This article is for general informational purposes only and does not constitute legal, regulatory, or professional compliance advice. ISO certification requirements vary by scope, sector, and certification body. Always verify requirements with your UKAS-accredited certification body or a qualified consultant before making compliance decisions.
ClauseWise is coming soon
Generate your ISO 9001 and ISO 27001 documentation without consultant fees.