How to Reduce Restoration Claims Before They Happen

Nate Jones, CPCU · Founder, Restoration Guard Insurance

Published July 17, 2026 · Reviewed by Nate Jones, CPCU

A worker prying rotted siding and sill boards from a weathered wood structure

There are two ways to lower the claims on a restoration business, and owners tend to talk about only one of them.

The one everyone talks about is prevention — do the work well enough that fewer things go wrong. That is real and it matters. But there is a second one that almost never gets named, and it is at least as important: make sure that when something does go wrong, the job reads as one that was done carefully and written down as it happened, rather than as a story the other side gets to tell without you in the room. The first kind of work lowers how often a claim happens. The second kind lowers how much a claim costs once it does. Both are won on ordinary jobs, long before anyone knows which job was the one that mattered.

The claim you prevent never files itself

Here is the frustrating thing about prevention: it is invisible. The claim you stopped from happening does not appear anywhere. It is not on your loss run, it is not in your record, and nobody sends you a note thanking you for the dispute that never started. You did the containment right, the moisture came out on schedule, the clearance was clean, and the job simply closed. From the outside, that is indistinguishable from luck.

That invisibility is why prevention gets under-invested in. The habits that produce it feel optional in the moment, because their entire payoff is an absence — the absence of a phone call months from now. But the businesses with short, quiet loss runs are almost never the lucky ones. They are the ones that built the boring habits and kept them on the days it felt unnecessary, which is most days.

So the first move is to stop thinking of prevention as something you do on the risky jobs. The risky jobs already get your attention. Prevention is what you do on the ordinary ones, precisely because you cannot tell which ordinary one is going to come back.

Every ordinary job is a file you might have to open

The claim that hurts a restoration business rarely comes from the job that looked dangerous going in. It comes from a routine one, months later — a buyer retests a house, a new owner finds a problem, an insurer on a later loss asks who did the earlier work. Suddenly a job you barely remember is the one you are answering for.

What decides how that goes is not how well you remember it. It is what you wrote down while you were standing in it. A restoration job is a chain of decisions made quickly in someone else’s damaged building, and every one of those decisions is only visible in retrospect if it was recorded at the time. The file you keep on the boring job is the whole difference between “here is exactly what we found, what we did, and when” and “we think it was fine, but that was a while ago.”

None of this changes the work. It changes whether the work is legible later, which — on the day a claim shows up — is the only thing anyone is actually arguing about.

Photograph the parts that feel too boring to photograph

Documentation discipline is the habit that pays off on both halves of the problem, so it is the one to build first.

The instinct most crews already have is to photograph dramatic damage. That is the least useful part of the file. The photographs that matter are the boring ones: the condition before anyone touched it, the moisture readings taken in sequence rather than once, the scope written down instead of carried in someone’s head, the state of the space at each stage rather than only at the start and end. A file built out of those is a file that can answer specific questions — what did you find, what did you do, in what order, and how did you know when you were done.

Three disciplines carry most of the weight, and none of them is a desk job:

Photograph before you demolish, and keep photographing through the stages. The picture that proves what a space was like before your crew arrived cannot be taken after they leave.
Log moisture as a series, not a snapshot. A single reading proves almost nothing; a sequence of readings over the drying period shows a process working, which is a different and far stronger claim.
Write the scope down and follow the written one. A scope that lives only in the lead technician’s head is not a scope you can produce later, and “produce later” is the entire point.

The businesses that struggle here are usually imagining documentation as paperwork done at a desk that night. That version does not survive and it does feel like a burden. Done on site, in the moment, folded into work the crew is already doing, it adds minutes and removes weeks.

Containment and clearance: where frequency actually moves

If documentation is where severity is managed, containment and clearance are where frequency is.

Containment is the discipline that keeps a problem from becoming a bigger one — keeping the affected area separated so contamination or moisture does not migrate into space that was fine when you arrived. A containment that holds is a claim that never spreads. A containment that was rushed or improvised is how a one-room job becomes a whole-floor one, and the second version is both a worse loss and a harder one to defend.

Clearance is the twin discipline, and it is mostly about not signing off early. The pressure to close a job and move to the next one is constant and real, and it is exactly the pressure that produces the clearance decision you regret. A reading that lands just inside the line on a day you were in a hurry is the reading you will be asked about later. The businesses that keep clean records are, more than anything, the ones that let the clearance decision be governed by the protocol rather than by the schedule.

Real-World Scenario: Two restoration companies handle nearly identical water-and-mold jobs in nearly identical houses. Both do competent work. On the first, the crew photographs before demolition, logs moisture as a sequence, follows a written scope, holds containment properly, and lets clearance be decided by the readings rather than the calendar. On the second, the work is fine but the file is thin — a few photos, a scope in someone’s memory, a clearance call made on a busy afternoon. Months later, both get the same phone call: a new owner has found a problem and is tracing it back. The first company opens a file that answers every question with something that predates the dispute. The second company has a good reputation and very little it can produce. The claims are not the same size, and the difference was not the quality of the work. It was decided on an ordinary day nobody thought was important.

