How to Write SOPs for a Small Business That People Actually Use

Most owners who try to learn how to write SOPs for a small business do it the same way. They block out a Saturday, open a blank document, and write down how the job is done from memory. By Sunday they have eleven pages nobody will read, describing a process that is not quite how anyone actually does it, including them.

The document fails for a simple reason. The owner is the worst person to write the first draft. You know the process so well that you skip the steps that feel obvious, and those are exactly the steps a new person gets wrong. Good standard operating procedures are written from someone else's hands, not from your memory: you watch the work being done, the person who will do it writes the draft, and you mark the few places where judgment is required.

This is the practical version, in six steps, with a template and a worked example.

What an SOP Is For (and What It Is Not)

A standard operating procedure is a written description of how a repeated task gets done, clear enough that someone competent can do it without asking you. That last clause is the whole test. An SOP is not a policy manual, not a training course, and not a record of everything you know. It is a tool for getting a specific job done the same way every time by someone who is not you.

The reason to bother is not tidiness. It is cost. Work through a hypothetical: an owner of a small design studio gets interrupted about twelve times a week with questions about client onboarding. Each interruption takes five minutes to answer and another ten to get back into whatever they were doing. That is three hours a week, or roughly 150 hours a year, spent answering the same questions. Add the errors: if one onboarding in ten misses the deposit invoice, and the average deposit is $1,500, a studio taking on forty clients a year has $6,000 a year in deposits that go uncollected until someone notices, plus the awkward call to chase each one.

A two-page SOP fixes both. The point is not the document. The point is the 150 hours and the $6,000.

An SOP is finished when somebody else can do the job without calling you. Until then, it is notes.

How to Write SOPs for a Small Business, Step by Step

Step 1: Pick the first three processes

Do not try to document the business. Document three things. To pick them, list every task that repeats at least monthly and score each one on three questions, one to three points each:

• How often does it happen?
• How expensive is a mistake?
• How often does it bring someone to your door with a question?

The three highest scores are your first SOPs. In most service businesses they turn out to be some version of new client onboarding, quoting or estimating, and invoicing and collections. In product businesses, order fulfillment and returns usually make the list.

Step 2: Record the work being done, not described

Watch the task done by the person who does it most often. If it happens on a computer, have them record their screen and talk through what they are doing. If it happens in the field, a phone video works. Do not interrupt to correct them. You are capturing what actually happens, including the workarounds, because the workarounds usually exist for a reason.

If you are the only person who does the task today, record yourself. The recording will catch the steps your memory would skip.

Step 3: Have the doer write the first draft

The person who will run the process writes the SOP from the recording, using a fixed template. You review it; you do not write it. This does two things. The draft uses the words the team actually uses, which makes it readable to the next person. And the team owns the process instead of receiving it, which is the difference between an SOP that gets followed and one that gets filed.

Keep the template short and the same for every process:

Step 4: Mark the judgment calls and give each one a rule

This is the step owners skip, and it is the one that decides whether you get interrupted less. Every process has a few points where someone has to decide something: whether a discount is allowed, whether a job needs a site visit, whether a client's request is in scope. If the SOP does not say how to decide, the question comes back to you.

For each judgment call, write a rule with a threshold. "Discounts up to 5% on orders over $2,000 are fine; anything else, ask the owner." "Change requests under two hours are absorbed; anything over two hours gets a written quote." The rule does not have to be perfect. It has to be clear enough that someone can apply it without you. This is the same move that makes delegation work in general: you are not handing over a task, you are handing over the right to decide within stated limits.

Step 5: Run the cold test

Give the SOP to someone who has never done the task and ask them to do it while you stay out of the room. Every time they get stuck, note where. Those are the gaps, and they are always somewhere the author thought was obvious. Fix the document, not the person. One or two rounds of this is usually enough.

If nobody in the business has ever done the task but you, the cold test is also the moment you find out how much of the business depends on one person. That is worth knowing for its own sake, as the post on key person risk explains.

Step 6: Give each SOP an owner and a review trigger

SOPs rot. The software changes, a supplier changes, someone finds a faster way and stops following the document. Every SOP needs one named owner and a trigger for review: every six months, or whenever the process produces an error, whichever comes first. When the owner updates it, they change the "Last tested" line. An SOP with a date two years old should be treated as a draft.

A Worked Example: Quote Follow-Up

Here is what a finished SOP looks like for a small renovation contractor. It fits on one page.

Title: Quote follow-up. Trigger: a quote is sent to a prospect. Owner: the office coordinator.

1. Log the quote in the pipeline sheet the same day, with the amount and the date sent.
2. On day 3, send the follow-up email from the template, personalized with one detail from the site visit.
3. On day 7, call. If no answer, leave a short voicemail and send a text.
4. On day 14, send the final email asking whether to keep the quote open.
5. Mark the quote won, lost (with reason), or open. Nothing stays open past day 30.

Judgment call: if the prospect asks for a lower price, you can remove optional items from scope. You cannot reduce the rate. Anything else goes to the owner. Done looks like: every quote in the sheet has a status and a date for its last contact.

Nothing in that list is clever. It works because it is specific, because it states the one decision that used to come back to the owner, and because it defines done. The same structure applies to the processes new staff learn first, which is why a good SOP set doubles as the backbone of onboarding a new employee.

What the Board Said About Getting Started

Here is how this question tends to play out at a board table. The scenario is an illustrative composite rather than a client's session: an owner of a twelve-person landscaping company who wants every process written down by the end of the quarter before hiring a general manager.

Dana Mitchell, Operations Advisor, liked the ambition and cut the scope. Her line: if it cannot be repeated, it is not a business, but a quarter is enough for three good SOPs, not thirty bad ones. She wanted the three highest-scoring processes done properly, cold-tested, with a named owner each, before anyone wrote a fourth.

Lisa Gomez, People & Culture Advisor, pushed on who writes them. If the owner writes the SOPs alone and hands them down, the crew leads will read them as a sign they are not trusted, and they will quietly keep doing it their own way. Her suggestion was that each crew lead drafts one, the owner reviews, and the lead presents it to the team. Slower, she said, but it is the only version people follow when the owner is not watching.

The disagreement was about pace, not direction. Dana wanted fewer processes done faster. Lisa wanted the right people doing the writing even if it took longer. The owner took Dana's scope and Lisa's method.

Common Mistakes When Writing SOPs

• Writing for yourself. If you need the SOP to do the task, it is a checklist, which is fine, but it is not an SOP for someone else.
• Documenting everything at once. Thirty half-finished SOPs are worth less than three tested ones.
• Leaving out the decisions. An SOP without judgment rules still routes every exception to you.
• Storing them where nobody looks. Put SOPs where the work happens: pinned in the shared drive folder for that client type, linked from the job ticket, printed in the van.
• Never retesting. An untested SOP drifts from reality within a year.

One Thing to Do This Week

Score your repeated tasks on frequency, cost of error, and interruptions. Pick the top one. Ask the person who does it most often to record themselves doing it next time, and to draft the SOP from the recording using the template above. Your only job is to review it and write down the judgment calls.

If you know the SOP work matters and it keeps sliding behind whatever is urgent this week, that is a follow-through problem, not a knowledge problem. It is the kind of commitment that an advisory board for a small business exists to hold you to, with a name and a date written down and someone who asks about it next week.