How to Build a Roofing Claim File an Adjuster Can't Dispute

There is a moment on every storm job that decides whether you get paid for the work the roof actually needs, or whether you spend three weeks emailing a desk adjuster about ridge cap. It happens before anyone climbs the ladder. It happens when you decide how you are going to document the damage and write the scope.

Most roofers think the adjuster meeting is where claims are won. It isn't. By the time the field adjuster is standing on the roof, the outcome is mostly baked in by the quality of the file the homeowner already submitted and the scope you are prepared to walk through. A thin file invites a low scope. A clean, organized, fact-based file changes the conversation from "is there damage" to "how much of this damage do we agree on."

Let me be precise about what we are doing here, because the line matters and it is a line that gets roofers in real legal trouble. You are not handling, negotiating, or adjusting the claim. You are not interpreting the homeowner's policy or telling them what is covered. You document the roof thoroughly, you write an accurate repair estimate for your own scope of work, and you hand that documentation to the homeowner. The homeowner files. The insurer decides coverage. Everything below lives strictly on the documentation and estimating side of that line, and I will flag the places where roofers cross it without realizing.

Done right, a claim file does one thing: it removes the adjuster's reasons to say no. Not by argument. By evidence. An adjuster can dispute an opinion all day. It is much harder to dispute a dated, geolocated photo of a hail bruise next to a chalk circle next to a tape measure, sitting in a report that matches a storm event the National Weather Service already confirmed for that ZIP on that date.

What "an adjuster can't dispute" actually means

First, a reality check, because the headline promise needs honesty under it. No file is literally indisputable. Adjusters work for carriers, carriers have cost pressure, and reasonable people disagree about whether a mark is hail or a manufacturing defect or foot traffic. You cannot document your way to a guaranteed approval, and any roofer promising a homeowner a specific payout or a guaranteed approval is making a promise they have no authority to keep.

What you can do is build a file with no soft spots. "Can't dispute" in practice means:

• Every claimed item is shown, measured, and located, not asserted.
• The cause of loss is tied to a verifiable weather event with a date and a source.
• The scope follows the manufacturer's installation requirements and local code, so line items aren't "upsells," they are requirements.
• The estimate is built in the same estimating language the carrier uses, so there is nothing to translate and nothing to argue about on price.
• The damage pattern is internally consistent. The roof, the soft metals, the screens, and the surrounding property tell the same story.

When those five things hold, the adjuster's job stops being "find a reason to deny" and becomes "agree on the scope." That is the whole game. You are not beating the adjuster. You are making agreement the path of least resistance.

The file structure pros use

Before the photos and the measurements, decide on the container. A claim file that arrives as 80 unnamed phone photos in a text thread gets treated like 80 unnamed phone photos. A claim file that arrives as a single organized PDF with a cover page, a damage summary, a labeled photo report, and an itemized estimate gets treated like a professional submission.

Here is the structure I have seen hold up best, in order:

1. Cover page. Property address, date of inspection, date of loss, your company and contact, the homeowner's name, and a one-line statement of cause ("Hail event, [date], confirmed by NWS for ZIP [#####]").
2. Damage summary. A half-page in plain English. What you found, where, and what it means for the roof's function. No drama, no "totaled," no "100% damage." Function-based language: "granule loss exposing asphalt mat in field; fractured mat at multiple impact sites; bruising on all slopes."
3. Weather verification. The storm report or data printout, with source and date. This is the spine of the cause-of-loss argument.
4. Photo report. Labeled, sequenced, slope by slope. Overview shots first, then detail shots, then collateral damage.
5. Measurements / diagram. An aerial measurement report or hand sketch with slope areas, pitch, and accessory counts.
6. Repair estimate. Itemized, in carrier-standard format, with notes that tie line items to code or manufacturer requirements.
7. Supporting docs. Manufacturer installation instructions for the specific shingle, relevant code sections, and prior maintenance records if the homeowner has them.

Notice that the photos are item four, not item one. The structure does as much work as the content. An adjuster who opens a file and immediately sees the cause of loss verified and the damage summarized in functional terms reads the rest of the file looking for confirmation, not contradiction.

Step one: verify the loss before you sell the job

