How to Handle an Adjuster Who Disagrees With Your Roof Damage

You did the inspection right. You chalked the test squares, you pressed every hit, you photographed the soft-metal collateral, and you walked the homeowner through what their roof actually took. Then the carrier's adjuster climbs up, spends eleven minutes on the roof, and writes it up as cosmetic, or wear, or a few isolated hits that don't meet their threshold. The homeowner is now looking at you, because you are the one who said the roof was damaged, and the person with the company logo on the truck just got told no by the person with the clipboard.

This is the moment that separates the contractors who build a real restoration book from the ones who churn through homeowners and burn out reps. A disagreement with an adjuster is not a sales failure and it is not a personality contest. It is a documentation problem and a process problem, and both are solvable if you understand what the adjuster is actually doing, what they are allowed to do, what their carrier requires of them, and where your evidence either holds or falls apart.

What follows is the playbook a disciplined contractor runs when an adjuster disagrees: how to read the disagreement, how to respond on the spot, what to put in writing, when and how to request a reinspection, where the line is between advocating with documentation and crossing into illegal claims handling, and how to keep the homeowner steady through all of it. The goal is not to "beat" anyone. The goal is to make the physical condition of the roof and the facts of the storm so clearly documented that the right outcome becomes the easy outcome for the carrier to reach.

A note before anything else, because it governs everything below. You are a roofing contractor. You inspect, you document conditions, you provide an estimate, and you do the work if it is approved. You do not adjust the claim, you do not negotiate coverage on the homeowner's behalf, and you do not represent the homeowner against their insurer. The homeowner owns the claim. The carrier decides coverage. In most states, stepping over that line is unlicensed public adjusting, and it is a real legal problem, not a gray area. Everything in this playbook lives strictly inside the contractor lane, and the parts where that lane gets narrow are flagged.

First, understand what an adjuster actually is and what they can do

A lot of contractor frustration comes from a wrong mental model of the person on the roof. Fix the model and the disagreements get easier to handle.

The adjuster who shows up is usually one of three things, and which one matters a great deal:

• A staff (company) adjuster. A salaried employee of the carrier. They handle that carrier's claims by that carrier's guidelines and have a reporting chain inside the company.
• An independent adjuster (IA). A contractor to the carrier, often deployed in volume after a large storm through an IA firm. They work the carrier's file under the carrier's guidelines, but they are not a carrier employee. After a major catastrophe, a huge share of roof inspections are handled by IAs flown in from out of state, sometimes with limited local context and a heavy daily file count.
• A catastrophe (CAT) adjuster. An IA specifically deployed for a declared storm event, typically the highest-volume, fastest-turnaround inspections of all.

This matters because the failure modes differ. A staff adjuster who disagrees is usually applying a consistent internal standard, so your path is documentation that meets that standard. An overworked CAT or IA adjuster who disagrees may simply have rushed a 100-square roof in ten minutes, missed the storm-facing slope entirely, or never got into the test square at all, in which case your path is a clean, factual reinspection request that points to specifically what was not inspected.

Now, what an adjuster is authorized to do, because this is where contractors waste energy fighting the wrong battle:

• They inspect the roof and determine whether the damage they observe is, in the carrier's view, covered storm damage versus excluded causes (wear, age, manufacturing defect, prior damage, cosmetic-only marks, mechanical or foot-traffic damage).
• They write a scope and an estimate, usually in estimating software the whole industry uses, applying the carrier's pricing database for your region.
• They apply the policy: perils covered, deductible, depreciation, any roof-specific endorsements or schedules, and any cosmetic-damage exclusions on the policy.

What they are generally not doing, and what you should not expect them to do for you: hunting for damage you didn't point out, advocating for the homeowner, or interpreting borderline marks generously. Their job is to apply the carrier's criteria to what is documented in front of them. That is the whole game. If the documentation in front of them clearly meets the criteria, approval is easy. If it doesn't, or if they never saw it, you get a disagreement. Most disagreements are really one of those two failures, not a conspiracy.

The handful of policy and coverage facts you have to know

