Notes

How to write an SOP for your one-person business (with a template)

A standard operating procedure sounds like something a factory needs. For a solo business it is simpler and more useful: a short page that says how a recurring job gets done, so you do not have to work it out again.

Why bother when you are the only one doing the work?

Three reasons come up again and again. First, memory is unreliable at the worst moments. The week you are ill, or juggling three bookings, is the week you forget to send the contract before the deposit. Second, a written process lets you improve it. You cannot fix a routine that only exists as a habit. Third, if you ever bring in a subcontractor, an assistant or a cover for holidays, the hard part is already done.

You do not need a manual. You need a handful of pages for the jobs you repeat most and the jobs where a mistake costs you money or goodwill.

Choose what to write first

Start by listing every task you did in the last two weeks. Mark the ones that happen more than once a month, and the ones you felt slightly anxious about. Those are your first candidates. For most service businesses the list looks like this:

Pick three. Writing twenty-five at once is how people give up in week one.

The shape of a good SOP

Keep it to one page. If it needs more, it is probably two procedures. Every SOP in this format has the same parts, which makes them quick to write and quick to read:

  1. Title and trigger. What is this called, and what sets it off? "New inquiry arrives" is a trigger.
  2. Purpose. One sentence on why it matters.
  3. Steps. Numbered, each starting with a verb. Five to ten is typical.
  4. Done when. A single line that tells you the job is finished.
  5. Notes. Exceptions, links, wording you reuse, things that went wrong before.

The "done when" line is the part people skip and the part that helps most. "Done when the client has replied with a date and the deposit invoice is sent" is far clearer than a feeling that you have probably handled it.

A template you can copy

SOP: [Name of procedure]
Trigger: [What starts this]
Purpose: [Why this matters, one sentence]
Time needed: [Minutes]

Steps
1. [Open the tool or file you need: link or location]
2. [First action, starting with a verb]
3. [Second action]
4. [Send or save, and where]
5. [Record it in the tracker]

Done when: [Observable finish line]

Notes
- [Exceptions, e.g. rush jobs, returning clients]
- [Wording to reuse: link to saved reply]
- [Last reviewed: date]

Copy it into a document, one file per procedure, and keep them all in one folder that is backed up.

A worked example: new inquiry

SOP: Reply to a new inquiry
Trigger: An inquiry arrives by form, email or message
Purpose: Reply fast and set up the next step
Time needed: 10 minutes

Steps
1. Read the whole message and note the date, place and budget if given.
2. Check the calendar for that date.
3. If free, reply using the saved "Available" reply. If not, use "Not available" and offer a referral.
4. Add the person to the client tracker with status "Inquiry".
5. Set a reminder for three days later to follow up.

Done when: A reply is sent and the tracker shows the next follow-up date.

Notes
- Reply within one working day where you can.
- Never quote a price in the first message without a scope.

Write it while you do the job

The easiest method is to write the SOP during a real task. Open a blank document, do the job as you normally would, and write each step as you go. Do not try to remember it afterwards; you will tidy it into a story that leaves out the awkward parts. The awkward parts are the point.

Afterwards, do a second pass. Cut anything that is explanation rather than action, move the explanation into notes, and check each step starts with a verb. Then test it: ask yourself whether someone competent but unfamiliar with your business could follow it. If you have a friend who will read it, better still.

Put placeholders where details change

Square brackets are a useful habit. Anything that changes per client, such as [client name], [session date] or [package], goes in brackets so you can see at a glance what needs filling in. It also stops you sending a message that still has last month's name in it. Search for "[" before sending anything that came from a template.

Keep them alive

An SOP that is out of date is worse than none, because it feels trustworthy. Build a tiny habit: whenever you catch yourself doing something differently from the page, change the page straight away. Once a quarter, put an hour in your calendar to read through them all. Delete the ones you no longer use. Add a "last reviewed" date in the notes so you can tell at a glance how fresh each one is.

Common mistakes

Where to go from here

Write your first three this week. Use them for a month, edit them, and then add the next three. In a quarter you will have a dozen pages that quietly take a lot of stress out of the week.

If you would rather start from finished drafts, the Solo SOP Pack has 25 editable one-page SOPs in exactly this format, and the free sampler gives you five to try. Either way, these are templates to adapt to your own business, not professional advice.