SOPs for a team of three: what to write down first

Why three people is the right time

With one person, everything lives in one head. With ten, you are forced into process whether you like it or not. Three is the awkward middle, and it is the point where unwritten knowledge starts to cost money.

Picture a coach, an assistant and a part time setter. The coach is away for a week and a client payment fails, and nobody else knows which tool sends the invoice, who to email or what to say.

The problem is small. The delay it causes is not.

Standard operating procedures, or SOPs, fix this. The usual mistake is trying to document everything at once, running out of steam by the fourth document and abandoning the folder.

Pick the first five by risk, not by size

Do not start with the biggest process. Start with the ones that cause the most damage when they go wrong or get missed.

Ask three questions of each recurring task:

1. If this was missed for a week, would a client or prospect notice?
2. Does only one person know how to do it?
3. Does it happen often enough that mistakes repeat?

A task that scores yes on all three goes to the top of the list. For most service businesses that sell through calls, the first five look something like this:

• New client onboarding. Payment confirmed, welcome email sent, access to materials granted, first session booked.
• Sales to delivery handover. What happens between a prospect saying yes and that client being onboarded, including who sends the contract and the invoice.
• Failed payments. Who is told, what message goes out and when access is paused.
• Lead follow up. How quickly new leads and booked calls are contacted, and by whom.
• Weekly numbers. Which figures are pulled, from where, and where they are recorded.

Record first, write second

The fastest way to create an SOP is not to write it from scratch. Next time the task is done, the person doing it records their screen and talks through what they are doing.

That ten minute recording becomes the raw material. Someone else, or an AI tool working from the transcript, turns it into a written checklist, and the person who knows the task reviews it once for errors.

This splits the work so the expert spends minutes on it rather than an afternoon.

What a usable SOP looks like

An SOP for a small team should fit on one page or one screen. If it is longer than that, it is probably two processes.

A simple template:

• Name of the task and what triggers it. "When a new client pays."
• Owner. One named role, not "the team".
• Tools and access needed. Where to find them, never the passwords themselves.
• Steps. Numbered, one action per line, each starting with a verb.
• Done means. What finished looks like. "Client has received the welcome email and the first session is in the calendar."
• Link to the recording.

If the only copy of a process is in someone's head, it leaves the business every time they take a holiday.

Test it on someone else

An SOP has not really been written until someone other than the author has followed it. Give it to another team member and ask them to complete the task using only the document and the recording.

Ask them to keep a short note as they go, something like: "Step 4, I could not find the welcome email template. Step 6, it was not clear whether I should copy the coach in."

Every question they ask is a gap. Add the answer to the document, then test again the next time the task comes round.

This also shows whether the process itself is wrong, or simply out of date. Plenty of teams discover, while writing things down, that a task has eight steps where three would do.

Keep it alive

Written procedures go stale quickly in a small business, because tools and offers change. A few habits stop the folder turning into a museum:

• Keep every SOP in one shared place with a consistent naming format.
• Put a "last checked" date at the top of each one.
• When someone follows an SOP and finds it wrong, they fix it there and then, not later.
• Review the first five once a quarter.

Once those five are solid, add one more each month. Start in September and by the end of the year you will have eight or nine processes written down.

That covers most of what goes wrong in a typical week. The business becomes far less dependent on whoever happens to be in that day.