Standard Operating Procedure Template (+ 3 Examples & Formats)

A blank page is the reason most SOPs never get written — and a good template is the cure. When you already know which sections to fill in and what “good” looks like, documenting a process stops being a project and becomes a 20-minute task. This page gives you a standard operating procedure template you can copy in three formats, the standard SOP structure laid out section by section, and three fully worked examples for real business functions — so you can stop staring at the cursor and ship your first SOP today.

Most results for “standard operating procedure template” either hide the template behind a download or show you a blank shell with no guidance. We have done the opposite: every template below is shown filled in, the standard SOP format is broken down field by field, and you get three SOP examples across admin, customer support, and marketing that you can adapt in minutes. This resource pairs with our deeper pillar on how to write SOPs — that one teaches the method; this one hands you the format and the fill-in-the-blanks. An SOP is just one format within the wider practice of process documentation, so if you are deciding which processes to capture and in what form, start there for the bigger picture.

Key takeaways

• A standard operating procedure template is a reusable, pre-structured document that prompts you for every section a good SOP needs — title, purpose, scope, roles, the steps, and revision history — so each procedure looks consistent and nothing gets forgotten.
• There is a widely-used standard SOP format: a header block, a purpose & scope statement, roles & responsibilities, the numbered procedure, references, and a revision/approval log. We give you that exact structure below.
• SOPs come in four common formats — step-by-step, hierarchical, flowchart, and checklist. Pick the format that matches how complex and how branching the task is.
• You get three copy-paste templates (basic step, hierarchical, flowchart) and three filled SOP examples for admin, customer support, and marketing.
• The best SOP is one written by the person who actually does the task — which is why a trained virtual assistant is often the ideal author and long-term maintainer of your SOP library.
• You do not need special software. A shared doc with the right headings beats an expensive tool nobody opens.

1. What Is a Standard Operating Procedure Template?

A standard operating procedure (SOP) template is a reusable document with the standard sections of an SOP already laid out — title, purpose, scope, roles, the step-by-step procedure, and revision history — so anyone can document a process by filling in the blanks. It keeps every SOP consistent in structure and ensures no critical field is forgotten.

The value of a template is not the formatting; it is the prompts. A blank document asks you nothing. A template asks “What triggers this task? Who owns it? What does done look like? Which tools are involved?” — and those questions are exactly what separate an SOP someone can follow from a vague set of notes only you understand. A standard operating procedure, as defined plainly, is simply the set of step-by-step instructions that document how a task is done; the template makes sure you capture all of it.

Templates also make SOPs scalable. Once every procedure shares a structure, a new team member learns to read any SOP in your library the same way, you can audit them at a glance, and updating them becomes mechanical rather than creative. That consistency is the whole point — and it is why we standardise on the format below.

2. The Standard SOP Format (Section by Section)

Across quality-management standards and government SOP guidance, the same sections appear again and again. The US Environmental Protection Agency’s Guidance for Preparing Standard Operating Procedures (QA/G-6) and ISO’s approach to documented information under ISO 9001 both converge on a common spine. Here is the standard SOP structure, what each section is for, and an example of what goes in it.

Section	What it is for	Example entry
Title & SOP ID	Names the task and gives it a unique reference so you can link and audit it	“SOP-014: Process a Customer Refund”
Document control	Version, author, owner, approval, effective date, next review	v1.2 · Author: J. Lee · Owner: Support Lead · Review: quarterly
Purpose	One or two sentences on why this SOP exists and the outcome it produces	“To issue accurate refunds within 24 hours and keep records audit-ready.”
Scope	When this SOP applies and when it does not; any boundaries	“Applies to refunds under $500 on standard orders. Disputes > $500 escalate.”
Roles & responsibilities	Who performs it, who approves, who is accountable for the outcome	Performed by: Support VA · Approves exceptions: Support Lead
Definitions / references	Terms, abbreviations, and links to related SOPs, policies, or tools	“RMA = Return Merchandise Authorization. See SOP-013 (Returns).”
Procedure (the steps)	The numbered, do-this-then-that core of the SOP	Steps 1–7 with screenshots and the exact button names
Revision history	A dated log of every change, so the SOP can evolve and stay trustworthy	“2026-03-01 v1.2 — added partial-refund path (J. Lee)”

You will not need every section for every SOP — a two-minute task does not need a definitions block — but starting from the full structure and deleting what you do not need is far safer than building up from nothing and forgetting the bits that matter. For a deeper breakdown of why each part exists, see the anatomy section in our guide to writing SOPs.

3. The 4 SOP Formats (and Which to Use)

“SOP format” means two things: the sections above (which stay constant) and the shape of the procedure itself (which changes with the task). There are four common ways to lay out the steps. Choosing the right one is the difference between an SOP people follow and one they ignore.

Format	What it looks like	Best for	Avoid when
Step-by-step	A simple numbered list, one action per line	Linear, repeatable tasks with one path (most admin and finance work)	The task branches a lot or has many sub-tasks
Hierarchical	Numbered steps with indented sub-steps (1, 1.1, 1.2…)	Detailed tasks where some steps need their own mini-instructions	The task is trivial — nesting just adds noise
Flowchart	A diagram of boxes and decision diamonds	Processes with branches — “if X do this, if Y do that”	The path is strictly linear with no decisions
Checklist	Tick-boxes for parallel items in no fixed order	Experienced staff who know how and just need to confirm what	Order matters or the task is new to the person

