How to Create Standard Operating Procedures for a Small Business
SOPs do not have to be binders nobody reads. A lightweight way to document how your business runs, so work gets done the same way without you.
A standard operating procedure is a written description of how a task is done in your business. The phrase conjures up corporate manuals, but the idea is simple: get the method out of someone's head and onto a page, so the task does not depend on one person being there.
Why bother
- You can delegate. If only you know how to do something, only you can do it.
- New staff get up to speed faster.
- Quality is consistent. Customers get the same experience whoever serves them.
- Vacations and sick days stop being emergencies.
- You can improve. You cannot refine a process that exists in five different versions.
- You can automate. A process must be defined before software can take it over.
Which tasks to document first
Do not try to write down everything. Start where the payoff is clearest:
- Tasks you want to hand off.
- Tasks only one person knows how to do.
- Tasks that go wrong often.
- Tasks done rarely enough that people forget, such as month-end or seasonal jobs.
- Tasks every new hire has to learn.
Pick three. Finish those before starting more.
A simple format
One page per procedure is the target. Include:
Title. What the task is.
Purpose. One sentence on why it matters. People follow steps better when they know the reason.
When it happens. What triggers it, or how often.
Who does it. A role, not a name.
What you need. Tools, logins, materials.
Steps. Numbered, one action each, starting with a verb.
What good looks like. How to know it was done correctly.
What to do if something goes wrong. The two or three most common problems and who to ask.
Writing the steps
Do the task while writing. Do not write from memory; you will leave out steps that have become automatic.
Be specific. "Send the confirmation" assumes knowledge. "Open the booking in the calendar, click Send Confirmation, check the customer's email is correct" does not.
One action per step.
Use screenshots or a short screen recording for software tasks. A two-minute video is often quicker to make and easier to follow than a page of text.
Include the judgment calls. "If the customer is outside our service area, offer the remote option. If they decline, refer them to..." These are the parts people most need written down.
An example
Responding to a new website inquiry
Purpose: a quick, helpful reply makes it far more likely the inquiry becomes a customer. Trigger: a new inquiry notification arrives. Owner: office coordinator.
- Open the inquiry in the CRM within 15 minutes of the notification.
- Check the ZIP code against the service area map.
- If outside the area, send the "Out of area" template and mark the lead as Lost: Area.
- If inside the area, call the customer on the number provided.
- If they answer, ask the four qualifying questions on the call sheet and book a site visit.
- If they do not answer, leave the standard voicemail and send the "Tried to reach you" text.
- Set the lead stage to Contacted and add a follow-up task for the next working day.
Done correctly when: the lead has a stage, a note and a next action with a date.
Test it
Hand the procedure to someone who has never done the task and watch them follow it without help. Every question they ask is a gap in the document. Fix it and try again.
Keep them somewhere people will look
A procedure nobody can find is useless. Store them where your team already works: a shared drive folder, a wiki, your project tool. Use clear titles and link to them from wherever the task begins.
Keep them current
Out-of-date procedures are worse than none, because people stop trusting all of them.
- Put a "last reviewed" date on each.
- Make the person who does the task responsible for updating it.
- Review when something changes: new software, new prices, a mistake that revealed a gap.
- Skim everything twice a year.
Checklists for the short version
Not every task needs a full procedure. For routine work that experienced staff already know, a checklist is enough: opening up, closing down, preparing for a job, handing over a completed project. A checklist does not explain how. It makes sure nothing is skipped.
From procedure to automation
Once a process is written as clear steps, look at which steps are pure routine: sending a template, updating a field, setting a reminder. Those are candidates for automation. The steps involving judgment stay with people. See what business process automation is.
