Construction SOPs —
If It Lives in Someone's Head, It's Not a System

I used to have a site superintendent who knew everything. And I mean that without any exaggeration — this guy was an encyclopedia of operational knowledge specific to our business.

He knew where every permit was filed and which filing system we used for which municipality. He knew which inspectors were particular about paperwork and which ones you could hand a coffee to and have a conversation with while they worked. He knew our default rough-in specs for half a dozen different project types, which suppliers gave us the best lead times on which materials, and — critically — who to actually call when an order came in wrong, because he'd learned through experience that the general number got you nowhere and the right name on the loading dock got you results in an hour.

He was irreplaceable. I thought that was a compliment.

Then he left. Not badly, not dramatically — he got an opportunity he couldn't pass up and he gave me fair notice and he was professional about it right to the end. And in the two weeks that followed, I found out exactly how much of my business existed exclusively inside one person's skull. The chaos that followed cost us real money and real time on active projects. New questions that should have had obvious answers went unanswered because nobody knew where to look. Processes that had run smoothly for years suddenly required improvisation because the person who'd been running them had taken the logic with him when he walked out the door.

All of it could have been avoided with one thing.

The Difference Between Knowledge and a System

There's a version of "experienced team" that most contractors are proud of and most contractors are also dangerously dependent on — the version where the knowledge lives in people rather than in the business. Your lead hand knows how to run the framing sequence. Your office manager knows which clients need extra communication and which ones prefer to be left alone until there's something to report. Your estimator knows the adjustments to make for certain soil conditions or certain municipalities or certain subcontractors whose quotes always run light.

That knowledge is valuable. The problem is where it lives.

When knowledge lives in people, the business is only as stable as the people who hold it. And people leave. They get sick. They get better offers. They retire. They have bad years and you have to let them go. Every one of those events, in a business where the knowledge hasn't been transferred out of their heads and into a documented process, is a crisis. Not a transition — a crisis. Because what walks out the door with that person isn't just their labour. It's the institutional knowledge that makes the operation function, and rebuilding it from scratch is expensive in ways that are hard to quantify until you're doing it.

What SOPs Actually Are — And What They Aren't

Standard operating procedures have a reputation problem. The phrase sounds corporate. It sounds like something a franchise operation produces to constrain the creative decision-making of the people actually doing the work, or like a binder that lives on a shelf and gets pulled out only when something goes wrong badly enough to require documentation of who knew what when.

That's not what I'm talking about.

What I'm talking about is writing down the things that already happen on every project, every time, in a way that someone new could follow without needing to call the person who used to do it. The permit filing process. The material procurement steps, including who approves the order and who verifies the delivery. The inspection sequence for each phase of a build, including what gets documented and where it goes. The communication cadence for clients — when do they hear from us, through what channel, and who owns that relationship on a given project. Even something like a callback is a process worth documenting; the difference between a client who walks and a client who stays is usually a system around callbacks, not a one-off response that depends on who happens to pick up the phone. The sales conversation belongs on that list too — a sales process only the owner can run is the same hostage situation with a nicer name.

None of that is glamorous. Nobody celebrates the day you finish your inspection checklist template or write out your material ordering process in plain language for the first time. But the absence of those documents is what turns a staff departure or a new hire's onboarding into a months-long disruption that costs you real money and real client relationships. A one-page first-week checklist is the cheapest place to start, and it's the first of the three changes that cut rework from my new hires.

SOPs aren't about distrust. They're not a signal that you think your people are replaceable or that you don't value their judgment. The best operators I know have both — highly capable people and well-documented processes. The processes don't constrain the capable people. They free them up to apply their judgment to the decisions that actually require judgment, instead of spending time reconstructing institutional knowledge that should have been written down years ago. A documented process is also how you get standards everyone on the crew knows instead of a different version of the job depending on who showed up that morning.

The Single Points of Failure You're Not Seeing

