SOPs for Small Business: How to Write Your First Five

Standard operating procedures (SOPs) for a small business are short, written step-by-step instructions for the jobs you do over and over, so anyone on your team can do them the same way without asking you. Start with five: how you quote, how you deliver your core service, how you invoice and collect, how you onboard a new customer, and how you close each day or week. Keep each one to a page.

If your staff phone you ten times a day with “how do I…?” questions, you already know the problem. The knowledge lives in your head. Every time you are away, sick or with a client, work slows down or goes wrong, and you end up fixing mistakes at 9pm.

Why small businesses need SOPs (even with three people)

Many owners think procedures are for factories and banks. In practice, a small team needs them more, because there is no manager layer to catch mistakes.

Unclear expectations are common everywhere. In a 2015 Gallup article on workplace expectations, only about half of employees strongly agreed that they know what is expected of them at work. Gallup also pointed out that a job description alone isn’t enough; people need ongoing guidance and feedback. An SOP is one of the simplest ways to give that guidance in writing.

SOPs also make improvement possible. As Brad Power put it in Harvard Business Review, “Our ability to improve the ways we do things depends on defining and shaping our daily habits of mind and practice.” You can’t fix a process nobody has written down.

Most of all, SOPs are how you reduce founder dependency in a small business. They turn “ask the boss” into “check the procedure”.

What a good small business SOP looks like

Forget thick manuals. A useful SOP for a small business fits on one page and has six parts:

  1. Name and purpose. “Sending a quote: so every quote goes out within 24 hours and is priced correctly.”
  2. Owner. The role responsible, not only a person’s name.
  3. Trigger. What starts the process, such as “a customer enquiry arrives”.
  4. Steps. Numbered, short, starting with a verb. Usually five to twelve.
  5. Standard. What “done well” looks like, such as “quote sent within 24 hours using the price list”.
  6. Tools and templates. Links to the price list, invoice template or checklist used.

Write it in the words your team uses. If your staff call it “the job card”, don’t call it a “work order form” in the SOP.

The first five SOPs to write

Don’t try to document everything. Start with the five processes that touch money and customers most often.

SOP Why it comes first What it should cover
1. Enquiry to quote Slow or inconsistent quotes lose work you already paid to attract Response time, pricing source, approval limits, follow-up dates
2. Delivering your core service or product This is where quality and complaints come from Preparation, the main steps, quality checks, sign-off
3. Invoicing and collections Late invoices mean late cash When to invoice, payment terms, reminder schedule, escalation
4. New customer onboarding First impressions shape repeat business Welcome message, information to collect, setting expectations
5. Daily or weekly close Stops small problems piling up Cash-up, stock check, task review, next-day prep

A Joburg caterer, for example, might write “Event set-up” as SOP 2 and “Post-event cash-up and stock count” as SOP 5. A Cape Town agency might write “Client brief to first draft” and “Friday work-in-progress review” instead. The names change; the logic doesn’t.

How to write an SOP in one afternoon

The fastest way to write an SOP is not to sit down and write it from memory. Capture the work as it actually happens.

  1. Do the task once and narrate it. Record a voice note or a short phone video while you or a team member does the job.
  2. Turn the recording into steps. Write each action as one short line starting with a verb: “Check”, “Send”, “Record”.
  3. Mark the decision points. Where does someone have to choose? Write the rule: “If the job is over R20,000, the owner approves the quote.”
  4. Add the standard. Write one line on what a good result looks like and how quickly.
  5. Test it with someone else. Ask a team member to follow the SOP without your help. Every question they ask shows a missing step.
  6. Fix and publish. Update it, date it and put it where the team can find it in seconds.

Don’t aim for perfect. A rough SOP your team uses beats a polished one sitting in a folder.

Getting your team to actually use them

