How to Write SOPs (Standard Operating Procedures): A Step-by-Step Guide

The work in your head is the work that can never leave your plate. Every recurring task you keep doing yourself — the one you “could explain faster than I could write it down” — is a task that traps you. How to write SOPs (standard operating procedures) is the skill that breaks that trap: it turns the know-how locked in your head into a document someone else can follow to the same standard, every time, without you watching over their shoulder.

This guide goes further than the usual list of steps. You will learn exactly what an SOP is (and how it differs from a process), when you actually need one, a step-by-step method to write SOPs people will actually use, a complete SOP template and a filled-in example, the four standard operating procedure formats and when to use each, the single biggest reason SOPs go stale — and the “self-evolving SOP” method that fixes it. It is built on the same framework we teach inside the Catalyst Infinity program, where the goal is never a prettier document; it is a task that finally belongs to someone else.

Key takeaways

• An SOP is the step-by-step “how-to” for executing one task to your quality standard; a process is the start-to-end map of a whole workflow. Write SOPs only for the steps you want to delegate — never one giant document for the entire process.
• A great SOP has eight parts: a “How to” title, objective, personnel (strategist / owner / manager), ingredients, a trigger, a video + written walkthrough, outputs, and an FAQ.
• The fastest way to write an SOP is to record yourself doing the task once on Loom, then have your assistant turn the transcript into a draft using an SOP template and an AI prompt — cutting your writing time to almost zero.
• The accuracy of the SOP your assistant produces is a free delegation-readiness test: an accurate draft means you can hand the task off; a vague one tells you to re-teach before you do.
• SOPs go stale because nobody owns updating them. In a self-evolving SOP, the person who runs the task owns its FAQ and updates the document every time something changes — so it always reflects the latest, most complete way to do the work.
• SOPs are what make real delegation possible: hyperlink one to each step of a process map and you go from owning every step to owning only the first.

1. What Is a Standard Operating Procedure (SOP)?

A standard operating procedure (SOP) is a documented set of step-by-step instructions for completing a specific, repeatable task to a defined quality standard, so that anyone following it produces the same result every time. A good SOP captures not just what to do, but the order, the tools required, the decisions involved, and what “done correctly” looks like — turning a skill in someone’s head into a repeatable system.

The point of writing one is not documentation for its own sake. It is to make a task transferable. As long as a task lives only in your head, you are the single point of failure for it — it cannot be delegated, audited, improved, or scaled. The moment it is a clear SOP, it can be handed to a team member, a specialist, or a virtual assistant, and it keeps running whether or not you are in the room. An SOP is one output of the broader practice of process documentation — capturing how work gets done so it lives in the business, not in your memory — which is why SOPs sit at the heart of any business that wants to grow without the founder working more hours.

Across most well-run organisations, SOPs deliver the same handful of benefits, which is why they are standard practice from clinical labs to call centres:

• Consistency — the task is done the same way every time, regardless of who does it.
• Faster onboarding — new hires and assistants ramp in days instead of months by following the document instead of shadowing you, which is why a strong SOP library is central to onboarding a virtual assistant well.
• Knowledge preservation — the know-how survives when a team member leaves; it lives in the SOP, not in their head.
• Quality & fewer errors — a clear sequence removes guesswork and the mistakes that come with it.
• Delegation & scale — you can finally take the work off your own plate.

2. Process vs. SOP: The Difference That Saves You a 47-Page Document

The most common SOP mistake is made before a single word is written: confusing a process with an SOP. Get this distinction right and everything downstream gets easier.

A process is the start-to-end map of a workflow and every step along the way. An SOP is the how-to for a single one of those steps. A process tells you what happens and in what order; an SOP tells you exactly how to execute one step so it meets your quality standard. They are different layers, and they answer different questions.

	Process	SOP
Scope	A whole workflow, start to end	One specific task or step
Answers	“What happens, and in what order?”	“How exactly do I do this step?”
Looks like	A map or flowchart with decision points	A step-by-step document or checklist
Example	Launching a VSL funnel (script → film → build → test → track)	“How to build the VSL funnel page”
You write one when	You need the whole team to see the workflow	You want to delegate that specific step

