A standard operating procedure for a small business is one page: the outcome the process produces, the one person who owns it, what triggers it and how often, the number that proves it ran, the steps in order with who does each one, and the handoffs in and out. That is the whole format. It takes about thirty minutes to write with the person who will run it, and it is the difference between a business where the owner explains the same process every month and one where a new hire ramps in weeks. The template is free: download the SOP template and cadence map (PDF).
Most SOP advice is written for companies with a compliance department. This is for an owner-led service business between $1M and $10M, where the process exists and works, and lives entirely in two or three people’s heads.
Why most SOPs never get used
Owners who have tried this usually have a folder of documents nobody opens. They failed for one of three reasons, and the format fixes all three.
They were written as tasks, not outcomes. “Send the welcome email” tells a team member what to do and nothing about why, so when the situation changes slightly, they stop. “New client is onboarded: contract signed, kickoff booked, files received, first invoice sent” tells them what done looks like, and a capable person will get there even when step four does not apply.
They had no owner and no number. A process with no name on it is nobody’s job, and a process with no number is never known to have failed. Both are on the template’s first line for that reason.
They were too long. A twelve-page procedure is a training manual. Nobody checks a training manual while doing the work. One page, eight to twelve steps, in the place the team already works.
The one-page format
| Field | What goes in it | Example (client onboarding, service business) |
|---|---|---|
| Outcome | What is true when this process has run, in one sentence | Client is set up to be delivered to: contract signed, kickoff booked, files received, first invoice sent |
| Owner | One name. The person asked first if it slips | The operations lead |
| Backup | Who runs it when the owner is out | The business owner, for now; the next hire, by Q1 |
| Trigger and cadence | What starts it, and how often it runs | A signed proposal. Runs per client, about six times a month |
| The number | The weekly figure that shows it ran, and ran well | Days from signed proposal to kickoff held. Target: five |
| Steps | Eight to twelve, in order, each with who does it, the tool, and what it produces | See the filled example below |
| Handoffs | What arrives from the previous process, what leaves to the next | In: signed proposal from sales. Out: kickoff notes and file folder to delivery |
| Exceptions | The two or three situations where the steps change, and what to do | Rush client: kickoff within 48 hours, skip the intake form and take it live |
| Last reviewed | A date and a name | Reviewed quarterly by the owner |
The steps table is the part people expect. The first five fields are the part that makes it a process. Without them it is a checklist, and checklists get abandoned the first time reality differs from the list.
A filled example
Here is the steps section for the client onboarding process above, as a service business might write it. Yours will differ; the shape will not.
| Step | Who | Tool | Produces |
|---|---|---|---|
| 1. Countersign the proposal and file it | Ops lead | E-sign tool | Signed contract in the client folder |
| 2. Create the client folder from the template | Ops lead | Drive | Folder with the standard subfolders |
| 3. Send the welcome email with the intake form | Ops lead | CRM template | Intake form sent, logged in CRM |
| 4. Send the first invoice per the contract terms | Ops lead | Invoicing | Invoice sent, due date set |
| 5. Book the kickoff within five business days | Ops lead | Calendar link | Kickoff on both calendars |
| 6. Chase the intake form at 48 hours if not returned | Ops lead | CRM task | Form received or a call booked |
| 7. Brief the delivery owner the day before kickoff | Ops lead | Kickoff brief template | One-page brief in the folder |
| 8. Run the kickoff; capture goals, contacts, and constraints | Delivery owner | Kickoff notes template | Notes in the folder, client confirmed |
| 9. Hand off: post the kickoff notes and mark the client active | Ops lead | Project tool | Client active, delivery process triggered |
Nine steps, one page, three tools the team already uses. The number (days from signed proposal to kickoff) goes on The Scoreboard with the ops lead’s name next to it, and the process is reviewed in The Weekly the week it goes off track.
How to write one in thirty minutes
- Pick a process only you run. Look at your Ownership Map for a row with your name on it that you have explained to another person this quarter. That is the one.
- Write the outcome first, alone. One sentence. What is true when this has run. Then the owner, the trigger, and the number. Ten minutes.
- Walk it with the person who will own it. Talk through the steps out loud while they write them down. They will ask the questions a new hire would ask, which is exactly what the page needs to answer. Fifteen minutes. Recording it and letting AI draft the steps works well here; cutting the draft to a page is still your job.
- Run the 80/20 on the steps. Every step that exists because of one bad week two years ago, every approval that is really a habit, every report nobody reads: cut them. Keep the steps that produce the outcome. Five minutes, and it is where the margin lives.
- Put it where the work happens. Not a binder, not a wiki nobody opens. The project tool, the CRM, the shared drive the team is already in every day. Then have the owner run it once while you do not watch.
The test is not that the document exists. It is that another person ran the process last week and you did not check.
The three to write first
For an owner-led service business, the first three are almost always the same, because they are the three the owner is still doing.
- Client onboarding, because it is the process where the client meets the business instead of the owner.
- The sales-to-delivery handoff, because it is where scope, promises, and margin get lost between the person who sold it and the people who deliver it.
- Invoicing and collection, because it is the one nobody owns and it is the reason cash is a surprise.
Write those three in three weeks, one each, with the owner. Then the cadence map on page two of the template lists every process the business runs, its cadence, its owner, where it lives, and when it last ran, so you can see the ones still unwritten and the ones that should be retired.
Where AI fits
After the page exists, not before. An SOP written as outcomes and steps is exactly what an AI assistant needs to run parts of a process consistently, draft from it, and check work against it, because it is reading the same page the team reads. Stop re-explaining your process to AI every single time covers turning a written process into a file the model loads automatically, and the honest math on when that pays back. Before the page exists, AI pointed at the process produces faster versions of the improvisation.
The template
Download the SOP template and cadence map (PDF). Two pages: the one-page procedure with every field above, and the cadence map with the 80/20 audit. Free, no form. If you want your core processes written and set up with your team, that is a Sprint, and if you are not sure process is where you are narrowest, the Origin Score is twenty-seven questions, about five minutes, and shows where your business is narrowest right now.
