Controlled SOP template: approval-tracked, version-controlled
A controlled SOP (standard operating procedure) template (purpose, scope, responsibilities, procedure steps, and references) with approval workflow, version control, and audit trail attached.
What the controlled SOP template: approval-tracked, version-controlled process is
An SOP in Word is not controlled. It exists in four versions on SharePoint, in an email thread, and in a printed binder by the machine, and none of them know the others exist. That's not a formatting problem, it's a control problem: without one authoritative place to pull the current version, you cannot document what an employee actually followed on the day a deviation occurred.
What makes an SOP controlled is four things: one current version, a documented approver, a versioned change history, and a set review interval. The template below keeps those four things attached to the content itself (purpose, scope, responsibilities, procedure steps, references and definitions) instead of leaving them in a separate document-control system nobody opens.
The other benefit of drawing the procedure instead of writing it in prose is that the branches become visible. An SOP in prose hides its exceptions in phrases like 'if the deviation is significant.' In a diagram, that becomes a decision with a named owner and two outcomes: something that can actually be trained on and audited against.
What this flowchart covers
In this template
- The header: document number, current version, owner, approver, effective date and the date of the next scheduled review
- Purpose and scope: what the procedure covers, which departments and locations it applies to, and what's explicitly out of scope
- Responsibilities and roles drawn as lanes, so every step has a named person or function rather than just a department
- The procedure itself, step by step, with the decisions and exceptions that a prose version usually buries in subordinate clauses
- Deviation handling: what the employee does when the procedure can't be followed, who gets notified, and how the deviation is documented
- References, definitions, related records, and a change history with a rationale for every revision
When to use this template
- You need to replace a Word-document SOP library where nobody can say for certain which version is current
- An auditor asked to see the current procedure and its approval, and you found three different versions
- You work in a regulated industry where the procedure needs to be retrievable exactly as it read on a specific date
- New employees are trained on a practice that's drifted from the written procedure, because the written one was never updated
- You need a fixed review interval and a way to see which SOPs are overdue
How it works
Set the header first
Document number, owner, approver and review interval need to live on the document itself.
Write the scope as a boundary
State both what the procedure covers and what it doesn't.
Draw the steps with their decisions
Replace 'if necessary' and 'as needed' with a decision node and a named owner.
Send it for approval, not for comments
Use the approval workflow so the version gets a signature and a timestamp.
Put the review on the calendar
State the interval on the document, and review the procedure when it lapses or when the process changes.
Frequently asked questions
What makes an SOP 'controlled'?
A controlled SOP has a single authoritative current version, a documented approver, a versioned change history, and a defined review cadence.
How is QueryChart's SOP different from a Word document?
Word documents drift between SharePoint, email, and printouts; there is no enforced approval gate or change diff. QueryChart's SOPs are versioned and approval-tracked by the platform itself.
What should an SOP contain?
A header, purpose, bounded scope, responsibilities, procedure steps with decisions, deviation handling, references and definitions, and a change history.
How often should an SOP be reviewed?
Most quality systems use a one-to-three-year interval, but the more important trigger is a process, system or requirements change.
How do I track the revision history of a controlled SOP?
This page is the SOP's own drafting and approval workflow. The dated log of what changed between versions is a separate artifact: see /templates/sop-revision-history-template.