A quick rule: if a new hire could follow it in one straight line, use step-by-step. If steps need sub-steps, go hierarchical. If the work depends on decisions, draw a flowchart. If the person already knows the job and just needs to not miss anything, a checklist is enough. The three templates in the next section cover the first three formats; the worked examples after that show all of them in real use.

4. Three Copy-Paste SOP Templates

Here are three ready-to-use templates — one for each of the most common formats. Copy the structure into a shared doc (Google Docs, Notion, Confluence, or Word all work), replace the bracketed fields, and you have a working SOP. We have filled the first one in completely so you can see the difference between a blank shell and a real SOP.

Template A — Basic step-by-step SOP

The workhorse format. Use it for the majority of your SOPs.

Template B — Hierarchical SOP

Use when individual steps need their own sub-steps. Replace every bracket.

Template C — Flowchart SOP

Use when the process branches on decisions. Keep the header sections, then describe the flow as text (a developer or VA can turn it into a real diagram). Here it is filled in for an inbound-email triage.

That is the entire mechanism: pick the format, keep the standard sections, fill the blanks. Next, three complete examples so you can see what “good” looks like across very different kinds of work.

5. Three SOP Examples for Real Business Functions

Generic templates only get you halfway; seeing a finished SOP for a job like yours is what makes it click. Here are three filled examples — an admin task, a customer-support task, and a marketing task — each using the format that suits it best.

Example 1 — Admin: Weekly Calendar & Inbox Reset (checklist format)

An experienced assistant already knows how; they just need to confirm what. That is the textbook case for a checklist.

This is exactly the kind of recurring task a founder should hand off first. Our guide to delegating to a virtual assistant covers how to choose those first handoffs, and you can browse a fuller menu of them on our tasks to delegate page.

Example 2 — Customer Support: Process a Refund (step-by-step format)

A linear task where accuracy and an audit trail matter — so a numbered step-by-step format is ideal.

Example 3 — Marketing: Publish a Blog Post (hierarchical format)

A multi-stage task where several steps need their own sub-steps — the natural home for a hierarchical SOP.

Notice how each example pairs the task with the format that fits it. If your marketing process is more complex than a single post — a whole campaign, say — you are better off mapping it first; our business process mapping guide shows how a process map and an SOP work together.

6. How to Use and Customise an SOP Template in 6 Steps

A template is a starting point, not a finished SOP. Here is how to turn it into a procedure your team will actually follow.

1. Record yourself doing the task once. The fastest way to a first draft is to narrate a screen recording while you do the real work — then transcribe it into the template. Document the process as it is, not an idealised version.
2. Pick the format that fits. Linear → step-by-step. Steps with sub-steps → hierarchical. Decisions → flowchart. Confirmation only → checklist.
3. Fill the header and purpose first. A clear title, owner, and one-sentence purpose force you to define what “done” means before you write a single step.
4. Write the steps in plain language. One action per step, exact tool and button names, and a screenshot wherever a word would be ambiguous. Assume the reader is competent but new.
5. Add the boundaries. Scope (when it does and does not apply), exceptions, and who to escalate to. This is what stops an SOP being misapplied.
6. Test it with someone else. Hand the draft to a person who has never done the task and watch them follow it. Every place they hesitate is a gap to fix before you call it v1.0.

That “record it once” approach is the core of the method in our how-to-write-SOPs pillar — if you want the full writing method behind these templates, start there.

7. Tools and Where to Store Your SOPs

You do not need dedicated software to write good SOPs — you need one searchable home for them and a screen recorder. Here is the honest tooling landscape.

