Roof Reinspection Guide for Contractors
Learn when to request a roof reinspection, what documentation to prepare, how to present additional damage, and how contractors can support accurate roofing claim review.
Claims Ninja Operations
Purpose
Roof reinspections are often needed when the original inspection or estimate does not fully reflect documented roof conditions. Common reasons include missed storm damage, additional affected slopes, matching disputes, repairability concerns, code upgrade issues, scope omissions, and material identification problems. This guide is the roofing contractor playbook for reinspections after a carrier inspection or estimate does not reflect documented field conditions — not legal advice and not a guarantee of claim outcomes. Claims Ninja supports contractors with documentation standards, supplement packaging, and claim recovery workflows — we are not a public adjuster, carrier representative, or legal counsel.
When to use
Carrier estimate omits documented storm damage on one or more slopes
Signal: Field photos show hail impacts, wind creases, or lifted shingles not reflected in carrier sketch or line items
Additional slopes or elevations affected beyond approved repair area
Signal: Damage boundaries extend past carrier-defined repair limits on sketch or measurement report
Matching or repairability concerns not addressed in carrier scope
Signal: Discontinued shingles, brittle material, or visible mismatch documented but absent from estimate
Code upgrade items or accessories missing from carrier estimate
Signal: Ice and water shield, drip edge, or ventilation items required by jurisdiction not on estimate
Adjuster offers or agrees to site revisit after supplement dispute
Signal: Denial letter cites need for on-site verification, or desk review cannot resolve scope from photos alone
Prerequisites
- Carrier estimate and claim number on file with sketch reference
- Complete documentation package assembled before requesting reinspection — not after scheduling
- Slope-labeled photo set and material identification attempted before reinspection request
- Supplement coordinator or project manager assigned as reinspection point of contact
Required documentation
Roof overview photos
Wide elevation shots of all visible slopes and ridge lines — establishes baseline before reinspection request.
Slope-by-slope damage photos
Each plane labeled consistently (front, rear, left, right, garage, dormer) with damage boundaries visible.
Close-up damage photos
Hail impacts, wind creases, lifted tabs, broken seals, and collateral damage with context shots.
Soft metal photos
Dented or damaged vents, flashings, gutters, downspouts, and other soft metals indexed to estimate lines.
Material identification
Shingle type, manufacturer, color, style, age, and weathering condition documented with supporting photos.
Matching documentation
Availability research, elevation photos, and mismatch concerns when matching is part of the reinspection scope.
Repairability documentation
Test observations, brittle notes, seal strip failure, and collateral damage photos when repairability is in dispute.
Carrier estimate comparison
Table linking carrier sketch lines to field photos, missing slopes, accessories, and code items.
Contractor narrative summary
One-page objective summary of what was missed, where it was found, and how documentation supports requested scope.
Supplement support notes
Indexed references tying each supplement line to specific photos, measurements, or field observations.
Step-by-step process
- 1
When Should a Contractor Request a Roof Reinspection?
- Missed damage — carrier estimate does not include hail, wind, or impact damage documented in field photos.
- Incorrect scope — repair boundaries, removal squares, or replacement areas do not match actual damage extent.
- Additional affected slopes — damage extends to planes not included in carrier sketch or line items.
- Repairability concerns — brittle material, seal strip failure, or collateral damage risk not addressed in approved scope.
- Matching concerns — discontinued shingles, color mismatch, or visible elevation differences not reflected in estimate.
- Code-related omissions — jurisdiction-required underlayment, ventilation, or fastening upgrades missing from carrier scope.
- New documentation after initial inspection — additional photos, measurements, or material identification gathered since carrier visit supports expanded scope.
Request reinspection when documentation supports additional scope — not as a substitute for building the indexed packet first.
- 2
Build the Documentation Package Before Requesting Reinspection
- Overview photos — wide elevations of all visible planes captured and labeled before reinspection request.
- Slope-specific photos — each plane documented with consistent naming in file metadata.
- Close-up damage photos — hail impacts, creases, lifted tabs, and seal failures with context shots.
- Material identification — manufacturer, color, style, age, and weathering recorded with supporting imagery.
- Repairability notes — test observations and collateral damage documentation when partial repair is in dispute.
- Matching documentation — availability research and elevation photos when matching concerns are part of the file.
- Scope comparison — carrier estimate lines indexed to field photos and measurement data.
See the Roof Matching Documentation Guide and Roof Repairability Documentation Guide for detailed standards on those documentation types.
- 3
Compare Carrier Scope to Field Conditions
- Missing slopes — identify planes with documented damage absent from carrier sketch or line items.
- Missing elevations — map street-visible and primary viewing angles where damage exists but scope omits replacement.
- Missing accessories — ridge cap, valley metal, drip edge, pipe boots, and ventilation items not on estimate.
- Missing code items — ice and water shield, starter strip, or ventilation upgrades required by jurisdiction.
- Missing labor — steep/high modifiers, detach-and-reset, or protection items documented but not charged.
- Incorrect repair assumptions — carrier approves partial repair where field conditions support expanded scope.
- 4
Document Additional Roof Damage Clearly
- Hail impacts — photograph impact marks with chalk or contrast aid; note density and test square results where applicable.
- Wind creases — capture creased or folded tabs along wind-exposed edges and ridge lines.
- Lifted shingles — document tabs with broken seal strips or uplift damage on affected courses.
- Broken seals — close-up photos of seal strip failure on shingles that must be disturbed during repair.
- Collateral damage — photograph adjacent courses, valleys, and flashings affected during damage assessment.
- Soft metals — dented vents, flashings, gutters, and downspouts with overview and detail shots.
- Gutters and accessories — document damage to drainage and roof-mounted components.
- Vents and flashing — capture pipe boots, chimney flashings, and penetration details.
- Interior damage if applicable — ceiling stains, attic decking, or insulation damage linked to roof penetration.
- 5
Support Matching and Repairability Issues
- Discontinued shingles — attach manufacturer discontinuation proof and comparable product difference notes.
- Mismatched materials — elevation photos showing visible differences between repair area and adjacent slopes.
- Brittle shingles — test observations and failed lift photos supporting repair limitations.
- Seal strip failure — document lifted tabs that no longer reseal on aged or weathered courses.
- Granule loss — close-up photos of exposed asphalt on shingles that must be disturbed.
- Collateral damage from attempted repair — photograph broken tabs and torn courses at repair boundaries.
See the Roof Matching Documentation Guide and Roof Repairability Documentation Guide for complete documentation standards on matching and repairability disputes.
- 6
Prepare a Clear Reinspection Narrative
- What was missed — list specific damage types, slopes, or line items absent from carrier estimate.
- Where it was found — reference slope labels, elevation names, and photo file identifiers.
- Why it matters — tie each omission to scope impact, code requirement, or repair feasibility.
- What documentation supports it — index photos, measurements, and material records to each claim.
- How it relates to requested scope — map narrative points to specific supplement or estimate lines.
- 7
Common Roof Reinspection Mistakes
- Requesting reinspection without documentation — desk review repeats the same failure when the packet is incomplete.
- Disorganized photos — unlabeled files without slope context make remote review impossible.
- No slope labeling — reviewers cannot locate damage without consistent plane naming.
- Unsupported matching claims — requesting full elevation replacement without availability research or elevation photos.
- Weak repairability notes — asserting brittleness without test observations or collateral damage photos.
- No scope comparison — strong photos exist but cannot be mapped to estimate lines.
- Emotional or speculative language — narratives with unsupported conclusions weaken professional credibility.
- 8
Roof Reinspection Documentation Checklist
- Roof overview photos — wide elevations of all visible planes included and labeled.
- Slope-by-slope damage photos — each plane documented with consistent naming.
- Close-up damage photos — hail, wind, seal failure, and impact detail with context.
- Soft metal photos — vents, flashings, gutters indexed to estimate lines.
- Material identification — type, manufacturer, color, style, age on file.
- Matching documentation — availability research and elevation photos when applicable.
- Repairability documentation — test results and collateral damage photos when applicable.
- Carrier estimate comparison — table linking lines to field evidence.
- Contractor narrative summary — one-page objective overview indexed to scope.
- Supplement support notes — each line tied to specific documentation references.
Roof reinspections are strongest when contractors provide organized, objective documentation that clearly shows what was missed, where it exists, and how it supports the requested scope.
- 9
When Roof Reinspection Supports a Supplement
- Missed damage — additional hail, wind, or impact damage documented on slopes omitted from carrier scope.
- Expanded scope — removal squares, accessory LF, or labor items supported by field photos and measurements.
- Matching issues — discontinued product, color mismatch, or elevation visibility concerns tied to documentation.
- Repairability concerns — brittle material or collateral damage supporting expanded removal scope.
- Code items — jurisdiction-required upgrades documented with permit or code reference.
- Additional materials — underlayment, ventilation, or fastening upgrades supported by field conditions.
- Estimate alignment — each supplement line references specific photos, measurements, or narrative points — educational and documentation-focused, not a guarantee of approval.
Reinspection supplements succeed when documentation, scope comparison, and narrative tell the same story. Carriers evaluate reinspection requests against evidence quality and field conditions — outcomes are never guaranteed.
Quality gates
Documentation package complete before reinspection request
Overview photos, slope photos, scope comparison, and narrative assembled before scheduling.
All photos slope-labeled and indexed
Consistent naming convention across elevations and file metadata.
Carrier scope comparison indexed to evidence
Missing slopes, accessories, and line items tied to specific photos.
Contractor narrative prepared
Objective summary linking omissions to documentation without speculative language.
Supplement lines aligned to documentation
Each requested line references specific photo, measurement, or field note.
Common mistakes
| Mistake | Impact | Correction |
|---|---|---|
| Requesting reinspection without complete documentation | Adjuster arrives without context; same desk review failure repeats after the visit. | Assemble indexed packet with photos, scope comparison, and narrative before scheduling. |
| Disorganized or unlabeled photos | Reviewers cannot locate damage on specific slopes — reinspection request lacks credibility. | Use consistent slope labels in filenames and pair close-ups with overview context shots. |
| No slope labeling in file metadata | Remote reviewers cannot map damage to carrier sketch planes. | Label every photo with slope name and date before uploading to claim file. |
| Unsupported matching or repairability claims | Scope expansion requests denied for insufficient evidence at reinspection. | Follow matching and repairability documentation guides before asserting scope changes. |
| No scope comparison table | Strong photos exist but cannot be mapped to estimate lines — supplement stalls. | Build carrier-to-field comparison indexed to each missing line item. |
| Emotional or speculative narrative language | Professional credibility weakened — adjuster treats file as advocacy rather than evidence. | Use objective language tied to specific photos, measurements, and field observations. |
Requesting reinspection without complete documentation
Impact: Adjuster arrives without context; same desk review failure repeats after the visit.
Correction: Assemble indexed packet with photos, scope comparison, and narrative before scheduling.
Disorganized or unlabeled photos
Impact: Reviewers cannot locate damage on specific slopes — reinspection request lacks credibility.
Correction: Use consistent slope labels in filenames and pair close-ups with overview context shots.
No slope labeling in file metadata
Impact: Remote reviewers cannot map damage to carrier sketch planes.
Correction: Label every photo with slope name and date before uploading to claim file.
Unsupported matching or repairability claims
Impact: Scope expansion requests denied for insufficient evidence at reinspection.
Correction: Follow matching and repairability documentation guides before asserting scope changes.
No scope comparison table
Impact: Strong photos exist but cannot be mapped to estimate lines — supplement stalls.
Correction: Build carrier-to-field comparison indexed to each missing line item.
Emotional or speculative narrative language
Impact: Professional credibility weakened — adjuster treats file as advocacy rather than evidence.
Correction: Use objective language tied to specific photos, measurements, and field observations.
Supplement opportunities
Carrier estimate omits documented slopes or elevations
Slope-labeled photos, measurement report, and scope comparison table showing missing planes.
Line item hint: Additional removal and replacement squares on omitted slopes with accessories
Accessories and soft metals damaged but not on estimate
Close-up and overview photos of vents, flashings, gutters, and ridge cap indexed to lines.
Line item hint: Vent, flashing, gutter, and ridge cap LF or EA items with detach-and-reset
Matching or repairability concerns support expanded scope
Matching availability research, repairability test photos, and elevation context.
Line item hint: Expanded slope or elevation replacement when partial repair is not feasible
Code upgrade items required but missing from carrier scope
Permit requirements, code reference, and pre-tear-off photos showing existing conditions.
Line item hint: Ice and water shield, drip edge, ventilation, or fastening upgrades per jurisdiction
Related resources
Other guides
FAQ
- When should contractors request a roof reinspection? →
- What documentation should be prepared for a roof reinspection? →
- Can missed roof damage be documented after the initial inspection? →
- Why do carriers deny roof reinspection requests? →
- How should contractors organize photos for a roof reinspection? →
- What documentation do carriers expect on roofing claims? →
- What is included in supplement support? →
More resources
- Roof Matching Documentation Guide →
- Roof Repairability Documentation Guide →
- Roofing Supplement Checklist →
- Roofing Claim Documentation Standard →
- Code Upgrade Documentation →
- Roof Measurement Documentation →
- Roof Reinspection Preparation →
- Roofing supplement playbook →
- What is a roof supplement →
- Claims Ninja platform →
Solutions
FAQ
Common questions
Quick answers related to this procedure.
Request a roof reinspection when the carrier estimate does not reflect documented field conditions — missed storm damage, additional affected slopes, matching or repairability concerns, code upgrade omissions, or scope gaps identified after the initial inspection. Build the complete documentation package before requesting the visit, not after scheduling. Reinspection is most effective when photos, scope comparison, and narrative are indexed and ready for adjuster review — outcomes vary by carrier and evidence quality.
Assemble roof overview and slope-by-slope photos, close-up damage shots, soft metal documentation, material identification, matching and repairability records when applicable, a carrier estimate comparison table, a contractor narrative summary, and supplement support notes indexed to estimate lines. Complete the packet before requesting reinspection so the adjuster arrives with context — not legal arguments or guaranteed outcomes.
Yes — contractors can document additional hail, wind, or impact damage discovered after the carrier's initial visit using dated slope-labeled photos, close-up damage shots, measurement data, and a scope comparison showing what was omitted from the carrier estimate. Documentation should be captured as soon as damage is identified and organized before requesting reinspection. Carriers evaluate post-inspection documentation against evidence quality and timing — approval is not guaranteed.
Common denial reasons include incomplete documentation packages, unlabeled or disorganized photos, scope requests not tied to field evidence, unsupported matching or repairability claims, reinspection requested before building the indexed packet, or carrier determination that desk review is sufficient from existing photos. Carriers may also deny when damage appears cosmetic-only or when policy language limits the requested scope — outcomes vary by carrier program and file specifics.
Label every photo with slope name, elevation, and date in file metadata. Capture wide overview shots of each plane before close-up damage detail. Pair every close-up with a context photo showing location on the slope. Group photos by slope and damage type in the claim file index. Tie each photo reference to a specific line in the scope comparison table and contractor narrative — organized, objective documentation supports accurate claim review.
Carriers expect photos of all slopes and damage, accurate measurements, line items aligned to how the roof was built, and code-related accessories where applicable. Supplement opportunities often hinge on drip edge, ice and water shield, ventilation, steep charges, and waste factors documented clearly.
Supplement support includes scope review, line-item analysis, documentation guidance, and carrier-ready supplement submissions. Expert teams identify missing items, pricing gaps, and code-related opportunities — then organize the file so adjusters can review efficiently.
Partner with Claims Ninja
Need help executing on your next claim?
Get a free claim review. We assess scope gaps, documentation, and supplement opportunities — then outline a recovery plan aligned with your operation.