SOP template for SMEs: how to write procedures people actually follow
Most growing businesses have tried to write standard operating procedures at least once. The usual result is a folder of long documents, written in a burst of enthusiasm, that nobody opens after the first month.
The problem is rarely the template. It is the approach: too many procedures, too long, written by the wrong person, stored in too many places and never used in training. This guide sets out a simpler method and a one-page template that works for small and medium businesses.
Why SOPs matter more than they seem
Written procedures do three jobs that are hard to do any other way.
- They let the business run without the owner. If only one person knows how to run payroll or approve a large order, the business stops when that person is away.
- They make training faster and more consistent. New staff learn the current way of doing things, not whichever version their colleague remembers.
- They add value when you raise money or sell. Buyers and investors look for a business that does not depend on its founder. Procedures are part of the evidence.
For family businesses there is a fourth job: procedures move knowledge from the founder's generation to the next in a form that does not depend on who asks whom.
Step 1: choose the 10 processes that matter most
Do not try to document everything. Start with the 10 processes the business depends on most.
A quick way to find them is to walk through a typical month: selling, delivering, purchasing, invoicing, collecting payment, hiring, paying staff and closing the month. List every process you touch, then rank them by the damage done if they go wrong.
Processes that usually make the top 10 include:
- taking and confirming a customer order,
- raising a quote and an invoice,
- chasing overdue payments,
- raising and approving a purchase order,
- receiving goods and checking them against the order,
- running payroll and paying statutory contributions,
- onboarding a new employee,
- the month-end close,
- handling a customer complaint, and
- backing up key data.
Your list will differ. A service business may have no goods received; a manufacturer may add a quality check at each production step. The point is to start with ten, not fifty.
Step 2: use one short template
Every procedure should follow the same structure, so staff know where to look. Keep each one under two pages; one page is better.
Here is a template that works for most SMEs:
| Section | What to write |
|---|---|
| Title and ID | A plain name ("Raise a purchase order") and a reference number (e.g. PRC-02). |
| Purpose | One sentence: why this process exists and what goes wrong without it. |
| Trigger | What starts the process: a customer email, the first working day of the month, stock below a reorder point. |
| Owner | The role responsible for the process being done correctly. One role, not a team. |
| Steps | Numbered steps, each starting with a verb. Five to fifteen steps is typical. |
| Tools | The systems, files or forms used, with links. |
| Checks | How you know it was done right: an approval, a reconciliation, a second signature. |
| Common mistakes | Two or three errors people actually make, and how to avoid them. |
| Version and review date | Version number, date of last change and next review date. |
The "common mistakes" section is the one most templates leave out, and often the most useful. It captures the knowledge that usually lives only with experienced staff.
Step 3: write while doing the task
The best procedures are written by the person who does the work, while they are doing it. Ask them to record each step as they go, adding screenshots where a system is involved. A manager or the process owner then edits it for clarity.
A few writing rules keep procedures usable:
- Start every step with a verb. "Check the delivery note against the PO", not "The delivery note should be checked".
- One action per step. If a step has "and" in it twice, split it.
- Name roles, not people. "Accounts assistant", not "Mei Ling". People move; roles stay.
- Put numbers in. "Invoice within 2 working days of delivery" is a standard; "invoice promptly" is not.
- Show decisions clearly. "If the order is over the approval limit, send it to the operations manager. Otherwise, approve it."
Step 4: store everything in one place
A procedure nobody can find does not exist. Keep all SOPs in one shared folder or wiki, organised by function: finance, sales, operations, people.
Three rules make the library trustworthy:
- Every procedure carries a version number and review date.
- Only the process owner can edit it. Others can suggest changes.
- Keep a register. One list of every procedure, its owner, its version and its next review date. When the register and the folder disagree, the register is wrong and gets fixed.
Step 5: use procedures in training
This is the step that decides whether SOPs survive. Add the relevant procedures to every new hire's onboarding checklist. The new hire performs each task once under supervision, then signs it off.
Two good things happen. New staff learn the right way first time, and every new hire tests the procedure. If they get stuck, the procedure is unclear and gets improved.
Step 6: test owner independence
Once the top 10 procedures exist, test them. The owner or founder steps back for one week, then two, then four. During each period, log every question that needed the owner. Each one becomes either a new or improved procedure, or a decision that is delegated with a clear limit.
This test is often uncomfortable in a family business, because it shows how much depends on one person. It is also the most direct way to reduce that dependence.
Step 7: review every year
Procedures go out of date when tools, suppliers or rules change. Put a review date in the calendar for each one, update it when something changes, and retire procedures that are no longer used. A day a year per process owner is usually enough.
What "good" looks like
When this is working, you should be able to say:
- the 10 most important processes each have a one-page procedure in the standard template,
- every procedure is in one place, with an owner, a version and a review date,
- the last two hires signed off their procedures during onboarding, and
- the business has run for two weeks without the owner with no major issue.
Where Mula OS fits
Standard operating procedures are one of the 22 areas in Mula OS's Corporate Readiness Assessment, under Stage 1 (Operate). The assessment asks four questions about them, covering how many processes are documented, their quality and ownership, their use in training, and how long the business can run without the owner, and tells you whether SOPs are among your top 3 priorities.
If they are, the Mula OS SOP Library workbook, part of Mula OS Operate, includes an SOP template, a starter set of process maps and an SOP register with owners and review dates.
Take the free Corporate Readiness Assessment to see where procedures rank among your priorities.