Claim File Operating System™: The Complete Roof Claim Playbook

What’s normal

• Small isolated sections at known leak points (chimney, valleys, penetrations)
• Localized edge rot where gutters/drip edges were compromised
• Decking conditions that are visible once shingles are removed (previously hidden)

What’s abnormal (requires extra scrutiny)

• Large widespread replacement with no visual evidence of long-term saturation
• No photo proof, no marked locations, no measured counts
• “We have to replace a lot” without showing the failing sections and why

Pricing boundaries (how to keep leverage)

• Request a clear unit basis (per sheet / per linear / per section) and a written change order
• Require marked locations + before/after photos
• Confirm the “minimum necessary to restore integrity” (not convenience)

Proof standards (what to document)

• Photo set: wide shot + close-up + a reference marker
• Count and location notes (diagram or annotated photos)
• Moisture/rot indicators: delamination, soft spots, crumbling, fastener failure
• Signed approval record before proceeding (when feasible)

Common failure modes (why roofs fail)

• Exhaust without intake → pulls from the house (moisture) instead of soffit
• Intake blocked by insulation or painted-over soffits
• Mixed exhaust types fighting each other (short-circuit airflow)
• Moisture symptoms: condensation, mold staining, deck warping, rusted fasteners

Pass/Fail verification (simple homeowner logic)

• Pass = intake present + exhaust present + airflow path not blocked
• Fail = one side missing, blocked, or short-circuited
• “Unknown” = no measurements / no photos / no diagram

Proof standards (what “done right” includes)

• Photo proof of intake points (soffit/edge intake) and exhaust points (ridge/roof vents)
• A simple diagram or counts per intake/exhaust type
• Clear statement of changes made (what was added/removed/blocked/unblocked)
• Close-up photos of baffles or clearance where relevant

How this affects warranties + claims

• Ventilation disputes often become warranty disputes later
• A documented ventilation “outcome standard” reduces future blame games
• When in doubt: document the system, not the opinion

High-probability leak zones

• Chimneys: step flashing + counterflashing + cricket geometry
• Walls: step flashing integration with siding/stucco/brick
• Valleys: line control + underlayment integrity
• Penetrations: pipe boots, skylights, vents, satellite mounts
• Transitions: porch to main roof, low-slope connections, dead valleys

Why leaks can show up after replacement

• Previously “sealed by debris” is now exposed (old failure becomes visible)
• Flashing reused when it shouldn’t have been
• Counterflashing not integrated correctly
• Penetration boots not matched/fastened/sealed correctly
• Water is entering upstream and showing up downstream

Diagnosis workflow (safe homeowner version)

• Document interior symptom (photo + date + location)
• Identify likely entry zones above the symptom (chimney/wall/valley/penetration)
• Compare “after install” photos to required assemblies
• Request targeted inspection—not “general reseal”

Safety note: Do not climb roofs. Diagnosis starts with documentation and targeted questions.

Proof standards (what resolves disputes)

• Close-up photos of flashing steps, counterflashing, and termination points
• Photos of penetration boots and fasteners
• Before/after comparisons at known risk zones
• Written statement: what was corrected + where + why

Level 1: Building Code (minimum legal standard)

• Authority: municipality (permit office / inspector)
• Proof: code references + inspection outcomes
• Key reality: code is often a minimum, not “best practice”

Level 2: Manufacturer System (warranty standard)

• Authority: manufacturer installation instructions
• Proof: spec sheets + required components + photo documentation
• Key reality: failing system requirements can void warranty even if code is met

Level 3: Insurance Scope (what the carrier agreed to pay)

• Authority: claim estimate + approvals + supplements
• Proof: approved line-items + documentation + invoices
• Key reality: insurance scope can be incomplete—supplements exist for a reason

How to win “authority disputes”

• Ask: “Which ladder level are we talking about?”
• Require the exact reference: code section or manufacturer instruction page
• Document the gap: code minimum vs system requirement vs scope payment
• Convert the gap into a proof packet (photos + reference + line-item request)

Legit supplement triggers (common)

• Carrier estimate missing required components (starter, drip edge, flashing, ventilation)
• Code-required upgrades (where applicable and provable)
• Documented tear-off discovery (decking/rot) with photos + counts
• Scope mismatch: carrier paid for less than required to restore integrity

Proof requirements (what “clean” looks like)

• Line-item list (what’s missing) + why it’s required
• Photo evidence (before/after/discovery)
• Reference basis: manufacturer system requirement or code/inspection requirement
• Clear pricing basis (units, counts, locations)

