What the template covers
Seven sections, top to bottom: the same shape a controlled procedure has carried for decades. The How to use tab covers what an SOP is and is not, the document-control context, and the failure modes that show up in audit: auditor-facing prose, happy-path-only steps, responsibilities assigned to departments, 'general update' revision notes. The SOP Template tab is the skeleton. The Worked Example tab completes it as an equipment-cleaning SOP for a generic manufacturing line — seeing one filled in settles the level-of-detail question faster than any instruction could.
- Document header — title, ID, version, effective date, owner, prepared by, approver, supersedes
- Purpose and scope — including an explicit out-of-scope row, plus a safety-and-precautions row
- Definitions, abbreviations, and responsibilities by role (not department)
- Procedure table — one action per row, each with the role that performs it and the record it leaves
- References, a records-and-retention pointer, and a revision history that records what changed and why
An SOP is not a work instruction
An SOP describes a process at the level of who does what, when, and in what order. When a single task inside that process needs hands-on-the-equipment detail — which button, which setting, which direction — that detail belongs in a work instruction the SOP references, not in the SOP itself. Keeping the two levels separate is what keeps the SOP readable and the work instruction usable at the workstation.
The other discipline the template enforces is one process per SOP. If the scope sentence needs 'and' more than once, it is probably two procedures — and two procedures that share a document also share every future revision, review, and retraining decision.
Where this fits in document control
An SOP is a controlled document: it carries a unique ID and version, it is approved before use, the current version is the one available at the point of use, and superseded versions are withdrawn. Revisions go through change control — our change control form template covers that decision trail — and the revision history in this template records what changed and why, because that is the first thing reviewers and auditors read.
Quality system standards expect documented procedures — ISO 13485:2016 clause 4.2 (documentation requirements) covers the documents a quality management system must include and how they are controlled — but no standard mandates a specific SOP format. What they require is that procedures are documented, controlled, and available where the work is done. Adapt this structure to your own document control procedure and have QA approve the adapted version. An inspector starts at the header — current version, approver, match at the workstation — then picks a step and asks to see the record it leaves.
