Most small businesses have the same standard operating procedure: ask the owner. It works when there are 2 of you. By 5 people it means the owner answers the same 12 questions every week, and the business stops the moment they go on holiday.

An SOP fixes that by writing the answer down once. The trouble is that most SOP templates you can download were designed for a factory or a hospital. They open with a document control table, a scope statement and a revision history, and by the time anyone gets to step 1 they have stopped reading.

This post gives you a shorter standard operating procedure template built for a team of 3 to 20, a worked example, and the handful of rules that decide whether an SOP gets used or ignored.

What an SOP is for, in a small business

A standard operating procedure is the written version of "this is how we do this here". It exists so that a task comes out the same way whoever does it, and so that the person doing it does not need to interrupt anyone to find out how.

In a large company SOPs are often about compliance. In a small business they are about 3 things:

You do not need an SOP for everything. You need one for every recurring task that more than one person does, or that one person does and nobody else could cover.

The SOP template

Copy this into a note and fill in each section. Most small business SOPs fit on one screen, and if yours does not, it is probably 2 procedures.

## [Task name]: how we do it

Owner: [the person who keeps this SOP up to date]
When: [what triggers this task, or how often it happens]
Takes: [roughly how long]
Last checked: [date]

## Why this matters
[1 or 2 sentences. What goes wrong when this is done badly?]

## Before you start
- [Access, tools or information you need]
- [Anything that must already be true]

## Steps
1. [Start each step with a verb]
2. [One action per step]
3. [Say what "done" looks like where it is not obvious]

## Decisions you can make
- [What the person is allowed to decide without asking]
- [Where the limit is, and who to ask beyond it]

## If something goes wrong
- [The 2 or 3 most common problems, and what to do about each]

## Done when
[How you know the task is finished and correct]

That is the whole template. It is deliberately missing a few things you will see elsewhere, like a purpose statement, a scope section and a definitions table, because at 3 to 20 people they add length without adding clarity.

A worked example

Here is the template filled in for a task most small businesses have.

## Sending a quote: how we do it

Owner: Priya
When: Within 1 working day of a customer asking for a price
Takes: 20 minutes
Last checked: September

## Why this matters
A quote that arrives after 2 days loses to whoever replied first,
and a wrong price is hard to walk back.

## Before you start
- The customer's name, email and what they asked for
- Access to the price list and the quote template

## Steps
1. Check the price list for every item they asked about.
2. Add delivery if the order is under the free-delivery threshold.
3. Fill in the quote template and save it as a PDF named
   "Quote - [customer] - [date]".
4. Email it with the standard covering note.
5. Create a follow-up task for 5 working days' time.

## Decisions you can make
- A discount of up to 10% on orders over the minimum.
- Anything larger, or any custom work, goes to Sam first.

## If something goes wrong
- Item not on the price list: ask Sam, do not estimate.
- Customer asks for a call: book one and note it on the task.

## Done when
The quote is sent, the PDF is in the customer's folder,
and the follow-up task exists with a date on it.

Notice what the example does. It says who owns the procedure, what triggers it, and exactly where the person's authority ends. Step 5 creates the next piece of work, which is how a procedure stops things falling through the cracks rather than just describing them.

How to write an SOP people follow

The template is the easy part. These rules decide whether anyone uses it.

Write it while you do the task. Not from memory. Do the job once with a note open and write each step as you take it. You will find 2 steps you always do and never think about, and those are exactly the ones a new person misses.

One action per step, starting with a verb. "Check the price list" is a step. "Make sure pricing is correct and everything is in order" is a hope.

Say where the authority ends. The "decisions you can make" section is the one most SOPs leave out, and it is the one that stops the questions. People interrupt the owner less because they cannot do the task and more because they do not know if they are allowed to decide.

Give every SOP an owner. Not the author, the person responsible for keeping it true. Procedures go stale when the process changes and nobody updates the page.

Have someone else test it. Hand the SOP to a person who has never done the task and watch, without helping. Every time they pause, the SOP is missing something.

Keep them where the work happens. An SOP in a shared drive folder nobody opens might as well not exist. Link it from the task or the routine it describes, so the procedure is one click from the work.

Which SOPs to write first

Do not try to document the whole business in a week. Start with the 5 procedures that cost you the most interruptions. For most small businesses those are some mix of:

Write one a week. In 5 weeks the questions you answer most often will have written answers, and the next hire will onboard in half the time.

Keeping SOPs in EvyOS

In EvyOS an SOP is a note: markdown, so the template above pastes in as it is, with folders to group them and a version history so you can see what changed and when. Notes in a shared workspace belong to everyone in it, so the whole team reads the same version.

Because notes link to other records, the SOP can sit next to the work it describes. The "Friday invoicing" routine links to the invoicing SOP. The quote task links to the quoting SOP. And if a contractor or customer needs to see one, a note can be shared by public link without giving them access to the workspace.

When the procedure is a recurring job, make the job itself a habit in the workspace. Each person gets their own record of how often it happens, so you can see that the Friday routine happens 5 weeks in 6 without asking anyone.

If you are building out onboarding at the same time, the onboard a new hire template plans a new person's first month, and it is a natural place to link your first SOPs from.

The short version

A small business SOP needs an owner, a trigger, numbered steps that start with verbs, the limits of the person's authority, and a definition of done. Write it while doing the task, have someone else test it, and keep it one click from the work it describes. Start with the 5 procedures that generate the most questions, and write one a week.

Start a workspace for your team, or see how EvyOS works for teams.