Free standard operating procedure (SOP) template

How to fill it in

Start at the header and work down. Most fields are quick; the procedure section is where the real work is.

• Header: give the SOP a clear title, assign it an ID number from your own numbering scheme, set the revision to 1 for a first release, and set the effective date to the day it takes effect, not the day you wrote it.
• Purpose and scope: say in a sentence or two why the procedure exists, then draw the boundary. State what it covers, where it applies, and what it deliberately leaves to another procedure.
• Roles: write responsibilities around roles such as Operator, Reviewer, or Process Owner rather than a person's name, so the SOP does not go stale when someone changes jobs.
• Procedure: list the steps in order, one action per step, numbered. Use the active voice and present tense, and include the specific setting, value, or tolerance at each step rather than a vague instruction.
• Safety and records: put the hazards and required protective equipment ahead of the steps, and name the forms or logs the process produces so the evidence is not an afterthought.
• Sign-off: the author signs as the person who prepared it, and the approver signs as the manager or quality officer authorizing it for use. Leave the next-review date one to two years out.

How to write the procedure steps

The procedure section is what people actually use at the bench or on the floor, so write it for them. EPA's guidance is blunt about the style, and it is good advice: write in a concise, step-by-step, easy-to-read format, use the active voice and the present tense, and keep it simple and short. The term 'you' is implied, not written, so a step reads 'Record the temperature' rather than 'You should record the temperature.' Put one action in each step and number them, so a reader can stop, do the step, and find their place again. Where a step has a decision in it, write both branches: if the reading is within range, continue; if it is not, stop and notify the supervisor. Where a step has a value, give the value and its tolerance instead of a word like 'enough' or 'about.' A good test is to hand the draft to someone who has the basic background but has not done this exact task, and watch them run it unsupervised. EPA recommends exactly that, having someone other than the writer test a draft before it is finalized, because the writer always fills gaps in their head that a new reader cannot.

Document control: numbers, revisions, and effective dates

An SOP is only trustworthy if you can tell which version was in force at a given moment, and that is what document control does. Give every SOP an ID number from a scheme you keep consistent, and put a short control line on each page: a short title or ID, the revision number, the date, and 'Page x of y.' EPA puts this notation in the upper right corner of each page after the title page, and it is worth copying, because the revision number and date are what let you tie a historical record, a batch, or an inspection finding back to the exact procedure that applied. Keep a master list of every SOP, its current revision, effective date, owner, and status, so a reader can confirm they are holding the current version and not a printout from two revisions ago. When a revision replaces an older one, the old version should be pulled from circulation and archived, not left in a drawer where someone can follow it by mistake. Storing SOPs read-only in a shared system handles most of this for you, because no one can quietly edit the authorized copy.

How often to review and update an SOP

There are two triggers for changing an SOP, and you need both. The first is change: whenever the process itself changes, update the SOP and have it re-approved before the new way of working starts, not weeks after. The second is the calendar. EPA recommends reviewing every SOP on a periodic basis, roughly every one to two years, to confirm it still matches how the work is actually done, or to decide the procedure is no longer needed and retire it. Add the review date to the SOP each time you check it, even when nothing changes, so the next reader can see it was looked at and not simply forgotten. The most common failure here is quiet drift: the floor finds a better way, everyone adopts it, and the SOP still describes the old method for two years until an auditor notices the gap. Setting a review date and naming the person responsible for keeping SOPs current, usually the process owner or a quality manager, is what stops that.

SOP vs policy, work instruction, and the employee handbook

These terms get used loosely, so it helps to draw clean lines. A policy is a statement of what the organization requires and why, for example that all lab equipment must be calibrated before use. An SOP takes a task that policy implies and documents exactly how to do it: the steps to calibrate that specific instrument, in order. A work instruction, where organizations use the term, is even narrower, often a single-task job aid or a checklist that sits inside or beside an SOP. And the employee handbook is a different document entirely. The handbook is the organization-wide collection of conduct, benefits, and HR rules that applies to everyone; an SOP is one process, for the people who run that process. If you are writing down how the whole company behaves, that belongs in the handbook. If you are writing down how one recurring task is performed and who signs off on it, that is an SOP, and this is the template for it.

Where SOPs are required by law or standard

For a lot of organizations an SOP is just good practice. For regulated ones it is often mandatory, and the wording in the rules is specific. In pharmaceutical manufacturing, FDA's current good manufacturing practice regulation states at 21 CFR 211.100(a) that 'there shall be written procedures for production and process control' designed to assure the drug has the identity, strength, quality, and purity it is represented to have, and at 211.100(b) that those procedures 'shall be followed' and 'documented at the time of performance,' with any deviation recorded and justified. For medical devices, FDA's Quality Management System Regulation took effect on February 2, 2026, amending 21 CFR Part 820 to incorporate the international standard ISO 13485:2016 by reference. Under OSHA's process safety management standard, 29 CFR 1910.119(f), an employer handling highly hazardous chemicals must develop written operating procedures, keep them readily accessible to the employees who work the process, and 'certify annually that these operating procedures are current and accurate.' Quality systems built on ISO 9001:2015 take a lighter touch on format, folding the old 'documents' and 'records' into a single idea the standard calls documented information and leaving the extent of it to the organization, but the expectation that key processes are controlled and documented remains. Check the rule that applies to your field; this template gives you a structure that fits all of them, but it does not replace the specific requirements of your regulator.

Signing and approving an SOP

An SOP becomes official when it is reviewed and approved, and the signatures are how you prove that happened. In the usual flow the author, a subject-matter expert who actually does the work, prepares the draft, and an approver, typically the immediate supervisor or a quality officer, signs to authorize it for use. As EPA puts it, signature approval indicates the SOP has been both reviewed and approved by management. Electronic signatures are fine for this. EPA points to the Government Paperwork Elimination Act of 1998 as the basis for accepting electronic signatures and electronic records in place of paper where practical, and you can sign and store an SOP entirely online. One thing to keep straight: signing an SOP is an internal approval, not a contract. It does not create legal obligations between two parties the way a signed agreement does; it certifies that this is the authorized way to perform the task, as of the effective date, until the next revision replaces it.