To create an SOP, choose one repeatable task, note who does it and what triggers it, then walk through it once while capturing each step in order. Write each step as a short instruction, add screenshots where the screen matters, have someone who didn't write it follow it, fix what they stumble on, and set a review date.
A standard operating procedure is simply the agreed way to do one job, written down so the result doesn't depend on who's doing it. Writing one isn't hard. Getting people to use it, and keeping it true months later, is where the effort goes, so this walkthrough spends as much time on testing and upkeep as on the writing. If you're still choosing where your procedures will live, my guide to SOP software compares the platforms.
Writing it: the six-step method
1. Pick one task and name it after the outcome
Choose a task that's repeated, error-prone or about to be handed over to someone new. One task per SOP keeps it short enough to follow. Name it after what it achieves, such as 'Send a new client their welcome pack', so people can find it by the result they need rather than by the software involved.
2. Record the owner, the trigger and what done looks like
Three lines at the top: who owns the task, what starts it, and how you know it's finished. The owner matters twice over, because they're also the person who reviews the SOP later. Without a named owner, nobody notices when it goes out of date.
3. Do the task once while you capture it
Work through the task for real and capture every click and decision as you go. Capturing as you work records what happens, not what you remember. Scribe and Tango both do this: you start recording, do the work, and they turn it into a step-by-step guide with screenshots.
4. Turn the capture into short, numbered steps
Edit the capture so each step is one action, written in the active voice: 'Open the client folder', not 'The client folder should be opened'. Short active steps are easier to follow than paragraphs. Add a screenshot only where the screen matters, and mark up the part that counts. If you're working in a dedicated procedure platform, SweetProcess includes an image editor for exactly that.
5. Hand it to someone who didn't write it
Ask a colleague who's never done the task to follow the SOP exactly as written, and watch where they hesitate. Every pause is a gap. The writer can't see those gaps, because they fill them in from memory without noticing. Fix each one, and run the test again if the changes were big.
6. Publish it, give it an owner and set a review date
Put the SOP where the team already works, name the owner on it and add the date it should next be reviewed. An SOP nobody can find, or nobody trusts to be current, goes unused. Trainual sends recurring review reminders to owners, which takes the remembering off you.
What every finished SOP should contain
- A title that names the outcome
- The owner and the trigger
- What done looks like
- Numbered steps, one action each
- Screenshots where the screen matters
- The review date and a note of which version this is
If you'd rather not start from a blank page, there's a free SOP template on this site with these sections already laid out, so you can go straight to the capture.
Why written procedures drift, and how to stop it
Most SOPs fail after the writing, not during it. The clearest guidance on this comes from the US Environmental Protection Agency, whose guide to preparing standard operating procedures, known as QA/G-6, was written for quality systems in government work. It's not aimed at small businesses, but it's a useful model because it deals head-on with what happens after the first draft.
It says drafts should be tested by people other than the original writer before they're finalised. It says SOPs should be reviewed on a periodic basis, giving every one to two years as an example, and that the review date should be added to each SOP reviewed. And it makes the point that even well written SOPs fail if they're not followed, so management needs to reinforce their use and keep current copies where the work is done.
In practice that gives you three habits: a tester who isn't you, a review date printed on the document, and one current copy kept where the work happens, with old versions out of circulation. Version history helps with that last habit. SweetProcess keeps tracked changes and lets you roll back, and Trainual flags content that's gone stale.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
The EPA guide is US government guidance, and the rules for your own industry will vary, so check what your regulator expects if your SOPs form part of compliance.
Five SOP tools by the part of the job they cover
| Tool | What it does | The part it helps with |
|---|---|---|
| Scribe | Captures a process as you click through it and turns it into a step-by-step guide, with an Autocapture feature. | Capturing and drafting the steps |
| Tango | You start recording, do the work, and it produces a guide with screenshots, highlights and descriptions. | Capture across any web tool, so one method covers every system |
| Trainual | Holds SOPs as checklists, flowcharts, video and screen recordings. | Version history and reminders when content goes stale |
| SweetProcess | Documents processes, procedures and tasks in one place, with an image editor and process maps. | Version history that shows tracked changes and rolls back |
| Process Street | Document management and policy control plus workflow automation. | Pairing SOP documents with automated workflows |
Capture tools and SOP platforms do different jobs, and plenty of teams use one of each: a capture tool to draft, a platform to store, assign and review. If you'd like software to do more of the drafting, my comparison of AI SOP generators covers that side.
My advice: test it before you trust it
Write the first SOP for the task that hurts most when it goes wrong, keep it to one job, and don't call it finished until someone else has followed it without asking you a question. Then put a review date on it and keep to it. A short SOP that's tested and current beats a thick manual nobody opens, and no tool can do the testing for you.
Want your tool on this list? Featured spots and reviews here are paid partnerships. Here's how to partner with me.
Frequently asked questions
What should an SOP include?
A clear title, the owner, what triggers the task, numbered steps and what done looks like. The EPA guidance also advises a review date and document control notation.
How long should an SOP be?
As short as the task allows. The EPA guidance says to write concisely in a step-by-step, easy-to-read format, using the active voice, and one task per SOP keeps it short.
Can software write the SOP for me?
Capture tools such as Scribe and Tango record your clicks and produce a step-by-step guide with screenshots. You still need to check the steps and have someone test them.
How often should I update an SOP?
The EPA guidance gives every one to two years as an example of periodic review, and suggests adding the review date to the SOP. Review it sooner if the task or the software changes.
Who should test a new SOP?
Someone other than the writer, ideally a person who'll do the task for real, so the gaps the writer fills in from memory show up.
