Free template

SOP format: the standard structure, section by section

What belongs in a Standard Operating Procedure, what each section is actually for, and the mistakes that turn a tidy document into an audit finding. Free Word template included, no email required.

Free SOP template (Word)

ISO 9001 aligned, all eight sections, with guidance notes you delete as you fill it in.

Download .docx

On this page

  1. What an SOP is, and what it is not
  2. The standard SOP format
  3. What goes in each section
  4. A worked example
  5. Five mistakes that fail audits
  6. Document control and revisions
  7. Common questions

What an SOP is, and what it is not

A Standard Operating Procedure describes how a process is carried out so that it produces the same result regardless of who performs it. That is the whole purpose. Everything in the format below exists to serve it.

An SOP is not a policy. A policy states intent, an SOP states method. It is also not a work instruction, though the two get confused constantly. An SOP covers a whole process, including who is responsible and what records come out of it. A work instruction covers one task at one station in more detail, and a good SOP references work instructions rather than swallowing them.

The practical test: if a competent new hire could follow your document and produce the same output as your most experienced operator, it is doing its job. If they would still need someone standing next to them, it is a summary, not a procedure.

The standard SOP format

ISO 9001:2015 does not prescribe a layout. Clause 7.5 requires that documented information be identified, reviewed and approved, version controlled, and available where it is used. It says nothing about section headings. The structure below is not a requirement, it is simply the arrangement that satisfies those obligations with the least friction, and the one most auditors expect.

SectionWhat goes thereWhy it exists
Document controlNumber, revision, effective date, owner, approvalsProves the document is controlled and current
1. PurposeWhy the procedure exists and what it ensuresTells a reader whether they are in the right document
2. ScopeWhat and where it applies, and the exclusionsDecides whether a problem falls inside this procedure
3. ResponsibilitiesRoles mapped to dutiesMakes accountability explicit before something goes wrong
4. Materials and equipmentTools, gauges, forms, reference documentsSurfaces calibration and traceability requirements
5. ProcedureNumbered single-action steps with checksThe part that actually gets followed
6. Safety and PPEHazards and required controlsPuts the hazard where the task is, not in a separate binder
7. RecordsForms and records created or referencedConnects the procedure to its evidence
8. Revision historyWhat changed, when, approved by whomShows the document is maintained, not written once

Numbering the sections is worth doing even though nothing requires it. Numbered sections can be cited in a nonconformance, a training record or a corrective action, and "step 5.4 was not performed" is a far more useful finding than "the inspection was missed".

What goes in each section

Purpose

One or two sentences stating the outcome the procedure guarantees. Write the outcome, not the activity.

Compare

Weak: This procedure describes the final inspection process.

Better: Ensures every machined housing is verified against the released print and inspection criteria before it is packed for shipment.

The weak version tells the reader nothing they did not get from the title. The better version tells them what breaks if the procedure is skipped, which is the information that makes someone follow it.

Scope

State what the procedure applies to, where it applies, and what it explicitly excludes. The exclusions matter more than people expect. Scope is the section an auditor reads to decide whether a nonconformance falls inside this procedure or a different one, and a vague scope means every problem in the vicinity gets attributed to your document.

Responsibilities

Map roles to duties in a table. Roles, never named individuals. People move on and the document should not need revising because someone changed jobs. Each row should be a duty this procedure actually assigns, not a general job description.

Materials and equipment

List tools, fixtures, gauges, forms and reference documents. Where a gauge is involved, state the calibration requirement alongside it. Measurement traceability is one of the most common sources of audit findings, and the fix is almost always upstream: the SOP named "calipers" instead of naming a calibrated instrument with an identifiable status.

Procedure

This is the section that gets used, and the one most often written badly. Three rules carry most of the weight:

  1. One action per step. If a step contains the word "and", it is usually two steps. Combined steps are the ones that get half-completed.
  2. Start with a verb. "Measure the bore diameter at three positions" is an instruction. "The bore diameter should be measured" is a description, and descriptions get skimmed.
  3. Put acceptance criteria in the step. Not in an appendix, not in a separate specification nobody opens at the machine. If the tolerance is plus or minus 0.05 mm, it belongs in the step where someone reads the gauge.

Where a step is a check rather than an action, mark it and state three things: what is checked, what passes, and where the result is recorded. Then, immediately after, state what happens when it fails and who is notified. A procedure that only describes the happy path is the procedure that gets abandoned the first time something goes wrong.

