How to Write an SOP (That Your Team Will Actually Use)

Most SOPs fail for the same reason: they're written by someone sitting at a desk, for someone who'll never read them. They end up in a folder, and your team keeps texting you instead.

A good standard operating procedure (SOP) is different. It's short, it's written in plain words, and a new person can follow it on their first day without calling you.

This guide shows you how to write an SOP in 7 simple steps, with a before-and-after example, the right format for each kind of task and an AI prompt that does the first draft for you.

Want to skip the blank page? Grab the free SOP template and fill it in as you read.

What is an SOP?

An SOP is a written set of steps for doing one routine task the same way every time. "Opening the shop." "Taking a phone booking." "Handling a refund."

For a small business, an SOP isn't a corporate binder. It's one page that answers four questions: what the task is, who does it, how to do it step by step, and what "done right" looks like.

How to write an SOP in 7 steps

1. Pick one task, and only one

Start with the task your team asks you about most. If people text you "how do I…?" about it, that's your first SOP.

Keep the scope small. "Closing the café" is one SOP. "Running the café" is twenty.

2. Watch the task being done (or do it yourself)

Don't write from memory. You'll skip the steps you do on autopilot, and those are exactly the ones a new person gets wrong.

Do the task, or watch the person who does it best, and write down (or voice-record) every step as it happens. Ask "why?" at each step: the reasons often become your tips.

3. Write the basics at the top

Before the steps, answer these in one line each:

• Task: what it's called
• Purpose: why it matters, in one sentence
• Who: the role that does it (not a person's name, since people change)
• When: the trigger or time of day
• Time needed: how long it takes
• What you need: tools, keys, logins, supplies

4. Write each step as one action, starting with a verb

This is the rule that makes the biggest difference.

• One action per step. "Count the drawer and fill in the cash sheet" is two steps.
• Start with a verb: Turn, Wipe, Count, Text, Check.
• Be specific. "Clean the area" is vague. "Wipe the counter with the green cloth" isn't.
• Put numbers on things: amounts, times, temperatures, quantities.
• Add a short tip only where people usually go wrong.

Aim for 8 steps or fewer. If you need more, it's probably two tasks.

5. Define "done right"

Write one sentence that describes the finished result. "Floor dry, cash sheet signed, alarm on, owner got the text."

This is the line most SOPs forget, and it's the one that stops people guessing whether they're finished.

6. Test it on someone new

Give the SOP to someone who has never done the task and stay out of the way. Every time they hesitate or ask you a question, that step needs fixing.

If they finish without calling you, the SOP works.

7. Store it where the work happens, and keep it current

An SOP nobody can find is useless. Print it and tape it where the task is done, or keep all your SOPs in one shared folder everyone can open on their phone.

Write an owner and a date at the bottom. Review it whenever the task changes, and at least once a year.

SOP example: before and after

Here's a real-world kind of SOP, written the usual way:

Phone bookings. Answer the phone professionally and book the client in. Make sure you get all the details and confirm everything. Be careful with double bookings.

Every sentence sounds fine, and none of them tells a new receptionist what to do. Here's the same task rewritten with the 7 steps:

• Task: Taking a phone booking (hair salon)
• Purpose: Every client gets the right service, with the right stylist, at the right time
• Who: Front desk
• When: Every incoming booking call
• Time needed: 3 minutes

Done right looks like: booking in the app with name, mobile number, service and stylist, and the client heard the price and the policy.

Same task, but now anyone can do it.

Which SOP format should you use?

You can mix them. A numbered-step SOP with one photo of what "done right" looks like is often the best of both.

Write the first draft with AI

You don't have to type it. Do the task once while recording a voice note on your phone, describing every step out loud. Turn it into text (most phones and AI apps can do it), then paste it into an AI assistant (ChatGPT, Claude, Gemini or Copilot) with this prompt:

Turn this transcript into a one-page SOP for a small business. Start with: task, purpose (one sentence), who does it, when, time needed and what you need. Then up to 8 numbered steps, each one action starting with a verb, with a short tip only where people often make mistakes. End with "Done right looks like" and 2 common mistakes. Plain English, short sentences. Transcript: [paste]

Then check it line by line. Fix anything wrong and remove anything you didn't say. AI drafts, you decide.

Common SOP writing mistakes

1. Too long. Nobody reads five pages in the middle of a shift. One page per task.
2. Written for the boss, not the doer. Use the words your team uses, not management language.
3. Vague verbs. "Handle," "manage" and "ensure" don't tell anyone what to do.
4. No reason given. A one-line "why" helps people make good calls when something unexpected happens.
5. Never tested. If you haven't watched someone new follow it, you don't know if it works.
6. Never updated. An out-of-date SOP teaches the wrong way, with your name on it.

Frequently asked questions

How long should an SOP be?

For most small business tasks, one page with 8 steps or fewer. If it's longer, split the task into two SOPs.

Who should write SOPs?

Whoever does the task best, with the owner or manager checking it. The person doing the job knows the real steps; the owner makes sure it matches how the business wants it done.

What's the difference between an SOP and a policy?

A policy says what the rule is ("refunds within 30 days"). An SOP says how to carry it out, step by step ("how to process a refund at the register").

How many SOPs does a small business need?

Fewer than you think. Start with the 5 to 10 tasks your team asks about most, such as opening, closing, cash handling, bookings and complaints. Add more as questions come up.

What's the best format for an SOP?

Numbered steps work for most tasks. Use a checklist when the order doesn't matter, and add "if…then" steps when the task involves a decision. A simple one-page SOP template covers all three.