SOP Template KitSOP manual template: one controlled home for all your procedures
A single SOP tells people how to do one job. An SOP manual is the collection plus the rules around it: how procedures are numbered, who approves them, where the current version lives and when each one is reviewed. Download the Word template and use the guide below to fill it.
Download the SOP manual template (.docx) Get 36 SOPs to fill it ($79)
What is in the manual template
The file is organised in three parts. The front matter makes the manual controllable, the body holds the procedures, and the appendices hold what the procedures point to.
Front matter
- Cover page with manual version, effective date, owner and the location of the master copy, plus a line stating that printed copies are uncontrolled.
- Approval of the manual: who prepared and approved this edition.
- How to use this manual: a short paragraph, already written, telling staff to follow the current version only and to stop and ask when a step cannot be followed.
- Numbering and versioning rules (shown below).
- How procedures are written, approved and changed: the 7-stage lifecycle (shown below).
- Master index: one row per SOP with number, title, owner, version, effective date and next review date.
- Manual revision log and a distribution list saying which teams hold which format.
Body: one section per department
The template has a divider page and a contents table for each of these sections, matching the departments in the kit:
- Section A: Finance
- Section B: Procurement
- Section C: Human Resources
- Section D: IT & Security
- Section E: Sales & Customer
- Section F: Operations
Rename or remove sections to fit your organisation. A small business might need only three; a manufacturer might add Production, Maintenance and Quality.
Appendices
An index of forms and templates, showing which SOP uses each one, and a list of retired procedures so nobody revives an old version by accident.
Numbering and versioning rules
Decide these before you write the second SOP. Renumbering forty procedures later breaks every cross-reference between them.
| Element | Rule | Example |
|---|---|---|
| Department code | Two or three letters per section of the manual | FIN, PRO, HR, IT, SAL, OPS |
| Sequence number | Two digits, issued in order within the department and never reused | FIN-07 |
| Major version | Goes up when a step, role, threshold or control changes; staff are retrained | 2.0 |
| Minor version | Goes up for wording, formatting or contact changes that do not alter the work | 2.1 |
| Effective date | The day the version applies; never earlier than the approval date | 2026-11-01 |
| Review date | Twelve months after the effective date unless a trigger brings it forward | 2027-11-01 |
Never reuse a retired number. If FIN-07 is withdrawn, the next finance SOP is FIN-08, so an old reference to FIN-07 can never point at the wrong procedure.
Document control: the lifecycle of each procedure
A manual stays trustworthy only if every SOP in it goes through the same path from draft to retirement. The template writes this lifecycle into section 4:
| Stage | Who | What happens |
|---|---|---|
| Draft | SOP owner | Writes or changes the SOP in the standard format and records the reason for the change. |
| Review | People who do the work, plus one person from a neighbouring process | Walk through the steps against real work and comment within a set number of days. |
| Approve | Process owner's manager, and quality or compliance where the work is regulated | Signs the approval block; the version number and effective date are set. |
| Issue | Manual administrator | Publishes the new version, withdraws the old one and updates the master index. |
| Train | Line managers | Brief or train everyone affected before the effective date and keep the evidence. |
| Review | SOP owner | Re-reads the SOP by its review date, or sooner after an incident, audit finding or system change. |
| Retire | Manual administrator | Marks a withdrawn SOP as retired, keeps an archive copy and removes working copies. |
Bring a review forward whenever one of these happens: an incident or near miss involving the process, an audit finding, a new system or form, an organisational change that renames roles, or a change in the law. A calendar review every twelve months catches the rest.
Some industries set these rules for you. For example, FDA's drug manufacturing rule requires written production and process control procedures, and any changes to them, to be drafted, reviewed and approved by the appropriate organisational units and reviewed and approved by the quality control unit. If you work to ISO 9001, procedures count as documented information, which the standard covers under its support requirements; note that a new edition, ISO 9001:2026, was published in September 2026, so confirm which edition your certification body audits against.
Sources: 21 CFR 211.100(a) (eCFR) and ISO 9001 (iso.org), checked 1 October 2026.
Building the manual in six weeks
Most teams stall because they try to write every procedure at once. This order gets a usable manual in place quickly and fills it in by risk.
| Week | Do this | Output |
|---|---|---|
| 1 | List every recurring process by department. Mark the ones where a mistake costs money, safety or a customer. | Process list with a risk mark on each |
| 2 | Fill in the front matter: numbering rules, lifecycle, owner, master copy location. Assign an owner to each high-risk process. | Approved front matter and an owner list |
| 3 | Write the document control SOP first (the SOP for SOPs), then the two highest-risk procedures. | Three approved SOPs |
| 4–5 | Each owner drafts their high-risk SOP; reviewers walk the steps against real work. | High-risk procedures approved |
| 6 | Publish the manual in its master location, brief every team and set review dates in the master index. | Manual version 1.0 issued |
Lower-risk procedures can follow at a steady pace after version 1.0, each one adding a row to the master index and a line to the revision log.
Binder or online?
Keep one master copy, wherever it lives, and treat everything else as a convenience copy. An intranet page, a shared drive folder with restricted edit rights, or a document management system all work. Printed binders still make sense on a shop floor or in a laboratory where screens are impractical; stamp them as uncontrolled copies and replace the pages when a version changes. What fails is having two editable copies, because they drift apart within months.
Whatever you choose, the master index is the backbone. The kit includes it as an Excel register with owners, versions and review dates, which you can paste into section 5 of the manual or keep alongside it.
Filling the manual
- Write individual procedures with the free Word SOP templates or the online SOP builder.
- Plan the sections each procedure needs with the SOP outline.
- See finished procedures in the SOP template examples, and the opening steps of 36 more in the SOP library.
The body of the manual, already written
Questions
What is the difference between an SOP and an SOP manual?
An SOP describes one process. An SOP manual is the controlled collection of all of them, plus the rules for numbering, approving, issuing, reviewing and retiring each procedure, and a master index that lists them.
Who should own the SOP manual?
One named person, often in quality, operations or the finance controller's team, owns the manual as a whole: the numbering rules, the master index and the master copy. Each procedure inside it has its own owner, usually the manager of that process.
How often should an SOP manual be reviewed?
Review each procedure at least every twelve months, and sooner after an incident, an audit finding, a system change or a change in the law. Review the front matter of the manual whenever the organisation changes shape.
Can the manual be a folder of separate files instead of one document?
Yes, and for more than a handful of procedures it usually works better. Keep the front matter and master index as one document and each SOP as its own file, so a change to one procedure does not reissue the whole manual.