How to write an SOP for a small business
Most advice about standard operating procedures is written for companies with a documentation team. If you are an owner with six employees and a truck, the useful version is shorter and starts somewhere different.
Start with what already went wrong
Do not start with an inventory of everything your business does. That list is long enough to guarantee you never finish, and it puts the procedure nobody needs next to the one that would have prevented last month's claim.
Instead, list the last ten things that cost you money. A callback, a damaged floor, a part ordered twice, a customer who left a two star review. Each one is a procedure that either did not exist or was not followed. Write those first, in that order.
Write it at the length someone will read
The realistic ceiling is about seven steps. Beyond that, people stop reading and start skimming, and a skimmed procedure produces the same behavior as no procedure while giving you the false comfort of paperwork.
If a task genuinely needs fifteen steps, it is two procedures. Split it at the natural pause, usually where the work moves to a different location or a different person takes over.
Write in the order the work happens
Number the steps and put them in sequence. Do not group them by category, do not use headings, and do not put the reasoning inside the step. The reason belongs in one line at the top, so a technician who wants to understand the point can read it and everyone else can get on with the list.
Use the words your crew uses
If your techs call it the disconnect, write disconnect. Translating shop language into formal English makes a document that reads like it came from somewhere else, and it will be treated that way.
Record it by talking, not typing
Owners who know the work often stall at the blank page. The fastest route is to do the job while narrating it to your phone, or to walk a technician through it and record the conversation. Turning that recording into numbered steps takes about ten minutes and produces better procedures than writing from memory, because you notice the steps you actually perform rather than the ones you think you perform.
Take photographs while you write it
One photograph replaces a paragraph of description, and it removes the argument about what good looks like. Photograph the correct setup and, where it helps, the common wrong one.
Decide who has to read it, then prove they did
A procedure filed in a shared folder is not distributed. It is available, which is a different thing, and the difference matters the day someone asks whether a specific person was trained.
Assign each procedure to named people or to a role. Ask for an acknowledgement. Record the date. Keep the record attached to the version they saw rather than the current version, because procedures change and a signature against text that has since been rewritten proves very little.
Review when something goes wrong, not on a calendar
Annual reviews produce documents that are updated and unimproved. The useful trigger is an incident, a callback or a technician saying the procedure is wrong. When that happens, change it the same week and re-issue it for acknowledgement.
What to skip
Skip the cover page, the revision history table on the front, the scope and purpose sections and the approval signature block. They exist to make a document look official to an auditor who is not coming. They also add a screen of scrolling before the first useful instruction.
A reasonable first month
Ten procedures covering your ten most expensive recurring mistakes, each under seven steps, each acknowledged by the people who do that work. That is more documentation than most shops your size will ever have, and it took an afternoon a week.
Keep the record, not just the paperwork
Copy any procedure on this page into your own documents at no cost. What Intulix sells is the part underneath: a signed, dated, version locked record of which technician read which version, exportable as a PDF when someone asks. Start free or see pricing from $59 a month.