All articles

Operations

How to write standard operating procedures (SOPs) for a small business

How to write standard operating procedures that people actually follow: what to document first, a simple format, how to keep them current, and a free fillable SOP template.

Genvora teamPublished 4 min read
Hand ticking off items on a checklist on a tablet

Most small businesses run on what's in a few people's heads. That works until someone goes on holiday, leaves, or the business grows past the point where everyone can just ask everyone else. Standard operating procedures, or SOPs, are the written version of "how we do this here". They don't need to be long or formal to be useful.

This guide covers which processes to write down first, a format people will actually read, and how to stop your SOPs going out of date. There's a free fillable template further down.

The short version

  • Start with the tasks that happen often, go wrong often, or only one person knows how to do.
  • Keep each SOP to one task, written as numbered steps by the person who does the job.
  • Test it by asking someone else to follow it without help.
  • Give every SOP an owner and a review date, and keep them all in one place.

What an SOP is, and what it isn't

An SOP is a short set of instructions for one repeatable task: the monthly invoice run, setting up a new client, publishing a blog post, cashing up at the end of the day. It isn't a policy document or an employee handbook. If it takes longer to read than to do the task, it's too long.

Which processes to write down first

You don't need to document everything. Start with tasks that tick one or more of these boxes:

  • They happen often, so small mistakes add up.
  • They go wrong regularly, or are expensive to fix when they do.
  • Only one person knows how to do them.
  • They touch money or customers directly, such as invoicing, refunds or complaints.
  • You'll need to hand them to someone new soon.

Five or six SOPs covering your most important tasks are worth far more than a folder of forty that nobody opens.

A simple format that works

Every SOP can follow the same short structure:

  1. 1A title that says what the task is, such as "Raising the monthly client invoices".
  2. 2Purpose: one sentence on why the task matters.
  3. 3When to use it: the trigger, such as "on the first working day of each month".
  4. 4Who does it, and who to ask if they get stuck.
  5. 5What you need before you start: logins, files, information.
  6. 6The steps, numbered, one action per step.
  7. 7How to check it's been done right.
  8. 8What to do if something goes wrong.
  9. 9The owner, and the date it was last reviewed.

Screenshots or a short screen recording help with anything done in software. Keep the language plain, and write the steps the way you'd explain them to a sensible new starter on their first day.

How to write one, step by step

  1. 1Ask the person who does the task to do it once while noting each step, or record their screen while they talk it through.
  2. 2Turn that into numbered steps. One action per step, each starting with a verb: open, check, send.
  3. 3Add the checks and the things that commonly go wrong. That's where the real know-how lives.
  4. 4Give it to someone who has never done the task and watch them follow it. Every place they hesitate is a step that needs rewriting.
  5. 5Agree an owner and a review date, then save it where everyone can find it.

Copy the template

Here's the same structure ready to use. Copy it into your own documents, or download the fillable PDF and type straight into it.

SOP template

STANDARD OPERATING PROCEDURE

Task name:
SOP owner:
Last reviewed:
Next review due:

PURPOSE
Why this task matters:

WHEN TO USE IT
What triggers this task:
How often:

WHO DOES IT
Done by:
If stuck, ask:

BEFORE YOU START
Logins, files and information you need:
- 
- 

STEPS
1. 
2. 
3. 
4. 
5. 
6. 
7. 
8. 

HOW TO CHECK IT'S DONE RIGHT
- 

IF SOMETHING GOES WRONG
Common problems and what to do:
- 

CHANGE LOG
Date / What changed / Who

Keeping SOPs up to date

SOPs fail quietly. A tool changes, a step gets skipped, and six months later the document describes a process nobody follows. Three habits prevent most of that: give every SOP a named owner, put a review date on it (every six or twelve months is usually enough), and make updating the SOP part of changing the process rather than an afterthought.

Keep them all in one place everyone can reach, such as a shared drive folder or your project management tool, with a simple index listing every SOP and who owns it.

Frequently asked questions

How long should an SOP be?

Usually one or two pages. If it's much longer, it probably covers more than one task and should be split.

Who should write SOPs?

The person who does the task, with someone else checking it's clear. When managers write SOPs for work they don't do themselves, the result tends to look tidy but miss the real steps.

Do SOPs need to be formal?

No. A short, clear document in plain language beats a polished one nobody reads. What matters is that the steps are right and someone owns them.

Need help getting organised?

Once your SOPs are written, they make it much easier to hand work to someone else. Our guide to outsourcing marketing, web and accounting explains how to do that cleanly, and our client onboarding checklist shows the kind of process we write down for every new client. Or book a call.

5d → 4h
Review time
−93%
Time to decision

See it in practice · FinTech

FinTech KYC review cut from 5 days to 4 hours

Read the story ›

Curious how your own site scores?

Run our free website audit. Simple report, about 10 seconds, no sign-up.

Run free audit
All articles