On this page
Why SOPs fail
Most businesses that say they have SOPs have a folder.
The documents were written once, by the founder, on a weekend, and nobody has opened them since. The team still asks the founder how to handle a complaint, and quality still depends on who is working that day. A procedure only counts if the person doing the work follows it when nobody is watching. That takes a document written for that person, and an accountability system that makes following it the normal way to work.
- They are written for filing, not for the person doing the job.
- They describe the ideal process, not the one the team runs.
- They have no owner, so they go stale as soon as something changes.
- They cover the normal case and say nothing about exceptions, which is where people need help.
- Nothing checks whether they were followed.
Three places a process breaks
When I audit an operation, every leak sits in one of three places. Each one needs a different fix, which is why I never deliver documents alone.
- Leak
Information.
The right person does not see it in time. A procedure fixes this one.
- Leak
Authority.
Nobody is clearly allowed to decide it. A written decision right fixes this one.
- Leak
Behavior.
The rule exists and is not followed. Only the accountability layer fixes this one.
How I write a procedure
Every procedure I write has the same six parts.
- Purpose. One sentence on why it exists, so the reader can use judgment when the steps run out.
- Trigger. The event that starts it.
- Steps. Numbered, in the order they happen, in the words the team uses.
- Outcome. What done looks like, in a form someone else can check.
- Owner. One named person, with written permission to make the routine calls.
- Exceptions. What to do when the normal process does not apply, and when to escalate.
I write them inside the real workflow, test them with the person who will run them, and change them until that person can do the job from the page. The free SOP template uses this structure. If you would rather start from procedures already written, the AI-Ready Procedure Pack has the twelve a service business needs first, and the cleaning business SOP template page gives two of them away, written for a cleaning company.
The accountability layer
A procedure tells people what to do. The accountability layer makes it visible whether it was done. In practice that means five things.
A named owner and a date on every open item.
At a private lender, every payoff opens a release register entry with a 90-day deadline.
A check built into the work.
At a cleaning company, an end-of-job walkthrough against a written standard for each service type.
A control where the stakes are high.
A two-person verification, by callback, on every outbound wire.
A short scoreboard.
A few numbers, updated weekly, that show whether the system is working.
A weekly review.
What moved, what is stuck, what needs a decision.
Who owns what.
Six routine calls in a growing business. Switch from before to after and watch where each one lands once it has a written owner. A made-up team, so the names are roles.
| The call | Owner | When it comes to you |
|---|---|---|
| A new inquiry | OCOffice coordinator | Only a custom quote |
| A complaint | OLOperations lead | Above the written credit rule |
| A sick call | CCoordinator | In one daily message |
| A schedule change | CCoordinator | Never. It has a rule |
| The weekly scoreboard | OLOperations lead | Friday review. AI prepares it, a person checks it |
| A price change | YYou | Always. It stays yours |
One decision still routes to you, by design. The rest have a written owner and a written rule.
Writing the owner down is the authority fix. The scoreboard and the weekly review are what show whether the owner acted.
Procedures plus the layer that makes them hold.
- 90%
Drop in an owner's daily involvement at a cleaning company, with a procedure handbook for every service type, an end-of-job walkthrough and a labor-hour floor on every job.
- 40%
Faster approvals at a YouTube production operation running 60 to 80 videos a month across 20-plus channels.
- 95%
Of a private lender's servicing routine configured inside its loan platform, without a developer.
The detail is on the Results page.
Where AI fits
I use AI for drafting: a first version of a reply, a quote, a file review. A person approves at every gate that matters. A procedure that says "AI drafts, a named person decides" is still a procedure with an owner. The human in the loop AI guide shows where the person goes.
How it starts
With a 45-minute Operations Leak Audit. Bring the three things that still route through you. You leave with a one-page leak map and the one build I would do first. For the wider picture, read what a fractional COO does or how an engagement runs.
The same work, in any business
I build AI systems and automations for growing businesses in any industry, and I work beside founders as their fractional COO. Procedures and owners are where every one of those builds starts, because a system with no owner stops being checked.
See what I build and how I work, or how it runs at a private lender and a cleaning and home-services company.
