Repair vs. replace: writing cause language that holds up

Every property file comes down to two sentences. What caused the loss, and whether the damaged material gets repaired or replaced. Everything else in the report — the photos, the test squares, the measurements — exists to make those two sentences stand up.

And those are exactly the sentences most adjusters write worst, because they're written last, at night, when the goal has quietly shifted from being defensible to being done. Here's how to write cause and repair-versus-replace language that holds when someone pushes on it — because on any file with real money in it, someone will.

Observation first, conclusion second

The single biggest upgrade to cause language is structural, not stylistic: separate what you observed from what you conclude, and put them in that order.

Weak cause language skips straight to the verdict — "the roof sustained hail damage from the storm" — and leaves the reviewer to reverse-engineer whether the file supports it. Defensible cause language walks the reader there:

Inspection of the north slope revealed eleven impacts per hundred square feet within the test square, with fractured granule surfaces and bruised mat. The east slope showed functional damage limited to nine shingles near the ridge; the south and west slopes showed no comparable impacts. This directional pattern is consistent with the reported storm event of April 12.

Observation, observation, conclusion. Nobody has to trust your judgment — they can watch you exercise it. That's the difference between an opinion and a finding.

Anchor the cause to the peril and the date

"Hail damage" is half a cause. The claim is for a specific peril on a specific date, and the strongest files tie the damage to both:

• Directionality — impacts concentrated on the slopes facing the storm track, clean slopes documented as evidence, not omitted as boring.
• Freshness markers — fractured granules, exposed asphalt still black and shiny rather than weathered gray. Old strikes look old; say so when they do.
• The age question, answered before it's asked — if the roof is fifteen years old, the reviewer is already wondering how much of what you found is wear. A defensible report addresses it head-on: what's storm damage, what's age, and how you told them apart. Silence on age doesn't make the question go away; it just means someone else answers it without you.

The repair-versus-replace call: show the reasoning

"Recommend replacement" is a conclusion. What makes it defensible is showing the factors that drove it, in the report, in plain terms:

• Extent — damage density and distribution. Eight hits per square across two slopes is a different argument than three hits confined to one.
• Repairability of the material itself — brittle, aged shingles that crack under handling don't survive spot repairs; if that's what you found, describe it as an observation, not an adjective.
• Matching — if the existing shingle is discontinued or a partial repair would leave a visibly mismatched slope, say so specifically. Matching arguments made vaguely read as padding; made concretely, they read as diligence.
• The line you're drawing — when you repair some elevations and replace others, state why the line falls where it does. A mixed scope with no stated logic is a supplement dispute waiting to happen.

The same discipline applies in the other direction. A repair recommendation with reasoning attached protects you too — "functional damage limited to nine shingles on the east slope; field repair appropriate" is a defensible call. An unexplained one is just the cheaper opinion.

Two ways language gives a file away

Cause language fails in opposite directions, and both are audible to a reviewer:

Hedging. "Appears to be consistent with possible hail activity." Three qualifiers deep, this sentence commits to nothing — and a reviewer can't approve what the adjuster wouldn't commit to. "Consistent with" on its own is a finding; it's the stacking — appears, possible, may have — that turns it into an escape hatch. If the evidence supports the finding, state the finding. If it doesn't, the answer is more evidence, not more hedges.

Overreach. The opposite failure: "clearly," "definitively," "beyond any doubt" — certainty the file can't back. Overreach invites the challenge it's trying to preempt, because absolute language turns every small counterexample into a credibility problem. The defensible register is plain and unheated: consistent with, supported by, revealed. Plain, committed phrasing — no adverbs doing the arguing.

And when something genuinely couldn't be verified, the professional move is the explicit flag — state what's pending confirmation rather than papering over it. A marked gap is a report being honest; a smooth sentence over a gap is where files get burned.

The spine, in five sentences

Strip everything above down and a defensible cause-and-scope section has a five-sentence skeleton:

1. What was inspected and when.
2. What was found, with counts and locations.
3. What was not found — the clean slopes, the dry rooms.
4. The cause conclusion, tied to peril and date, age addressed.
5. The repair-or-replace call, with the reasoning that drove it.

Every claim is different; the spine isn't. Write those five in that order and the file argues for itself.

---

The counts and clean slopes that feed sentence 2 and 3 come from the roof — that's the 10-minute capture routine and test-square documentation done right. For why this is what the desk is actually reading for, see what desk reviewers kick back. And to see the full spine written out in carrier format, read a sample report — LossNarrative drafts the narrative in this structure from your field notes, and flags anything unverified as [ADJUSTER TO CONFIRM] instead of writing a smooth sentence over it.