In short: a standard operating procedure has nine sections: identification, purpose, scope, responsibilities, definitions, required resources, the procedure, records and references, and revision history. The template below explains what belongs in each section, shows a worked example for a receiving inspection, and gives a checklist to run before the SOP is approved. Use it on paper if you must, or as the structure of a digital SOP that operators execute step by step.
The SOP template
| Section | What it contains | Tip |
|---|---|---|
| 1. Identification | Title, SOP number, version, owner, date of approval, next review date | Title = process + object: "Receiving inspection of purchased parts" |
| 2. Purpose | Why the procedure exists, in one or two sentences | Refer to the policy or requirement it serves |
| 3. Scope | Where it applies and where it does not: sites, products, departments, situations | Name the exclusions explicitly |
| 4. Responsibilities | Which role does what: performs, checks, approves, records | Use roles, never names |
| 5. Definitions | Terms and abbreviations that could be misread | Leave out if everything is obvious |
| 6. Required resources | Tools, materials, equipment, forms, software, qualifications, protective equipment | Everything the operator must have before starting |
| 7. Procedure | Numbered activities in sequence, with decision points and acceptance criteria; references to work instructions for detail | One activity per number, verb first |
| 8. Records and references | Which records are created, where they are kept, for how long; related SOPs, standards, drawings | Records are the evidence auditors ask for |
| 9. Revision history | Version, date, what changed, who approved | Automatic in a digital system with version control |
Section by section
1. Identification
The header makes the document findable and traceable: a unique number, a version, an owner and the dates of approval and next review. In a digital system these fields are properties of the procedure and update themselves when a new version is published. On paper they are the fields most often out of date, which is why auditors look at them first.
2. Purpose
One or two sentences: what the procedure achieves and which requirement it serves. "This procedure ensures that purchased parts are inspected against the drawing before they are released to stock, as required by our quality policy and ISO 9001 clause 8.4."
3. Scope
Where the SOP applies and, just as important, where it does not. "Applies to all purchased mechanical parts received at the Ugchelen site. Excludes packaging materials and consumables, which are covered by SOP-014." Clear exclusions prevent two SOPs from claiming the same activity.
4. Responsibilities
List roles and their duties: the warehouse operator performs the inspection, the quality inspector decides on deviations, the purchaser informs the supplier. Roles instead of names keep the SOP valid when people change jobs. In a digital SOP, roles map to user permissions: who may execute, who may analyse, who may edit.
5. Definitions
Only the terms that could be misread: "lot", "first article", "deviation". If the vocabulary is common in your company, skip the section rather than padding it.
6. Required resources
Everything the operator needs before starting: the drawing, calipers with a valid calibration, the inspection form or digital step, protective gloves. Listing resources up front prevents the most common interruption: starting the procedure and discovering halfway that a tool is missing.
7. Procedure
The heart of the document: numbered activities in the order they happen, each starting with a verb, with decision points ("If the quantity differs from the delivery note, go to 7.6") and acceptance criteria ("Release when all sampled parts are within tolerance"). Keep the activities at procedure level and refer to work instructions for the hands-on detail of individual steps, such as how to measure a specific dimension.
8. Records and references
State which records the procedure produces (inspection results, deviation reports, release stamps), where they are stored and how long they are kept. Add references to related SOPs, standards, drawings and forms. In a digital SOP the record is created automatically at each step: values, photos, signatures and timestamps land in the audit trail without extra work.
9. Revision history
Version, date, summary of the change and approver. This is what proves to an auditor that the procedure is maintained. With version control the history is complete by definition; on paper it depends on discipline.
Worked example: receiving inspection of purchased parts
A shortened example to show the level of detail. The full procedure would reference two work instructions (measuring with calipers, creating a deviation report).
| Title | SOP-021 Receiving inspection of purchased mechanical parts, v3, owner: Quality Manager, review: yearly |
|---|---|
| Purpose | Ensure that purchased parts meet the drawing before release to stock. |
| Scope | All mechanical parts received at the Ugchelen warehouse. Excludes packaging and consumables (SOP-014). |
| Responsibilities | Warehouse operator: identification, count, visual and dimensional check. Quality inspector: deviation decisions. Purchaser: supplier communication. |
| Resources | Delivery note, drawing (current revision), calibrated calipers, inspection step in the app, release labels. |
| Procedure | 7.1 Compare the delivery note with the purchase order; enter the quantity. 7.2 Check the packaging for damage; photograph any damage. 7.3 Select the sample size from the table in appendix A. 7.4 Measure the dimensions marked on the drawing (WI-021-1); enter each value. 7.5 If all values are within tolerance: apply the green release label and book the parts into stock. 7.6 If a value is out of tolerance: apply the red hold label, create a deviation report (WI-021-2) and notify the quality inspector. |
| Records | Inspection record per delivery (quantity, values, photos, operator, timestamp), kept 5 years. Deviation reports in the quality system. |
| References | ISO 9001 clause 8.4; SOP-014; WI-021-1; WI-021-2; drawing register. |
| Revision history | v3 (2026-08): sample table updated; v2 (2025-03): photo of packaging damage added; v1 (2024-01): first release. |
Common mistakes in SOPs
- Too long. If the procedure section exceeds three pages, the hands-on detail has crept in. Move it to work instructions.
- Names instead of roles. The SOP breaks the day someone leaves.
- No acceptance criteria. "Check the part" without a tolerance leaves the decision to the operator.
- Records that nobody keeps. If the procedure says a form is filled in but the form is not in the workflow, the record does not exist when the auditor asks.
- Revision history maintained by hand. It is the first thing to be forgotten and the first thing an auditor checks.
Checklist before approval
- Number, version, owner and review date are filled in.
- Purpose refers to a policy or requirement.
- Scope names the exclusions.
- Every responsibility is a role.
- Every activity starts with a verb and has one clear result.
- Every decision point has a criterion and a next step.
- Every record is named, with location and retention time.
- Referenced work instructions exist and are current.
- The procedure was walked through once by someone who did not write it.
From template to digital SOP
The same nine sections work as the structure of a digital procedure: the header becomes the workflow properties, the procedure section becomes the executable steps, and records are captured at the step where they arise. That removes the two weakest points of paper SOPs, outdated headers and missing records, and turns the procedure from a document into something operators actually use. See what an SOP is for the background and SOP software for how the Work Instruction App supports it.