• Docs & wikis — Google Docs, Notion, Confluence, or Microsoft Word/SharePoint. Perfect for the templates above. A shared folder or wiki space with a consistent naming convention (SOP-### + task name) is enough for most small businesses.
• Screen recording — Loom, Tango, or Scribe capture the steps as you work and auto-generate first drafts. This is the single biggest time-saver for SOP creation.
• Dedicated SOP platforms — tools like Trainual, SweetProcess, or Process Street add version control, assignments, and read-receipts. Worth it once you have dozens of SOPs and a team to hold accountable; overkill before then.

Whatever you choose, the rule is the same: one source of truth, a consistent template, and a link to the SOP from wherever the work actually happens. An SOP nobody can find is an SOP nobody follows. SOPs are also the connective tissue of a wider business operating system — the documented layer that lets the rest of your systems run without you.

8. Common SOP Template Mistakes (and How to Fix Them)

Most failed SOPs fail for the same handful of reasons. Here they are, with the fix.

Mistake	Why it hurts	The fix
Writing the ideal process, not the real one	Nobody can follow steps that skip what actually happens	Record yourself doing the task live and transcribe that
Vague steps (“handle the request”)	Leaves judgement calls the reader cannot make	One concrete action per step; name the tool and the button
No owner or review date	The SOP goes stale and no one notices	Fill document control; set a quarterly review owner
Wrong format for the task	A checklist for a branching task loses people at the first decision	Match format to complexity (see the table above)
No “definition of done”	The task ends inconsistently and quality drifts	End every SOP with an explicit “done when…” line
Writing once and never updating	Reality changes; the SOP lies; people stop trusting it	Log every change in revision history; let it evolve

If you are still unsure whether you should be writing an SOP at all (versus a broader process map or a one-off note), our explainer on the difference between a process and an SOP clears that up.

9. How to Know Your SOP Is Actually Working

A template gives you a tidy document; the goal is a task that runs reliably without you. Judge your SOPs against outcomes, not appearance.

• Pass-the-stranger test — can someone who has never done the task complete it correctly using only the SOP? If not, it is not done.
• Bounce-back rate — how often the task still comes back to you with questions. Trending to zero means the SOP holds.
• Consistency — the output looks the same regardless of who performed it.
• Time-to-competence — how quickly a new person reaches reliable output on the task. Good SOPs shorten it sharply.
• Freshness — the last-reviewed date is current. An SOP older than its process is a liability, not an asset.

As a rough guide, a focused SOP for a single task usually runs one to two pages and takes well under an hour to draft from a screen recording — figures that are illustrative, since a 3-step inbox routine and a 20-step onboarding sequence are not the same animal. If an SOP is sprawling past several pages, it is probably two or three SOPs wearing a trench coat; split it.

10. Who Should Build and Maintain Your SOPs

The best SOP is written by the person who actually performs the task — they know the real steps, the edge cases, and where things go wrong. For a founder, that creates a tension: you do not want to document everything yourself, but you also do not want SOPs written by someone who has never done the work.

The resolution most growing businesses land on is to have a virtual assistant own the task and the documentation together. As a VA takes over your inbox, your refunds, or your publishing workflow, they write the SOP as they learn the job — turning a screen recording into a filled template — and then they become the long-term maintainer, updating the revision history each time the process changes. Your SOP library stops being a one-time heroic project and becomes a living asset that improves on its own.

This is also what makes delegation stick: a documented SOP is the handoff. It is the difference between “I’ll just do it myself because explaining is harder” and a process that genuinely leaves your plate. If you want to see how SOPs unlock delegation in practice, our guide on how to delegate to a virtual assistant connects the two directly.

Frequently Asked Questions

What is a standard operating procedure template?

A standard operating procedure template is a reusable document pre-structured with the standard sections of an SOP — title, document control, purpose, scope, roles, the numbered procedure, and revision history. You document any process by filling in the blanks, which keeps every SOP consistent and ensures nothing important is left out.

What should an SOP template include?

At minimum: a title and unique SOP ID, document control (version, owner, approval, review date), a purpose, a scope, roles and responsibilities, the step-by-step procedure with a clear “definition of done,” and a revision history. Add definitions and references when the task uses specialist terms or links to other SOPs.

What is the standard format of an SOP?

The standard SOP format is a header block (title, ID, version, owner, dates), followed by purpose and scope, roles and responsibilities, the numbered procedure, references, and a revision/approval log. This structure appears across quality standards like ISO 9001 and government SOP guidance, which is why it is the safest skeleton to start from.

What are the types or formats of SOPs?

There are four common SOP formats: step-by-step (a numbered list for linear tasks), hierarchical (numbered steps with sub-steps for detailed tasks), flowchart (a diagram for processes that branch on decisions), and checklist (tick-boxes for experienced staff confirming parallel items). Match the format to how complex and how branching the task is.

Can you give an example of an SOP?

Yes — a refund SOP is a clear example: title (“SOP-014: Process a Customer Refund”), purpose (issue accurate refunds within 24 hours), scope (refunds under $500), roles (performed by a support VA), then numbered steps from verifying the policy to logging the refund, ending with a “done when” line. This page includes three full examples for admin, support, and marketing.

How long should an SOP be?

A single-task SOP is usually one to two pages — long enough to be unambiguous, short enough that people read it. If an SOP runs to many pages, it is likely covering several tasks and should be split into separate, linked SOPs. The right length is “every step a stranger needs, and nothing more” (an illustrative rule, not a fixed limit).

Who should write and maintain SOPs?

The person who actually performs the task should write the SOP, because they know the real steps and edge cases. In practice, many businesses have a virtual assistant document a process as they take it over, then maintain it — updating the revision history whenever the process changes — so the SOP library stays current without the founder doing it.

Turn Your Know-How Into a Documented SOP Library

Templates solve the blank-page problem; they do not solve the time problem. The reason most SOP libraries stay half-built is that the founder who knows the processes is the one with no hours to write them down. That is exactly the work to delegate.

Catalyst Outsourcing pairs business owners with trained virtual assistants who can shadow your processes, record each one, fill these templates, and maintain your SOP library as it grows — usually starting within about two weeks. Explore our virtual assistant services, see the tasks you can hand off first, or book a free consultation to start turning what is in your head into a system your team can run. As ISO 9001 puts it in its own way: a business that documents how it works is a business that can improve how it works.