How to Request a Reinspection on a Denied Roof Claim: What to Document

A denied roof claim almost never means the roof is fine. More often it means the first inspection was short, the conditions were bad, the adjuster was carrying forty files that week, or the damage that exists wasn't documented in a way anyone could review later. The homeowner gets a letter, the letter says "no covered damage found," and everyone assumes the story is over.

It isn't. Most carriers have a defined process for a second look. The homeowner can ask the carrier to send the file back out, and that second visit is your chance to make sure the roof is evaluated against what's actually on it. Your job as the roofer is narrow and important: document the roof so thoroughly and so clearly that the facts make the decision instead of a five-minute glance from the driveway. You inspect, you photograph, you measure, you write an accurate repair estimate for your own scope, and you hand that package to the homeowner. The homeowner requests the reinspection. The carrier decides coverage. Stay on that side of the line and you are doing real, defensible work.

What follows is the documentation playbook: how a reinspection actually gets requested, what evidence holds up versus what gets waved off, the test-square method that separates damage from noise, how to build a photo report an adjuster can follow without you in the room, the estimate detail that makes a scope line stick, and the things even experienced crews get wrong. Numbers, checklists, and worked examples throughout. No theory you can't use on a roof Monday morning.

First, get the compliance line straight

Before any of the field work, you need to know exactly where your lane ends, because the difference between a sharp restoration roofer and an unlicensed public adjuster is a real legal line in most states, and crossing it can cost you your license and the homeowner their claim.

Here is the simple version. A roofer may:

• Inspect a roof and the rest of the building envelope.
• Document conditions with photos, measurements, and notes.
• Write an accurate estimate to repair or replace the roof, priced for the work you would actually do.
• State facts about your scope to the carrier, the same way any contractor discusses the job they are bidding.
• Be present during a reinspection at the homeowner's request to point out and explain physical conditions.

A roofer may not, for a fee, do the work a licensed public adjuster or attorney does:

• Negotiate, adjust, or "handle" the claim on the homeowner's behalf.
• Interpret the policy, tell the homeowner what is or isn't covered, or argue coverage.
• Promise a specific payout, an approval, or any settlement amount.
• Promise the deductible will be waived, absorbed, or paid by anyone but the homeowner. In many states that is insurance fraud, full stop.
• Advertise a "free roof" or a roof at "no cost to you."
• Represent the homeowner against the insurer.

A useful test case to keep in mind: in Stonewater Roofing v. Texas Department of Insurance the courts upheld that a roofer cannot even market itself as a "claims specialist" or "insurance specialist" without running into public-adjusting rules. So watch the words on your truck, your website, and your door-knock script as carefully as the words in your estimate.

The frame that keeps you safe and still does the homeowner a lot of good: document thoroughly, write an accurate estimate, hand it over, and let the homeowner file and the insurer decide. Everything below lives inside that frame.

The do-not-say list, for your whole team

Print this and put it where your sales reps and field techs will see it. These phrases get roofers in trouble, and they show up constantly in door-knock pitches:

The instinct behind these lines is fine. The homeowner is overwhelmed and you want to help. Just route the help through documentation and an honest estimate, not through promises about money or coverage that aren't yours to make.

How a reinspection actually gets requested

The homeowner requests the reinspection. You build the case that makes it worth requesting. Knowing the mechanics keeps you from giving bad procedural advice and keeps your name off the request itself.

The realistic sequence

1. The denial letter arrives. It will cite a reason: "no storm-created damage," "damage below deductible," "wear and tear / maintenance," "cosmetic damage excluded," or "damage predates the policy / date of loss." The stated reason tells you exactly what your documentation has to address. Read it carefully and keep it.
2. The homeowner reviews the loss report if they can get it. Many adjusters leave an estimate or summary, often built in estimating software, sometimes with photos. If the homeowner has it, you get a window into what the first inspection saw and missed. They are entitled to ask their carrier for a copy of the inspection report and the estimate.
3. You re-inspect and build the documentation package. This is your part. Detailed below.
4. The homeowner contacts the carrier and requests a reinspection, usually through the assigned adjuster or the claims line, in writing. The request references the new documentation. The homeowner can ask that the original adjuster's supervisor or a different adjuster attend, and can ask for a re-inspection rather than a formal appraisal at this stage. The specifics depend on the policy and the state, and that is a conversation for the homeowner and the carrier, not you.
5. The reinspection happens. Ask the homeowner to request that you be allowed on site. You are there to point at physical conditions and explain what you documented. You are not there to argue coverage or talk dollars with the adjuster.
6. The carrier decides. They may reverse, partially approve, hold the denial, or move to the policy's appraisal clause if there's a dispute over the amount of loss. Where it goes from there is between the homeowner, the carrier, and possibly a licensed public adjuster or attorney the homeowner chooses to retain.

