Guide
Standard Operating Procedures for a Small Business, Without Writing Them Yourself
What an SOP is, which five to write first, a free template with three filled examples, and how to get them written by answering questions.
By Automindly. Published 28 October 2026. Updated 29 October 2026.
A standard operating procedure (SOP) is a written, step-by-step instruction for a job a business does again and again, such as answering a new enquiry, sending a quote or chasing a late payment. The US Environmental Protection Agency's guidance on writing them calls an SOP "a set of written instructions that document a routine or repetitive activity". A good one lets someone new do the job the way you would, without asking you.
This guide covers what goes in an SOP, which ones a small business should write first, a template with three filled examples, and how to get them written when you never have a free afternoon.
What is a standard operating procedure?
An SOP describes how one job is done in your business: who does it, when, the steps in order, and what to do when something doesn't go to plan. It's written for the person doing the job, in the words they'd use.
It sits beside a few documents people confuse it with:
Document | What it answers | Example |
|---|---|---|
Policy | What we do and don't do | "We give refunds within 30 days." |
Standard operating procedure | How we do it, step by step | How to process a refund, from the customer's email to the money leaving |
Work instruction | How to do one detailed task inside a job | How to issue a refund in the accounts software |
Checklist | Did we do everything? | The five things to check before an order goes out |
Process map | How the jobs connect | A diagram from enquiry to paid invoice |
A small business needs SOPs and checklists most. A policy can be one line inside an SOP, and process maps help once more than a handful of people are involved.
Why does a small business need SOPs?
Because the alternative is asking the owner. APQC, a research body on benchmarking and knowledge management, surveyed 982 knowledge workers in 2021 and found the average person spent 2.8 hours a week looking for or requesting information. Its later analysis added 2.0 hours a week recreating work that already existed and 1.7 hours giving the same answers again. Those were people in larger organisations. In a business of eight, the person being asked is usually the owner.
Written procedures pay back in several places at once:
The same result every time, whoever does the job.
Faster training. A new hire reads the procedure instead of shadowing you for a week.
Time off. The business keeps running while you're away.
A better price if you sell. Valuers discount a business that depends on its owner; the advisory firm William Buck puts its typical key person discount at 10 to 25%. Our guide on exit planning explains more.
Useful AI. An AI assistant can only follow your way of doing things if it's written down.
Which SOPs should a small business write first?
Start with the jobs that touch money or customers every week and that people ask you about most. For almost any business, that's these five:
Before you start, check the list against your own week. For one week, make a mark every time someone asks you how to do something. The jobs with the most marks go first, even if they're not on this list.
What goes in an SOP? A free template
Copy this table into a document, one per job. Keep each to a page where you can.
Field | What to write |
|---|---|
Title | The job, in the words staff use. "Sending a quote", not "Quotation management process". |
When it applies | What starts the job. |
Who does it | A role, not a name, so it survives someone leaving. |
What you need | The files, tools or logins, and where to find them. |
Steps | Numbered, each starting with a verb, one action per step. Add a screenshot or photo where a step happens on a screen or at a machine. |
Exceptions | What to do when things don't go to plan, and who decides. |
Done when | How the person knows the job is finished. |
Owner and last checked | Who keeps it current, and the date it was last reviewed. |
If you're audited or work in a regulated trade, add these at the top: an SOP number, its purpose and scope, any terms that need defining, who approved it and when, a version history listing each change, and a line for staff to sign that they've read it. Your regulator or certifier may set its own format, so check theirs first.
Three filled examples
Answering a new enquiry
When it applies: a new customer emails, calls or fills in the website form.
Who does it: whoever is on the front desk that day.
What you need: the shared inbox and the price list.
Reply within two working hours, by the same channel they used.
Thank them and repeat back what they asked for.
Ask the two questions we always need: how many, and by when.
Log the enquiry in the customer list with today's date.
If they asked for a price, follow "Sending a quote".
Exceptions: anything larger than a usual order, or a request we don't normally do, goes to the owner the same day. Done when: they've had a reply and the enquiry is logged.
Sending a quote
When it applies: a customer has asked for a price and told us how many and by when.
Who does it: the office manager.
What you need: the price list, the customer list and the quote template.
Check the customer list for anything agreed with this customer before, such as a discount or payment terms.
Work out the price from the price list, then apply any agreed discount.
Fill in the quote template with the items, the price, the delivery date and how long the quote is valid.
Send it, and log the quote and its value against the customer.
If there's no reply in five working days, send one follow-up.
Exceptions: any discount beyond what's already agreed, or a delivery date we haven't met before, needs the owner's yes before sending. Done when: the quote is sent and logged with a follow-up date.
Chasing a late payment
When it applies: an invoice passes its due date unpaid.
Who does it: whoever handles accounts.
What you need: the list of unpaid invoices and the reminder templates.
Every Monday, list the invoices past their due date.
One day late: send the polite reminder with the invoice attached.
Seven days late: call the customer's accounts contact and note what they said.
Fourteen days late: send the firm reminder and tell the owner.
Log every reminder and call against the invoice.
Exceptions: a customer with an agreed payment plan, or a dispute about the work, goes to the owner instead of the reminders. Done when: the invoice is paid, or the owner has taken it over.
The timings and limits above are examples. Use your own.
Which format should an SOP use?
Numbered steps for most jobs: anything done in the same order every time.
A checklist for jobs where the order doesn't matter but nothing can be missed, such as opening up in the morning or checking an order before it goes out.
A simple flowchart for jobs with decisions in them, where the next step depends on an answer: "Is the customer on a payment plan? Yes, go to the owner. No, send the reminder."
Photos or screenshots beside any step that happens on a screen or at a machine, because one picture saves a paragraph.
How do you write an SOP?
Pick one job. The one you're asked about most this week.
Involve the people who do it. If two staff do the job differently, write down both ways before choosing one, and ask them which works better.
Do it and talk it through. Record yourself on your phone while you do the job, saying each step out loud. It's usually faster than writing from memory, and it catches steps you'd skip.
Turn the recording into numbered steps. One action per step, each starting with a verb.
Add the exceptions. Ask "what usually goes wrong here?" and write what you do when it does.
Test it on someone else. Have a member of staff do the job using only the page. Every question they ask is a missing line.
Fix it, date it, and put it where people look. One shared folder for every procedure.
Set aside an hour for each. At one a week, the five above are done in five weeks. A month later, check whether the job now goes the same way every time, and change the page if it doesn't.
How do you get SOPs written when you never have time?
Answer questions instead of writing. Many owners who stall on a blank page can explain a job easily when someone asks about it. So have someone ask: a manager, a family member, or an assistant who writes down your answers in your words and turns them into steps for you to correct.
Correcting a written page is usually quicker than writing one, and the result still sounds like the business.
How do you keep SOPs up to date?
Give each one an owner. The person who does the job most often keeps its page current.
Change it when the job changes. If someone does it differently and it works better, update the page that day.
Review twice a year. A quick read of each page, with the date updated.
Keep them in one place. A shared folder everyone can open beats a clever tool nobody uses.
What are the common mistakes?
Writing a manual. A 60-page binder gets written once and never read. One page per job gets used.
Leaving out the exceptions. The normal case is easy. The unusual ones are why people still call you.
Writing it for the wrong reader. Write for the person doing the job, in their words.
Never testing it. If nobody has done the job from the page alone, you don't know it works.
Starting with the rare jobs. Start with what happens every day.
Where does AI fit?
An AI system can do the asking and the writing: it asks you about a job in plain language, writes the procedure from your answers, and lets staff ask it questions later instead of asking you. That's what Automindly sets up around a business; our How It Works page shows what it looks like.
The owner still decides. An AI can write the steps from your answers, but only you know which exceptions matter and who gets to make them, so read every procedure it writes before your staff use it.
Questions owners ask
How long should an SOP be?
As short as the job allows. Aim for one page; if a procedure runs much longer, it's usually two jobs.
Is there a free SOP template for a small business?
Yes: the table under "What goes in an SOP?" above. Copy it into a document, one per job, and add the regulated fields if you're audited.
Can AI write SOPs for my business?
It can write the first draft from your answers to its questions, which is usually the slow part. It can't know your exceptions until you tell it, so treat every draft as something to correct before staff rely on it.
Do I need special software for SOPs?
No. A shared folder of plain documents works for most small businesses. Software helps once you have many procedures, many staff, or want people to be able to ask questions of them.
What's the difference between an SOP and a work instruction?
Larger organisations sometimes split them: the SOP covers the whole job, and a work instruction covers one detailed task inside it. In a small business, one page per job usually does both.
Sources: US Environmental Protection Agency, Guidance for Preparing Standard Operating Procedures (EPA QA/G-6), EPA/600/B-07/001, April 2007. APQC, survey of 982 knowledge workers, 9 November 2021. APQC, "KM Makes Knowledge Workers More Productive and Less Stressed Out", 17 November 2022. William Buck, "Assessing the impact of key person risk on business valuation", 14 January 2025.