You can't respond intelligently to a denial if you don't know the coverage terrain. You are not interpreting the policy for the homeowner (that is their carrier's and their own job), but you need to recognize these because they change which disagreements are winnable:

• ACV vs. RCV. Replacement Cost Value pays to replace the roof at today's cost; Actual Cash Value pays RCV minus depreciation. Many policies pay ACV first, then release the recoverable depreciation after the work is completed and invoiced. A homeowner who thinks they were "shorted" may simply be looking at an ACV check with depreciation held back until completion. Knowing this stops you from chasing a "disagreement" that isn't one.
• Roof payment schedules / ACV roof endorsements. A growing number of policies, especially on older roofs and in hail-heavy states, cap roof payments at ACV regardless, or apply a roof-age payment schedule that pays a declining percentage as the roof ages. If the homeowner's policy has one of these, even a fully approved hail claim may pay far less than a full replacement, and that is a coverage term, not an adjuster being unfair.
• Cosmetic damage exclusions/endorsements. Some policies, particularly on metal roofs but increasingly elsewhere, exclude purely cosmetic hail damage. If that endorsement is on the policy, "it's only cosmetic" is a coverage position the policy supports, and your fight (if there is one) is whether the damage is genuinely functional, not cosmetic.
• Deductible. This is the homeowner's money and their obligation. You do not "handle," waive, absorb, rebate, or "eat" the deductible, and you do not advertise or imply any of that. In many states that is insurance fraud, full stop, and it has put contractors out of business. The deductible is between the homeowner and their carrier.
• Date of loss and reporting deadlines. Coverage is tied to a specific dated storm event, and policies have notice/filing time limits. A "disagreement" that is really a wrong-date-of-loss or late-notice problem is a different animal and usually not winnable by arguing about shingles.

You don't quote policy language to the homeowner as advice. You recognize these so you can tell the difference between a disagreement worth documenting and a coverage term that simply is what it is.

Diagnose the disagreement before you respond to it

The single biggest mistake contractors make is reacting to "denied" as if every denial is the same. They are not. Your response should be completely different depending on why the adjuster disagreed. Spend the first move diagnosing, not arguing.

There are really six common shapes a roof disagreement takes. Name the one you have before you do anything else.

The six common disagreements, and what each one actually means

1. "It's cosmetic, not functional." The adjuster agrees hail hit the roof but says the impacts didn't fracture the mat or compromise water-shedding. This is the most common substantive disagreement and it is winnable only with physical evidence of mat fracture, not with opinion.
2. "This is wear and tear / age, not storm damage." The adjuster attributes the condition to the roof aging out: granule loss, thermal cracking, blistering, brittleness. Common on old roofs, and it is where roof age cuts both ways (an old roof is more hail-vulnerable but also easier to write off as "just old").
3. "There aren't enough hits to meet our threshold." The adjuster found some damage but says it doesn't reach the carrier's count within a test square to total the slope or roof. This is often a slope-selection or test-square-placement problem.
4. "This is old damage / prior storm, not this date of loss." The adjuster says the marks are weathered and predate the claimed event. This is a freshness-and-dating problem.
5. "I didn't find storm damage at all." A flat no. Frequently this means the adjuster inspected the wrong slopes, rushed, or never got into a test square, especially with high-volume CAT files.
6. "It's mechanical / foot-traffic / manufacturing defect / installation." The adjuster attributes the marks to something other than hail. This is a pattern-recognition disagreement.

Each of these has a specific, factual response, and the responses do not transfer. Arguing "but there's clearly damage" against a cosmetic-exclusion position is useless; proving mat fracture is the only thing that moves it. Arguing freshness when the real problem is the adjuster never inspected the north slope wastes everyone's time. So before you respond, get the adjuster to tell you, ideally in writing on the estimate or denial, exactly which of these it is. The denial letter or the estimate notes usually say. If they don't, that itself is something to request.

A diagnostic table you can run on any disagreement

Notice the right-hand column. In almost every row, the thing that does not help is louder opinion, and the thing that does help is a specific, photographable physical fact. That is the entire philosophy of handling a disagreement: convert it from a contest of opinions into a comparison of documented conditions against the carrier's own stated criteria.

The on-the-roof and on-site response, in real time

The best place to resolve a disagreement is on the roof, during the adjuster meeting, before anything is finalized. A contractor who knows how to be present at that meeting, professionally and inside their lane, resolves a large share of disagreements before they ever become denials in writing.

Be at the inspection, and run it like a professional

Schedule to be there when the adjuster inspects. Not to argue, but to make sure the adjuster sees what you saw. This is completely legitimate: you are the contractor who inspected the roof, and you are showing the person evaluating it the conditions you documented. You are not negotiating coverage; you are pointing at shingles.

How a sharp contractor runs the adjuster meeting:

1. Get the date of loss and the claim basics straight up front, so you are both working the same event. Confirm which storm date the claim is filed under.
2. Walk the soft-metal collateral first, from the ground. Gutters, downspouts, vents, turbine caps, AC fins, window screens. This establishes, before anyone is on the roof, that a real hail event of meaningful size hit this specific property. It frames everything above as "given that hail clearly hit here, let's look at what the field did."
3. Get the adjuster into your test squares. You already chalked representative slopes during your inspection. Take them to the storm-facing slope you identified, not a random one. Let them count what you counted.
4. Press-test in front of them on a couple of hits. A soft, mat-fractured bruise that gives under a thumb is the single most persuasive thing on the roof. You are not telling them it's functional; you are letting the shingle show them.
5. Point out the directional pattern between slopes. If the south and west slopes are hammered and the north is clean, that consistency with the wind-driven event is itself evidence it's hail and not random wear.
6. Stay factual and unemotional. The moment you get adversarial, a borderline call tilts against you, and you have given the adjuster a reason to dig in. Treat them as a professional applying a standard, and make meeting the standard easy.

If the adjuster agrees on the roof, you have resolved it before it became a disagreement at all. Get the scope and estimate, and move on. Most of the rest of this is for when that doesn't happen.

When they disagree on the roof, do this, not that

The instinct is to argue. Don't. Instead:

• Ask them to articulate the specific reason, in their words, mapped to the six shapes above. "Help me understand what you're seeing. Is the call that the impacts are cosmetic, or that the count doesn't meet threshold?" You need to know which battle you're in.
• Ask which slopes they inspected and where they placed their test square. A startling number of disagreements come from an adjuster who scored a single, non-storm-facing slope. If they didn't test the slope the soft-metal read points to, that is a factual gap you can name calmly.
• Show, don't tell. If they called it cosmetic, lift a shingle and show the mat fracture. If they called it old, show the fresh stripped asphalt next to weathered marks. Put the physical fact in front of them.
• Document the disagreement itself. Note what they inspected, what they concluded, and what you showed them. You'll want this if it goes to reinspection.
• Do not promise the homeowner anything about how this resolves, and do not start "negotiating" the claim. Your job is to make the conditions clear. The homeowner and carrier own the outcome.

A note on tone that pros internalize: the adjuster talks to a dozen contractors a week, and most of them are either incompetent or combative. Being the calm, precise, evidence-first contractor makes you the one whose roofs get the benefit of the doubt on every borderline call after this, not only this one. Your reputation with the local adjuster pool is an asset you are building or spending at every meeting.

Build documentation that wins before the disagreement happens

Here is the uncomfortable truth: most disagreements are won or lost at your inspection, days before the adjuster shows up. If your documentation is thin, no clever response saves it. If it's airtight, you barely have to argue. The strongest move against an adjuster who disagrees is documentation so complete that disagreeing requires them to ignore specific, dated, photographed physical facts, which a professional is reluctant to do on the record.

The documentation packet that holds up

For every roof you intend to stand behind, build this before the adjuster ever arrives:

• A dated, mapped storm reconstruction. The specific date of loss, the NWS severe thunderstorm warning and its stated hail size, ground reports (SPC/Local Storm Reports) of stone sizes near the address, and a radar-derived hail swath (MESH within the MRMS framework) showing the property sat in a damaging core. This is corroborating context that a real, sizable hail event hit the area on that date. It is not proof of damage to the specific roof, and you never present it as such, but it answers "did anything even happen here" before the adjuster can wave the claim off as a fishing expedition.
• Soft-metal collateral photos. Dented gutters, downspouts, vent caps, turbines, AC fins, screens, with the directional pattern noted. This proves an event of meaningful hail size struck this property, which is the foundation under everything on the roof.
• Per-slope test-square documentation. A chalked 10-by-10 test square on each slope, scored separately, with the storm-facing slopes emphasized. Photos wide, mid, and macro, with a coin or tape for scale next to representative bruises.
• Press-test/mat-fracture evidence. Close-ups of bruises showing granule-stripped centers and, where you can do it without further damaging the roof, a lifted shingle showing the fractured mat. This is the evidence that defeats "cosmetic."
• Freshness indicators. Fresh stripped asphalt and displaced granules versus weathered, re-oxidized old marks, to tie the damage to the claimed date and defeat "old damage."
• Pattern documentation. Photos establishing the random distribution of impacts across the slope, contrasted with any genuinely patterned marks (so you can address, not ignore, the foot-traffic or manufacturing-defect argument honestly).
• Roof particulars. Shingle type, layers, approximate age range, slope orientations, pitch, and any prior repair evidence.
• Your estimate. A clean, itemized repair/replacement estimate at realistic local pricing, including code-required items (more on code below).

The difference between a packet like this and a handful of blurry roof photos is the difference between a five-minute approval and a three-week fight you lose.

Photograph like the adjuster's supervisor will see it

Assume your photos will be reviewed by someone who was never on the roof, in an office, weeks later. That reviewer is who you are really documenting for in a disagreement, because a reinspection or escalation gets decided by people looking at images, not memories. So:

• Every test square gets a wide shot (locating it on the slope), a mid shot (the chalked area), and macro shots (individual bruises with scale).
• Caption everything with slope orientation and what it shows. "South slope test square, 9 functional hits" beats an uncaptioned photo every time.
• Show, don't crop. A close-up of a single bruise with no context can be dismissed; a sequence that locates it on a slope full of chalked hits cannot.
• Capture the collateral in the same visit so the date ties together.

The code angle that adjusters routinely under-scope

A frequent, legitimate disagreement is not about whether there's damage but about scope: the adjuster writes a repair or a partial that ignores what local building code requires when you open the roof. This is squarely in your lane as the contractor, because you are the one who has to build a code-compliant roof.

Common code-driven scope items that get missed:

• Ice-and-water shield in eaves/valleys where the local code amendment to the International Residential Code requires it.
• Drip edge, which the IRC requires at eaves and rakes and which many older roofs lack.
• Decking/sheathing requirements when the existing deck won't meet fastening or spacing requirements once exposed.
• Number of layers / tear-off requirements where code prohibits another overlay.
• Ventilation requirements that trigger when you re-roof.
• Matching issues where a discontinued shingle or a partial-slope repair can't be made to match, which many states' insurance regulations and policy "matching" provisions address.

When you cite code, cite the specific provision (the IRC section or the local amendment), and provide it as a documented part of your estimate. You are not arguing coverage; you are stating what code requires to legally and properly complete the roof, which the estimate has to reflect. Adjusters and carriers generally accept documented, code-required line items when they are specific and sourced. This is one of the most reliable places to recover a too-low scope, and it is entirely inside the contractor lane.

How RoofPredict strengthens the documentation, honestly

A lot of what wins disagreements is the front-end work: knowing the roof was genuinely old enough to be vulnerable, knowing the storm physics actually hit that specific roof, and showing up to the adjuster meeting with a dated, mapped basis for being there at all. That front-end is exactly what RoofPredict is built to provide, and it's worth being precise about what it does and does not do, because overstating it would be the fastest way to get a contractor in trouble.

RoofPredict gives you two things per address before anyone climbs a ladder. First, a roof-age estimate expressed as a range (for example, "this roof reads as roughly 18 to 24 years old"), derived from aerial imagery over time. Second, storm modeling at the level of the individual roof, not the ZIP or the county: it models hail and wind physics per roof to estimate which specific roofs in a storm's path most likely took meaningful impact, rather than only showing where the storm passed. A hail map tells you where it hailed; the per-roof modeling estimates which roofs the storm most likely wore out.

Where that helps a disagreement:

• It supports your "why I'm here" basis. Going into an adjuster meeting on a roof that the modeling flagged as both aging and in the damaging part of a storm track means your inspection wasn't a fishing expedition, it was a targeted look at a roof the data said was vulnerable. That context, paired with your physical documentation, makes the claim look exactly like what it is.
• The age range supports a borderline functional call. When an adjuster is on the fence between "cosmetic" and "functional," an older roof bruises at lower thresholds, and a defensible age range corroborates that the roof was at a vulnerable age. It supports your physical evidence; it does not replace it.
• It tightens which roofs you stand behind in the first place. The cleanest way to never lose a disagreement is to only file the roofs that genuinely have functional damage. Ranking by age and per-roof storm exposure up front means your reps spend their hours on the roofs most likely to verify, so the claims you do support are the strong ones.

Now the honest limits, because they matter and because pretending otherwise crosses lines:

• The age output is a range, not a date, and the storm modeling is odds, not proof. Neither is evidence of damage on a specific roof. You never hand an adjuster a RoofPredict report and call it proof the roof is damaged, because it isn't, and presenting modeled data as proof of loss is exactly the kind of move that gets contractors and claims in trouble. The physical inspection proves the damage. The modeling tells you where to look and supports the context.
• It does not handle, file, negotiate, or approve any claim, and neither do you. It is front-of-funnel intelligence and documentation support. The homeowner owns the claim; the carrier decides coverage.
• It is not a lead service and it does not replace getting on the roof. It ranks the doors and supports the context; your hands, eyes, chalk, and camera prove the damage.

Used that way, the data does the part it's good at (targeting the right roofs and supplying dated, mapped, age-aware context) and your inspection does the part only an inspection can do (proving functional damage on the actual roof). That division is also what keeps everything UPPA-safe.

The formal disagreement path: reinspection, escalation, and the homeowner's tools

When the on-roof and documentation work doesn't resolve it and you have a written denial or an under-scoped estimate, there is a defined path. Walk it in order, and stay in your lane at every step: you supply documentation and a code-compliant estimate; the homeowner makes the requests and decisions to their carrier.

Step 1: Get the denial in writing and read it precisely

Before responding, get the carrier's position in writing, the estimate, the photos the adjuster relied on if available, and the specific reason. You cannot rebut a position you can only half-hear over the phone. The written denial usually states which of the six shapes you're dealing with, and which policy provision (if any) it leans on. If the homeowner only has a verbal "no," have them request the written explanation. Many states' insurance regulations require carriers to provide a written basis for a denial.

Step 2: Assemble a focused supplement or rebuttal packet

This is documentation, not argument. The packet, which the homeowner submits to their carrier, should contain:

• A short, factual cover summary: date of loss, what was inspected, what was found, and what specifically is in dispute (named precisely, mapped to the adjuster's stated reason).
• The targeted evidence that defeats the specific position (mat-fracture close-ups for "cosmetic," freshness photos for "old damage," per-slope test squares for "not enough hits," skipped-slope photos for "no damage found").
• Your itemized, code-cited estimate.
• The dated storm reconstruction as context.

Keep it tight and on-point. A focused packet that answers the exact objection beats a 200-photo dump that buries the three images that matter.

Step 3: Request a reinspection

If the disagreement is substantive and your documentation supports it, the homeowner requests a reinspection (sometimes a second adjuster, sometimes a re-ladder by the same one). Be present for it, run the same disciplined on-roof process, and make sure the reinspecting adjuster gets into the storm-facing test squares this time. A clean reinspection request that says, factually, "the prior inspection did not include the south and west slopes where the soft-metal collateral indicates the hail concentrated" is far more effective than "we disagree."

Step 4: Escalate within the carrier

If a reinspection still misapplies the criteria, the homeowner can escalate: ask for a supervisor or claims manager review, and submit the supplement formally. Again, the homeowner is the one escalating their own claim. Your role is to keep supplying clean documentation.

Step 5: The homeowner's policy and regulatory tools (theirs, not yours)

These exist and you should know them so you can keep the homeowner informed about who does what, but be very careful: invoking, managing, or advocating these for the homeowner against the carrier is where you risk crossing into public adjusting. You inform; the homeowner (or a licensed professional they choose) acts.

• Appraisal. Most property policies contain an appraisal clause for disputes over the amount of loss (not coverage). Each side picks an appraiser, the two pick an umpire, and they resolve the dollar dispute. It's the homeowner's contractual right to invoke, not the contractor's, and it applies to amount, not whether the peril is covered.
• A licensed public adjuster. If the homeowner wants professional representation against the carrier, that is what a licensed public adjuster is for. You are not one (unless you actually hold that license, which most roofers do not and cannot while also doing the work), and you must not act as one. Pointing a homeowner to the existence of licensed public adjusters is informational; doing the public adjuster's job without the license is illegal in most states.
• The state Department of Insurance. Homeowners can file a complaint with their state DOI (in Texas, the Texas Department of Insurance) if they believe the carrier handled the claim improperly. Again, the homeowner files it.
• Attorney / legal counsel. For coverage disputes (not only the dollar amount), the homeowner's recourse may be legal. That's their decision and their counsel's domain.

The reason the lane discipline here is more than legal caution, it is good business: a contractor who tries to be the homeowner's adjuster and lawyer takes on liability, invites a regulatory complaint, and muddies the clean contractor role that makes adjusters trust their documentation. Stay the documentation expert. Let the homeowner own the claim and bring in licensed help if they want it.

A worked example: turning a "cosmetic" denial around the right way

Walk it end to end so the path is concrete.

A homeowner's roof took 1.5-inch hail on a dated April event. The contractor's inspection found clear functional damage: soft, mat-fractured bruises in a random pattern on the south and west slopes, granule-stripped centers, fresh asphalt, plus dented gutters and mashed AC fins on the south side. The contractor documented per-slope test squares (south: 11 functional hits; west: 9; north: 2; east: 3), photographed the collateral, and built a code-cited estimate.

The carrier's IA, working a heavy CAT file, climbed up, scored a single test square on the east slope (3 hits), and wrote it up as "cosmetic, does not meet threshold." A flat under-call driven by inspecting the wrong slope.

Here's the disciplined response, in order:

1. Diagnose. The denial says "cosmetic" and "doesn't meet threshold," but the real defect is slope selection: the adjuster scored the least-damaged slope. This is shapes 1 and 3 layered over a skipped-slope problem.
2. Get it in writing and confirm which slope and test square the adjuster used.
3. Assemble the packet: the south/west per-slope test squares with chalked counts, macro mat-fracture photos defeating "cosmetic," the directional soft-metal collateral showing the hail concentrated south/west, and the dated storm reconstruction. Cover summary names the issue: "the inspection scored only the east slope; the storm-facing south and west slopes, where the soft-metal collateral indicates the hail concentrated, show functional mat fractures at counts well above threshold."
4. Homeowner requests a reinspection, the contractor is present, and the reinspecting adjuster is taken to the south and west test squares and shown press-tested bruises.
5. Resolution: the reinspection scores the storm-facing slopes, the functional damage is documented and meets the carrier's criteria, and the claim is approved with a corrected scope that includes the code-required drip edge and ice-and-water the original repair-only estimate had omitted.

The contractor never argued coverage, never touched the deductible, never represented the homeowner against the carrier, and never called the modeled storm data "proof." They simply made the physical conditions and the storm facts impossible to overlook and let the carrier's own criteria do the rest.

The mistakes that turn a winnable disagreement into a lost one

Even good contractors blow winnable disagreements in a handful of predictable ways. These are the ones that cost the most.

Getting adversarial with the adjuster

The fastest way to lose a borderline call is to make it personal. The instant you treat the adjuster as the enemy, you've given them a reason to defend their position and you've spent your reputation with the local adjuster pool. Stay factual, stay calm, and make meeting the standard easy. The adjuster who trusts your documentation today approves your borderline roof tomorrow.

Arguing opinion instead of showing evidence

"There's clearly damage up there" is worthless. A press-tested, chalked, photographed mat fracture is decisive. Every disagreement is a chance to convert opinion into a physical fact the adjuster has to look at. If you find yourself arguing rather than pointing at a shingle, you've already lost the thread.

Misdiagnosing the disagreement

Responding to a "wrong slope inspected" problem with a freshness argument, or to a cosmetic-exclusion policy with "but it's obviously hail," wastes the one or two real chances you get. Name which of the six shapes you have before you respond, and answer that one.

Letting documentation be thin

If your inspection produced blurry photos, no per-slope test squares, no soft-metal collateral, and no dated storm basis, there's nothing to win the disagreement with. The fix isn't a better argument later; it's a disciplined inspection earlier. Document like the adjuster's supervisor will review it in an office in three weeks, because they might.

Chasing claims that don't have functional damage

Some roofs are cosmetic-only or genuinely just worn out, and writing them up as storm damage is how you lose adjuster trust, get denied, and stick the homeowner with a denial story attached to your company name. The discipline to walk away from a roof that doesn't have functional damage protects every other claim you bring. An honest "no functional damage here" is a long-term asset.

Crossing the UPPA / claims-handling line

This is the one that can end a business, not merely a claim. Negotiating the claim for the homeowner, advertising or implying you'll "handle the insurance," "get it approved," "maximize the settlement," "fight the adjuster," or do anything with the deductible (waive it, rebate it, eat it, "work with you on it"), or presenting yourself as a claims/insurance specialist, can constitute unlicensed public adjusting and, with the deductible, insurance fraud, in many states. Courts have held that even labeling yourself a claims specialist can violate public-adjusting statutes. Stay in the contractor lane: inspect, document, estimate, build. The homeowner owns and files the claim; the carrier decides coverage; a licensed public adjuster (not you) is the one who can represent the homeowner against the insurer.

Treating modeled data as proof

A storm report, a hail-verification report, or a per-roof model says damaging hail probably fell. None of it is proof the specific roof is damaged, and no adjuster approves on "probably." Use modeled and mapped data to target the right roofs and to supply dated context. Let the documented physical inspection prove the damage. Handing an adjuster a model and calling it proof of loss is both ineffective and exactly the kind of overstatement that gets claims and contractors in trouble.

Losing the homeowner's confidence in the gap

A reinspection and escalation can take weeks, and a homeowner left in silence assumes the worst, sometimes that you oversold them. Manage that gap deliberately (next section). A homeowner who understands the process stays steady; one who doesn't churns and tells the neighborhood you couldn't deliver.

Keeping the homeowner steady through the disagreement

The homeowner is watching all of this, and how you manage them often matters as much as how you manage the adjuster. They filed the claim, they own it, and they are anxious. Your job is to keep them informed and inside their lane (their carrier, their decisions) without ever stepping into yours.

What that looks like in practice:

• Set expectations before the adjuster ever shows up. Tell them a disagreement is normal, that adjusters sometimes inspect the wrong slope or rush a CAT file, and that there's a defined reinspection process. A homeowner who's told in advance that a first "no" isn't the end doesn't panic when it happens.
• Explain the roles cleanly. "I document the condition of your roof and give you an estimate. You file and own the claim with your carrier. Your insurer decides coverage. If we disagree with the call, you can request a reinspection, and I'll be there to show the adjuster what your roof took." That sentence, said early, prevents the homeowner from expecting you to "handle the insurance," which you can't and won't.
• Never promise an outcome, a payout, or anything about the deductible. Not "we'll get this approved," not "you won't pay anything," not "we'll take care of the deductible." Those are the exact promises that are both unkeepable and, in the deductible's case, often illegal.
• Give them the supplement to submit, don't submit it as them. You build the documentation packet; the homeowner sends it to their carrier. That keeps the request coming from the policyholder, where it belongs.
• Keep them updated through the gap. A quick honest update during the reinspection wait ("the reinspection is scheduled for the 12th, I'll be there, here's what we're showing them") keeps them steady and keeps your company's name attached to competence, not silence.
• If they want professional claim representation, point them to a licensed public adjuster or counsel, and step back into your contractor role. That protects them and you.

Handled this way, even a claim that takes three weeks and a reinspection leaves the homeowner telling neighbors that you were the contractor who knew exactly what they were doing and stuck with them, which is worth more than any single roof.

A disagreement-response checklist you can hand to a crew

Compress the whole playbook into something a project manager or lead rep can actually run when a denial lands.

Before the adjuster meeting (your inspection):

• Build the dated storm reconstruction (warning, ground reports, radar swath, date of loss).
• Photograph soft-metal collateral with directional notes.
• Chalk and score a test square on every slope; emphasize storm-facing slopes.
• Capture mat-fracture close-ups (defeats "cosmetic") and freshness indicators (defeats "old damage").
• Document the random impact pattern; note any patterned marks honestly.
• Record shingle type, layers, age range, slope orientations, pitch.
• Build an itemized, code-cited estimate.

At the adjuster meeting:

• Be present; confirm the date of loss and claim basics.
• Walk soft-metal collateral first to establish a real event hit this property.
• Take the adjuster to your storm-facing test squares; let them count.
• Press-test a couple of bruises in front of them.
• Stay factual and unemotional; show, don't argue.

When they disagree:

• Get the specific reason and map it to one of the six shapes.
• Ask which slopes they inspected and where the test square was placed.
• Put the defeating physical evidence in front of them.
• Document the disagreement (what was inspected, concluded, shown).

If it's not resolved on the roof:

• Get the denial/estimate in writing with the specific reason.
• Assemble a focused supplement that answers that exact reason.
• Have the homeowner request a reinspection; be present for it.
• If still wrong, support the homeowner's escalation within the carrier.
• Keep code-required scope items itemized and sourced.

Always (lane discipline):

• Inspect, document, estimate, build. Nothing about handling/negotiating the claim.
• No promises of approval, payout, or anything touching the deductible.
• Never call modeled storm data proof of damage.
• Homeowner owns and files the claim; carrier decides coverage; licensed PA or counsel represents the homeowner if they want it.

Putting it together

An adjuster who disagrees is not a wall, it's a documentation problem wearing a clipboard. Diagnose which of the six disagreements you actually have, because the responses don't transfer. Resolve it on the roof when you can, by showing rather than arguing and by getting the adjuster into the storm-facing test squares. When it goes to paper, answer the exact objection with a tight, evidence-first supplement, request a reinspection, and support the homeowner's escalation, always as the contractor who documents conditions, never as the unlicensed adjuster who negotiates coverage.

Most of the win is built before the disagreement, in an inspection thorough enough that disagreeing means ignoring specific, dated, photographed facts. Target the right roofs up front so the claims you stand behind are the strong ones, document like a supervisor in an office will review it weeks later, cite the code that scope-cutting estimates miss, and keep the homeowner informed and inside their lane. Do that consistently and your documentation earns a reputation with the local adjuster pool that pays off on every borderline call after this one. That reputation, the contractor whose roofs are documented right and whose word holds up, is the real asset. A single disagreement handled well is how you build it, one correctly documented roof at a time.

FAQ

What should I do first when an adjuster disagrees with my roof damage assessment?

Diagnose the disagreement before you respond to it. A roof denial usually takes one of six shapes: cosmetic-not-functional, wear-and-tear, not-enough-hits-to-meet-threshold, old-or-prior-damage, no-damage-found, or mechanical/defect/install. Get the adjuster's specific reason in writing, map it to one of those, and answer that exact objection. The responses do not transfer, so arguing the wrong one wastes the limited chances you get. Almost every disagreement is really a documentation gap or a slope/test-square selection problem, not a conspiracy.

How do I respond when an adjuster calls hail damage cosmetic instead of functional?

Cosmetic-versus-functional hinges on mat fracture, so respond with physical evidence, not opinion. Show press-tested bruises that give under a thumb, close-ups with granule-stripped centers, and where possible a lifted shingle showing the fractured mat. The soft, mat-fractured bruise is the single most persuasive thing on the roof. Insisting it looks bad does nothing; proving the mat is fractured is the only thing that moves a cosmetic call. If the policy carries a genuine cosmetic-damage exclusion, the dispute is specifically whether the damage is functional, which makes the mat-fracture evidence even more central.

Should I be present at the adjuster's inspection?

Yes, when you can schedule it. Being present is legitimate and effective: you are the contractor who inspected the roof, and you are showing the person evaluating it the conditions you documented. Walk the soft-metal collateral first to establish a real hail event hit the property, take the adjuster to your storm-facing test squares rather than a random slope, press-test a couple of bruises in front of them, and stay factual. A large share of disagreements get resolved on the roof before they ever become written denials, simply because the adjuster saw what you saw.

Can I negotiate the insurance claim or handle it for the homeowner?

No. In most states, negotiating or representing the homeowner against their insurer is unlicensed public adjusting, which is illegal for a contractor who is not a licensed public adjuster. You inspect, document conditions, and provide an estimate. The homeowner files and owns the claim, and the carrier decides coverage. You also must never touch the deductible (waive, rebate, or absorb it), advertise that you will get the claim approved, or call yourself a claims specialist, since courts have held that even that label can violate public-adjusting statutes. Stay strictly in the contractor lane.

How do I request a roof claim reinspection the right way?

The homeowner requests the reinspection from their carrier, because they own the claim. Make the request factual and specific rather than a general we-disagree. For example: the prior inspection scored only the east slope, while the soft-metal collateral shows the hail concentrated on the south and west slopes, where functional mat fractures appear at counts above threshold. Then be present for the reinspection, run the same disciplined on-roof process, and make sure the reinspecting adjuster gets into the storm-facing test squares. A precise, evidence-pointed request is far more effective than emotion.

What documentation actually wins a roof damage disagreement?

Most disagreements are won at your inspection, days before the adjuster arrives. Build a packet with a dated, mapped storm reconstruction, soft-metal collateral photos with directional notes, per-slope chalked test squares scored separately, mat-fracture close-ups, freshness indicators, pattern documentation, the roof particulars, and a code-cited estimate. Photograph everything as if a supervisor who was never on the roof will review it in an office weeks later, because in a reinspection or escalation that is exactly who decides. Airtight documentation makes disagreeing mean ignoring specific, dated, photographed facts.

What if the adjuster says the damage is old or from a prior storm?

That is a freshness-and-dating disagreement, so answer it with freshness evidence and storm dating. Document fresh stripped asphalt and displaced granules that have not re-oxidized, contrasted with weathered older marks, and tie the impacts to the claimed date of loss using the dated storm reconstruction (the warning, ground reports, and radar-derived swath for that specific date). Confirm up front that the claim is filed under the correct date of loss, because a wrong-date or late-notice problem is a different issue that arguing about shingles will not fix.

Does roof age help or hurt when an adjuster disagrees?

Both, which is why you document it carefully. An older roof bruises at lower hail thresholds, so a defensible age range supports a borderline functional call. But age also makes it easier for an adjuster to write the condition off as wear and tear, and some policies apply roof-age payment schedules or ACV roof endorsements that cap payment regardless of approval. So use the age range to corroborate vulnerability with your physical evidence, and recognize when a low payout is a coverage term rather than a disagreement you can win by documenting more damage.

Can I show the adjuster a storm report or hail model as proof of damage?

No. A storm report, hail-verification report, or per-roof storm model says damaging hail probably fell. None of it proves the specific roof is damaged, and no adjuster approves on probably. Presenting modeled data as proof of loss is both ineffective and the kind of overstatement that gets contractors and claims in trouble. Use dated, mapped storm data to target the right roofs and to supply context for why your inspection was warranted, then let the documented physical inspection, the chalked test squares and mat fractures, prove the damage.

What are the homeowner's options if a reinspection still does not resolve the dispute?

These are the homeowner's tools, not yours, and invoking them for the homeowner risks crossing into public adjusting. Most property policies contain an appraisal clause for disputes over the amount of loss, which the homeowner can invoke. The homeowner can hire a licensed public adjuster for representation against the carrier, file a complaint with their state Department of Insurance, or consult an attorney for a coverage dispute. Your role stays the same throughout: supply clean documentation and a code-compliant estimate, keep the homeowner informed about who does what, and let them or their licensed professional act.