The single most common reason a file collapses is that the damage is real but the date of loss is wrong, vague, or unsupported. Carriers deny and underpay storm claims constantly on causation, not on whether damage exists. If you cannot tie the damage to a specific covered event, you have a maintenance problem, not a claim.

So do the weather work first, before you have invested a single roof in the homeowner's hopes.

Pull the storm history for the address. The National Weather Service and the NOAA Storm Prediction Center maintain storm event databases and storm reports. Local NWS offices publish Local Storm Reports (LSRs) with hail size and wind estimates by location and time. For hail specifically, you want the date, the estimated stone size, and how close the report is to the property. A 1.75-inch hail report two miles away on a date that matches the homeowner's memory is a strong spine. A vague "sometime last spring" with no report near the address is a weak one.

Match the damage to the event. Hail and wind leave different signatures. If the homeowner reports a wind event but the roof shows omnidirectional bruising with no creased or lifted shingles, your story doesn't hold together, and a competent adjuster will notice. Make the cause of loss and the physical evidence agree before you write a word.

Be honest about age and pre-existing condition. This is where roofers get sloppy and where adjusters live. A 22-year-old three-tab with widespread granule loss has age-related wear that is going to be part of the conversation whether you like it or not. Pretending it is all hail damages your credibility on the items that genuinely are hail. Document the storm damage as storm damage and don't claim wear as impact. A file that over-reaches gets every line scrutinized. A file that is conservative and exact gets the benefit of the doubt.

This verification step is also where a lot of wasted windshield time disappears. If you are knocking a neighborhood after a storm, you are guessing which houses took the worst of it and which roofs were already near the end of their life and therefore most likely to show actionable damage. That guessing is exactly the part that data can tighten up, and I'll come back to how below.

Step two: photo documentation that holds up

Photos are where most files are won or lost, and most roofers shoot them wrong. A great damage photo answers three questions at once: what is this, how big is it, and where on the roof is it. If a photo answers only one, it is decoration.

The photo system

Work in a fixed sequence on every roof so you never come down missing a shot:

1. Address verification shot. A photo that shows the house number or a recognizable feature, establishing this is the right property.
2. Four elevation overviews. Front, back, left, right of the structure from the ground. These orient everything that follows.
3. Slope overviews. One wide shot per slope from the roof, so the adjuster can see overall condition and the test-square locations in context.
4. Test squares. A 10-by-10-foot area marked off (chalk corners or a square tool) on each slope, with hits circled and counted. This is the heart of hail documentation. Carriers and many estimating standards think in hits per test square per slope.
5. Individual impact detail. Close shots of representative hits with a measurement reference and the chalk circle. Show fractured mat, not merely a dark spot.
6. Soft metals and collateral. Gutters, downspouts, gutter aprons, valley metal, vents, flashing, gas caps, AC fins, window screens, and any wood surfaces. Soft-metal denting is the corroborating evidence that turns "maybe granule loss" into "yes, hail came through here at this size."
7. Manufactured accessories. Ridge vents, pipe boots, turtle vents, satellite mounts, skylights, any penetration that is damaged or compromised by the work.

What makes a photo defensible

• Scale in frame. A coin, a chalk line of known length, or a tape measure next to the impact. "It's about an inch" is an opinion. A photo with a tape reading 1" is a fact.
• Marked, not bare. Chalk-circle the hits. A bare close-up of shingle granules means nothing to a desk reviewer; a circled cluster with a count tells them exactly what you are claiming.
• Geotag and timestamp. Use an app that embeds GPS coordinates and date/time, or shoot in a documentation tool that does it for you. A photo that proves itself was taken at this address on this date is much harder to wave off than a loose image that could be from any roof anywhere.
• Consistent and complete. If you photograph hits on the south slope, photograph the north slope even if it is clean. Showing the clean slope is not a weakness; it shows you inspected the whole roof and reported honestly, which makes your damaged-slope photos more credible.

Test squares the right way

The test square is the unit of measurement that adjusters actually negotiate around, so do it the way they do it. Mark a 10x10 area, identify every impact within it that shows functional damage (fractured mat, granule displacement exposing the asphalt, never a mere scuff), circle each one, and record the count. Do one on each slope. The pattern across slopes tells the causation story: directional damage concentrated on the windward slopes is consistent with a directional hail event; uniform damage on all slopes including low-slope and shaded areas argues against foot traffic and for hail.

