How to Write an SOP Your Team Will Actually Follow
You stepped away for two days.
You came back to four messages asking where the client folder is, a proposal sent without your approval, and an invoice with the wrong bank details.
This is not a team problem. It is a documentation problem.
Most SOPs fail before anyone reads them. Here is what actually makes a process stick, and how to write one in under an hour.
You wrote that SOP for yourself
That is the most common reason nobody else follows it.
There are two completely different documents that founders call an SOP. The first is a knowledge-preservation document: every exception, every nuance, every thing learned over years of doing the job. Written in the way a founder thinks, structured around how they would explain it to someone who already understands the context. The second is an operating document: one path through one process, written for someone doing it for the first time, under pressure, without the chance to ask a question.
These are not different versions of the same thing. They are different documents with entirely different jobs. Most founders write the first one. Most teams need the second one.
Every step in an operational SOP is a decision you are making now so your team does not have to make it later. That shift — from recording knowledge to pre-empting decisions — changes everything about how you write it. The measure of a usable SOP is not whether it is thorough. It is whether a capable person can follow it when you are not available.
A useful SOP answers one question: what should a person do next, when they cannot ask you? Everything beyond that standard is overhead.
Start with the processes that cost the most
Not every process deserves to be documented first.
Documenting everything at once is the most common reason founders write one SOP and never write another. The effort is too high, the return feels distant, and the business does not slow down while you write. A more precise approach is to identify the three processes where a mistake or missed step produces the highest cost: in lost time, client trust, or cash.
For most service businesses, those three areas are client facing communications, invoicing and payment, and new client onboarding. Together they determine how the client experiences the business, whether cash arrives on time, and whether new work starts without the founder's intervention. At a conservative EUR 120 per hour for a founder's time, five unnecessary interruptions per week — questions an SOP should have answered — cost roughly EUR 3,000 per month in distracted founder capacity. That is the actual price of not writing the document.
A four person brand consultancy in Utrecht billing EUR 18,000 per month had no documented onboarding process. Every new project started differently depending on which team member took the first call. In one quarter, two of three kick-off engagements required the founder to step back in after the first week because key information had not been collected upfront. After one eight-step onboarding SOP was written and tested twice, both problems stopped. The founder recovered an estimated three hours per client engagement. Across six clients in the following quarter, that was 18 hours she no longer spent correcting the first week of a new relationship. (Composite, not a real client.)
Getting all three areas documented is a two-week project. Start with the one that would hurt the most if it went wrong this week.
The format that determines whether it gets read
Format is not a stylistic choice. It is a cognitive design decision.
A process document is used by someone under time pressure, without the option to ask clarifying questions, who needs to know exactly what to do next. That reader needs a different structure than the one most founders naturally produce when they sit down to explain something they know well.
Here is the five part format that works for a team of two to ten people.
"Use this when preparing and sending a client invoice." One sentence. One scope. If the SOP covers more than one scenario, it is two SOPs.
Any login, template, or confirmation that must exist before starting. Maximum three items. If you need more, two processes are being combined into one document.
"Open the invoice template in the shared folder." Not "The invoice template should be found in the shared folder." The imperative form removes ambiguity. Every step fits on one line. If a step needs more than one line, it is two steps.
This is the most valuable part of the document. Not a list of warnings. One sentence: the specific thing that goes wrong most often, stated plainly. Most founders leave this out. The ones who include it are the ones who stop explaining the same error to the same people.
The SOP handles the standard situation. It does not need to handle every edge case. It only needs to point people somewhere when it does not apply.
A complete SOP for a standard process fits on one page. If it does not, split it. Two short documents that get used are worth more than one complete document that does not.
Test it before you call it done
An untested SOP is a hypothesis, not a standard.
An SOP that requires a meeting to understand has already failed its purpose.
The measure is not whether the document is thorough. It is whether a capable person can follow it alone, under pressure, when you are not reachable.
The final step is to hand the document to one team member, ask them to complete the process without explanation or assistance, and watch exactly where they stop. Each pause or question marks a gap. Fix the document, not the person. When they can run the full process without a single question, it is ready to become the operating standard.
This step takes under 30 minutes. Most founders skip it because they assume their writing is clear. It rarely is on the first version, and that is completely normal. The founders who do not skip the test are the ones who stop being pulled back into processes they thought they had already handed off.
When team members begin training new people using the same document without involving you, the process has genuinely moved out of your head and into the business.
Skip the blank page
The SOP Starter Kit includes five ready-to-use templates covering the processes small businesses need to document first: client onboarding, weekly review, content publishing, invoicing, and team handover. Each is pre-formatted in the structure above so you begin with a working skeleton, not a blank page.
Get the SOP Starter Kit — EUR 37Do-Creates works with SME founders on financial clarity and business strategy. This post does not constitute financial or legal advice.