How to write your first SOP: a step-by-step guide for small businesses

Fifty-six per cent of small business owners owners spend more than half their working time managing the business. Not doing the actual work. Managing it.

You know you need a system to fix this. But every time you sit down to document a task, you get two paragraphs in, decide it's quicker to just do it yourself, and close the document. Three weeks later you're doing the same task again and the document is still empty.

That's not a discipline problem. That's a starting point problem. This guide fixes that. By the end you'll have a working SOP. Not a template, not a framework, an actual written process for one real task in your business.

What is a standard operating procedure?

A standard operating procedure, SOP, is a documented process for completing a recurring task the same way every time.

That's it. It's not a manual. It's not a policy document. It's the written instructions for how a specific task gets done in your business, detailed enough that someone else could follow it and produce the same result you would.

The working definition: if you handed this document to a capable person who had never worked in your business before, could they complete the task correctly? If yes, it's an SOP. If not, it needs more work.

What an SOP is not

It's not a job description. It's not a business plan. It's not a values statement. Those things have their place, but they're not SOPs. An SOP is task-level: one specific thing your business does, documented step by step.

It's also not permanent. An SOP that was accurate six months ago might need updating today. The goal isn't to write a perfect document once. It's to write a working document that you actually use and improve over time.

"An SOP is what makes AI tools like ChatGPT sound like you. Generic prompts get generic results. Your documented process is the brief."

Why does a small service business need SOPs?

Because you can't hand off a task you haven't defined.

Every time you do a recurring task from memory, you're relying on yourself to be available, focused, and consistent. When you're not, because you're tired, busy, sick, or just not thinking about it, the task gets done differently. Or it doesn't get done at all.

An SOP breaks that dependency. Once a task is documented, it can be delegated to a team member, handed to a virtual assistant, or given to an AI tool with enough context to do it properly.

The AI connection

The quality of what an AI tool produces is directly tied to the context you give it. When you use a tool like ChatGPT to help with recurring tasks, drafting a follow-up email, summarising meeting notes, responding to a common enquiry, that context is the difference between output that sounds like you and output that sounds like everyone else.

Generic prompts get generic results. Your documented process is the brief.

A prompt that says "write a follow-up email to a client" produces something forgettable. A prompt that draws on an SOP describing your tone, your typical clients, your standard follow-up structure, and what a good outcome looks like produces something that sounds like you actually wrote it.

Which task should I write my first SOP for?

Not the most important one. The most annoying one.

Most people try to start with their most critical business process. That's the wrong place to begin. Critical processes are complex, have edge cases, and are hard to document completely. The ambition stalls the project.

Start with something you do every week that you'd rather not be doing. The task you could do in your sleep because you've done it so many times. That task has two things going for it: you know it well enough to document it quickly, and getting it off your plate has an immediate effect on your week.

Good candidates for your first SOP

Invoice follow-up: the message you send when an invoice is overdue. You've typed a version of it forty times. Write it down once.

New enquiry response: how you handle a first contact from a potential client. What you ask, what you send, what happens next.

Booking confirmation: what a new client receives when they book. The confirmation, the prep instructions, the next step.

Weekly report or update: if you send regular updates to clients, the structure and standard content that goes into every one.

Onboarding checklist: what a new client receives in the first 48 hours after saying yes.

The five-task shortlist method

If you're not sure which task to start with, try this. Write down the five things you do on repeat every single week — the stuff that's always there, always taking time. Then circle the one you least enjoy doing. That's your first SOP.

How do I actually write an SOP?

Seven steps. They take longer to read than to do.

Step 1: Do the task once while you document it

Don't try to write the SOP from memory. Instead, the next time you do the task, open a document alongside it and write down what you're doing as you do it. Every click. Every decision. Every thing you check before you move to the next step.

This sounds slow. It isn't. Most recurring tasks take longer in your head than they do in reality, and documenting while doing is faster than reconstructing after the fact.

Step 2: Write it like you're explaining it out loud

Address the document to "you", as if you're talking to the person who will follow it. Use the second person. "Open the invoice in Xero. Check that the client name matches the contact record." Not "the invoice should be opened" or "one should verify."