Why this matters: if you try to write a single SOP for an entire process, it becomes a 47-page book — and nobody reads a 47-page book. No assistant, specialist, or manager will ever master it, and you should not expect them to. Instead, map the process into steps, then write SOPs only for the steps you actually want to hand off.

Take a video sales letter (VSL) funnel launch. The process has five steps: script the VSL, film it, build the funnel, test and launch it, and set up tracking and reporting. You might keep the scripting and filming yourself because you are the face of the business — so you write no SOP for those. But you can write a tight SOP for “building the funnel” and another for “tracking funnel performance,” and delegate exactly those. Everyone sees the whole process; you only invest writing time where you want work to leave your plate. For a deeper treatment of this distinction, see our companion guide on the difference between a process and an SOP.

3. When Do You Actually Need an SOP?

Not every task deserves an SOP. Writing them is an investment, so spend it where it pays back. A task earns an SOP when it is recurring, important enough that doing it wrong is costly, and something you want someone other than yourself to own. If a task is one-off, trivial, or fully automated with no human in the loop, skip it.

A simple tie-breaker: two people doing the same task differently is an SOP problem. If inconsistency in a task is costing you — rework, client complaints, errors, or your time spent fixing other people’s output — that task is shouting for an SOP. Practical triggers that mean “write one now”:

• You explain the same task to someone more than twice.
• The task is recurring and you want to delegate it (inbox triage, invoicing, content scheduling, client onboarding).
• Getting it wrong is expensive — a botched onboarding, a missed compliance step, a broken funnel.
• It is a step inside a process you are mapping for handoff.

If you are still deciding which tasks to offload first, our delegation matrix guide helps you sort tasks by value and energy so you document the right ones in the right order.

4. The Anatomy of an SOP That Is Impossible to Misunderstand

Most SOP templates online give you a header, a purpose line, and a numbered list. That is enough to look like an SOP, but not enough to delegate one. A document built for handoff needs eight parts. Miss any of them and the task tends to bounce back to you. If you would rather start from a ready-made structure, our standard operating procedure template gives you the standard format plus filled examples to copy.

1. “How to” title. Every SOP name begins with “How to…” — “How to clone and customise a lead-magnet funnel,” “How to edit a short-form video.” It forces the document to describe one clear task.
2. Objective. A line or two on why this task exists. Without it, people go through the motions without understanding the outcome they are serving — and that is exactly when judgement calls go wrong.
3. Personnel. Name three roles (covered in detail below): the strategist who designed the task, the owner who executes and updates it, and the manager who checks it is done accurately and consistently.
4. Ingredients. List everything needed to run the task without getting stuck — account access, the raw-footage folder, the software login, naming conventions, the relevant copy. Missing ingredients are the number-one reason a task bounces back with “I couldn’t finish this.”
5. Trigger. When the SOP runs. For a recurring responsibility, the trigger is a cadence (“start of day,” “every Tuesday”). For a task inside a process, the trigger is the preceding step (“when step 2 of the onboarding process is complete”), so steps hand off cleanly.
6. Walkthrough — video and written. Include both. The video shows nuance words miss; the written steps let someone jump straight to step 6 without re-watching ten minutes of footage. This pairing is what most templates get wrong by offering one or the other.
7. Outputs & results. What the finished work should look like — the deliverable, the format, the standard. This is how the owner self-checks and how the manager reviews.
8. FAQ. The living section. Every time the owner hits a question or makes a mistake that gets corrected, the answer is logged here. This is what turns a static document into a self-evolving SOP (Section 7).

The three roles every SOP should name: strategist, owner, manager

Most SOP templates list a single “author” or “owner.” That is not enough for delegation, because three distinct jobs are involved in any task — and confusing them is how work quietly drifts back to you.

• Strategist — the person who designed how the task should be done (often you, the founder, at first).
• Owner — the person who actually executes the task and keeps the SOP up to date.
• Manager — the person who checks the task is done accurately, consistently, and on time.

The trap is making yourself the manager forever. If you are still the one checking that the task happened at the right time and to the right standard, you have not really delegated — you have just added a task. In a well-run handoff, your assistant is both owner and manager, holding themselves accountable through a workflow checklist rather than waiting for you to chase. As your team grows, those roles split out: an associate becomes the owner, and a department lead becomes the manager. Naming the three roles on the SOP makes the accountability explicit from day one. This is the same principle behind our guide to managing a virtual assistant without micromanaging.

