One Documented Process Saves 240 Hours

If you've explained how your shop does something twice, you're going to explain it a hundred times. Every one of those explanations is time the person who knows best isn't spending on paying work. Write the process down once and it stops. The proposal that gets built the same way every time, the permit that gets closed out the same way, the supplement packet that gets filed right whether or not it's Friday at nine at night. One well-chosen process, written down and run the same way every time, gives your office back something like 240 hours a year, six full weeks, and it stops walking out the door when your office manager does.

There's an old rule from a coaching methodology that stuck with me. If you've explained something twice, write it down. The third explanation is a system failure. It sounds obvious until you actually count how many times a week your shop re-figures out things it already knows how to do.

What does keeping it all in your head actually cost?

A few costs, and they compound quietly.

The explanation tax. Every process that lives in a head instead of on a page needs a live person to hand it over. Usually that's you, or the one office person who "knows how we do it." You stop what you're doing to walk the new hire through how you price a re-roof, how the warranty registration gets submitted, which customers get called twice. Every hire, the tax goes up. Your day fills with teaching instead of running the shop.

The inconsistency cost. Taught out loud, a process comes out a little different every time. Five people quoting five different ways. Two techs filing supplement paperwork, one thorough, one sloppy, and the sloppy one quietly leaves money on the table on every storm job. Nobody can trace the errors to a cause, because there's no standard to measure against. There's just "how so-and-so does it."

The departure risk. When somebody leaves, everything they carried in their head leaves with them. Your office manager quit in March and took with her the half-dozen procedures that were never anywhere but between her ears, and you've been reconstructing them ever since, finding the gaps only when something breaks. In a small shop, most of how the place runs sits in two or three people. That's not a stable way to run anything.

Add the three up and, for a shop your size, you're looking at real five-figure money a year in wasted hours, redone work, and knowledge you had to rebuild from scratch.

Why doesn't every shop just write it down?

Because it feels slow. Writing a process down takes forty-five minutes. Explaining it takes ten. The math looks like it favors talking, until you multiply by the twenty times you'll explain it this year. Forty-five minutes that kills twenty future explanations saves you five hours. The payback is six to one. You just never feel it, because it's spread across months.

Because "we're too small." Owners think documented procedure is corporate overhead, something a 500-person company needs and a twelve-person shop doesn't. Backward. The fewer heads your knowledge lives in, the more it matters that it's written down. Fragile knowledge needs a backup more than distributed knowledge does.

Because nobody owns it. A procedure written once and dropped in a shared folder goes stale in six months. The way you actually do it moves on; the document doesn't. Now it's wrong, which is worse than empty. A new hire follows it and does it the old way. Documentation without an owner and a review date is just an artifact.

What should you write down first?

Not everything. The returns fall off a cliff fast. Write down the handful of processes that get explained most often, run most frequently, and hurt most when done wrong. For most shops that's five to eight. Here's where they usually land:

Process to document first	Why it makes the list
Turning field notes into a proposal	Run daily, explained to every new estimator, and the source of your margin
Estimate follow-up (day 3 / 10 / 30)	High-dollar, easy to skip, and the single biggest leak in most shops
Permit pull and close-out	Done wrong, it stalls a job and risks a fine
Warranty and supplement paperwork	Real money left on the table when it's filed sloppily
Invoicing and AR follow-up	Directly your cash flow; drifts the moment the office gets busy

Do those and you've covered most of the value. Try to document all fifty and you'll maintain none.

The format doesn't need to be fancy:

• What is this? One sentence.
• When does it happen? What kicks it off.
• The steps. Numbered, specific, in order.
• Who owns it? One name, not "the office."
• Last checked. A date, looked at every quarter.

If a new hire can follow it and get an acceptable result without asking anyone, it works. If they can't, it needs a fix, and every fix makes it better.

How do you get it written without adding another job to your night?

You don't sit down and type a binder. You talk each process through once, the way you'd walk a new hire through it, and those words get turned into a written procedure you edit instead of author. The whole set of five to eight goes from a couple of days of writing to an afternoon of reviewing. And here's the part that matters after it's written: the procedure doesn't just sit there. The same steps run the same way every time, on the third proposal of the night as reliably as the first, without forgetting the supplement paperwork because it's late and everyone's tired. The document stops being a thing you hope people read and becomes the way the work actually gets done.

That's the whole game. The shop that keeps its money and its nights isn't the one with the best memory. It's the one that only had to figure each thing out once.

Start this week with the process your crew asks about most. Spend thirty minutes writing it down. Next time somebody asks, send the page instead of the speech. That one document will save you four to six hours over the next year, and prove the model for the other seven.