SOP Templates: 12 Free Templates + How to Write One (2026)

TL;DR

• An SOP template is a reusable, pre-structured document you fill in to turn a repeatable process into a clear, step-by-step standard operating procedure.
• This post gives you 12 free SOP templates: 4 by format (step-by-step, hierarchical, checklist, flowchart) and 8 by function (onboarding, support, sales, IT, HR, finance, marketing, safety).
• A good SOP has the same bones every time: title, purpose, scope, roles, materials, numbered steps, and a version history.
• The fastest way to write one is to copy the template that matches your process, fill each field in plain language, then have one person actually run the steps before you publish.
• Written SOPs get skimmed and skipped. Pairing the doc with a short video of the process is the single biggest thing that lifts whether people follow it correctly.

Why most SOPs fail before anyone reads them

I’ve written and inherited a lot of SOPs. The ones that fail almost never fail because the process was wrong. They fail because the document was a wall of text nobody opened twice. A folder of dense procedures is not the same as a team that runs the process the same way every time.

A template fixes half of that problem. When every SOP looks the same, with the same headings, order, and fields, people know where to look, writers stop reinventing structure, and reviewers can spot what’s missing in seconds. Grab the right SOP template, fill it in, and you’ve skipped the hardest part of documentation: the blank page.

Below are 12 you can copy today, a plain-language guide to writing one, and an honest note on the format problem that no template alone solves.

What is an SOP template?

An SOP template is a pre-built document structure for writing a standard operating procedure, which is a documented, agreed-upon way to carry out a recurring task so it’s done the same way, every time. The template supplies the sections (purpose, scope, roles, steps, revision history) and you supply the specifics of your process.

Think of it as the difference between a form and an essay. Without a template, every SOP author decides from scratch what to include and in what order, and the results drift. With one, the structure is settled and the writer only has to answer questions. That consistency is exactly what auditors, new hires, and your future self are looking for. If you want the full breakdown of what an SOP is and where it fits alongside policies and work instructions, our companion guide on what a standard operating procedure is covers the definitions and components in depth.

What to include in an SOP (the standard format)

Regulators and quality frameworks are remarkably consistent on what belongs in a standard operating procedure. The EPA’s guidance for preparing SOPs and the ISO 9001 quality management standard both point to the same core: write in concise, active-voice steps, and make the document traceable and controlled.

Every template below is built from these fields:

• Title and SOP number: a unique, findable name (for example, SOP-114: Monthly Books Close).
• Purpose: one or two sentences on why this procedure exists and the outcome it guarantees.
• Scope: where it applies, and where it doesn’t (which team, site, or situation).
• Roles and responsibilities: who performs each step and who approves.
• Materials, tools, and access: systems, logins, equipment, or documents needed before you start.
• Procedure: the numbered, step-by-step instructions. The heart of the document.
• References: linked policies, related SOPs, or regulations.
• Revision history: version number, date, author, and what changed. This is what makes an SOP auditable.

Keep steps short and imperative. Write “Open the billing dashboard,” not “The billing dashboard should be opened.” One action per step. If a step has a decision (say, if the amount is over $5,000), break it out so nobody has to guess.

The 12 free SOP templates

The first four are format templates. Pick the shape that matches how complex your process is. The next eight are function-specific starting points you can adapt in minutes.

Templates by format

1. Step-by-step SOP template. The default. Best for linear processes with a clear start and finish.