5. How to Write an SOP in 6 Steps (the Record-It-Once Method)

Here is the part that trips most founders up: they sit down to write an SOP from a blank page, find it agonisingly slow, and quit halfway. The fix is to never write from scratch. You already know the task — so capture yourself doing it, and let a draft fall out of that. This method cuts your writing time to almost nothing.

1. Pick one task you want off your plate. Start with a recurring, high-cost, low-judgement task — the kind that drains hours but is easy to hand off. Resist the urge to begin with your scariest, most complex process.
2. Record yourself doing it once, narrating as you go. The next time the task comes up, hit record in Loom (or any screen recorder) and talk through every click and decision while you work. You were going to do the task anyway — now you are documenting it for free. As an alternative, invite your assistant to shadow you on a Zoom call and ask questions live while you work.
3. Grab the transcript and draft from a template. Pull the auto-generated transcript from the recording and feed it, plus your SOP template, into an AI assistant such as ChatGPT or Claude. It restructures your spoken walkthrough into the eight-part format in seconds. (The exact prompt is in Section 6.)
4. Review the draft for accuracy — and read it as a test. Never publish the AI output verbatim. Check it against the task as you actually do it: are any steps or ingredients missing? Crucially, if your assistant produced this draft, its accuracy tells you how well they understand the task — a precise draft means you can delegate with confidence; a vague one means re-teach first.
5. Fill the gaps and add outputs. Add the ingredients the transcript skipped (it always misses a few), specify the trigger, and spell out what “done correctly” looks like. Paste the finished version into a clean copy of your SOP template.
6. Hand it off, then let the FAQ grow. Delegate the task to its owner with the SOP attached. From here on, every question they raise and every mistake you correct gets logged in the FAQ — so the document keeps improving without you rewriting it.

This works for two reasons. First, recording costs you no extra time because you were doing the task regardless. Second, a consistent template plus AI means your assistant can produce a comprehensive first draft without you writing a word — and the review step doubles as a check on whether they are ready to own the work. Independent operators have popularised similar “record → transcribe → AI → SOP” workflows; what we add is the template structure, the personnel roles, the accuracy-as-delegation-test, and the self-evolving FAQ that keeps it alive.

6. The AI Prompt That Turns a Loom Transcript Into a Draft SOP

Once you have a transcript and a template, this is the prompt we hand assistants to generate a first draft. Attach your SOP template file to the chat, then paste this in with your transcript:

Role: You are a world-class operator with years of experience building SOPs and processes for companies.

Objective: Help me create a written SOP that is impossible to misunderstand.

Structure & rules: Follow the structure of the attached document (the SOP template). The SOP title must start with “How to.” Use clear, numbered steps and call out every required ingredient (access, files, tools).

Source: Below is a transcription of me walking through the task. Restructure it into the SOP format. [paste transcript]

A few rules keep the output trustworthy. Always attach the template so the format is consistent. Never let your assistant paste the result in verbatim — the AI reliably misses a couple of ingredients (the copy file, the raw asset folder) and the occasional judgement step, and those gaps are exactly what cause a handoff to fail. Treat the AI as a fast first-drafter and your review as the quality gate. For more on equipping your assistant to work this way, see our guide on how to delegate to a virtual assistant.

7. The Self-Evolving SOP: How to Keep SOPs From Going Stale

Here is the failure mode that quietly kills most SOP libraries: they are written once, saved in a folder, and never touched again. Within months the tools have changed, a step has been added, and the document is wrong — so people stop trusting it and go back to asking you. The cause is almost always the same: nobody owns updating the SOP.

The fix is structural, not heroic. In a self-evolving SOP, the person who runs the task owns the document — and updates it every time they run it and something changes. The mechanism is the FAQ section. Whenever the owner hits a question, makes a mistake that gets corrected, or finds a better way, that learning gets logged straight into the SOP. The document is never “finished”; it gets a little more complete every cycle, and it always reflects the latest, most comprehensive way to do the task.

The rule that keeps SOPs alive: if you change how a task is done, the SOP is updated before the change goes live — and the person who owns the work is the person who owns the update. A procedure with no owner is a procedure no one maintains.

