Insights

How to document your business processes so the work survives your best employee

A former CRA auditor on documenting SOPs so the work survives your best employee: what to write first, how to keep it simple, and why it lifts your firm's value.

---

Here is a test I run in my head when I visit a business for the first time. If the owner had to leave for a month, no phone, no email, what would break by Friday? In most small companies the answer is almost everything, because the business does not really run on systems. It runs on one or two people who carry the whole thing in their heads. That is a fragile way to own a company, and it is fixable.

I spent years as an auditor at the Canada Revenue Agency reading how businesses actually work versus how their owners described them. Now I run an operations firm and hold a Lean Six Sigma Black Belt. The single change that does the most good for an owner-run company is also the least glamorous. Write down how the work gets done, so the work survives the person who does it best.

Why an undocumented business is fragile

When nothing is written down, the knowledge of how to run the place lives in people. That feels efficient. Your best employee just knows how to close the month, handle the difficult client, quote the tricky job. Nobody needs a manual because Sarah has done it three hundred times. The problem shows up the day Sarah is sick, on vacation, poached by a competitor, or simply having a bad week.

An undocumented business has a few predictable weaknesses. Quality swings depending on who happens to be doing the work. Training a new hire takes months because it happens by osmosis, watching over a shoulder. Mistakes repeat because the fix lived in someone's memory and left with them. And the owner cannot step back, because the owner is the backup for every role that was never written down. This is the heart of owner-dependence, and it is the first thing a buyer, a lender, or a tired founder runs into.

What to document first

Do not try to document everything. That is how these projects die. You end up with a binder nobody opens and a team that resents the exercise. Start with the processes that earn their keep. I point owners at two buckets.

• Highest-volume work. The things your business does every day or every week. Order intake, invoicing, the core service you deliver, scheduling, the weekly payroll run. A small improvement to something you do fifty times a week pays for itself fast.
• Most painful when it goes wrong. The processes where a mistake costs you real money or a customer. A botched quote, a missed compliance filing, a shipment sent to the wrong address, a safety step skipped. These do not happen often, which is exactly why nobody remembers the right way under pressure.

If a task is both frequent and expensive to get wrong, document it this week. Everything else can wait. A useful way to find these is to ask your team a plain question. What do people keep coming to you to ask? Every repeated question is a process that lives in one head and belongs on paper.

How to capture a process without building a binder

The format matters less than most people think, and simple beats thorough almost every time. A written procedure that fits on one page and gets used is worth more than a forty-page manual that sits on a shelf. Match the format to the task.

• A checklist for anything with steps that must happen in order or must not be skipped. Opening the shop, closing the month, onboarding a client. Pilots and surgeons use checklists for a reason. They are fast to make and hard to argue with.
• A one-pager for a process that needs a little judgment. What the task is, who owns it, the steps, the common mistakes, and where to go when something is unusual. Plain language, the way you would explain it to a new hire over coffee.
• A short screen recording for anything on a computer. Talking through how you enter an order or run a report while you actually do it takes five minutes and captures the small clicks a written doc always misses. Free tools do this. The narration is the documentation.

Keep the language concrete. Write "phone the supplier before 2 p.m. so the order ships same day," not "coordinate with vendors in a timely manner." A good procedure tells a nervous new person exactly what to do. It is not a policy statement. It is a set of instructions you would trust a competent stranger to follow.

Who should actually write them

Not you. The person doing the work should write the procedure, because they know where the real steps and the real traps are. When an owner writes the SOP from memory, it describes how the job is supposed to work, which is often not how it actually works. The person on the floor knows the workaround, the exception that comes up every third Tuesday, the step that the official version skips.

This has a second benefit. When people write down their own work, they own it, and they tend to notice waste while they do. More than once I have watched someone documenting a process stop halfway and say, "actually, why do we do this step at all?" Writing the work down is often the first time anyone has looked at it straight on. Your job as the owner is to set the standard, ask for the draft, and review it. Not to write it alone.

Standard work, borrowed from Lean and sized for your shop

In Lean manufacturing there is an idea called standard work. It means the current best-known way to do a task, written down and followed by everyone, until someone finds a better way and updates it. It is not about turning people into robots. It is the opposite. When the routine parts of a job are settled and consistent, people stop reinventing them every time and get to spend their judgment on the parts that actually need it.

You do not need a factory to use this. A five-person accounting practice, a twenty-person trades company, a fifty-person distributor, all of them run on repeated processes that could be done the same reliable way each time. Standard work gives you three things a growing firm needs. A baseline, so quality does not depend on who is working. A training tool, so a new hire learns the proven way instead of a random way. And a starting point for improvement, because you cannot improve a process that changes every time you look at it. For a deeper build, our fractional COO work puts these systems in without adding a full-time executive to your payroll.

Keeping SOPs alive so they do not rot

Here is where most documentation efforts fail. Someone writes a stack of procedures, everyone feels good for a month, the business changes, and within a year the documents describe a company that no longer exists. A wrong procedure is worse than none, because it teaches new people the old way and quietly loses trust.

Keeping SOPs alive takes very little effort if you build in a habit or two.

• Store them where the work happens. A shared drive, a simple wiki, a folder everyone can reach. Not a printout in a drawer. If finding the procedure is harder than asking a coworker, people will ask the coworker and the document dies.
• Put a name and a date on each one. Someone owns each procedure. When that step changes, they update the doc same week. Ownership is what separates a living system from a dead archive.
• Fix it at the moment of friction. When a procedure is wrong or a mistake slips through, update the doc right then, while it stings. That is the cheapest and most honest time to improve it.
• Review the important ones once or twice a year. Not all of them, just the frequent and the costly. A short scheduled look keeps drift from piling up.

The payoff, in plain terms

Documenting your processes is unglamorous work, so it helps to be clear about what you get back. Hiring and onboarding get faster and cheaper, because a new person learns from a proven procedure instead of tying up your best employee for two months. Quality gets steadier, because the work is done the same reliable way no matter who is on shift. Your team gets more capable, because the knowledge is shared instead of hoarded, on purpose or by accident.

And the business gets less dependent on any one person, including you. That is worth money in real terms. A buyer pays more for a company that runs on systems than for one that runs on a founder who cannot take a two-week holiday. A lender sees less risk. And you get your evenings back, because the business no longer needs you to be the answer to every question. If you want a straight read on where you stand, our operations health check maps your most owner-dependent processes and where to start. You are always welcome to reach out and talk it through.

Frequently asked questions

How many SOPs does a small business actually need? Fewer than you think. Start with five to ten procedures covering your highest-volume and most-painful-when-wrong work. A focused handful that people use beats a hundred that nobody opens.

What is the difference between an SOP and standard work? An SOP is a written procedure for a task. Standard work is the Lean discipline of everyone following the current best-known method and updating it when a better one is found. Standard work is the habit that keeps your SOPs honest.

Should I use software to manage this? Not at first. A shared folder and a simple naming habit will carry a company of five to fifty people a long way. Buy a tool once your volume of procedures genuinely outgrows a folder, not before.

How long does it take to document a process? A checklist takes fifteen minutes. A one-page procedure takes an hour. A screen recording takes as long as doing the task once. The barrier is starting, not the time.