Number your test squares and reference them in the damage summary. "Test square 1 (south slope): 9 impacts. Test square 2 (west slope): 7 impacts. Test square 3 (north slope): 6 impacts." Now the adjuster is looking at a quantified, repeatable observation, not your gut feeling.

Reading the difference between hail, wind, and wear

A file that calls everything "storm damage" is a file that gets everything questioned. Train yourself, and your crews, to separate the three signatures cleanly, because an adjuster who catches you mislabeling one will distrust the rest of the report.

Hail leaves circular or near-circular bruises with a soft, dented feel where the mat is fractured underneath, often with displaced granules exposing the asphalt. The hit has no consistent directional pattern within a slope, but the overall damage tends to concentrate on the slopes that faced the storm. On a laminated architectural shingle, you press a suspected hit and feel a give that a sound shingle doesn't have. The collateral, dented soft metals, splatter marks on painted surfaces, dinged AC fins, all sizes consistently with the same event.

Wind leaves creased, lifted, torn, or missing shingles, usually along edges, ridges, and the windward eave, and the damage runs directional. A wind-creased shingle has a clean fold line where it folded back and snapped the seal; you photograph the crease and the broken sealant strip underneath. Wind and hail can both be present from the same storm, which is fine, document each with its own signature rather than blending them.

Wear and mechanical damage is the trap. Age-related granule loss is diffuse and uniform, heaviest where water sheets and where sun hits hardest, not in discrete circular bruises. Foot-traffic damage shows as scuffed granules in walkable lines and around penetrations, with no fractured mat underneath. Blistering, the small popped bubbles from trapped moisture or manufacturing, looks like hail to an untrained eye but has a hollow or open blister rather than a dented bruise, and it appears on slopes the storm never touched. If you claim blisters or wear as hail, the adjuster finds the same marks on a shaded north slope that no hail reached, and your whole report loses credibility.

The move that separates pros: when you find wear or blistering, note it in the report as wear or blistering, openly. "North slope shows diffuse age-related granule loss and scattered blistering, distinct from the impact bruising documented on the south and west slopes." That single honest sentence makes the impact bruising you did claim far more believable, because it proves you can tell the difference and chose to report only what qualified.

Step three: measurements that match the estimate

If your photos prove the damage and your weather report proves the cause, your measurements prove the quantity. A scope is only as defensible as the numbers under it, and "I eyeballed about 30 squares" is not a number anyone has to honor.

Use an aerial measurement report or a careful hand measurement that gives you:

• Total roof area by slope, with waste already separated out so you can show your waste math.
• Predominant pitch and any pitch changes (steep-slope and high pitches carry legitimate labor modifiers).
• Ridge, hip, valley, rake, and eave linear footage.
• Accessory counts: pipe boots, vents, chimneys, skylights, drip edge runs.
• Number of stories and access notes (these drive legitimate labor and dumpster placement costs).

The estimate you write later must reconcile to these measurements line for line. When the field adjuster pulls their own measurements, they should land within a small percentage of yours. If your file says 31 squares and the adjuster's says 30, you round to a shared number and move on. If your file says 31 and you can't show where that came from, you lose the whole conversation about waste and pitch.

Worked example: reconciling waste

Say you measure a hip roof at 2,850 square feet of actual surface, which is 28.5 squares. A hip roof with multiple slopes and valleys legitimately runs higher waste than a simple gable because of all the cuts. Document it like this:

When waste is shown as math tied to the roof's geometry, it stops being a number an adjuster can knock down to a flat 10 percent. You are not arguing; you are showing the work.

Pitch, stories, and access: the labor modifiers people forget

Waste is the visible negotiation, but the quiet money is in labor modifiers that a thin file leaves on the table. Three of them recur:

Steep charges. Most estimating systems apply a labor modifier once pitch passes a threshold (commonly 7/12) and a higher one past 9/12 or 10/12, because the crew slows down and rigs differently for safety. If your measurement report shows a 10/12 predominant pitch and your estimate carries no steep charge, you under-billed the labor and handed back money the carrier would have paid. Document the pitch with the measurement and let the line item follow it.

High / multi-story charges. A second or third story adds legitimate cost: longer material handling, taller ladders, more staging. Note the number of stories and the access constraints (no driveway access, backyard-only loading, tight lot) in your access notes, because each of those drives a real charge that an adjuster who never visited the site won't add on their own.

