Most small businesses have SOPs somewhere. A binder in the back office, a shared drive folder called "Procedures", a Word document someone wrote three years ago before they left. The trouble is rarely that the procedures do not exist. It is that nobody opens them.

When that happens, the real process lives in people's heads. New hires learn by shadowing whoever has time. Two people do the same job two different ways. And when the one person who knows how month end works goes on vacation, everything waits.

This guide is for owners and operations leads in Niagara, Hamilton and across Ontario who want standard operating procedures that people actually use. It also matters for AI: you cannot sensibly automate or hand part of a task to an AI tool until you can describe how the task is done today.

Why most SOPs get ignored

Before writing anything new, it helps to know why the old ones failed. The same reasons come up again and again:

They are too long. A twelve page document for a task that takes ten minutes will not be read in the middle of a busy day.
They describe the ideal, not the reality. If the SOP says one thing and the team does another, people stop trusting it.
Nobody owns them. Software changes, a supplier changes, a step gets added, and the document quietly goes out of date.
They are hard to find. If it takes longer to find the procedure than to ask a coworker, people will ask the coworker.
They were written for an auditor, not for the person doing the work. Formal language and policy text bury the three steps that matter.

Good SOPs fix each of these on purpose.

Step 1: Pick the right processes to document first

You do not need to document everything. Start with a short list of processes that meet at least one of these tests:

It happens often, weekly or more.
Mistakes are costly, such as payroll, invoicing, customer refunds or safety checks.
Only one or two people know how to do it.
New staff need to learn it in their first month.
You are thinking about automating it or using AI to help with it.

For a typical 15 person business, that might be five to ten processes: quoting, onboarding a new client, processing supplier invoices, opening and closing procedures, scheduling, and handling a customer complaint. Leave the rest for later.

Step 2: Watch the work before you write it

The fastest way to write an accurate SOP is to sit with the person who does the task and watch them do it once, start to finish. Ask them to talk out loud as they go. Write down every click, every check and every "oh, and I always do this because the system sometimes gets it wrong".

Those small workarounds are the most valuable part. They are exactly the knowledge that walks out the door when someone leaves, and they are often where the process is broken and worth fixing.

If watching is not practical, a short screen recording with the person narrating works well too. You can turn the recording into written steps afterwards.

Step 3: Write it short, in plain language

A good SOP for a routine task fits on one or two screens. Use a simple structure:

Purpose: one sentence on what this process is for.
When to use it: the trigger, such as "when a new client signs the engagement letter".
Who does it: a role, not a person's name, so it survives staff changes.
What you need: logins, templates or information to have ready.
Steps: numbered, one action per step, starting each with a verb.
Done looks like: how the person knows the task is complete.
Owner and last reviewed date.

Compare "The accounts payable function shall ensure all supplier invoices are subject to appropriate review prior to remittance" with "Check the invoice amount matches the purchase order. If it is off by more than $50, send it to the office manager before paying." The second one gets followed.

Screenshots help for software steps. A photo helps for physical tasks, like how a finished workstation should look at close.

Step 4: Test it with someone new

Hand the draft to someone who has never done the task and ask them to follow it with no help. Every place they get stuck or ask a question is a gap in the document. Fix it, then test again if the changes were big.

This one step does more for quality than any amount of editing. It is also a quick way to find steps that only make sense to the person who wrote them.

Step 5: Put it where the work happens

An SOP is only useful if it is in front of the person when they need it. Some practical options:

Link the procedure directly from the tool where the task starts, such as a pinned link in your job management system or a bookmark in the shared browser at the front desk.
Keep one home for all procedures, with a simple naming pattern people can search.
For checklists that repeat, such as month end close or new client setup, run them as a live checklist each time instead of a document people read once.

That last point is where dedicated software can help. Once your process is written down and tested, tools built for running repeatable checklists can turn a static SOP into something your team ticks off as they go, with due dates, assignments and a record of what was done.

Disclosure: some links in this post are affiliate links. If you sign up through them, Adapting Services may earn a commission at no cost to you. We only mention tools we would suggest to clients.

Two that fit small teams well:

Process Street turns a procedure into a checklist you run each time, which suits recurring work like client onboarding, month end or equipment checks.
Trainual is built around documenting how your business runs and training new staff on it, which suits onboarding and role based knowledge.

Neither tool will write a good procedure for you. If the process is unclear or nobody agrees on how it should work, software just makes the confusion easier to find. Get the steps right first, then pick the tool.

Step 6: Give every SOP an owner and a review date

Procedures go stale when nobody is responsible for them. Assign each one to a role, and set a simple rule: review it every six or twelve months, and update it straight away whenever the software, supplier or regulation behind it changes.

A quick way to keep this honest is to ask, in your regular team meeting, "Did anyone hit a step this month that was wrong or missing?" Small, frequent fixes beat a big rewrite every few years.

How SOPs set you up for AI

Clear procedures are the starting point for almost any useful AI or automation project. When a process is written down step by step, you can see which steps are repetitive, rules based and low risk, and which need human judgement. That makes it much easier to decide where an AI tool could draft, sort, check or summarise, and where a person should stay in charge.

It also gives you a baseline. If you know how long a task takes and where it goes wrong today, you can tell whether a new tool actually made things better.

Many of the businesses we work with find that writing the SOP is half the improvement on its own. Steps get removed, duplicate checks disappear and the team agrees on one way of working, before any technology is involved.

A simple plan for the next month

Week 1: list your recurring processes and pick the top five using the tests above.
Week 2: watch or record each one being done, and note the workarounds.
Week 3: write short drafts and test each with someone new.
Week 4: publish them in one place, assign owners and set review dates.

That is enough to make a real difference to training time, consistency and how much depends on any one person.

Find out which processes to document first

If you are not sure which of your processes are worth documenting, fixing or automating first, start with our free Process Scan. It takes a few minutes, looks at how work moves through your business today and points to the areas where clearer procedures, and later the right tools, will help most.