What you write vs. what the homeowner writes

Keep this separation clean:

• You write: the inspection report, the photo documentation, the measurements and diagram, and the repair estimate. These are factual contractor work product about your scope.
• The homeowner writes (or you help them organize, in their words): the actual request to the carrier. Some roofers draft a request "on behalf of" the homeowner. Don't. Provide the documentation; let the homeowner submit it under their own name. A simple, honest cover note from the homeowner is enough: "I'm requesting a reinspection. My roofing contractor re-inspected and documented conditions I'd like the adjuster to review. The report and photos are attached. Please advise on scheduling."

That one boundary, who signs the request, is where a lot of well-meaning roofers drift into adjusting. Don't sign it, don't send it from your email, don't negotiate the response.

What the denial reason tells you to document

The denial reason is a map. Each common reason has a specific factual rebuttal, and your documentation should be built to answer the one you actually got. Documenting the wrong thing wastes everyone's time.

"No storm-created damage found"

The most common denial. The adjuster either didn't get on the roof, didn't find the hits, or attributed marks to something else. Your documentation has to prove storm-created damage exists and is consistent with a storm event. This is where test squares, directional evidence, and collateral damage carry the weight (all below).

"Wear and tear / maintenance / deterioration"

The carrier is saying the roof is old and failing on its own, which is a policy exclusion almost everywhere. Your job is to distinguish age-related deterioration (uniform granule loss, curling, thermal cracking, blistering) from impact damage (fresh, random, directional bruises with granule displacement and a soft mat). Document both honestly. If the roof has both, say so. An estimate that pretends a 24-year-old roof is pristine except for hail destroys your credibility. The honest position is: the roof has normal aging AND discrete storm impacts, and the storm impacts are what created the new functional damage.

"Cosmetic damage only"

Some policies, especially on metal roofs and some shingle policies, carry a cosmetic-damage exclusion that pays only for damage affecting function, not appearance. Your documentation must show the damage is functional: granule loss exposing the asphalt mat (which shortens service life and is a manufacturer-recognized failure mode), fractured mats, punctures, displaced or creased shingles, compromised seals. "Functional vs cosmetic" is a documentation problem, not an argument problem. Show the function.

"Damage below deductible"

The adjuster found some damage but scoped it small, often as a repair to a few shingles rather than a slope or full replacement. This is where a complete, correct estimate matters most. If matching, code-required items, and full-slope repairability are documented and the adjuster scoped a spot repair, the corrected scope can move the number above the deductible. You are not arguing about money; you are providing a complete estimate of the real repair scope. The carrier does the deductible math.

"Date of loss / pre-existing"

The carrier doubts the damage happened on the claimed storm date, or thinks it predates coverage. Storm-date verification data becomes central: documented hail or wind events at that address, with dates and sizes, plus damage characteristics consistent with fresh impact (sharp edges, exposed black mat not yet weathered, granules still present in gutters and at downspout outlets).

The reinspection documentation package: the full checklist

This is the spine of the work. Build the same package every time so nothing gets missed and so it reads consistently to whoever opens it. A reinspection package that an adjuster can follow without you standing next to them is the goal.

Package contents, top to bottom