Read what you've written out loud. Anywhere you stumble or add a word that's not in the draft, rewrite it. The voice test is: would I say this to someone standing next to me?

Step 3: Be specific, not general

General: "Check the client details are correct."

Specific: "Check that the client's email address matches what's in the contact record in Xero. If it doesn't match, update the contact record before sending."

Specificity is what makes an SOP usable. A step that requires interpretation is a step that will get done differently by different people, or skipped entirely.

Step 4: Format for skimming

The person following this SOP is busy. They're doing the task, not reading an essay. Format accordingly: one idea per paragraph, two to four sentences maximum, numbered steps for sequences where order matters, bullet points for lists of three or more items, and the key action bolded in each step so it's visible on a scan.

Step 5: Include the decision points

A task done in real life has forks in it. What do you do when the client hasn't replied after three days? What do you do if the invoice total is different from the quote? What do you do if the booking system shows a conflict?

A good SOP documents the most common decision points and tells the person following it what to do at each one. You don't need to cover every edge case, just the situations that come up regularly.

Format: "If [condition], then [action]. If [different condition], then [different action]."

Step 6: Add the "done" definition

Every SOP should end with a clear description of what done looks like. Not just the last step, what the finished state is. "The invoice is marked as sent in Xero, the client has received the email, and the task is closed in your project management tool."

Without this, tasks get half-completed and left in ambiguous states. The done definition closes that loop.

Step 7: Test it on the next person who does the task

Hand the SOP to someone and ask them to follow it without your input. Watch where they hesitate, where they ask questions, and where they make a different decision than you would. Every hesitation is a gap in the document.

If you're a solo operator and there's no one to test it on, read it back 48 hours after writing it. You'll see the gaps you couldn't see when the task was fresh in your mind.

What does a finished SOP actually look like?

Here's a complete example for a recurring task that most service businesses do: sending a seven-day invoice reminder.

That's a complete SOP. One page. Specific enough to follow without asking questions. Includes the decision points. Clear done definition.

How do I use my SOP with AI tools?

Once you've written an SOP, it becomes the context block for any AI tool you use to help with that task.

Instead of typing "write a follow-up email to an overdue invoice client" — which gets you something generic, you paste your SOP into the prompt alongside the specific details for this particular client.

The SOP tells the AI how your business works. The specific details tell it what this particular message needs to say. The output sounds like you, because the brief is built from how you actually operate.

"That's the difference between generic AI output and AI that reflects your business. The SOP is the brief."

What are the most common SOP mistakes service businesses make?

Starting with the wrong task

Trying to document your most complex or important process first. It's too hard, too long, and the ambition kills the project. Start with something small and repetitive. Build the habit before you tackle the hard stuff.

Writing it for an imaginary perfect person

Writing as if the person following the SOP already knows your systems, your clients, and your preferences. They don't. Write it for someone capable but new, and be specific about the decisions they'll need to make.

For example: "If the client hasn't responded after three days, send a second reminder using the 14-day template. Don't wait and assume." That's a decision point. "Handle client non-responses appropriately" is not.

Making it too long

An SOP that's ten pages long won't get used. If a task genuinely requires ten pages to document, it's not one SOP, it's several. Break it into smaller, linked documents.

Skipping the done definition

Without a clear done state, tasks get left in ambiguous half-completed states. The done definition is the last step and the most important one.

Never updating it

An SOP is only useful if it's accurate. When your process changes, new tool, new step, new decision point, update the document. Add a "last updated" date at the top so you know how current it is.

Where should I keep my SOPs?

For most small service businesses, a Google Drive folder called "How We Work" or "Systems" is perfectly sufficient. One document per task, named clearly. "Invoice Follow-Up SOP", not "Process Doc 1". No special software required to start.

If you bring on team members or a VA, you can migrate to a tool like Notion or ClickUp that makes SOPs more searchable and linkable. But that's a problem for later. A Google Doc you actually open and follow is worth more than a sophisticated system you built and never use.

Nardia Barrett

Founder of BossKit. Small business systems consultant with over a decade in mortgage broking and eight years running WEBS, a free networking group for small business owners in Western Sydney. BossKit helps service businesses work out what to automate, what AI can assist with, and what to keep human.