This is also why the FAQ is so valuable: it is where your hardest-won, most specific knowledge accumulates — the edge cases, the “what do I do when…” answers that a template never anticipates. Beyond the running owner, most operators recommend a light review cadence as a safety net: review high-frequency or high-risk SOPs roughly quarterly and everything else every six to twelve months, and trigger an immediate review whenever a tool, system, or policy in the SOP changes, regardless of the schedule (see practical guidance from BOC Group on keeping SOPs up to date). But the heavy lifting is done by the owner updating in the flow of work — not by a calendar reminder nobody honours.

8. The 4 Standard Operating Procedure Formats (and When to Use Each)

“SOP format” refers to how you structure the instructions on the page. The right format depends on the task — matching them well is part of what makes an SOP easy to follow.

Format	Best for	Example task
Checklist	Tasks where order does not matter and you just need every item done	Pre-publish blog checklist; end-of-day close
Step-by-step	Linear tasks that must be done in a precise order	Issuing an invoice; editing a short-form video
Hierarchical	Complex tasks with sub-steps or multiple sections	Client onboarding with several stages
Flowchart	Tasks with decision points and branching paths	Support-ticket triage; escalation rules

Two notes. First, most delegated tasks are well served by a step-by-step or checklist format — reserve flowcharts for genuinely branching work. Second, format and medium are different choices: any of these can be paired with a video walkthrough, which is why our eight-part anatomy includes both a video and a written version regardless of format. When a task has real decision points, that is your signal you are dealing with a process, not a single step — which is where process mapping comes in.

9. From SOPs to Process Maps: How SOPs Enable Delegation

SOPs come into their full power when you connect them to a process map. A process map has four building blocks: a start point, an end point, the steps in between, and decision points that tell people what to do when conditions vary (“Is this client ICP 1 or ICP 2?”, “Do they already use Slack?”). The map is the single source of truth so that everyone on the team shares one picture of how work moves from A to B — instead of each person carrying a different mental model, which is how operations descend into chaos.

The magic move is this: once the map exists, hyperlink the SOP for each step into the map. Now the step is not just named — it is fully documented and owned. Do that across a process and you go from being the person in charge of every step to the person in charge of only the first. The support work is delegated; you keep only the high-level thinking. This is exactly how delegation scales: not by handing off one task at a time forever, but by documenting a whole workflow into transferable steps — the core habit behind delegating effectively as a business owner. Our business process mapping guide walks through building one, and the business operating system guide shows how processes and SOPs fit into the wider system that runs your company.

Like SOPs, process maps are never perfect on the first draft — they evolve as you run them with real clients and team members. The point is to start: draft the first version, run it, and refine. A map that exists and is improving beats a perfect one that never gets made.

10. A Complete SOP Template (Copy This)

You do not need special software — a document or a wiki page works. Use these sections, in this order, for every SOP:

Section	What goes in it
Title	Starts with “How to…” — one specific task
Objective	Why this task exists; the outcome it serves (1–2 lines)
Personnel	Strategist / Owner / Manager — named people or roles
Ingredients	Every account, file, tool, login, and naming convention needed
Trigger	A cadence (e.g. “every Tuesday”) or a preceding process step
Video walkthrough	Link to the Loom/Zoom recording
Written walkthrough	Numbered steps; note decision points and judgement calls
Outputs & results	What “done correctly” looks like; the deliverable and standard
FAQ	Owner-maintained log of questions, mistakes, fixes, edge cases

A filled-in example: “How to clone and customise a lead-magnet funnel”

Competitors hand you a blank template; here is what a real, populated SOP looks like, distilled to its essentials:

Section	Example content
Title	How to clone and customise a lead-magnet funnel
Objective	Stand up a new lead-magnet landing page and opt-in form quickly and on-brand, so the founder no longer customises every funnel by hand.
Personnel	Strategist: Founder · Owner: Marketing VA · Manager: Marketing VA (via workflow checklist)
Ingredients	Funnel-builder login; form-builder & automation access; design tool (e.g. Canva); the lead-magnet raw file; the page copy/text; thumbnail and naming convention
Trigger	Recurring — whenever a new lead magnet is approved for launch
Walkthrough	Video: 18-min Loom. Written: 1) Clone the template funnel → 2) Rename per convention → 3) Swap copy & images → 4) Connect the opt-in form to the automation → 5) Test the opt-in end to end → 6) Publish
Outputs	A live, on-brand funnel with a working opt-in that delivers the lead magnet automatically
FAQ	“Form not delivering the PDF?” → check the automation trigger is published, not just saved. (Logged by the owner after it happened once.)