1. Cover summary (1 page). Property address, claim number, date of loss, date of your inspection, and a plain factual summary: what you inspected, what you found, what the estimate covers. No coverage opinions, no dollar demands. Just "here's what's on the roof."
2. The original denial reason, quoted. So anyone reviewing knows what's being addressed.
3. Roof and storm context. Roof age range (more on this below), roof system type, slope, square count, and documented storm history for the address.
4. Photo report. The core. Organized, labeled, oriented. Detailed below.
5. Test square documentation. Marked squares per slope with hit counts.
6. Measurement / diagram report. Aerial or hand measurements, slope-by-slope, with a labeled diagram.
7. The repair estimate. Line-item, software-based, matching the documented scope.
8. Collateral / supporting evidence. Soft metals, screens, gutters, AC fins, painted surfaces, neighboring damage if visible from the property.

The field checklist (print and clip to your ladder)

• Confirm the homeowner has the denial letter and, if possible, the original loss report
• Verify the date of loss and pull documented storm events for the address
• Walk the ground first: gutters, downspout splash, soft metals, AC unit, fence caps, mailbox, window wraps
• Photograph each elevation from the ground before climbing
• Get on the roof safely (fall protection per OSHA; if you can't do it safely, don't)
• Chalk and shoot a test square on each slope, all directions represented
• Count and mark hits in each square; note size and direction
• Document granule loss, mat exposure, creasing, and seal condition
• Photograph all penetrations, flashings, ridge, hip, valleys, drip edge
• Note and photograph existing aging/wear honestly alongside impact damage
• Measure every slope; build a diagram
• Note code items that apply to a repair on this roof (drip edge, ice barrier, ventilation, fastening) per your local code
• Build the estimate to match every documented condition
• Assemble the package and hand it to the homeowner

Photo documentation that actually holds up

Most roofer photo sets are useless to a reviewer: 60 blurry close-ups with no slope reference, no scale, no order. A reviewer can't tell where a shot was taken, whether the mark is fresh, or how big it is. Fix that and your documentation jumps ahead of most of what carriers see.

The four-shot rule for every condition

For each individual damage point you want to count, take four photos in this order:

1. The orientation shot. Wide, showing the whole slope with the damage area in frame, so the reviewer knows which slope and where.
2. The context shot. Medium, the test square or a few-foot area, showing the cluster of hits in relation to each other.
3. The detail shot. Close, the single impact, filling the frame.
4. The scale shot. The same impact with a reference: a coin, a chalk circle of known size, a hail gauge, or a tape. A bruise means more when the reviewer can see it's the size of a quarter, not a freckle.

Four shots per point sounds like a lot. On a real hail roof you're documenting maybe 8 to 15 representative points per slope, not every hit, so it's manageable and it's the difference between "some marks" and a documented, measurable pattern.

Labeling and metadata

• Keep the timestamps and geotags on. Date-stamped, location-tagged photos answer the "when and where" question before anyone asks. Most phones embed this; don't strip it. Use an inspection app that preserves EXIF data.
• Chalk the slope and direction on the deck where it'll appear in your orientation shots: "FRONT / S-facing" etc. Now every close-up traces back to a slope.
• Number your test-square hits in the photo with chalk so the count in the photo matches the count in the report.
• Shoot in good light. Overcast or low-angle light shows bruising and surface deformation far better than flat noon sun. If the first adjuster shot it at high noon and missed everything, that's part of why.

The photo log

Every photo gets a row:

A logged, oriented, scaled photo set is what lets a reinspection be decided on evidence. It also protects you: months later you can reconstruct exactly what you saw.

The test square: the single most important technique

If there's one method that separates documented damage from "trust me," it's the test square. It's the standard way the industry quantifies hail, and doing it right is most of your credibility.

How to do it

1. Mark a 10-foot by 10-foot square (100 square feet, a "test square") on the slope with chalk. Some inspectors use a 10x10; the point is a defined, repeatable area.
2. Do one on every slope and make sure all roof orientations (N/S/E/W facing) are represented. Hail is directional; the storm-facing slopes take more hits. Showing the pattern matches a real storm direction is powerful evidence against the "it's just wear" denial.
3. Find and circle every impact inside the square. A true hail impact on asphalt shingles shows: granule loss exposing the black mat, a bruise that feels soft/spongy when you press it (the mat fibers are fractured), often a roughly circular shape, and random distribution.
4. Count the hits per square. Many carrier guidelines and the broader industry treat a threshold number of hits per 100 sq ft (commonly cited around 8 to 10 functional hits per square, though carriers vary) as the line for slope or roof replacement versus repair. Document the actual count; don't manufacture it.
5. Photograph the marked square (orientation, context, detail, scale) with the hits numbered.
6. Record direction. Note which way the bulk of impacts face. Directional consistency across slopes tells the storm story.