The biggest risk with SOPs is that you write them and nobody reads them. A few habits help:

  • Involve the people who do the work. They know the shortcuts and the problems. They are also far more likely to follow a procedure they helped write.
  • Point to the SOP, not to yourself. When someone asks how to do something that is documented, ask “What does the SOP say?” It feels slow at first. After a month, the questions drop.
  • Use SOPs for training. New staff learn from the documents, then shadow someone, then do the job while being checked.
  • Review them regularly. Put a quarterly reminder in the calendar. If the process has changed, update the SOP the same week.

SOPs work best alongside proper handover. Our guide to delegation for small business owners covers what to hand over first and how to check the work without taking it back.

Common SOP mistakes to avoid

  • Writing too much. If an SOP runs past two pages, split it into two processes.
  • Documenting the ideal instead of the real. Write what should happen, but check it against what actually happens, or nobody will trust it.
  • No owner. Every SOP needs one role responsible for keeping it current.
  • Hiding them. SOPs buried in your personal email are useless. Keep them in one shared place.
  • Starting with rare tasks. Annual stock-takes can wait. Document what happens every day or every week first.

If you’re not sure which process is causing the most trouble, a quick look at how to decide what to fix first will help you pick the right starting point.

How B.E.T helps you build and run your SOPs

Writing SOPs is easier when you’re not starting from a blank page. B.E.T’s ready-to-use templates give you a starting structure for common documents, and the plan builder’s guided prompts help you think through who owns each process and what “done” looks like.

Once your procedures are written, task and team tracking lets you assign the recurring jobs they describe, so you can see whether the weekly close or the invoice follow-up actually happened. The business diagnostic can also show you which area of operations needs documenting first.

You can start a free B.E.T trial and set up your first five processes this week.

Frequently asked questions

What is an SOP in a small business?

An SOP, or standard operating procedure, is a written set of steps for a task you do regularly. It explains who does it, when, how and what a good result looks like. In a small business it is usually one page and written in plain language.

How long should a standard operating procedure be?

For most small business tasks, one page is enough, with five to twelve numbered steps. If it runs longer than two pages, it is probably more than one process and should be split up.

Who should write SOPs in a small business?

The person who does the task most often should help write it, with the owner checking that it meets the standard. That way the SOP reflects how the work really happens, and the team has a stake in using it.

How often should SOPs be updated?

Review each SOP at least once a quarter, and update it immediately when the process changes, for example after a new supplier, new software or a repeated mistake. Date every version so everyone knows which one is current.

What is the difference between an SOP and a checklist?

An SOP explains the full process, including who is responsible, the steps and the standard expected. A checklist is a short list of items to tick off while doing the work. Many small businesses attach a checklist to each SOP for daily use.

Five pages that buy back your time

You don’t need a manual. You need five clear pages covering the work that happens every day, written with your team and actually used.

Pick your first process today, and take the free B.E.T business health check to see which area of your operations needs a procedure most.

Related reading

Dishen Maharaj

Dishen Maharaj is a business advisor at YVR Consulting, the team behind B.E.T. He works with small business owners and founders on diagnostics, planning and day-to-day business structure, and writes practical guides for the B.E.T blog.

Recent Posts

LivePlan Alternative for South African SMEs: An Honest Comparison

LivePlan is a strong forecasting and planning tool. Here is a fair comparison with B.E.T…

2 hours ago

How to Price Your Product or Service So You Actually Make Profit

Busy but not profitable? Learn to price from real costs, avoid the markup vs margin…

2 days ago

CIPC Registration Explained: Company vs Sole Proprietor in South Africa

Sole proprietor or private company? What each means for liability, tax and funding, what CIPC…

2 weeks ago

Small Business Self-Assessment: 30 Questions Every Owner Should Answer

Thirty honest questions across money, customers, operations, people, compliance and planning, with a simple scoring…

2 weeks ago

How to Write a Business Plan Without a Consultant

You know your business better than any consultant. Here is a clear structure and step-by-step…

2 weeks ago

Busy But Broke: Why Revenue Grows and the Bank Balance Doesn’t

Sales are up but the bank balance isn't. Here is why growing businesses run short…

3 weeks ago