Safety and PPE

Name the hazard, not just the equipment. "Wear gloves" is an instruction without a reason, and instructions without reasons erode. "Hot surfaces above 60 C: heat-resistant gloves required" survives, because the person reading it understands what the control is for.

Records

List every record the procedure creates or references, who creates it, and how long it is retained. Every record named here must exist as a real, findable form. This is one of the fastest ways to fail an audit: the SOP references a form that was never made, or was made once and lives on somebody's desktop.

Skip the blank template

Describe the process and get a complete SOP, purpose through records, ready to edit and export to Word or PDF. Free, no account needed.

Generate an SOP free

A worked example

An extract from a final inspection SOP, showing how the rules above look in practice.

SOP-014 Rev 2 · Final inspection of machined housings

1. Purpose. Ensures every machined housing is verified against the released print before packing, so that no unverified part reaches a customer.

2. Scope. Applies to all housings completing operation 40 at the Cell 3 inspection bench. Excludes prototype parts, which follow SOP-021, and in-process checks at operations 10 through 30.

5. Procedure.

5.1 Confirm the traveler revision matches the print revision on the released drawing. If they differ, stop and notify the supervisor.

5.2 Measure the bore diameter at three positions using a calibrated bore gauge.

5.3 VERIFY: all three readings fall within 25.00 mm plus or minus 0.05 mm. Record each reading on FORM-014.

5.4 If any reading is out of tolerance, quarantine the part on the red rack and raise a nonconformance report. Do not rework without supervisor authorization.

5.5 Sign and date FORM-014, then release the lot to packing.

Notice what step 5.3 does. It names the check, states the criteria in the step rather than pointing elsewhere, and says where the result goes. Step 5.4 covers the failure path, which is the step most procedures leave out.

Five mistakes that fail audits

  1. Referencing a record that does not exist. The SOP cites a form number, the auditor asks to see a completed one, and nobody can produce it. Create the form before you reference it.
  2. No approval evidence. An unapproved procedure is not a controlled document. The document control block needs a name and a date, and the approver should not be the author.
  3. Naming people instead of roles. The document goes stale the moment somebody changes jobs, and then it is out of date rather than merely inconvenient.
  4. An empty revision history. A document at revision 4 with no record of what changed between revisions raises the obvious question of whether the changes were reviewed at all.
  5. Steps that describe rather than instruct. "The operator should ensure that..." is not a step anyone can be found to have skipped, which makes it useless both for training and for corrective action.

Document control and revisions

Document control is what separates a procedure from a memo. The block at the top of the template carries a document number, a revision, an effective date, the process owner, the standard it aligns to, and both the preparer and the approver with dates.

Two conventions save trouble later. Put the document number and revision in the footer of every page, so a printed copy found on the floor can be checked against the current revision at a glance. And mark printed copies as uncontrolled, because the copy taped to a machine is the one that will still be at revision 1 two years from now.

When you revise, record what changed rather than that something changed. "Updated section 5" tells a future reader nothing. "Added bore diameter check at 5.3 following NCR-2291" tells them why the step exists, which is exactly what they need before deciding to remove it.

Download the template

All eight sections, document control block, revision history table. Word format, free, no email required.

Download .docx

Common questions

Does ISO 9001 require a specific SOP template?

No. ISO 9001:2015 requires documented information to be identified, reviewed, approved, version controlled and available where it is used. It does not prescribe sections or a layout. The format on this page satisfies those requirements without adding anything the standard does not ask for.

How long should an SOP be?

As long as the process and no longer. Most single-process SOPs run two to five pages. If yours is past about eight pages you are probably documenting several processes at once, and splitting it makes each one easier to revise and to train against.

What is the difference between an SOP and a work instruction?

An SOP describes a whole process, including responsibilities and resulting records. A work instruction covers a single task in more detail, usually for one role at one station. SOPs commonly reference work instructions rather than absorbing them.

Who should approve an SOP?

At minimum the process owner, who is accountable for the content, and one approver independent of the author, typically quality. Record both names and dates, because approval evidence is what an auditor checks first.

How often should an SOP be reviewed?

Set a review interval, commonly annually, but treat it as a floor rather than the trigger. The real triggers are a process change, a nonconformance that the procedure failed to prevent, and a corrective action that changes the method. A document only ever revised on its anniversary is usually a document nobody is using.

Back to Dropfeed