SOP Template: Free Standard Operating Procedure Format
November 11, 2026 · 13 min read
SOP Template: A Standard Operating Procedure Format You Can Copy
An SOP template gives every procedure in your team the same skeleton: a control block, purpose, scope, roles, numbered steps, records, revision history and sign-off. Below is a free standard operating procedure template in plain Markdown and a filled-in example. You also get a method for writing steps and a route into Word or Google Docs.
What Goes in a Standard Operating Procedure Template?
A standard operating procedure (SOP) is a written set of instructions for one routine task. Anyone trained on it does the task the same way every time. It names the task, who does it, when, with what, and what record it leaves behind. One SOP covers one task with a clear start and finish. A workflow that crosses several roles or teams calls for a process documentation template instead.
The US EPA's Guidance for Preparing Standard Operating Procedures (QA/G-6) splits SOPs into two kinds. Technical SOPs have a title page, table of contents, procedures, quality assurance/quality control and references. Administrative SOPs add a purpose section. Our template merges both into twelve sections, in this order:
- Document control block: SOP ID, revision, effective date, owner, review cycle.
- Purpose: why the task exists and what goes wrong without it.
- Scope: what it applies to, and the exclusions people ask about.
- Roles and responsibilities: who performs, who checks, who gets the escalation.
- Definitions: terms a new hire wouldn't know.
- Materials and equipment: tools, forms, systems and protective gear.
- Safety notes: hazards and controls, stated before the first step.
- Procedure: numbered steps, one action each.
- Quality checks and records: what gets verified and where the record lives.
- References: related SOPs, forms and regulations.
- Revision history: one row per change.
- Approval: who prepared it and who signed it off.
We left out G-6's table of contents on purpose. G-6 says one may be needed for quick reference, especially when the SOP is long, and a two-page procedure isn't.
The SOP Template in Markdown (Copy and Paste)
Copy this block into any Markdown file or into the editor. Replace every bracketed placeholder, and delete sections that genuinely don't apply rather than writing "N/A" under them.
# SOP-OPS-001: [Task name]
| Field | Value |
|---|---|
| SOP ID | SOP-OPS-001 |
| Revision | 1 |
| Effective date | YYYY-MM-DD |
| Owner | [Role, not a person] |
| Applies to | [Team, site or department] |
| Review cycle | Every 12 months |
| Next review | YYYY-MM-DD |
## Purpose
[One or two sentences: why this task exists and what goes wrong without it.]
## Scope
- Applies to: [who, where, which equipment or system]
- Does not apply to: [the exclusions people ask about]
## Roles and responsibilities
| Role | Responsibility |
|---|---|
| [Performer] | Carries out the steps and records the result |
| [Checker] | Reviews records and handles escalations |
## Definitions
- **[Term]:** [what it means in this SOP]
## Materials and equipment
- [Tool, form, system or protective gear]
## Safety notes
- [Hazard and the control that prevents it]
## Procedure
1. [Verb] [object] [detail].
2. [Verb] [object] [detail].
- If [condition], go to step 4.
3. [Verb] [object] [detail].
4. [Escalation or recovery step].
## Quality checks and records
- [What gets checked, by whom, how often]
- [Record name, where it's kept, for how long]
## References
- [Related SOPs, forms, regulations]
## Revision history
| Rev | Date | Author | Change |
|---|---|---|---|
| 1 | YYYY-MM-DD | [Name] | First issue |
## Approval
| Role | Name | Signature | Date |
|---|---|---|---|
| Prepared by | | | |
| Approved by | | | |
The Owner field holds a role, such as "Warehouse lead", because people leave and roles don't. The Applies to row stops a site-specific SOP from being read as company-wide policy. If you need other document types, such as a README or meeting notes, our Markdown templates post has ten more.
SOP Template Example: A Filled-In Walk-In Cooler Check
Here's the same template filled in for a short kitchen task. It's realistic on purpose: it has a decision step, a safety note and a record that someone initials.
# SOP-FS-004: Walk-In Cooler Temperature Check
| Field | Value |
|---|---|
| SOP ID | SOP-FS-004 |
| Revision | 2 |
| Effective date | 2026-11-11 |
| Owner | Kitchen manager |
| Applies to | Main kitchen, walk-in cooler 1 |
| Review cycle | Every 12 months |
| Next review | 2027-11-11 |
## Purpose
Catch a failing cooler before chilled food sits above a safe temperature for hours.
## Scope
- Applies to: opening and closing cooks on every shift
- Does not apply to: reach-in fridges (see SOP-FS-005)
## Roles and responsibilities
| Role | Responsibility |
|---|---|
| Opening or closing cook | Takes and logs the readings |
| Kitchen manager | Reviews the log daily and handles escalations |
## Definitions
- **Cold-holding limit:** the highest temperature the local food code allows for chilled food, printed at the top of the log sheet.
## Materials and equipment
- Calibrated probe thermometer
- Cooler temperature log (form FS-004-A)
## Safety notes
- Check that the interior door release works before entering the cooler.
## Procedure
1. Read the wall thermometer inside the cooler.
2. Probe one item on the middle shelf and read the probe.
3. Write both readings, the time and your initials in the log.
4. Compare the higher reading with the cold-holding limit.
- If it's at or below the limit, close the door and stop.
- If it's above the limit, go to step 5.
5. Move high-risk food to the backup reach-in.
6. Call the kitchen manager and note the call in the log.
## Quality checks and records
- The kitchen manager initials the log each day.
- Logs stay in the office binder for 90 days.
## Revision history
| Rev | Date | Author | Change |
|---|---|---|---|
| 1 | 2026-03-02 | J. Ortiz | First issue |
| 2 | 2026-11-11 | J. Ortiz | Added probe reading and escalation steps |
## Approval
| Role | Name | Signature | Date |
|---|---|---|---|
| Prepared by | J. Ortiz | J. Ortiz | 2026-11-11 |
| Approved by | M. Chen | M. Chen | 2026-11-11 |
Rendered, the control block, the roles section and the last two sections become tables, and the procedure becomes a numbered list with two indented bullets under step 4. We deliberately left the actual temperature out of the example. Food codes differ by jurisdiction and edition, so the SOP points to the limit printed on the log sheet instead.
Here's a cut-down version you can edit live. Change a step or add a revision row and the preview updates as you type.
The tables and numbered steps render in the preview. Exporting it as DOCX turns the same text into a Word file, which uses one of the 3 free server operations a day.
How Do You Write an SOP That People Actually Follow?
EPA QA/G-6 asks for SOPs written "in a concise, step-by-step, easy-to-read format," in active voice and present tense. It also says to imply "you" rather than write it, which imperative steps do naturally. In practice, that comes down to six habits:
- Pick one task with a clear trigger and a clear end. "Opening the store" is three SOPs. "Counting the till float" is one.
- Watch someone do it before you write. The person who does the job daily skips steps they no longer notice.
- Start every step with a verb, and give it one action. "Read", "Log", "Call". If a step has "and then" in it, split it.
- Put warnings before the step they protect. A caution after the step arrives too late.
- Make decision steps say where to go next. "If the reading is above the limit, go to step 5" beats "deal with any problems".
- Test it on someone new. Hand the draft to a recent hire and fix every spot where they pause or ask a question. G-6 calls it especially helpful when someone other than the writer tests the draft.
Here's the kind of weak step most first drafts contain:
5. The temperature should be checked and if there is a problem the manager needs to be informed and food should be moved.
And the rewrite:
4. Compare the higher reading with the cold-holding limit.
- If it's at or below the limit, close the door and stop.
- If it's above the limit, go to step 5.
5. Move high-risk food to the backup reach-in.
6. Call the kitchen manager.
The original hides three actions inside passive voice and never says what "a problem" means. The rewrite gives each action its own number and turns the vague condition into a test. For numbering and indented sub-steps, see our guide to Markdown lists.
Simple SOP Template or Detailed: Choosing a Format
SOPs come in four common shapes, and the task decides which one fits.
- Simple steps: a short numbered list of actions. Fits most office, retail and kitchen tasks.
- Hierarchical steps: numbered steps with lettered sub-steps. Fits longer technical work where each step needs detail.
- Checklist: a run sheet people tick off during the task. In Markdown that's a GFM task list, written as
- [ ] Probe reading taken. Our editor's preview shows those as disabled checkboxes. - Flowchart: for tasks with several branches. Our editor's preview renders Mermaid flowcharts in
mermaidcode fences live, so you can sketch the branches next to the steps.
A work instruction is narrower than an SOP. The SOP says what happens, who does it and when. A work instruction zooms into one step or one station and shows exactly how, often with photos. A checklist is a memory aid that sits inside an SOP, not a replacement for one.
We prefer the simple format with a full control block for most business SOPs. It fits on a page or two, and the control block still answers "which version was in force on 2 March?". Longer formats with a section for every possible topic are worth the weight only where a regulator or auditor asks for them.
Revision History and Approval: Keeping an SOP Under Control
The control block, revision history and approval table do one job: they let anyone prove which version of a procedure was in use on a given day. EPA G-6 recommends that each organisation set up its own numbering scheme. It also suggests a short title, ID, revision number, date and page count on every page after the title page.
A numbering scheme can stay simple. SOP-FS-004 reads as "standard operating procedure, food safety, number 4". Never reuse a retired number, or old records will point at the wrong document.
Every change gets a new revision number and a row in the revision history, even a one-word fix. Set the review cycle as a field rather than a habit. G-6 offers every 1 to 2 years only as an example, so pick an interval that matches how often the task drifts.
The approval table records who prepared the SOP and who signed it off. G-6 accepts electronic signatures for SOPs kept in a computerised database.
The limitation is simple: these are sections of the document, not features of any editor. Nothing in a Markdown file enforces a sign-off, blocks an unapproved edit or locks an old revision. Word's editing restrictions help a little, but they aren't document control. If you work under ISO 9001, GMP or a similar regime, keep the master copies in your document control system and use the Markdown version for drafting.
Is There an SOP Template in Word or Google Docs?
You don't need a gated download. Paste the template above into the editor, fill it in, then choose Export as DOCX from the Download/Export menu. You can also paste it into the Markdown to Word converter, which returns a document.docx file. Tables stay tables and numbered steps stay numbered. That's a free SOP template in Word without a sign-up form.
Both routes run on our server. Free users get a shared pool of 3 server operations a day, no account needed, and the editor toolbar exports documents up to 5,000 characters. Pro ($6 a month) removes the daily cap and the character limit. The filled-in cooler SOP above is well under 5,000 characters.
The export gives you a clean document, not a branded one. Add your logo, header, footer and page numbers in Word, and put the document control line in the header so it repeats on every page. For a long SOP, add a table of contents in Word at this stage too.
For Google Docs, upload the .docx to Google Drive and double-click it. Google's Work with Office files help page explains how Docs opens and edits Word files, and how to save one as a Google Docs file. For Pandoc and other conversion routes, see how to convert Markdown to Word.
SOP Questions: Reviews, Work Instructions and Formats
A good SOP template is short enough that people read it and strict enough that an auditor can trace every change. Copy the blank version, fill it in for one real task, test it on a new hire, then revise. When it's ready, paste it into the editor and export a Word file in a few clicks, no sign-up required.