That scenario has no bad crew in it, which is the point. The exposure was not created by doing the job badly. It was created by not writing the ordinary job down, and it became visible only once it was too late to fix.

The conversation you can prove you had

The last habit is the one owners forget because it does not feel like restoration work at all: keeping a record of what you told the customer.

A large share of the disputes that reach a restoration business are not really about the work. They are about expectations — what the property owner believed was going to happen, what they think they were promised, what they say they were never told. In a trade where you are often working inside insurer-funded scopes, where the property owner’s insurer sets the scope you are paid on, the gap between what was said and what was heard is a live source of claims. A written trail of what you communicated, and when, closes that gap before it opens.

This does not have to be elaborate. It has to exist. A record that the customer was told what the scope covered, what it did not, and what the clearance decision meant is often the entire defense against a dispute that is otherwise one person’s memory against another’s.

How a clean file reads to the people who price you

There is a secondary benefit to all of this, and it is worth being honest about its size.

A business that keeps good files and holds good habits produces a short, legible claims history, and a short, legible claims history reads well when your account is underwritten. An underwriter looking at a restoration contractor is trying to answer one question — how are this company’s claims likely to behave — and a clean, well-documented record is the most direct evidence you can offer. It reads well on the general liability side, and it reads well on the professional liability side, where the exposure is a judgment someone relied on rather than damage you caused.

But be clear about what this does and does not buy. It does not buy a promised discount. Anyone who tells you a clean file lowers your premium by a specific amount is guessing, because your pricing reacts to your whole account, not to one input. What good habits change is how your claims actually behave — and how your claims behave is the thing your premium is ultimately responding to. That is a slower and less satisfying mechanism than a coupon, and it is the real one.

Before the next ordinary job

None of this is exotic, and that is exactly why it gets skipped. The habits that reduce restoration claims are unglamorous, they pay off invisibly or on a delay, and they feel most optional on precisely the jobs where they turn out to matter most.

So the discipline is to stop treating the ordinary job as the one where documentation is a waste of time. It is the one where it is quietly most valuable, because it is the one you will not see coming. Photograph the boring parts, log the readings as a series, hold containment, let the protocol decide clearance, and write down what you told the customer. If you want the insurance program underneath a business that runs this way — restoration contractor coverage built to sit on top of good habits rather than to paper over their absence — ask us for a quote.

<rect x="250" y="52" width="200" height="76" rx="10" fill="#C7683F" stroke="#12703F"/>
<text x="350" y="82" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#1A1A1A">The file you keep</text>
<text x="350" y="104" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#1A1A1A">On a routine job where</text>
<text x="350" y="120" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" fill="#1A1A1A">nothing went wrong</text>

<path d="M 300 128 L 200 168" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#claims-arrow)"/>
<path d="M 400 128 L 500 168" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#claims-arrow)"/>

<rect x="40" y="174" width="290" height="104" rx="9" fill="#F1E5D6" stroke="#DCC9B0"/>
<text x="185" y="200" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">Documented as it went</text>
<text x="185" y="224" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">Photos before demolition, readings</text>
<text x="185" y="240" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">in sequence, a scope on paper, a</text>
<text x="185" y="256" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">record of what the customer was told</text>

<rect x="370" y="174" width="290" height="104" rx="9" fill="#ffffff" stroke="#DCC9B0"/>
<text x="515" y="200" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="13" font-weight="600" fill="#12703F">Thin, from memory</text>
<text x="515" y="224" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">A few photos, a scope nobody</text>
<text x="515" y="240" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">wrote down, a clearance call made</text>
<text x="515" y="256" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">on a busy afternoon</text>

<path d="M 185 278 L 185 300" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#claims-arrow)"/>
<path d="M 515 278 L 515 300" fill="none" stroke="#12703F" stroke-width="2" marker-end="url(#claims-arrow)"/>

<rect x="40" y="306" width="290" height="58" rx="9" fill="#ffffff" stroke="#12703F"/>
<text x="185" y="332" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-weight="600" fill="#12703F">A defensible job, smaller claim</text>
<text x="185" y="352" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">The record predates the dispute</text>

<rect x="370" y="306" width="290" height="58" rx="9" fill="#ffffff" stroke="#DCC9B0"/>
<text x="515" y="332" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-weight="600" fill="#5A5048">Memory against memory</text>
<text x="515" y="352" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="11" fill="#5A5048">Good reputation, little to produce</text>

<text x="350" y="398" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-style="italic" fill="#5A5048">The claim you prevent never shows up on your record.</text>
<text x="350" y="418" text-anchor="middle" font-family="Inter, system-ui, -apple-system, 'Segoe UI', Roboto, sans-serif" font-size="12" font-style="italic" fill="#5A5048">The claim you document shows up smaller.</text>