Notice the FAQ entry: it was not in the original draft. It was added by the owner the first time the form silently failed — which is precisely how a self-evolving SOP gets smarter than the person who wrote it. As your library grows, store SOPs in one central, searchable place and link each into its parent process map. To prepare a task for handoff cleanly, our notes on securely sharing passwords and account access cover the “ingredients” side safely.

11. Six SOP Mistakes to Avoid

1. Writing one giant SOP for a whole process. You produce a 47-page document nobody reads. Map the process, then write SOPs only for the steps you delegate.
2. Skipping the ingredients. A perfect step list is useless if the owner lacks access to the file or tool. Missing ingredients are the top reason tasks bounce back.
3. Documenting a task only in your head. You cannot hand off what you have not recorded. Record a Loom the next time you do it — the document writes itself.
4. Publishing AI output verbatim. The draft is a starting point. Always review for missing steps and ingredients before you delegate; the review is also your read on whether the owner is ready.
5. Owning the “manager” role forever. If you are still chasing whether the task got done, you have not delegated. Hand the owner a workflow checklist and let them hold themselves accountable.
6. Treating the SOP as finished. An SOP that never updates rots. Make the owner responsible for the FAQ and update before any change goes live.

Frequently Asked Questions

What is an SOP?

An SOP (standard operating procedure) is a documented, step-by-step set of instructions for completing a specific recurring task to a defined quality standard, so anyone who follows it gets the same result every time. Its real purpose is to make a task transferable, so it can be delegated instead of living only in your head.

How do you write an SOP?

Pick one recurring task, record yourself doing it once on a screen recorder while narrating, then turn the transcript into a draft using an SOP template and an AI assistant. Review the draft for missing steps and ingredients, specify the trigger and outputs, hand it to an owner, and let the FAQ section grow as questions and fixes come up.

What is the difference between a process and an SOP?

A process is the start-to-end map of a whole workflow and all its steps; an SOP is the how-to for executing one of those steps to standard. The process answers “what happens and in what order,” while the SOP answers “how do I do this specific step.” Write SOPs only for the steps you want to delegate, not the entire process.

What should an SOP include?

A delegation-ready SOP has eight parts: a “How to” title, an objective, personnel (strategist, owner, manager), ingredients (every access, file and tool), a trigger, a walkthrough in both video and written form, outputs, and an FAQ that the owner keeps updated. The ingredients and FAQ are the parts most templates miss.

What are the formats of an SOP?

The four common SOP formats are checklist (order does not matter), step-by-step (precise order), hierarchical (complex tasks with sub-steps), and flowchart (tasks with decision points). Most delegated tasks suit a step-by-step or checklist format, and any format can be paired with a video walkthrough.

How often should you update SOPs?

Update an SOP immediately whenever a tool, system, or step it covers changes — before the change goes live — with the person who owns the task owning the update. As a safety net, review high-frequency or high-risk SOPs roughly quarterly and everything else every six to twelve months.

How do SOPs help with delegation?

An SOP converts a task that only you can do into one anyone can follow, which is the precondition for delegating it. Hyperlink an SOP to each step of a process map and you move from owning every step to owning only the first — handing off the support work while keeping the high-level thinking.

Turn Your Know-How Into a Team That Runs Without You

Writing the SOP is only half the job. The payoff comes when the task actually leaves your plate and someone else owns it — records the walkthrough, drafts the document, runs the work, and keeps the FAQ alive. That is the difference between a folder of nice documents and a business that runs without you in the room.

Catalyst Outsourcing helps Singapore business owners get there: trained, AI-fluent virtual assistants who can turn your recordings into SOPs and own the work, matched in about two weeks with onboarding support so the handoff sticks. Explore our virtual assistant services, see what a VA costs, or book a free consultation to start building your delegation system. The best operators are not the ones who do the most — as Harvard Business Review notes, they are the ones who hand off the best.