Document Control
ISO 9001 SOP Template: How to Write a Standard Operating Procedure
A Standard Operating Procedure is the backbone of a well-run quality management system. This guide covers what belongs in an ISO 9001 SOP, what auditors actually look for, the mistakes that get organizations cited, and a free template with a filled-in example you can use today.
Free Template — Ready to Download
Word document (.docx) — use immediately, no sign-up required
⬇ Download Blank TemplateWorked Example — ABC Precision Manufacturing
⬇ Download ExampleThis template won't tell you when it's out of date
Every time a procedure gets revised, someone has to manually track down who was trained on the old version and make sure they're retrained. Training Tiger does that automatically — document changes trigger retraining assignments without anyone lifting a finger.
See how it works →1. What Is a Standard Operating Procedure?
A Standard Operating Procedure (SOP) is a documented set of instructions that describes how a process should be performed. The purpose is consistency: when ten different people perform the same task, a well-written SOP ensures they all do it the same way — the right way.
SOPs typically operate at the process level. They answer: what is this process, why does it exist, who is responsible, and what are the key steps? For more granular, task-level instructions — particularly for shop floor or operational work — organizations use Work Instructions, which are subordinate to SOPs and provide step-by-step detail.
SOP vs. Work Instruction — the quick distinction
Standard Operating Procedure
- Process level — the whole picture
- What to do, who is responsible
- Covers multiple steps or activities
- Example: Incoming Material Inspection Procedure
Work Instruction
- Task level — one specific operation
- Exactly how to do it, step by step
- Enough detail for an operator to follow alone
- Example: CNC Lathe Setup — Mazak QT-350
2. What ISO 9001 Actually Requires
ISO 9001:2015 does not use the word “SOP.” The standard requires “documented information” to the extent necessary to support the operation of processes and to have confidence they are being carried out as planned (Clauses 7.5 and 8.1).
This is actually broader than the old ISO 9001:2008 requirement, which mandated exactly six documented procedures. The 2015 standard leaves it to the organization to determine what needs to be documented. The guiding principle: if the absence of a document could lead to inconsistent results or a nonconformity, you probably need that document.
“The organization shall maintain documented information to the extent necessary to have confidence that the processes have been carried out as planned.”
— ISO 9001:2015, Clause 8.1
In practice, most manufacturing, service, and quality organizations maintain SOPs for any process where variability in execution would affect product or service quality — purchasing, production, inspection, nonconforming product control, corrective action, internal audits, and more.
3. Required Sections in an ISO 9001 SOP
ISO 9001 does not mandate a specific SOP format, but there is a well-established structure that satisfies auditor expectations and makes SOPs genuinely useful. Here is what every ISO 9001 SOP should include:
Document Number and Title
Every SOP needs a unique identifier and a clear, descriptive title. Document numbers should follow a consistent naming convention — for example, QMS-SOP-008 for the eighth SOP in your QMS. The title should tell a reader exactly what process this document covers without reading further.
Purpose
One or two sentences explaining why this SOP exists. What process does it control? What quality outcome does it ensure? Auditors use the purpose statement to understand what they should be verifying when they evaluate this procedure.
Scope
Define where this procedure applies — which departments, processes, product lines, or facilities. Also state what it does not cover, if there is potential for confusion. A well-defined scope prevents scope creep and tells everyone whether this SOP applies to them.
References
List any other documents, standards, or regulations this SOP references or links to — related SOPs, work instructions, forms, ISO clauses, OSHA standards, customer specifications. This supports your document hierarchy and helps auditors trace requirements.
Definitions
Define any terms that could be ambiguous or that have specific meanings within your QMS. You do not need to define common words — only terms where different interpretations could lead to different actions.
Responsibilities
Assign clear accountability for each activity in the procedure. Use role titles, not names — people change, roles do not. Example: "The Quality Inspector is responsible for performing incoming inspection on all received material."
Procedure Steps
The core of the SOP. Numbered steps describing the process from start to finish. Each step should be clear, actionable, and in sequence. Include decision points, acceptance criteria, and what to do when something does not go as expected (the nonconformity path).
Records / Associated Forms
List any records generated by this procedure and the forms used to create them. This connects your SOP to your records control requirement (ISO 9001 Clause 7.5.3) and makes it easy for auditors to pull the evidence they need.
4. What Not to Put on the Document Itself
Many organizations waste the top third of every SOP page on metadata: revision history tables, approval signature blocks, effective date fields, document owner boxes, review date fields, and classification stamps. This is largely a legacy of older ISO 9001 interpretations and paper-based document control.
With a document control system — even a simple one — all of this metadata lives in the system, not on the document. The document itself should start with the content that employees need to do their jobs. Metadata on the document creates a maintenance burden (every metadata change requires a new revision) and adds clutter that reduces readability.
Cluttered — put in document control system instead:
- ✗ Revision history table on page 1
- ✗ Author / reviewer / approver signature blocks
- ✗ Effective date field
- ✗ “Controlled document” stamp
- ✗ Review cycle / next review date
- ✗ Distribution list
What belongs on the document:
- ✓ Document number
- ✓ Document title
- ✓ The procedure content itself
- ✓ A note pointing to your document control system for the current version
Note: If you are not yet using a document control system and managing SOPs on paper, some of this metadata on the document is unavoidable. But if you have a system, let it do its job.
5. What Auditors Check For
When an ISO 9001 auditor reviews your SOPs, they are typically checking for three things:
Are the right processes documented?
Auditors will trace requirements from the standard to your process documentation. For example, for Clause 8.4 (external providers), they will expect to see a documented purchasing or supplier management procedure. If a process has potential for significant quality impact and there is no documented procedure, expect a finding.
Do employees know and follow the procedures?
The classic audit question: "Can you show me the procedure for this?" followed by "Can you walk me through how you do it?" Auditors compare what the SOP says to what actually happens on the floor. If employees have not been trained on the current revision, or if actual practice deviates from the written procedure without a documented reason, that is a nonconformity.
Are procedures current?
An SOP that describes a process you changed two years ago is worse than no SOP — it is documented evidence of a gap between what you say you do and what you actually do. Auditors will check that SOPs reflect current practice, that revision history is maintained, and that obsolete versions are not in circulation.
6. Common SOP Mistakes
✗ Writing for compliance, not for clarity
SOPs written to satisfy an auditor rather than to guide an employee are always worse. If you would not hand this document to a new hire and expect them to perform the process correctly, it needs work.
✗ No decision points or exception handling
Real processes have forks. What happens when incoming material fails inspection? What does an operator do if the machine reading is out of tolerance? SOPs that only describe the happy path leave employees without guidance when things go wrong — which is exactly when they need it most.
✗ Too vague to be useful
"Inspect the product for defects" is not a procedure step. "Inspect each piece for dimensional conformance per drawing; measure critical dimensions using calibrated calipers and record on QMS-F-023" is. Vague steps lead to inconsistent execution, which is the opposite of what an SOP is for.
✗ Not training employees on revisions
Every significant revision to an SOP should trigger retraining for the employees affected. A surprisingly common audit finding: employee training records show they were trained on Rev B, but the current version is Rev D. The gap between what people were trained on and what the current procedure says is a real nonconformity.
✗ Procedures that describe aspirations, not reality
Write what you actually do, not what you wish you did. If your SOP says you perform 100% inspection but you actually do 10% sampling, you have just created a major nonconformity. An SOP that accurately describes a less rigorous process is better than one that describes a rigorous process you do not follow.
7. SOP Example: Incoming Material Inspection
Here is a summary of the key sections from our filled-in SOP example for ABC Precision Manufacturing — a CNC precision machining company. This gives you a sense of the right level of detail for each section.
INCOMING MATERIAL INSPECTION PROCEDURE
Document Number: QMS-SOP-008 | ABC Precision Manufacturing, LLC
Download the Free SOP Template
Get the blank template to build your own, or download the filled-in example from ABC Precision Manufacturing to see a complete SOP in action.
8. Training Employees on SOPs
Writing the SOP is only half the job. ISO 9001 Clause 7.2 requires that employees be competent to perform their work — and for process-critical procedures, that means documented evidence that employees were trained and understood the content.
For every SOP, you need a clear answer to three questions:
- Who needs to be trained on this SOP?
- How do you verify they understood it? (Not just that they read it)
- What triggers retraining? (New revision, role change, performance issue)
The most common audit finding related to SOPs is not a poorly written procedure — it is an employee who was trained on Revision B when Revision D is the current version. The delta between what people were trained on and what the procedure currently says is exactly what auditors look for.
Automate SOP Training Tracking with Training Tiger
When you upload a new SOP revision, Training Tiger can automatically assign retraining to everyone who needs to be trained on the new version — and send them an email. Managers get a completion dashboard. Auditors get a timestamped Skills Matrix showing who was trained on which revision.
9. Frequently Asked Questions
Does ISO 9001 require SOPs?
ISO 9001:2015 does not use the term "SOP" but requires documented information to support the operation of processes (Clause 7.5). In practice, SOPs are the most common way organizations meet this requirement. Auditors expect documented procedures for your key processes — particularly those with direct quality impact.
What sections should an ISO 9001 SOP include?
Purpose, scope, references, definitions, responsibilities, step-by-step procedure steps, and records/forms used. Revision history and approvals belong in your document control system, not on the document itself.
What is the difference between an SOP and a work instruction?
An SOP covers a process at a higher level — what to do and who is responsible. A work instruction covers how to do a specific task with step-by-step detail. SOPs reference work instructions; work instructions support SOPs.
How many SOPs does ISO 9001 require?
ISO 9001:2015 does not specify a number. ISO 9001:2008 required six documented procedures; the 2015 revision replaced that with a more flexible approach. The right number depends on your organization — document any process where inconsistency would affect quality.
Does every SOP need management approval?
ISO 9001 requires that documented information be approved for adequacy prior to use (Clause 7.5.2). This means yes — someone with appropriate authority must review and approve each SOP before it becomes active. Who that is depends on your organization; it does not have to be top management for every document.
How often should SOPs be reviewed?
ISO 9001 does not specify a review frequency. Most organizations review SOPs annually or whenever a relevant process changes. A good rule: review any SOP after a related corrective action, after a process change, and at least every 1-3 years.