The same bad day, months later, reads two different ways depending on the file kept on an ordinary job — which is why prevention and documentation are the two habits that actually move a restoration company’s claims.

The bottom line

Reducing claims in a restoration business is two different jobs that owners tend to collapse into one. The first is lowering how often a claim happens at all, and that work is almost entirely about habits on ordinary jobs — containment that holds, clearance you do not rush, a scope you actually follow. The second is making sure that when a bad day comes anyway, it reads as a job that was done carefully and documented as it went, rather than as a story only the other side gets to tell. That second job is won or lost long before the dispute, on the boring jobs where nothing went wrong and it felt like there was nothing to write down. The claim you prevented never shows up on your loss run, so you never get credit for it in a way you can see. The claim you documented shows up smaller, shorter, and more defensible than the identical claim on a business that kept no file. Neither habit comes with a promised discount, and anyone who tells you a clean file moves your premium by a fixed amount is guessing — but both change the thing your premium is ultimately reacting to, which is how your claims actually behave.

Frequently asked questions

If I could fix only one habit to cut claims, which one moves the needle most?

Documentation, because it is the habit that improves both halves of the problem at once. Better containment and slower clearance lower how often a claim happens, which matters, but documentation is what changes how every claim behaves once it exists — including the ones you could not have prevented. A job photographed, scoped, and logged as it went gives you a record that predates the dispute, and a record that predates the dispute is worth more than any argument made after one starts. If you are going to build a single discipline into the company first, build the one that helps on the good days and the bad ones alike.

Does all this documentation slow a crew down enough to matter?

Less than owners fear, and far less than a disputed claim costs in time later. The documentation that matters is not a second job layered on top of the work; it is a few minutes folded into the work the crew is already doing — photographs before demolition, moisture readings logged where they are already being taken, a scope written down instead of carried in someone’s head. The crews that resist it are usually picturing paperwork done at a desk that night, which is the version that does not survive. Done on site, in the moment, it adds minutes to the job and removes weeks from the argument that occasionally follows one.

The job went fine and it closed. Why keep a thick file on it?

Because you cannot tell in advance which ordinary job is the one that comes back. The claims that hurt a restoration business rarely come from the jobs that looked risky going in; those get attention. They come from the routine ones nobody flagged, months later, when a buyer retests or a new owner finds a problem and traces it to work you did. The file you keep on the boring job is insurance against exactly that, and it costs almost nothing to keep. The job that closed cleanly is precisely the one where it feels pointless to document and is quietly most valuable to have.

Does a clean loss run actually lower what I pay for insurance?

It affects how you are priced, but not by any number anyone can promise you in advance. A business with a short, well-documented claims history is easier to understand and easier to price than one with a messy record, and that reads well when your account is underwritten. What nobody can honestly tell you is a fixed amount — anyone who says a clean file lowers your premium by a specific figure is guessing, because pricing reacts to your whole account, not to one input. The honest version is that good habits change how your claims behave, and how your claims behave is what your premium is ultimately responding to.

Who on the crew should own the documentation?

Someone specific, named, and the same person every time, rather than whoever remembers. Documentation that belongs to everyone belongs to no one, and it is the first thing to disappear on a fast, chaotic loss when every hand is busy. The businesses that keep good files usually make it one role on the crew — the person who shoots the photos before demolition, logs the readings, and confirms the scope was captured before the equipment goes in. It does not have to be the owner, and on a growing company it should not be. It has to be someone, consistently, so that the file exists whether or not the day was calm.

We already take photos on every job. Isn’t that enough?

Photos are the start, not the whole file, and photos alone tend to answer the wrong question later. A wall of images shows that something was wet; it does not show what your scope was, what the moisture readings were over time, when clearance was reached, or what you told the property owner and when. The file that holds up is the one that ties the photos to a written scope, a log of readings, a record of the clearance decision, and a trail of what was communicated. Photographs are necessary and they are not sufficient, and the gap between the two is exactly where a well-run business separates itself from one that merely has a camera.

About the author

Nate Jones, CPCU, is the founder of Wexford Insurance and Restoration Guard Insurance, a specialty insurance agency placing restoration contracting and radon mitigation coverage in 48 states through a 22-market specialty panel. He underwrites and places restoration contractors, and the file is the first thing he asks to see, because in a trade where the work happens fast and in someone else’s flooded building, the difference between a manageable claim and an expensive one is almost never the skill of the crew — it is whether the ordinary job that later went sideways was documented while the crew was still standing in it, which is a habit an owner either built into the company or did not. Reach him via the Restoration Guard Insurance quote form or call 317-942-0549.

Let a CPCU-led agency read your program

Tell us whether you respond to losses or mitigate radon — and we will take your real operation to the markets that write this class.

Get a Free Quote Call 317-942-0549