What Does the Adjuster Actually Want? Writing the Report That Gets Insurance Work Approved

Every week the same thread shows up in the contractor forums: "First time dealing with insurance — the adjuster cut my estimate, what do I do?" This week it was a carpenter quoting flood repairs for a friend's basement, and a GC staring at an $80,000 packout estimate wondering how anyone gets a carrier to pay that. The answers in those threads are usually about rates. Rates are almost never the problem.

I work on insurance-heavy jobs every week. The difference between the operators who get paid on claims and the ones locked in a permanent knife fight isn't estimating software, negotiation skill, or even relationships with adjusters. It's the report. Most contractors have never been told what that document is actually for, so they write the wrong one.

Why does the same scope get approved from one contractor and fought from another?

Because the adjuster isn't really deciding whether your work was worth the money — they're deciding whether they can defend paying you. An adjuster's approval carries their name. It can get audited by their own reviewer, questioned by their supervisor, re-opened months later. When your file makes that defense easy, it gets approved close to as-written. When it makes the defense hard, the cutting starts — not because the adjuster thinks the work wasn't done, but because an undocumented line item is exactly the thing their reviewer will flag.

That reframe changes how you write everything. You're not submitting an estimate. You're submitting the evidence the adjuster will use to justify the check.

What does the adjuster do with what you send?

They triage it, fast. An adjuster is carrying a stack of open claims at once — yours is not the day's project, it's one of the day's decisions. Within the first minute of opening your file they've sorted it into one of two piles: forward as-sent or this becomes a negotiation.

The lump-sum estimate with a folder of unlabeled photos goes in the second pile every time. Not out of malice. There's simply no way to defend "water damage repairs — $14,600" to a reviewer, so the adjuster has to reconstruct your scope themselves, and their reconstruction will be smaller than yours.

The file that goes in the first pile answers the reviewer's questions before they're asked. Which brings us to what goes in it.

What goes in the report, and in what order?

The cause, first paragraph, with the photo taken before anyone fixed it. What failed, when it failed, how you know. A supply line, a roof penetration, an appliance — named, dated, photographed in place. This is the single most expensive thing contractors skip. The most natural instinct on a loss is to stop the source immediately and clean up; do that before documenting it and the entire claim downstream becomes debatable, because coverage itself hangs on cause.

Scope broken into line items that mirror the carrier's structure. Carriers price claims in estimating platforms — Xactimate, mostly — as discrete line items: remove and replace baseboard by the linear foot, casing by the opening, flooring by the square foot with underlayment separate, labor and material visible, overhead and profit stated. You don't need their software. You need your scope to be comparable line by line with what their software produces, because "comparable in minutes" is what makes approving you the easy option. One block number is un-reviewable, and un-reviewable gets rebuilt from scratch by someone with less incentive than you.

Readings on a dated timeline. If your trade produces measurements — moisture content, relative humidity, temperature — log them at every visit, dated, from first walk to dry standard. A trend line is an argument no adjuster wants to fight. "It was really wet" is not.

Photos referenced by line item. Wide shot to place the room, mid shot to show the damage, close shot to justify the specific line. Then — the part that does the work — key them: the insulation-removal line points to the photo of saturated blown-in sitting in the cavity. A photo nobody can connect to a line item argues for nothing, no matter how dramatic it looks.

The paper trail, in one thread. Scope discussed on the phone doesn't exist. After every call: "Per our conversation, you approved X." One email thread, top to bottom, so the whole conversation is reconstructable by someone who wasn't on any of the calls.

What gets a line item cut?

Four patterns account for nearly all of it. The line with no photo behind it. The scope that appeared in invoice-stage but was never in the submitted file — anything discovered mid-job gets documented and submitted when discovered, not remembered at billing. The cause section that's missing or vague, which invites the everything-below-it fight. And phone-approved changes with no written confirmation, which evaporate the moment the adjuster rotates off the claim — and adjusters rotate constantly.

Notice none of these are about price. High numbers with complete evidence get paid slower than they should and more often than you'd think. Undocumented numbers of any size get cut.

When do you send it?

Progressively, not at the end. The report that lands as a finished 40-page PDF three weeks after the loss reads like a story someone assembled. The file that builds visit by visit — cause documentation the first day, readings appended each trip, scope additions submitted as discovered — reads like a record of events. Adjusters trust records. They audit stories.

Progressive submission has a second effect nobody mentions: it surfaces the disagreement early, while it's small. Finding out at final invoice that the carrier never accepted your insulation line is a fight over money already spent. Finding out day two is a scope conversation.

What did working this way actually change for us?

I'll admit what it cost to learn. Early on we ran jobs the way most contractors do — fix first, photograph what's convenient, argue at the end. We ate scope on claims where the work was legitimately done, because done and defensible are different things, and I couldn't prove cause on damage we'd already repaired. There is no negotiating skill that recovers a line item you can't evidence. That money is just gone, and it was tuition.

The habits above didn't make our estimates bigger. They made them stick — the gap between what we submit and what gets approved is now thin enough that we can price jobs knowing the number is real. And they compounded somewhere I didn't expect: adjusters remember whose files don't waste their afternoon. We get called about losses now, by adjusters, which is a sentence most contractors won't believe until it happens to them.

Where does insurance work come from in the first place?

The report gets you paid. It doesn't get you the job — that happens earlier, at the referral: the insurance agent whose insured just called in a panic, the plumber standing at the burst pipe, the property manager with a flooded unit. The operators who win claims work consistently have systematized those relationships, not just the paperwork after them.

We wrote down how we run that side of the business — choosing partners, structuring the two-way flow, keeping the channel warm — in the Referral Partner Playbook. It's free, and none of it requires our software. Download it, run the system, and the reports above will have more claims to get approved.

About Joshua Barnes

Joshua Barnes is the founder of ServiceReady. WORKFORCE™ started as the software his own field crews use every day — dispatch, estimates, insurance documentation, and referral tracking included.

Get the Referral Partner Playbook

The exact system trades businesses use to turn plumbers, adjusters, and agents into a steady referral channel — at a fraction of what paid leads cost.

Get the Playbook