Writing Down How Your Restoration Company Actually Works

Published by
Throne of Profit Editorial

Reviewed by
William Hassell
Founder & Chief Editor, Throne of Profit

Ask a restoration owner how a water job should run and you'll usually get a clear, confident answer — extract, set equipment by the calc, monitor daily, document moisture, adjust, demo only what's wet. Then watch three different crews run three water jobs and you'll see three different jobs. One crew documents beautifully. One under-sets air movers because the truck was low. One skips the daily readings when they're busy. The knowledge of how to run a good job lives in a few people's heads, which means your quality is only as reliable as which of those heads shows up.

That's the quiet risk in a restoration company. The work is technical, weather-driven, and urgent, and the difference between a clean file and a denied claim comes down to steps done in order, on time, and documented. When those steps aren't written down, every new hire relearns them by trial and error, and every job rides on the individual.

   HOW THE JOB ACTUALLY RUNS

   the "right way"
        │
        ├─ in your head + best techs → great job IF they show up
        ├─ written down as an SOP    → same job, every crew, every time
        └─ nowhere                   → reinvented per job → quality swings

Owner symptoms

• Job quality and documentation swing depending on which crew or lead is assigned.

• New hires take months to get up to speed because there's nothing to hand them.

• You get pulled onto jobs to fix or check things only you seem to know how to do.

Why this happens

Restoration companies grow fast off of storms, referrals, and hustle, and the founder usually is the process. Everything — how to scope a fire job, how to set a drying chamber, what the file needs to survive an adjuster's review — lives in the owner's judgment and a couple of trusted leads. It works until you add crews faster than you can personally train them. Then the knowledge doesn't transfer; it dilutes. Each new tech copies whoever trained them, good habits and bad, and the "standard" quietly becomes whatever that day's crew remembers to do.

Common mistakes

• Keeping the process in your head, so it can't be taught, checked, or scaled.

• Confusing SOPs with a binder no one reads — long documents written once and never used on an actual job.

• Documenting the easy steps, not the judgment — writing down "set air movers" but not how to decide how many.

• Writing SOPs from theory instead of from how your best crew actually works.

• Never updating them, so they drift out of sync with how the work really gets done.

Business consequences

When how-the-work-runs isn't written down, every job carries hidden risk: incomplete documentation that weakens the claim, inconsistent drying that invites callbacks and mold complaints, and equipment set by feel instead of by the moisture calc. Training stays slow and expensive, and the owner stays trapped as the quality-control department. The owner who documents the real process gets consistent files that hold up with adjusters, crews that ramp in weeks instead of months, and the freedom to be off a job without it slipping. The work stops depending on who shows up.

How experienced operators think about it

They treat a written procedure as a way to move judgment out of a few heads and into the whole company. The goal isn't a fat manual; it's a short, usable checklist for each job type — water, fire, mold — that captures the steps that must happen, in order, with the few decisions that actually matter flagged. They build the SOP by watching their best crew work and writing down what that crew does, not what a certification course says. And they treat it as living: when a job goes sideways, the fix goes into the procedure so the next crew doesn't hit the same wall.

Practical actions

1. Start with one job type — usually water — and document the flow end to end: intake, scope, extract, set, monitor, dry, verify, close.

2. Write it from your best crew, not from theory. Shadow them, ask why they do each step, and capture the reasoning behind the judgment calls.

3. Make it a checklist, not an essay. If a crew can't use it on-site from a phone, it's too long to survive a real job.

4. Flag the decisions that matter — equipment counts, moisture targets, what triggers demo, what the file must contain — instead of only the obvious steps.

5. Put it where the work happens. Tie each SOP to the job so following it is the path of least resistance, not extra paperwork.

6. Update it when reality changes. Review after a callback or a denied claim and fold the lesson back in.

Questions every owner should ask

• If my best lead quit tomorrow, could a new crew run a job to the same standard?

• Is our "standard process" actually written down, or does it live in a few people's heads?

• When a job goes wrong, does the lesson get into the procedure — or just into that one crew's memory?

Frequently asked questions

We're too busy running jobs to stop and write SOPs. Where do we even start?
Don't try to document everything at once — that's why binders die. Pick your highest-volume job type, usually water, and capture just that flow the next time your best crew runs one. Have someone follow them, note each step and the reasons behind the judgment calls, and turn it into a one-page checklist. You're not inventing a process; you're writing down the one you already run well. One good SOP that crews actually use beats a complete manual nobody opens.

Won't documented procedures make good techs feel like robots?
Good SOPs do the opposite. They lock down the steps that shouldn't vary — documentation, safety, what the file needs — so your techs' skill goes where it matters: reading a structure, adjusting a drying plan, solving the odd problem. A checklist handles the parts that should be automatic so judgment is spent on the parts that aren't. Experienced techs usually welcome it, because it stops them from getting blamed for steps no one ever told them were required.

Related articles

• Running a Profitable Restoration Company — the pillar.

• Choosing Restoration Job Software Your Crews Will Use — where SOPs get enforced in the field.

• Building the Plumber and Property Manager Referral Network — consistent work is what keeps referrals coming.

• Why Jobs Take Longer Than You Quoted — the general problem SOPs help contain.

• Where Time Leaks on a Typical Job — the step-level leaks a procedure catches.

Every business has more decisions than time

Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.

Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.

Explore Throne of Profit