Detach and reset. Solar mounts, satellite dishes, lightning protection, snow guards, and certain HVAC penetrations have to come off and go back on. Each is a documented line, with a count. Crews routinely do this work and never bill it because nobody wrote it down during inspection.

None of these are upsells. They are the actual cost of doing the actual work on this specific roof, and a measurement report plus honest access notes is what makes each one defensible rather than a number you appear to have invented.

Ventilation: replace like-for-like, document the existing

Ventilation gets dropped or downgraded constantly. If the existing roof has continuous ridge vent, the repair gets continuous ridge vent, not a couple of static box vents that cost less. Photograph and count the existing ventilation during inspection (linear feet of ridge vent, number of turtle vents, number of powered or static vents, soffit configuration) so the replacement is a documented like-for-like swap. Mixing ventilation types on a repair can also create code and warranty problems, so the existing-condition photo protects both the scope and the install.

Step four: write the scope in the carrier's language

Here is where roofers leave money and credibility on the table. They write a one-page proposal in their own format, hand it over, and then get frustrated when the adjuster's estimate looks nothing like it. The fix is to write your repair estimate in the same itemized, unit-cost structure the carrier already uses, so there is nothing to translate.

Most storm carriers estimate in Xactimate, which prices line items by region using periodically updated unit costs. You do not have to fight the pricing. The published unit prices are what they are. What you control is whether every legitimate line item is present and correctly quantified. The two failure modes are: items missing from the scope entirely, and items present but under-quantified.

Build the scope from the roof up

Write the estimate as a complete reconstruction of the work the damage requires, in installation order. A defensible roof replacement scope typically includes, and an incomplete one typically omits:

