How to Write an SOP: A Simple 7-Step Guide
The process for creating standard operating procedures your team will actually follow, even if you have never written one. Capture it, write it, test it, done.
By David Jenyns, founder of SYSTEMology and systemHUB · Updated November 2026
How to write an SOP: the short answer
To write an SOP, pick one process, record it being done and turn the recording into numbered steps with a clear trigger and endpoint. Test it with someone who didn’t write it, then store it where your team can find it.
Writing comes fourth, not first.
The biggest mistake people make is starting with a blank document. They try to remember every step. The result is half wrong, twice as long as it needs to be and ignored by everyone.
This guide gives you the seven steps that work instead. It’s the same method we’ve used to help thousands of businesses create SOPs that actually get followed. (Not sure what an SOP is yet? Start with what an SOP is and the five essentials, then come back.)
The method at a glance
1. Record
Capture the work being done: a screen recording, a phone video or a voice memo.
2. Document
Turn the recording into short numbered steps with a trigger and an endpoint.
3. Test
Have someone who didn’t write it follow it. Fix every place they get stuck.
3 decisions before you write an SOP
Get these right and the writing almost takes care of itself.
Which process first?
Not all of them. One. Pick the process causing the most pain right now: the one that breaks when a key person is away or generates the same questions over and over. If everything hurts equally, start on the path your customer travels because that’s where inconsistency costs you money.
Who writes it?
Not the owner and not a committee. In SYSTEMology, creating systems is a two-person job. The knowledgeable worker (whoever does the task best) does it while a Systems Champion documents it. The worker then reviews the draft for accuracy. The owner hands over knowledge and sets priorities. (The full method is in the SYSTEMology book.)
How much detail?
Write for the newest person on your team, not the expert. Could a competent new hire follow this without asking questions and get the same result? That’s the level. Any more and it becomes a wall of text nobody reads. Any less and it’s a vague reminder rather than a procedure.
Why we don’t write from scratch: I stumbled onto this years ago while trying to systemise my digital agency. A mentor suggested hiring a consultant to document my processes. I hated the idea but the principle stuck: I didn’t have to be the one writing. So I started a podcast where I interviewed experts about how they did specific tasks and my team turned the interviews into SOPs. One person shares the knowledge and another documents it. That became the extraction method we use today.
How to write an SOP in 7 steps
Writing doesn’t show up until step 4. That’s deliberate. The best SOPs are captured from reality, not composed from memory.
- Pick one process and define its edgesPut a fence around it. Where exactly does it start and where does it end? “Sales” is not a process. “From a new enquiry arriving to a discovery call being booked” is. Small and specific beats big and vague.
- Record the process being doneDon’t write from memory. Capture from reality. Next time the task happens, record it: a screen recording for computer work, a phone video for physical work or a voice memo of the person talking through what they do. People who write from memory skip the steps they do on autopilot. Those are exactly the steps a new person needs. Recording takes 10 minutes instead of an afternoon because the person just does their job.
- Note the trigger and the endpointEvery SOP needs a clear start signal and a clear finish line. The trigger tells someone to begin (“a new enquiry lands in the inbox”). The endpoint tells them they’re done (“the discovery call is booked and confirmed”). Write these two lines first. They anchor everything in between.
- Turn the recording into numbered stepsNow you write. It’s more transcription than composition. Watch the recording and list the steps in order. One action per step, start each with a verb and use plain language. Ten to fifteen steps is typical. If you’re pushing past twenty you’ve probably fenced off two processes. Split them. Then send the draft to the person who does the task to check it’s accurate. Most people prefer editing something that exists to writing from scratch.
- Add the essentialsA verb-first title (“Process a customer refund”), the owner, links to any templates or tools and screenshots where a picture saves a paragraph. Our SOP essentials guide covers the five must-haves in detail.
- Test it with someone who didn’t write itHand the document to a team member who wasn’t involved and have them follow it literally, step by step. Every place they pause, ask a question or improvise is a gap in the document, not a gap in the person. One test pass catches most of the problems.
- Store it where the team will find itAn SOP saved to someone’s desktop doesn’t exist. Put it in one central home, give it an owner and set a review date (every 6 to 12 months or whenever the process changes). Then use it: link it in training, reference it when questions come up and update it when the process evolves.
Skip the blank page entirely
Grab 100+ free SOP templates covering sales, operations, finance, HR and more. Start from a proven structure and adapt it to your business.
Get the free SOP templatesThe SOP format that works
People overthink SOP format. You don’t need document control and three levels of appendices. For most small business procedures a simple structure is all it takes.
Trigger
What starts the process.
Steps
What to do, in order.
Endpoint
How you know it’s done.
The simple SOP format
- Title: verb first and specific (“Send the weekly newsletter”)
- Owner: the one person responsible for keeping it current
- Trigger: what starts the process
- Steps: numbered, one action each, plain language
- Endpoint: how you know it’s done
- Resources: links to templates, tools and related procedures
Three common formats
Simple list
Suits linear tasks, which is most of your procedures.
Hierarchical
Main steps with sub-steps. Suits complex tasks like end-of-month close.
Flowchart
Suits processes with decision points, like a refund path that depends on the amount.
When in doubt use the simple list. You can always upgrade later. A plain checklist that gets followed beats an elaborate flowchart that doesn’t. Already have an SOP in the wrong shape? Paste it into our free SOP formatter and get it back with clean structure and your wording untouched.
A worked example
Say only Sarah knows how to qualify inbound leads. When she’s sick, leads fall through the cracks. That’s a perfect first SOP. Sarah records herself handling a call and a Systems Champion writes up the steps. Sarah checks the draft and adds a missed detail. Then Tom, a new team member, follows it on his next call and flags one step that needs more detail. The SOP is updated. Done. Here’s how the finished SOP looks.
Respond to a new website enquiry
Owner: Sales lead
Trigger: A new enquiry notification arrives from the website form.
- Open the enquiry and log the contact in the CRM within 30 minutes
- Send the “thanks for reaching out” email template, personalised with one line about their enquiry
- Call the number provided (if during business hours)
- No answer? Send the follow-up SMS template and set a reminder to call again in 24 hours
- When you connect, use the discovery questions sheet and book the next call before hanging up
- Update the CRM record with notes and the booked call
Resources: email template, SMS template, discovery questions sheet.
Endpoint: Discovery call booked and confirmed. Otherwise the lead is marked unqualified with a reason.
Want more to model from? We’ve published 15 standard operating procedure examples across every department, each following this structure.
Use AI to draft your SOPs
That recording from step 2? Feed its transcript to an AI tool and ask it to draft the procedure in the format above. What used to take an afternoon now takes minutes.
The workflow: record the task, transcribe it, let AI produce the first draft and then run steps 6 and 7 as before. AI drafts and your team still tests, because the new-hire test is the one thing a machine can’t do for you.
No recording yet? Describe the process in a few sentences and the free AI SOP generator writes the first draft. Already have a recording? Process Pal turns the transcript into an SOP.
Watch: using AI to go faster (6 minutes).
This is the shift we cover in The Systems Champion: AI isn’t replacing the method. It’s collapsing the time it takes. The businesses winning right now pair the two-person extraction method with AI drafting.
Common mistakes when writing SOPs
Most SOP projects stall for the same few reasons.
Writing from memory
You’ll document the process as you think it happens, not as it happens. Record it being done and then write. This is the single biggest quality lever.
Chasing perfect
A rough SOP your team uses this week beats a polished one that ships next quarter. Simple beats perfect and you’ll improve it every time the process runs.
Documenting everything at once
The businesses that succeed document one process, get it used and move to the next. The ones that stall try to write 50 SOPs in a weekend.
The owner writing everything
If every SOP lives in your voice and your head you’ve built a more organised bottleneck. Hand the capture to the people who do the work.
Skipping the test
An SOP nobody has followed is a guess. The new-hire test is the only way to know it works.
No home, no owner, no review date
An SOP without these three things quietly dies. Give it a central home, a named owner and a review date. Every time.
What’s the chaos actually costing you?
Undocumented processes have a price: rework, repeated questions and mistakes. Put a number on it with the free Cost of Chaos calculator.
Run the numbersFrequently asked questions
What is the format of an SOP?
The simple format that works for most businesses: title, owner, trigger, numbered steps, endpoint and resources. Complex processes can use a hierarchical format (steps with sub-steps) or a flowchart when there are decision points. Start simple and upgrade only if the process demands it.
How do I write a simple SOP quickly?
Record the task being done (a screen recording or phone video), write down the steps as they actually happened, add the trigger and endpoint and have someone else follow it once. For most processes that's under an hour of total effort and 10 minutes of it is writing.
What are the essential parts of an SOP?
Five things: a clear verb-first title, the trigger that starts the process, numbered steps in plain language, an endpoint that defines done and an owner responsible for keeping it current. Links to the templates and tools used are a strong sixth.
How long should an SOP be?
As short as it can be while still passing the new-hire test. Most sit between half a page and two pages (10 to 15 numbered steps). If it's longer than that you're probably documenting two processes. Split them.
Who should write SOPs in a business?
It's a two-person job. The knowledgeable worker (whoever does the task best) performs it while it's captured. The Systems Champion turns the capture into a consistent document, which the worker then reviews for accuracy. The owner's role is to hand over knowledge and set priorities, not to write every procedure.
What software should I use to write SOPs?
Start with whatever your team will actually open. The tool matters less than the habit. That said, SOPs scattered across Google Docs get lost fast, which is why growing teams move to a dedicated home like systemHUB where procedures are organised, searchable and versioned.
What is the difference between an SOP and a checklist?
A checklist is a short list of critical steps to confirm or complete. An SOP is the fuller document with the trigger, the numbered steps, the endpoint and the context. Most businesses start with checklists and grow them into SOPs over time.
I'm brand new to this. Where do I start?
Start with one process and follow the 7 steps above. Free SOP templates help too, because adapting a template beats authoring from scratch.
Start with one
You now know how to write an SOP: pick one process, record it being done, capture the trigger and endpoint, turn the recording into numbered steps, test it and give it a home. Choose the one process that generates the most questions in your business and run it through the 7 steps this week. Don’t aim for perfect. Aim for done and in use.
One documented process this week becomes a habit. The habit becomes a library. And the library becomes a business that runs without you.
Keep reading
Or browse all guides and the free AI tools.
Give your SOPs a home your team will use
systemHUB gives you one place to find, follow and keep every SOP current.
14-day free trial. No credit card required.