Building systems and SOPs for an owner-run business

Do not try to document everything. Start with the processes that cost money when they are missed or done inconsistently. For most contractors and small service businesses that list is short, and it is usually the same.

A simple test: for one week, write down every question someone asks you that only you can answer. The processes behind those questions are your first SOPs.

• Quote-to-invoice: how an enquiry becomes a quote, a job, an invoice and a payment
• Purchasing: who can order what, from whom, and how costs are allocated to a job
• Variations: how a change in scope is priced, agreed in writing and invoiced
• Job close-out: snag list, sign-off and the final invoice going out the same week
• Staff onboarding: what a new person needs on day one and in the first month
• Month-end: capturing costs, following up debtors and reviewing the numbers

A good standard operating procedure fits on one page. If it needs more, it is probably two processes. It is written as steps in the order they happen, and each step has a named owner: a role, not just whoever is available.

It is written in the words your team uses on site and in the office, not in management language. It ends with a short checklist that can be ticked on a phone, because most SOPs are used in the middle of the work, not at a desk.

A good SOP also says what to do when the job does not fit the procedure. Real work has exceptions. The SOP should name who decides in those cases, so the exception does not land back on the owner every time.

An SOP is not finished when it is written. It is finished when someone other than the owner has used it on a real job without needing to ask. Until then it is a draft.

During the engagement your team runs each procedure on live work. We watch where people get stuck, where a step is missing, and where the written process does not match how the work really happens. Then the page is fixed and run again. After a few rounds most SOPs stop generating questions, which is the sign they work.

This is also where templates help. A quote template, an onboarding pack or a job start-up checklist gives each SOP a ready-made tool, so the procedure and the paperwork match.

Systems fail when they are handed over on paper alone. The people who own each step need to understand why the step exists, not only what to do. That is what keeps a procedure from quietly drifting back to the old way.

Training is part of the handover. It covers the procedures each person owns, the checklists they use, and what to do when something does not fit. For teams that also capture costs and invoices, it can be combined with training on processing the accounts, so the records the SOPs produce are captured correctly.

When someone values a small business, one of the first questions is how much of the earnings depend on the current owner. Documented systems, trained staff and consistent records reduce that risk. A buyer can see how the business runs and believe it will keep running after the sale.

The same applies when bringing in a partner or planning succession. Written procedures make the business easier to understand, easier to hand on, and easier to trust. Keeping them current matters: a short review whenever prices, suppliers, staff or regulations change keeps the system true to the business, rather than a document that describes how things used to be.