Reading what you find honestly

This is where your integrity shows and where your documentation either survives scrutiny or collapses.

• Hail bruise: soft when pressed, granules displaced, mat exposed and possibly fractured, fresh black appearance, random. Functional damage.
• Mechanical / foot-traffic / blistering: often hard, raised, regular, or in walk paths. Not storm. Don't count it.
• Manufacturing defect / thermal cracking: straight-line or pattern cracks, uniform. Not storm.
• Normal granule loss / aging: uniform across the slope, heaviest in water paths, no soft spots. Not storm.

Write down the non-storm conditions too. A report that distinguishes the four and counts only true impacts reads as the work of someone who knows the roof, which makes the impacts you DO count believable. A report that calls every blemish hail reads as a sales pitch and gets discounted entirely.

Worked example: a test-square report that holds up

Slope: Rear, North-facing. Test square: 10' x 10' chalked at center of slope. Impacts counted: 11. Characteristics: circular granule loss 0.75"-1.25" diameter, mat exposed, soft/spongy on palpation at 9 of 11, consistent with hail. Distribution random. Predominant impact direction: from NW (consistent with documented storm track). Non-impact conditions noted: light uniform granule loss in water channels (age-consistent, not counted); one mechanical scuff near plumbing boot (foot traffic, not counted). Photos 040-058. Square marked, hits numbered 1-11 in photo 041.

That paragraph does more than a hundred unlabeled close-ups. It's specific, it's honest about what isn't damage, and it ties to a storm direction and date.

Storm-date and storm-event verification

For any denial touching "no storm," "wrong date," or "pre-existing," you need to connect the roof's condition to a real, dated weather event at that exact address. This is also where good data saves you from chasing roofs that never actually got hit.

What counts as verification

• Documented hail reports near the address with date and estimated stone size. NOAA's Storm Prediction Center and Storm Events Database catalog reported hail and wind events. Local National Weather Service offices issue storm summaries.
• Radar-derived hail estimates for the location and date (many weather-data providers reconstruct hail swaths and max estimated stone size from radar).
• Wind event records for wind-driven denials (creased, lifted, or torn shingles; missing tabs).
• The physical evidence's freshness corroborating the date: sharp impact edges, mat not yet weathered gray, granules still loose in gutters and at downspout outlets rather than washed away.

Matching the physics to the roof

The strongest documentation lines up three things:

1. A dated storm event of sufficient intensity at the address.
2. Directional damage on the storm-facing slopes consistent with that storm's track.
3. Collateral soft-metal damage (gutters, vents, AC fins, screens) at sizes consistent with the reported stones.

When those three agree, the "it's just old" or "wrong date" story gets hard to maintain, because age doesn't dent an aluminum gutter on only the NW elevation on a specific Tuesday.

Ground-level and collateral evidence: the part most reports skip

The roof gets all the attention, but the strongest hail documentation often lives at eye level. Soft metals and painted surfaces dent and spatter at hail sizes that barely mark a shingle, so they're an independent record of the storm's intensity and direction that an adjuster can verify without a ladder. Walk the property before you climb and document every one of these:

• Gutters and downspouts. Dents, especially on the storm-facing elevations. Photograph with a tape or coin for scale. Dent diameter roughly tracks stone size.
• Window screens and wraps. Hail tears or dimples aluminum screen frames and bends mesh. Photograph the screens and the bent frames.
• Air-conditioner condenser fins. The single best soft-metal witness. Combed-over or flattened fins on one side of the unit show both that hail hit and which direction it came from. Photograph the damaged side and the undamaged side together.
• Fence caps, mailboxes, light fixtures, garage doors. Aluminum and thin steel show dents and spatter marks. Spatter (clean spots where the stone knocked dirt or oxidation off a painted or weathered surface) is fresh-impact evidence that washes away over time, so its presence helps the date story.
• Window-sill paint, deck boards, and grills. Spatter and chips, photographed with scale.
• Neighboring damage visible from the property. If the house next door has obvious storm damage visible from your client's yard, note it. Don't trespass; document only what's visible from where you're standing.