Homeowner red flags (possible padding)

• No “why”—just “insurance always pays this”
• No proof photos or counts
• Large additions unrelated to missing scope or discoveries
• High-pressure tactics or confusing paperwork

The decision tree (simple)

• Question 1: What exact line-items are missing?
• Question 2: Is there proof (photos/diagram/requirements)?
• Question 3: Is it tied to code/system/discovery?
• If yes: legit supplement (submit clean packet).
• If no: request proof or decline the item.

When escalation is appropriate

• Repeated missed deadlines with no explanation
• Carrier requests the same documents repeatedly (processing failure)
• No owner of the next step / no named blocker
• Clear scope errors with proof that aren’t addressed

When escalation backfires

• Escalating without a clean packet
• Threat-based language (“I’ll sue”) before a documented basis exists
• Multiple conflicting contacts causing duplication and resets

Escalation order (practical)

• 1) Primary contact (adjuster/desk) with clean packet + specific ask
• 2) Supervisor/team lead request (same packet, same thread)
• 3) Formal follow-up referencing prior attempts and missing action
• 4) Education-only pathways vary by policy/state (appraisal/complaints)—use carefully

Script (copy/paste style)

• Subject: Claim #____ — Missing line-items packet submitted — request review by ____
• Body: “We are in the Scope Alignment phase. The blocker is approval of the attached missing line-items packet. Please confirm receipt and the expected review date. If additional documentation is needed, please list it in one response so the packet can be completed without resets.”

10-day fast track checklist

• Call lender the day the check arrives
• Get their endorsement steps + upload/email method
• Ask: draw rules, inspection/photo requirements, final release triggers
• Open one ticket number and keep one thread
• Submit a clean packet once (avoid “drip feeding” docs)

Clean packet contents (typical)

• Copy of insurance estimate/approval
• Contractor agreement or invoice (per lender requirement)
• Completion photos (or progress photos if partial draw)
• Permit/inspection proof if applicable
• Check images + requested lender forms

Reset-avoidance rules

• Never submit through multiple portals “just in case”
• Never start a second ticket unless instructed
• Always confirm receipt and expected review date
• Keep the packet identical (version control)

Email template (copy/paste)

• Subject: Endorsement Request — Loan #____ — Claim Repair Funds
• Body: “Attached is the requested endorsement packet. Please confirm receipt, provide the case/ticket number, and the expected review date. If you require additional documentation, please list all missing items in one response to avoid resets.”

RCV packet (minimum standard)

• Final invoice (matches approved scope)
• Completion photo set (wide + details at risk zones)
• Permit final / inspection closeout if required
• Supplement approvals (if any)
• Request message: “Please release recoverable depreciation for Claim #____”

Common rejection reasons

• Invoice doesn’t match approved scope/quantities
• Missing completion photos or unclear photos
• Open supplement items not reconciled
• Missing permit/inspection proof where required

Timing expectations (reality)

• Carrier queue times vary (storm volume matters)
• Clean packets move faster than repeated clarifications
• Best practice: request confirmation + expected review date

Submission script (copy/paste)

• Subject: Claim #____ — RCV Release Request — Completion Packet Attached
• Body: “Attached is the completion packet (invoice + completion photos + permit closeout if applicable). Please confirm receipt and the expected processing date for the recoverable depreciation release.”

Repair-leaning scenarios (often)

• Isolated damage limited to a small, repairable area
• Matching materials are available and repairs won’t create new failure points
• No widespread functional compromise indicators

Replace-leaning scenarios (often)

• Widespread impacts across multiple slopes
• System integrity compromised (multiple failure zones)
• Repair would be patchwork with high leak risk
• Matching/repairability issues create continuity failures

Documentation standard (what matters)

• Map damage by slope + density where relevant
• Show functional risk, not just cosmetic debate
• Keep evidence date-stamped and organized (Vault Map)

The decision gate question

• “Can a repair restore full function and continuity with low future leak risk?”
• If no → replacement is the defensible outcome.

High-risk patterns (common)

• Door-knocker urgency (“today only” pressure)
• Deductible “waiver” promises or vague discounts tied to insurance
• No written scope, no proof standards, no closeout process
• Ghost crews: no accountable local office or verifiable track record

Proof-based vetting (safe checklist)

• Ask for their documentation standard (photos + diagrams + closeout packet)
• Ask how they handle decking discoveries (proof + boundaries)
• Ask how they verify ventilation/flashing outcomes
• Ask how they handle supplements (clean packet + proof)
• Require clear responsibility separation (warranty vs insurance)