• Tear-off of existing roofing, by layer (note if there are two layers, that's a real labor difference)
• Felt or synthetic underlayment
• Ice and water shield where code or manufacturer requires it (eaves, valleys, penetrations)
• Drip edge / starter at eaves and rakes
• Starter course
• Field shingles
• Hip and ridge cap (a separate line, separately priced, frequently dropped)
• Ridge vent or other ventilation, replaced like-for-like
• Pipe boots, including the count
• Step and counter flashing at walls and chimneys
• Valley metal or closed-cut valley material
• Detach and reset or replace for items like satellite dishes, where applicable
• Dumpster / debris haul-off
• Roof loading or delivery access charges where the site requires them
• Permit, where the jurisdiction requires one
• Steep and high charges where pitch and stories warrant them

The items that get dropped most often are the small, technically-required ones: hip and ridge cap as its own line, ice and water shield to current code, starter as its own line rather than "cut from field," drip edge, and proper flashing counts. None of these are upsells. Each one is either a manufacturer installation requirement or a code requirement, and that is exactly how you should annotate them.

Tie line items to requirements, not preferences

This is the move that makes a scope hard to cut. Next to each line that an adjuster might question, note the authority that requires it:

• Ice and water shield at eaves: cite the local adoption of the International Residential Code requirement for an ice barrier in regions subject to ice damming, and the manufacturer's installation instructions for the specific shingle.
• Drip edge: the IRC requires drip edge at eaves and rakes for asphalt shingle roofs in current code cycles; this is not optional.
• Starter strip: the shingle manufacturer's published instructions specify a starter course; field shingles flipped as starter void the wind warranty.
• Synthetic underlayment / full deck: per manufacturer instructions for the warranty to apply.
• Hip and ridge cap: manufacturer-specified cap product, not field shingles, for the warranty and for proper coverage.

When a line item is annotated "required by [code section]" or "required by [manufacturer] installation instructions for warranty," the adjuster isn't cutting your preference, they are deciding to write a non-compliant roof, and they generally won't. Attach the relevant pages of the manufacturer's installation instructions to the file. A printed page that says "a starter strip course is required" ends the starter strip debate.

Step five: code upgrades and the supplement, done honestly

When a roof has to be brought to current code during a covered repair, those code-driven items are part of an accurate scope. A 1998 roof being replaced after a 2026 storm has to meet 2026 code, and current code likely requires drip edge, a certain underlayment, and ice barrier where it didn't before. Document the code requirement with the specific adopted section and let the homeowner's policy and adjuster sort out coverage. Your job is to write the accurate, code-compliant scope and show why each item is required. Whether the policy covers code upgrades is a coverage question, and coverage is the homeowner-and-insurer conversation, not yours.

A supplement is just a correction to a scope that missed something the work actually requires, supported by documentation. The legitimate supplement workflow is:

1. You discover, usually at tear-off, a condition that wasn't visible during inspection: rotted decking, a second layer, inadequate or rusted flashing, a deck that won't hold fasteners.
2. You photograph it immediately, in place, before you cover it. Decking replacement claimed without a before photo of the rotted deck is a supplement that dies on submission.
3. You document the quantity (how many sheets of decking, how many linear feet of flashing) and tie it to a requirement (you cannot install over a deck that won't hold nails per manufacturer instructions).
4. You provide the corrected line items in the same estimate format.

What a supplement is not: a way to inflate. Padding a supplement with items the job doesn't need is fraud, and it is the fastest way to lose a carrier relationship and your credibility on every future file. The defensible supplement is conservative, photographed, and quantity-driven. Decking is the classic example: you can't see rotten plywood under shingles during inspection, so it legitimately shows up at tear-off, and a clean before-photo of the rot makes it nearly automatic.

A tear-off documentation routine that prevents lost supplements

The supplements that die are the ones nobody photographed in time. Build a fixed routine so the crew captures hidden conditions before they vanish under new material:

1. Before the first square comes off, photograph the deck plane from the eave so you have a baseline of the existing surface and any obvious sag.
2. As tear-off exposes the deck, the crew lead photographs every defect in place, in context, with a reference: rotted or delaminated sheathing (show the soft spot and a screwdriver pushed through if it's that far gone), gaps over 1/8 inch that need re-nailing or sheathing, plank decking that won't hold modern fasteners, and any prior layer revealed.
3. Mark and tally as you go. Spray-mark each bad sheet and keep a running count on a tally sheet, then photograph the marked deck wide so the count is verifiable against the photos. "7 sheets of 7/16 OSB replaced, marked and photographed" beats "some bad decking."
4. Photograph flashing and penetrations as they're removed, especially rusted or undersized step flashing, valley metal that was reused last time, and pipe boots that are cracked.
5. Tie each item to a requirement. Decking that won't hold a fastener can't carry the new roof per the manufacturer's nailing instructions, so its replacement is required, not optional, and you say exactly that in the supplement note.

A crew that runs this routine on every tear-off never loses a legitimate supplement to a missing photo, and never has to claim a hidden condition it can't prove.

The do-not-say list: staying on the right side of the line

Everything above keeps you in the safe lane: you document, you measure, you write an accurate estimate, you hand it over. The homeowner files; the insurer decides. There is a specific set of things roofers say and do that cross from documentation into unlicensed public adjusting or worse, and they will get you fined or sued depending on your state. A 2024 Texas case underscored that even labeling yourself an insurance or claims "specialist" can run afoul of public-adjusting law. Treat this as a compliance checklist, not legal advice; check your own state's department of insurance rules.

Do not say, do not do:

• "We'll handle / manage / negotiate your claim." Negotiating or adjusting a claim on the homeowner's behalf, for a fee, is public adjusting and is licensed in most states. You prepare documentation and an estimate for your own work. The homeowner deals with their carrier.
• "We'll get your claim approved" / "guaranteed approval." You cannot promise an outcome you don't control. Promise thoroughness, not approval.
• "We'll get you a new roof for free" / "your deductible is covered/waived/absorbed." Advertising a free roof and offering to eat, waive, or rebate the deductible is illegal in many states and is insurance fraud in others. Never put it in writing, never say it on a door. The homeowner is responsible for their deductible.
• "This is covered under your policy" / interpreting coverage. Reading the policy and telling the homeowner what is and isn't covered is interpreting an insurance contract. You can describe what the roof needs; what the policy pays is between the homeowner and the carrier.
• "We'll fight / beat the adjuster" / "maximize your settlement." This is public-adjusting framing. You agree on a scope; you don't represent the homeowner against their insurer.

Do say:

• "We document the damage thoroughly and write an accurate, code-compliant estimate to repair our scope of work."
• "We'll give you and your adjuster a complete file so everyone is working from the same facts."
• "Whether it's covered, and what your policy pays, is between you and your insurance company."

The irony is that staying in the safe lane also produces the strongest claim files, because the safe lane is the documentation lane, and documentation is what wins. The roofers who get in trouble for over-promising are usually the same ones with thin files, because they are selling the outcome instead of building the evidence.

How to hand the file to the homeowner without crossing the line

The handoff is the moment most likely to drift into the danger zone, because the homeowner is anxious and wants you to tell them it'll be covered. Script it so you stay on the right side:

• Give them the file, not a verdict. "Here's the full documentation of what we found and an itemized estimate to repair it. You'll submit this to your carrier, and they'll decide what your policy covers." You are a witness and an estimator, not their representative.
• Let them file, or file with their explicit direction, but don't negotiate. It's the homeowner's claim. You can answer the adjuster's factual questions about your scope and walk the adjuster through your documentation. You don't argue coverage or settlement on the homeowner's behalf.
• Decline the deductible conversation entirely. If a homeowner asks you to waive, absorb, or rebate their deductible, the answer is no, and it's worth telling them why: it's illegal in many states and it's the kind of thing that voids the work for everyone. The deductible is theirs to pay.
• Put nothing in writing you can't stand behind. No "we'll get this approved," no "this'll be a full replacement," no payout numbers. Your contract should be clear that the price reflects the work, contingent on nothing you're promising about the carrier.

This posture isn't just legally safer; it's more persuasive to the homeowner, because it sounds like a professional describing facts rather than a salesperson promising a free roof. The homeowners who've been burned, and after a storm a lot of them have, relax when you stop promising and start documenting.

What a desk reviewer sees, and why it decides the claim

The field adjuster who climbs your roof is rarely the final word. Their scope goes back to a desk reviewer or auditor who never visits the property and approves or trims based entirely on the file. That person is your real audience. They are asking: is the cause of loss supported, are the quantities backed by measurement, is each line item required or merely requested, and is there anything here I'd have to defend in an audit. A file built to satisfy that reviewer, sourced weather, scaled and counted photos, reconciled measurements, code-and-manufacturer annotations on every contestable line, gives them nothing to cut and full cover to approve. That is the practical meaning of a file an adjuster can't dispute: every link in the chain, from the field adjuster to the auditor, has a defensible reason to say yes and no defensible reason to say no.

Finding the roofs worth documenting in the first place

Everything to this point is about a roof you are already standing on. The earlier, quieter problem is choosing which roofs to chase. After a storm, you have a finite number of crew-days and a neighborhood full of doors, and most of them are wrong doors: roofs too new to have actionable wear, roofs the storm barely grazed, roofs whose owners already signed with someone else. The wasted windshield time and the wasted documentation hours come from working the wrong roofs, not from working the right ones poorly.

This is where knowing which roofs are due changes the economics. A roof that is aging out of its service life and that sat under the worst of a confirmed storm cell is the roof most likely to show genuine, well-supported damage, which means it is the roof where a careful file actually leads somewhere. A three-year-old roof on the same street under the same cell is far less likely to produce a claim you can defend, no matter how good your photos are.

RoofPredict is built for exactly that targeting problem. It estimates a roof-age range for each address from aerial imagery and models storm physics, hail and wind, per roof rather than per ZIP, then ranks the addresses so your crews work the roofs the storm most likely wore out plus the roofs aging out on their own. It also enriches your own CRM or mailing list with those roof-age and storm signals, so the list you already paid for tells you which doors to knock first. Two honest limits worth stating plainly: the roof age is a range, not a manufacture date, and the storm model gives you odds that a given roof took meaningful impact, not proof that it did. The verification, the photos, the test squares, the estimate, all the work above, still has to happen on the roof. What the targeting does is make sure the roof you climb is one where that work pays off, so your documentation hours land on claims that can actually be supported instead of on doors that were never going to produce a defensible file.

Used that way, it sits cleanly inside the safe lane: it tells you which roofs are likely due and likely storm-affected so you know where to focus, and you still do the honest documentation and estimating on site. It does not handle claims, it does not promise approvals, and it has no opinion about anyone's deductible.

The pre-meeting checklist

Before the adjuster meeting, run the file against this list. If any line is missing, the file has a soft spot.

• Date of loss is specific and tied to a verifiable storm event with a source.
• Weather verification (NWS/SPC storm report) is in the file with hail size or wind speed and distance from the property.
• Four ground elevation overviews are present.
• Each slope has an overview and at least one numbered test square with a counted, circled impact count.
• Representative impact close-ups show fractured mat with a scale reference and chalk circle.
• Soft-metal collateral (gutters, vents, screens, AC fins) is photographed and corroborates the hail size.
• Photos are geotagged and timestamped.
• Clean slopes are documented too, showing a complete and honest inspection.
• Measurements are from a report or careful field measurement, with slope areas, pitch, and accessory counts.
• The estimate is itemized in carrier-standard format and reconciles to the measurements.
• Every contestable line item is annotated to a code section or manufacturer installation requirement.
• Manufacturer installation instructions and relevant code pages are attached.
• Nothing in the file or your verbal pitch promises approval, payout, a free roof, or anything about the deductible.

A file that clears every box doesn't need you to argue. It argues for itself.

How the adjuster meeting actually goes when the file is clean

When you have done the work, the meeting is short and unremarkable, which is the goal. You walk the adjuster to your numbered test squares. You show the same impacts you photographed. Your measurements match theirs within rounding. You point out the soft-metal denting that confirms the hail size. When the adjuster's first scope comes back missing the ridge cap and the ice barrier, you don't argue; you hand over the manufacturer's installation page and the code section, and the supplement for those items is documentation, not a debate.

The roofers who treat the adjuster as the enemy tend to produce thin files and loud meetings, and they lose. The roofers who treat the adjuster as someone who needs to be able to justify the scope to their own carrier produce clean files and quiet meetings, and they get full scopes. Your file's real audience is not even the field adjuster; it is the desk reviewer and the file auditor the field adjuster reports to. Build the file so that person, who will never visit the roof, can look at it and approve the scope without exposure. That is what "can't dispute" really means: there is nothing in the file that gives anyone in the chain a defensible reason to cut it.

Common mistakes that sink otherwise-good files

• No date of loss, or a guessed one. Causation is the most common denial path. Nail the date and source it first.
• Bare photos with no scale and no marking. A close-up of a dark spot proves nothing. Circle it, scale it, count it.
• Over-claiming wear as storm damage. It poisons your credibility on the legitimate items. Be conservative and exact.
• Skipping the clean slopes. It looks like you only photographed what helped you. Document the whole roof.
• A proposal instead of an itemized estimate. Write in the carrier's line-item structure so there is nothing to translate.
• Dropping required line items. Ridge cap, starter, drip edge, ice barrier, flashing counts. Each is a requirement, not an upsell, when annotated.
• Supplementing without before photos. Decking and hidden flashing claimed without an in-place photo before they were covered are dead on arrival.
• Selling the outcome. Promising approval, a free roof, or a handled deductible is both a legal problem and a sign of a thin file.

Putting it together

A claim file an adjuster can't dispute is not a clever document. It is a complete one. You verify the loss against the weather record before you invest in the roof. You photograph in a fixed, scaled, marked, geotagged sequence that proves what, how big, and where. You measure so your quantities are real. You write the scope in the carrier's own line-item language and annotate every contestable item to a code section or a manufacturer requirement. You supplement honestly, with before photos and quantities, never with padding. And you stay rigorously on the documentation-and-estimate side of the line, because that lane is both legal and, not coincidentally, where the strongest files come from.

The roofs where all of this pays off are the ones that were genuinely due, the ones aging out and the ones a real storm cell actually hit. Spend your documentation hours on those, hand the homeowner a file with no soft spots, and let the evidence do the work. The homeowner files, the insurer decides, and a clean file makes that decision easy.

If the targeting half of that equation, knowing which roofs are due and which the storm most likely wore out, is where you are bleeding time, that is the part RoofPredict was built to fix: a per-roof age range and per-roof storm model so your crews and your documentation land on the doors most likely to turn into claims you can actually defend. The roof work is still yours. The guessing about which roof doesn't have to be.

FAQ

What makes a roofing claim file hard for an adjuster to dispute?

Completeness and consistency. Every claimed item is shown, scaled, and located rather than asserted; the cause of loss is tied to a verifiable storm event with a date and source; the scope follows code and manufacturer requirements; the estimate uses the carrier's own line-item format; and the damage pattern across the roof and soft metals tells one consistent story. When those hold, the adjuster's job shifts from finding a denial to agreeing on scope. No file is literally indisputable, but a file with no soft spots makes agreement the easy path.

How many photos do I need, and what should they show?

Quantity matters less than coverage. Shoot a fixed sequence every time: an address-verification shot, four ground elevation overviews, one overview per slope, a numbered 10x10 test square per slope with impacts circled and counted, representative impact close-ups with a scale reference, and soft-metal collateral (gutters, vents, screens, AC fins). Photograph clean slopes too. Each defensible photo should answer what it is, how big it is, and where on the roof it sits, with a tape or coin for scale and a chalk circle around the damage.

Why does the date of loss matter so much?

Causation is the most common reason storm claims get denied or underpaid. If you can't tie the damage to a specific covered event, you have a maintenance issue, not a claim. Pull the storm history for the address from the National Weather Service and the NOAA Storm Prediction Center, get the hail size or wind speed and how close the report is to the property, and confirm the physical damage signature matches the event type. Verify the date and source before you invest time in the roof.

What is a test square and how do I document one?

A test square is a marked 10-by-10-foot area on a slope where you identify, circle, and count every impact showing functional damage (fractured mat or granule displacement exposing the asphalt, not a scuff). Do one per slope and number them. Record the count per slope in your damage summary, for example test square 1 south slope 9 impacts. It's the unit adjusters negotiate around, and the pattern across slopes supports your causation story: directional damage on windward slopes is consistent with a directional hail event.

How do I write an estimate the adjuster won't cut?

Write it in the carrier's itemized, unit-cost format (most storm carriers use Xactimate) so there's nothing to translate, and include every line the work requires: tear-off by layer, underlayment, ice and water shield where required, drip edge, starter, field shingles, hip and ridge cap as its own line, ventilation, pipe boots by count, flashing, valley metal, debris haul-off, and steep or high charges where warranted. Annotate every contestable item to a code section or manufacturer installation requirement so it reads as required, not optional.

Can a roofer help with the insurance claim without breaking the law?

Yes, within a strict line. You may inspect, document damage thoroughly, and prepare an accurate estimate to repair your own scope of work, then hand that to the homeowner. What you may not do, for a fee, is negotiate, manage, or adjust the claim, interpret the policy or coverage, promise an approval or payout, advertise a free roof, or do anything with the homeowner's deductible. Those cross into unlicensed public adjusting or fraud depending on the state. Document and estimate; the homeowner files and the insurer decides.

What is a legitimate supplement versus padding?

A legitimate supplement corrects a scope that missed something the work actually requires, usually a condition only visible at tear-off such as rotted decking, a hidden second layer, or rusted flashing that won't hold. Photograph it in place before you cover it, document the quantity, and tie it to a requirement. Padding a supplement with items the job doesn't need is fraud and destroys your credibility on every future file. The defensible supplement is conservative, photographed, and quantity-driven.

Are code-upgrade line items like drip edge and ice barrier really claimable?

They are part of an accurate, code-compliant scope when current code requires them for the repair, which it often does for older roofs being replaced. Document the specific adopted code section and the manufacturer's installation instructions, and write the line item as required. Whether the homeowner's policy covers code upgrades is a coverage question that belongs to the homeowner and their insurer, not to you. Your job is to write the accurate scope and show why each item is required.

Why are soft-metal dents important if the shingles already show hail?

Soft metals like gutters, downspouts, vents, AC fins, and metal screens dent at predictable hail sizes, so they corroborate both that hail struck and roughly how large it was. That turns an ambiguous granule-loss spot on a shingle into a consistent story. When the field adjuster or the desk reviewer sees denting that matches the hail size in the storm report and the bruising on the roof, the causation argument becomes internally consistent and much harder to wave off as wear or foot traffic.

How does targeting which roofs to inspect improve my claim outcomes?

Documentation hours only pay off on roofs likely to produce a defensible claim, typically roofs aging out of service life that also sat under the worst of a confirmed storm cell. Working newer roofs or doors the storm barely grazed wastes inspection and photo time. Estimating a roof-age range per address and modeling storm impact per roof, as RoofPredict does, ranks the doors so crews focus where a careful file actually leads somewhere. The age is a range and the storm model is odds, not proof, so on-roof verification still has to happen.