Why collateral evidence carries weight

A shingle bruise requires the adjuster to trust your read of "soft and fresh." A dented AC fin or a torn screen frame is unambiguous and verifiable on the ground. When the soft-metal damage is directional and the sizes match the reported stone, it independently corroborates the roof impacts and the storm date, which is exactly the kind of evidence that's hard to wave off as wear and tear. Build a soft-metal section into every reinspection package, with its own short photo log, even when the roof evidence feels strong. It often does more work than the roof shots.

Interior and attic documentation when it applies

For leaks, wind-driven rain intrusion, or denials that question whether damage is "functional," interior evidence can close the loop. Don't manufacture it, but document it when it's real:

• Attic deck and underside. Daylight visible through the deck, wet or stained sheathing under specific impact or wind-damage locations, and lifted fasteners. Photograph from inside with the location noted so it maps to the slope above.
• Ceiling and wall stains beneath documented roof damage, photographed with a moisture-meter reading where you have one. A moisture reading turns "looks like a stain" into a recorded number.
• Date correlation. Fresh water intrusion that lines up with the claimed storm date and with exterior damage at the same location ties the interior to the event.

Keep the interior documentation factual and tied to physical locations. The point isn't to inflate the claim; it's to show that the exterior damage you documented has consequences inside, which is the definition of functional rather than cosmetic.

Keep a clean timeline and chain of custody

Months can pass between a denial, a reinspection request, and a decision. Your documentation has to hold up against the question "how do we know this is the same roof on the same date you say?" Protect it:

• Date- and location-stamp everything by keeping EXIF data intact and using an inspection app that logs the capture time and GPS.
• Keep your originals. Store the unedited photo files. Annotated copies are fine for the report, but keep the originals so the metadata is verifiable.
• Log who inspected, when, and in what conditions (weather, light, access method). A one-line entry per visit is enough.
• Don't edit photos beyond cropping and labeling. Brightness adjustments and markup that obscure the underlying image undercut credibility. Add chalk and arrows on the roof, in the real photo, not in software afterward.

This isn't bureaucracy for its own sake. A package with intact metadata, preserved originals, and a clear inspection log is one a reviewer can trust at face value, which is the entire goal of a reinspection: let the facts decide without anyone having to take your word for it.

How RoofPredict fits the documentation side

Most of the wasted effort in storm restoration is upstream of the reinspection: crews knock streets that never took a real hit, or chase a denial on a roof that genuinely has only age-related wear. The data that prevents that is the same data that strengthens an honest reinspection package, which is where RoofPredict is built to help.