SOP-[###]: [Process name]
Purpose: [Why this exists / the outcome it guarantees]
Scope: [Team / site / situation it applies to]
Owner: [Role]   Approver: [Role]   Last reviewed: [Date]
Tools & access needed: [Systems, logins, equipment]

Procedure:
1. [Action] > [expected result]
2. [Action] > [expected result]
3. [Action] > [expected result]
...

References: [Linked policies / related SOPs]
Revision history: v[#] | [Date] | [Author] | [What changed]

2. Hierarchical SOP template. For processes where steps have sub-steps. Best for detailed technical or regulated tasks.

1. [Major step]
   1.1 [Sub-step]
   1.2 [Sub-step]
2. [Major step]
   2.1 [Sub-step]
      2.1.1 [Note / exception]

3. Checklist SOP template. For recurring routines where “done or not done” matters more than narrative. Best for opening and closing routines, pre-flight, and QA checks.

[Process name] — [Frequency: daily / per shift / per release]
Performed by: ____   Date/time: ____

[ ] Step 1 — [action]
[ ] Step 2 — [action]
[ ] Step 3 — [action]
Verified by: ____   Signature: ____

4. Flowchart SOP template. For processes with branches and decisions. Best for approvals, escalations, and troubleshooting.

Start
  > [Step]
  > Decision? — Yes > [Step A] > End
              — No  > [Step B] > [Escalate to role] > End

Templates by function

Each uses the standard field set above. The notes below are what to prioritize for that team.

5. Employee onboarding SOP. Accounts to provision, day-one setup, training to assign, and the 30/60/90 check-ins. Owner: HR or the hiring manager. Pair it with your employee onboarding videos so new hires can watch each setup step, not just read it.

6. Customer support and ticket-handling SOP. Triage rules, response-time targets, escalation path, and canned-but-personal responses. Owner: Support lead. Keep the escalation branch as a flowchart.

7. Sales process SOP (lead to close). Qualification criteria, CRM hygiene, follow-up cadence, and handoff to onboarding. Owner: Sales ops. Define what “qualified” means so the stage means the same thing for everyone.

8. IT access and offboarding SOP. Provisioning on join, permission changes on role change, and full revocation on exit. Owner: IT and Security. This is a compliance favorite, so keep the revision history airtight.

9. HR recruiting SOP. Job-req approval, screening rubric, interview loop, and offer sign-off. Owner: Talent. Use a checklist for the interview loop so no candidate skips a stage.

10. Finance month-end close SOP. Reconciliations, accruals, approvals, and the reporting deadline. Owner: Accounting. Hierarchical format works best here because each close task has sub-steps.

11. Marketing content-publishing SOP. Brief, draft, review, SEO and QA, publish, and distribute. Owner: Content lead. A flowchart handles the “needs another review round?” branch cleanly.

12. Safety and compliance SOP. Hazard steps, required PPE, checkpoints, and sign-off. Owner: Ops or EHS. Follow the EPA and ISO structure closely, and consider compliance training videos so frontline staff can see the step at the moment they perform it.

How to choose the right SOP template

Match the template to the shape of the work, not the department. Use this quick guide:

Format	Best for	Example	Skip it when
Step-by-step	Linear tasks, one clear path	Publishing a blog post	Steps branch or nest
Hierarchical	Detailed, multi-layer tasks	Month-end financial close	The process is short and simple
Checklist	Repeated routines, pass or fail	Store opening procedure	Steps need explanation, not just a tick
Flowchart	Decisions and branches	Support ticket escalation	The path never varies

When in doubt, start with step-by-step. You can always promote a step to a sub-list or split a decision into a flowchart later.

How to write an SOP in 7 steps

A template gives you the skeleton. Here’s how to fill it so the SOP actually gets used.

1. Pick the process and the template. Choose one recurring task and the format that matches it. Don’t try to document your whole operation at once. Ship one good SOP.
2. Name the outcome and scope. Write the purpose and scope first. If you can’t say what “done correctly” looks like, you’re not ready to write the steps.
3. Do the task and capture each step. Actually perform the process and note every action as you go. This is where most SOPs go wrong, because they’re written from memory and skip the “obvious” steps that trip up new people.
4. Write steps in plain, active voice. One action per step. Start with a verb. Add the expected result so the reader knows they did it right.
5. Assign roles and add references. Say who does what and link the related policies or SOPs. Ambiguity about ownership is why steps get dropped.
6. Test it with someone who’s never done it. Hand the draft to a person outside the process and watch them follow it, silently. Every question they ask is a gap to fix.
7. Version it and set a review date. Fill in the revision history and schedule the next review. An SOP with no owner and no review date is a stale SOP waiting to happen.

The writing is the easy part. The test in step 6 is what separates an SOP people follow from a document that quietly rots in a shared drive.

SOPs the Velo way: when the doc isn’t enough

Here’s what most SOP guides skip. Even a perfectly formatted SOP is still a page of text, and people follow a procedure best when they can see the step and replay it at the moment they’re doing the task. That’s not a content problem. It’s a format problem.

This is the lane Velo’s SOP videos work in. Point it at the SOP you’ve already written, or record the process once, and it produces a clear, narrated, step-by-step video, with the written SOP kept in sync alongside it. Velo’s document-to-video turns your existing doc into a walkthrough, and its video-to-document keeps a clean written version updated automatically, so editing one updates both. When the process changes, you fix the script and every version regenerates, so your library doesn’t drift out of date.

Two more things matter for real teams. Velo narrates in your own cloned voice, so you’re not re-filming, and its multilingual output re-voices and captions each SOP in other languages for a distributed or frontline workforce. Teams that switched to producing SOPs and demos this way have reported real gains. import.io cut its video turnaround time by roughly 60% without adding headcount.

An honest note on scope: Velo isn’t an LMS and doesn’t grade quizzes, and it won’t write the procedure’s logic for you. You still own what the steps are. It makes the following of them far more reliable. If your SOPs live in training flows, our guide on creating employee training videos shows how the two fit together.

SOP template FAQ

What is an SOP template? An SOP template is a reusable document structure for writing a standard operating procedure. It provides the standard sections (purpose, scope, roles, step-by-step procedure, and revision history) so you only fill in the details of your specific process instead of designing the document from scratch.

What should an SOP include? At minimum: a title and SOP number, a purpose statement, the scope, roles and responsibilities, any required tools or access, the numbered procedure steps, references to related documents, and a revision history with version and date. Regulated environments may add QA and QC and approval sections.

What is the best format for an SOP? It depends on the process. Use step-by-step for linear tasks, hierarchical for detailed multi-layer tasks, a checklist for repeated pass-or-fail routines, and a flowchart when the process has decisions or branches. Most everyday SOPs work well as a simple step-by-step document.

How do I write an SOP quickly? Start from a template that matches your process, perform the task and capture each step as you go, write the steps in short active-voice sentences with the expected result, assign roles, then have someone who’s never done the task follow the draft and fix whatever they stumble on. Finish by adding a version number and review date.

Should I write SOPs in Word or Google Docs? Either works, because the format matters more than the tool. Word is common for regulated, version-controlled environments, and Google Docs is easier for collaborative editing and linking. Pick whichever your team already lives in, and keep one master list of all SOPs with their version numbers.

What’s the difference between an SOP and a work instruction? An SOP describes the overall standardized process and who’s responsible, while a work instruction zooms in on exactly how to perform a single task within it. A support SOP might define the ticket-handling process, and a work instruction shows precisely how to issue a refund in the billing tool.

Can I turn a written SOP into a video? Yes. Tools like Velo take an existing written SOP and generate a narrated, step-by-step video from it, keeping the written version in sync. This helps because people follow a visible, replayable step more reliably than a block of text.

Ready to make SOPs your team actually follows?

Templates get you a consistent, findable document. Start with the format that matches your process, fill in the standard fields, and test it on a real person before you publish. Then close the gap most SOP libraries never do: pair the doc with a short video so the step is easy to see and replay at the moment of the task.

That’s what Velo was built for, turning the SOPs you’ve already written into clear videos, kept in sync and in any language.

Try Velo for free or book a demo.