Here's the exercise I give to every business owner I work with who pushes back on documentation: map out the ten most critical recurring processes in your operation — the ones that, if they went wrong or didn't happen at all, would have a direct negative impact on a project or a client relationship. Then, for each one, answer a single question: if the person who currently runs this process left tomorrow, how would the next person know how to do it?

Most people get through two or three before they start to feel uncomfortable. By the time you've gone through the full list, the picture is usually pretty clear. There are single points of failure everywhere, and they're concentrated exactly where you'd expect them to be — in the most experienced people, the ones who've been around longest and who run things smoothly enough that nobody ever thought to write down how they do it because there was never any obvious reason to. The same undocumented-risk problem shows up in the security habits that quietly protect a small trades business — the password nobody wrote down, the invoice-verification step that lives only in one person's routine.

The reason to write it down is not because anything is going wrong right now. The reason to write it down is because everything running smoothly is exactly the moment when you have the capacity to do it, and the moment after a key person walks out the door is exactly when you no longer do. Growth exposes the same gap the hard way: the standard that lived in your head worked fine until the team got big enough that quality started slipping through the cracks proximity used to cover.

The same trap shows up with decisions, not just knowledge. When every call still routes through one person, you've built a single point of failure out of judgment instead of paperwork — which is the slow way the owner becomes the bottleneck without ever meaning to.

How to Actually Build the Documents

The biggest obstacle to building SOPs in a small trades business is that nobody has time to do it and it's never urgent enough to prioritize. There's always a project that needs attention more immediately, a client call that needs to be returned, a delivery that needs to be verified. Documentation lives permanently in the "important but not urgent" category, which in most small businesses means it never gets done at all.

The approach that actually works is not carving out a week to document everything at once — you will never find that week and even if you did you'd produce documents that are too abstract to be useful because you're writing them from memory rather than from observation. The approach that works is documenting one process at a time, while the process is actually happening.

Ask your superintendent to walk you through how they handle a permit application, out loud, while they're doing it. Write it down as they talk. Ask your estimator to narrate their process while they're building a quote. Record it if that's easier. The person doing the work knows the steps, the shortcuts, the decision points, and the things that can go wrong — your job is to capture that knowledge while it's being demonstrated and turn it into something that exists outside their head.

One process a week. Twelve weeks. You have twelve documented processes, which is more than most trades businesses have ever had, and you've done it without stopping the operation to do it.

The Return You Don't See Until You Need It

Building out our standard operating procedures was one of the most unglamorous stretches I've put into this business. There were no milestones to celebrate, no visible progress on a job site, no client who called to say they appreciated the fact that I'd documented my material verification checklist. The return on that investment is invisible until the moment you need it — and then it's the most obvious thing in the world.

The first time a new hire ran a project from start to finish without needing to call me six times a day, I understood what I'd built. Not just the checklist — the freedom. My freedom to be working on the next project or the next client relationship or the next thing the business needed from me, instead of being the human answer key for a process that should have been written down three years earlier. Documented processes are also what let you finally delegate without it falling apart — you can hand work to someone else because the work no longer lives only in your head.

The Bottom Line

If your business is running on the knowledge inside a few key people's heads, you don't have systems — you have an arrangement that works until it doesn't, and the moment it stops working will almost certainly be a moment when you have the least capacity to absorb the disruption.

Document the boring stuff. The permit process, the ordering procedure, the inspection sequence, the client communication cadence. Write it down while things are running smoothly, with the people who currently run those processes, in enough detail that someone new could follow it without guessing. It will take longer than you want and feel less urgent than everything else on your list. Do it anyway. And do it before you go shopping for a platform to manage it all — more software won't fix a people problem, and it can't document a process you haven't defined.

The first time you need it, you'll understand exactly what it was worth.

If your business has more knowledge in people's heads than in documented processes — and most trades businesses do — that's one of the most practical things we work through in coaching. Getting it out of your head and onto paper is one of the moves that breaks the pattern of staying small. The fix is usually less complicated than people expect once you actually start building it. Here's how my contractor coaching works.