RoofPredict tells a contractor, address by address, which roofs are most likely due: a roof-age range estimated from aerial imagery (a range, not a precise install date, because you can't read a permit off a satellite photo), plus storm exposure modeled per individual roof from hail and wind history. It's a targeting and enrichment tool. You point it at a neighborhood or feed it your own list, and it ranks the roofs by the combination of aging-out and storm-worn so your crews and your mailers hit the doors most likely to have a real, documentable problem.

For a reinspection specifically, two outputs do honest work in your package:

• The per-roof storm history supports the "when and how hard" question with documented hail/wind events modeled to that address, which complements (never replaces) the official NOAA/NWS records you cite.
• The roof-age range gives context for the wear-vs-impact discussion: a roof in a 6-to-12-year range with fresh directional impacts tells a different story than a 28-year-old roof, and naming the range honestly is more credible than pretending you know the exact install date.

Honest limits, because the documentation only holds up if you're straight about it: an age range from imagery is not a manufacture date or a permit, and storm modeling gives you odds and exposure, not proof that a specific shingle failed on a specific day. The roof itself, your test squares, and your photos are the evidence. RoofPredict tells you which roofs are worth the climb and gives you supporting storm context; it does not handle claims, decide coverage, or replace what you document on the deck. Used that way it keeps your crews on the roofs that can actually buy a re-roof and keeps your reinspection packages pointed at roofs that genuinely have something to find.

The estimate: where most reinspection packages fall apart

You can document the damage perfectly and still get nowhere if the repair estimate is thin, generic, or doesn't match the photos. The estimate is a factual statement of what your repair scope costs. Build it like one.

Use estimating software the carrier recognizes

Most carriers and adjusters work in Xactimate, and many also use Symbility. An estimate built in line-item software with current local pricing speaks the same language as the adjuster's own estimate, which makes a line-by-line comparison possible. A one-line "replace roof $14,500" can't be compared to anything. A 40-line itemized estimate can be checked, agreed, or disputed line by line, and that's exactly the conversation you want, because it's about scope, not about pressure.

Build the scope to match the documentation, exactly

Every line in the estimate should trace to something in your photos and notes:

• Tear-off and disposal by the documented square count and layers
• Underlayment, ice-and-water barrier where code or the existing condition requires it
• Drip edge, starter, ridge/hip, and the specific flashings you photographed
• Ventilation components present on the roof
• Steep/high charges where slope and stories warrant
• The shingle and accessory items that match the existing system

If a line isn't in your documentation, don't put it in the estimate. If a condition is in your documentation, make sure there's a line for it. Mismatch between the photos and the estimate is the fastest way to lose credibility.

Don't skip the code items

The single most common reason a corrected estimate legitimately moves above a deductible is code-required work the first scope ignored. When a repair triggers your local code (a percentage-of-slope rule, current fastening requirements, ice-barrier requirements in cold climates, drip-edge requirements, ventilation minimums), those items belong in the estimate because the law requires them on the actual repair. Cite the applicable code section. The International Residential Code and your locally adopted amendments are public; reference the real section, not a vague "code requires it."

A short worked example of how code items legitimately change a number:

Notice what's happening: you're not inflating anything. You're documenting that a real repair to this roof, done to code, is a slope or a roof, not three shingles. The carrier still decides. You just gave them a complete, accurate scope to decide on instead of an incomplete one.

Matching: document it, don't argue it

When damaged shingles can't be matched to the existing roof (color, profile, or a discontinued line), that's a documentation task. Photograph the existing shingle, identify the product if you can, and note availability. Many states and many policies address matching for line-of-sight uniformity. Your job is to document the mismatch factually (here's the existing product, here's why a partial repair won't match the surrounding slope) and let the policy and the carrier handle the coverage question. Document the fact; don't argue the law.

The reinspection visit itself

The package is built, the homeowner has requested the reinspection, and the carrier scheduled it. Here's how to be useful on site without stepping over the line.

Before the visit

• Confirm the homeowner has formally requested your presence with the carrier.
• Re-chalk your test squares if rain or time washed them out, so the adjuster sees exactly what you documented.
• Have your package printed and on a tablet. Hand a copy to the adjuster at the start.
• Brief the homeowner: they file and decide, you point at the roof. Keep roles clear.

During the visit

• Get the adjuster on the roof. A surprising number of original denials come from ground-only or drone-only looks. The single most valuable thing you can do is have your test squares marked and ready so the adjuster counts hits in the same squares you did.
• Point at physical conditions. State facts. "Here's the test square, eleven impacts, here's the soft spot, here's the mat exposed, here's the directional pattern matching the storm track, here's the dented gutter on the same elevation."
• Stay off coverage and money. If the adjuster raises policy interpretation, deductible, or settlement, that's between them and the homeowner. You talk about the roof.
• Don't get adversarial. "Fighting the adjuster" is both bad strategy and the kind of language that gets roofers accused of adjusting. You're a contractor showing your scope. Be the most factual, least dramatic person on the roof.

After the visit

• The carrier issues a decision. If the scope is agreed, you proceed with the repair on the agreed scope.
• If a genuine dispute over the amount of loss remains, the policy's appraisal clause may be the mechanism, where each side picks an appraiser and an umpire decides. Whether to invoke it is the homeowner's decision with their carrier (and possibly their own retained professional). You can explain that the mechanism exists; you don't run it.
• If the homeowner wants someone to actually represent them on coverage, that's a licensed public adjuster or an attorney, which is a different licensed role than yours. Refer, don't become it.

What pros get wrong

Even experienced crews lose reinspections for avoidable reasons. The pattern across all of them: documentation that's incomplete, inconsistent, or oversold.

Overcalling damage

The fastest way to lose every borderline claim you'll ever submit is to get a reputation, with the local adjusters, for calling every roof a total. Adjusters talk, and they remember which contractors' reports they can trust. Count real impacts. Note non-storm conditions honestly. A roofer whose reports are calibrated gets the benefit of the doubt on the close ones. A roofer who cries hail on every roof gets a skeptical second look on everything, forever.

Photos with no orientation or scale

Covered above, and it's the number-one fixable failure. A close-up of a dark mark, with no slope reference and nothing for scale, proves nothing. Four-shot rule, every condition, every time.

Ignoring the stated denial reason

Documenting hail beautifully doesn't help if the denial was "date of loss." Read the letter. Build the package to answer the actual reason. A reinspection package that addresses a different objection than the one in the letter just confirms the denial.

Estimates that don't match the photos

A full-roof estimate stapled to photos of three damaged shingles, or a slope of documented impacts with a three-shingle estimate, both fail. The estimate and the documentation have to tell the same story, line for line.

Crossing the compliance line

Drafting the request, negotiating the response, talking deductibles, promising approval, advertising free roofs. Every one of these can void the homeowner's claim, expose you to a public-adjusting violation, or both. The discipline of staying on the document-and-estimate side isn't just legal cover; it's what makes your work credible, because you're not the party with a thumb on the scale.

Wasting the climb on roofs with nothing to find

The quieter failure: spending your crew's time re-inspecting and re-documenting roofs that genuinely have only age-related wear, because someone wanted a claim that isn't there. Honest targeting, knowing which roofs actually took a storm and which are simply aging, keeps your documentation effort on roofs that have a real, defensible finding. That's better for your numbers and for your reputation with carriers.

A clean reinspection workflow, start to finish

Put it together as a repeatable process your whole team runs the same way:

1. Intake. Homeowner has a denial. Get the denial letter and, if available, the original loss report. Read the stated reason.
2. Pre-qualify the roof. Confirm there's a documented storm event at the address for the date of loss and that the roof's age and condition make a real finding plausible. Don't re-inspect roofs with nothing to find.
3. Inspect. Ground first, then roof with proper fall protection. Test squares on every slope, all directions. Honest reading: count impacts, note non-storm conditions.
4. Document. Four-shot rule per condition. Photo log. Test-square report with counts and directions. Measurements and diagram. Storm-event verification.
5. Estimate. Line-item, software-based, scope matched exactly to the documentation, code items included and cited.
6. Assemble. Cover summary, denial reason quoted, context, photo report, test squares, measurements, estimate, collateral evidence. One clean package.
7. Hand off. Give the package to the homeowner. The homeowner requests the reinspection from the carrier, in their own name, attaching your documentation.
8. Attend (if invited by the homeowner). Re-chalk squares, hand the adjuster a copy, get them on the roof, point at physical facts, stay off coverage and money.
9. Proceed or refer. If scope is agreed, do the work. If a coverage dispute remains, the homeowner pursues appraisal or retains a public adjuster/attorney. You stay in your lane.

Run that the same way every time and your reinspection results stop being luck. They become the predictable output of documentation good enough that the facts decide.

The bottom line

A denied roof claim is a documentation problem far more often than it's a "the roof is fine" problem. The reinspection exists precisely because first looks miss things. Your leverage as a roofer is entirely on the evidence side: inspect thoroughly, run honest test squares, shoot oriented and scaled photos, verify the storm and date, and write an accurate, code-correct estimate that matches every condition you documented. Hand that package to the homeowner, let them request the reinspection and let the carrier decide coverage, and stay rigorously off the negotiate/handle/promise side of the line.

Do that consistently and two things happen. Your reinspections start going your way because the documentation is too clear to wave off, and the local adjusters learn that your reports are honest, which helps you on every borderline roof for years. The roof tells the truth. Your job is to make that truth impossible to overlook, on roofs that actually have something to find.

Start with targeting that keeps your crews on the roofs most likely to be due, by age and by storm, and your documentation effort lands where it counts. RoofPredict ranks the roofs and gives you the per-roof storm context; the test squares, the photos, and the estimate are still yours to earn on the deck.

FAQ

Can a roofer request a reinspection on a denied claim for the homeowner?

No. The homeowner requests the reinspection from their carrier, in their own name. The roofer's role is to re-inspect the roof, document conditions with photos and test squares, write an accurate repair estimate, and hand that package to the homeowner to submit. Drafting or sending the request yourself, or negotiating the carrier's response, crosses into public-adjusting territory in most states. Provide the documentation; let the homeowner file.

What is the single most important thing to document for a reinspection?

Test squares. Chalk a 10' x 10' area on every slope, with all roof orientations represented, find and circle every true impact, count the hits, note the direction, and photograph it with the hits numbered. A documented, honest hit count per square is the standard way the industry quantifies hail and is the evidence most likely to change a 'no damage' denial. Count real impacts only; note non-storm conditions separately.

How do I document hail damage so an adjuster takes it seriously?

Use the four-shot rule for each condition: an orientation shot showing the whole slope, a context shot of the cluster, a detail shot of the single impact, and a scale shot with a coin, chalk circle, or hail gauge for size reference. Keep timestamps and geotags on. Chalk the slope and direction on the deck so every close-up traces back to a location. Distinguish soft, fresh, granule-displaced hail bruises from hard mechanical marks and uniform aging, and only count the true impacts.

The denial says 'wear and tear.' How do I respond?

Distinguish age-related deterioration from impact damage in your documentation. Uniform granule loss, curling, thermal cracking, and blistering are aging. Fresh, random, directional bruises with displaced granules, exposed mat, and a soft feel are impacts. Document both honestly. If the roof has normal aging and discrete storm impacts, say exactly that. The storm impacts are the new functional damage; the honest framing is far more credible than pretending an old roof is pristine.

Can I tell the homeowner their deductible will be covered or waived?

No. The deductible is set by the homeowner's policy and is their responsibility. Promising to waive, absorb, or cover it, or advertising a 'free roof,' is insurance fraud in many states and can void the claim. Keep all of your messaging on documentation and an accurate estimate, never on coverage outcomes, payout amounts, or the deductible.

What makes a reinspection estimate stronger than the original?

Three things: it's built in line-item software the carrier recognizes (Xactimate or Symbility) so it can be compared line by line; every line traces to a documented condition in the photos; and it includes code-required items the first spot-repair scope ignored, with the actual code section cited. Code items on a real repair (ice barrier, drip edge, fastening, ventilation) are the most common legitimate reason a corrected scope moves above a deductible. The carrier still decides; you just provide a complete, accurate scope.

How do I prove the damage happened on the claimed storm date?

Connect the roof to a documented, dated weather event at that address. Use NOAA Storm Prediction Center and Storm Events Database records, local National Weather Service summaries, and radar-derived hail estimates for the location and date. Corroborate with physical freshness (sharp impact edges, unweathered mat, granules still in the gutters) and directional collateral damage on storm-facing slopes and soft metals consistent with the reported stone size.

Should I get adversarial with the adjuster at the reinspection?

No. 'Fighting the adjuster' is poor strategy and the kind of language that gets roofers accused of unlicensed adjusting. Be the most factual, least dramatic person on the roof. Get the adjuster onto the deck, hand them your documentation, point at the marked test squares and physical conditions, and state facts about your scope. Leave policy interpretation, deductibles, and settlement amounts to the homeowner and the carrier.

What if the carrier still won't agree after the reinspection?

If a genuine dispute over the amount of loss remains, the policy's appraisal clause may be the mechanism, where each side picks an appraiser and an umpire decides. Whether to invoke it is the homeowner's decision with their carrier. If the homeowner wants someone to represent them on coverage, that's a licensed public adjuster or an attorney, which is a different role than a roofer's. Explain that these options exist, then refer; don't take them on yourself.

How do I avoid wasting time re-inspecting roofs with no real damage?

Pre-qualify before you climb. Confirm there's a documented storm event at the address for the date of loss, and that the roof's age and condition make a defensible finding plausible. Targeting data that ranks roofs by age range and modeled storm exposure, such as RoofPredict, helps keep your documentation effort on roofs that actually took a hit, which is better for your numbers and for your credibility with the local adjusters who remember whose reports they can trust.