How to Recover Revenue From Old Roofing Claims That Were Never Supplemented

Every roofing company that has been in storm work for more than two or three years is sitting on money it already earned and never collected. It is buried in old job files: claims that were paid at the initial scope, jobs that closed without anyone going back to write the supplement, depreciation that was never released because the final invoice never went out, deductibles that quietly got eaten, and approved jobs where the carrier estimate was missing two-thirds of the code-required line items. The work was real. The documentation existed at some point. The revenue was recoverable. It just fell through the cracks while the crews were busy and the office was understaffed.

This is one of the highest-margin opportunities in a roofing business, and almost nobody works it on purpose. New leads cost money to generate, money to canvass, money to close. A supplement or a recoverable-depreciation release on a job you already built costs you a few hours of file review and a clean packet. The roof is already on. The crew is already paid. The customer relationship already exists. You are not selling anything new; you are finishing the billing on work you completed.

Below is the full operational playbook for mining your old claim files and recovering the dollars that were left on the table — what to pull, how to find the gaps, how to document them, what the legal lines are, and how to build this into a repeatable monthly motion instead of a one-time cleanup. Everything here stays strictly on the contractor's side of the line: you document your own scope, you write an accurate repair estimate, and you hand it to the homeowner. The homeowner files and the insurer decides. That distinction is what keeps you out of unlicensed public adjusting, and we will come back to it repeatedly because it is the thing that gets contractors in trouble.

What "never supplemented" revenue actually looks like

Before you can recover it, you have to know what you are looking for. The phrase "old claims never supplemented" hides at least six distinct buckets of money, and each one has a different recovery workflow. Lumping them together is the first mistake most offices make.

Bucket 1: Unfiled supplements on under-scoped initial estimates

The carrier's first estimate is almost always written conservatively, sometimes by an adjuster who spent twelve minutes on the roof and sometimes from aerial measurements alone. Common omissions: drip edge, ice-and-water shield where code requires it, starter strip priced as field shingle, ridge ventilation, step and counter flashing, pipe boots, two layers of tear-off priced as one, steep or high charges, and the dumpster/disposal line. If you built the roof to code and to the actual field conditions, the gap between what you installed and what they paid for is a documentable supplement. This is the single biggest bucket for most companies.

Bucket 2: Recoverable depreciation never released

On a replacement-cost-value (RCV) policy, the carrier pays actual cash value (ACV) up front and holds back the depreciation until the work is done and a final invoice is submitted. If your office never sent the completion documentation and final invoice, that held-back depreciation — frequently 20 to 40 percent of the total claim — is still sitting at the carrier. The homeowner was supposed to get it, and on most jobs it flows to you as the final payment. This is pure recovery: no scope argument, just paperwork you forgot to finish.

Bucket 3: Deductibles that were never collected

If a job closed and the deductible was never billed or collected from the homeowner, that is your revenue, not the insurer's. We will be careful here — you cannot waive, absorb, eat, or rebate the deductible, and you cannot advertise that you will. But a deductible that is genuinely owed and was never invoiced is collectible.

Bucket 4: Code-required items the original estimate ignored

Many jurisdictions have adopted code requirements (ice barrier, drip edge, ventilation ratios, decking re-nail or replacement, sometimes full second-layer removal) that the original carrier estimate did not include. If the applicable building code in effect at the time required an item and you installed it, that is a code-driven supplement supported by the code citation itself.

Bucket 5: Trade and accessory items dropped at closeout

Detached structures, gutters and downspouts damaged by the same event, gutter screens, satellite dish detach-reset, HVAC fin combing, soft metals, paint to match — small lines that add up. On a high volume of old files, the accessory recovery alone can be material.

Bucket 6: Denied or partially-denied claims that were never re-documented

A denial is not always the end. Frequently a roof was denied on a documentation problem — no date-of-loss photos, no clear directional damage, an adjuster who called it wear-and-tear. If you have evidence the original inspection missed, the homeowner can ask the carrier to re-open or reinspect. Your job is to supply better documentation, not to argue coverage. More on the line between those two below.

The honest legal frame — read this before you touch a single old file

This work lives next to a bright legal line, and crossing it can cost you your license to operate and expose you to unlicensed-public-adjusting penalties in most states. Get this right first, then go make money.

What a roofing contractor MAY do:

• Inspect the roof and document damage with photographs, measurements, and notes.
• Prepare an accurate, itemized repair estimate for your own scope of work, aligned to standard estimating practice (Xactimate line items and pricing where applicable).
• State facts about your scope to the carrier — what you installed, why code required it, what the field conditions were.
• Cite the applicable building code and manufacturer installation requirements as the basis for line items.
• Hand the homeowner a clean documentation packet and a final invoice so they can pursue the balance owed under their policy.

What a roofing contractor MAY NOT do (this is unlicensed public adjusting in most states):

• Negotiate, adjust, or "handle" the claim on the homeowner's behalf for a fee.
• Interpret the policy or tell the homeowner what is or is not covered.
• Promise a specific payout, approval, or supplement amount.
• Promise, advertise, or imply that the deductible will be waived, absorbed, rebated, or "taken care of," or advertise a "free roof."
• Represent the homeowner against the insurer.

The safe operating model is simple and you should be able to recite it: you document thoroughly, you write an accurate repair estimate for your scope, and you give it to the homeowner. The homeowner files or submits, and the insurer decides coverage. You are a contractor finishing the billing on your own work, not an advocate fighting the carrier on the homeowner's behalf. Every template, letter, and packet described below is built to stay on that side of the line, and the language matters: "here is the documentation and the itemized estimate for the work we performed" is contractor speech; "we got your claim approved and waived your deductible" is a problem. Many state departments of insurance publish guidance on this exact distinction; if you operate in a state with an Assignment of Benefits or anti-public-adjusting statute, read it before you build the program.

Step 1 — Pull the right files and triage them

You cannot work what you cannot see. The first phase is purely archaeological: assemble every old storm/claim job into one list and score it for recovery potential.

Define the pull window

Two constraints set your window. First, the statute of limitations on the insurance policy or contract in your state — many homeowner policies carry a one-to-two-year suit-limitation clause, though depreciation release and supplement timing are governed by the claim being open and the work being done, not the suit clause. Second, your own records: most companies have clean data going back three to five years. A practical first pass is the trailing 24 to 36 months, then a second sweep on anything older that looks high-value.

Do not assume an old claim is closed just because your file is closed. A claim is frequently still open at the carrier — especially where depreciation was never released — long after your office moved on.

What to pull per job

For each job, assemble:

The payment ledger is the fastest triage signal. If a job shows an ACV payment received but no final/depreciation payment, you have a Bucket 2 recovery candidate before you read anything else.

Score and rank

Not every file is worth working. Triage into three tiers:

1. Fast money (work first): depreciation never released with completion docs already on file; deductibles billed but uncollected. These are paperwork, not arguments.
2. Solid supplements (work second): under-scoped initial estimates where you have photos and a clear code or field basis for the missing items.
3. Long shots (work last or never): denials with thin documentation, jobs where you have no photos, files past the suit-limitation window. Be honest about these — chasing weak files burns your team's morale and your credibility with adjusters.

A simple recovery-potential score per file: estimated dollar gap × documentation strength (1–5) × likelihood the claim is still actionable (1–5). Sort descending. Work the top of the list.

Step 2 — Find the gap: line-by-line scope comparison

This is the analytical heart of recovery. For each in-scope file, you compare what the carrier paid for against what you actually installed and what code required, and you produce a defensible list of missing line items with quantities, pricing basis, and evidence.

Build the three-column comparison

Lay it out as a worksheet:

Every row needs three things to survive review: a quantity, a pricing basis (the standard estimating database line item, not a number you invented), and an evidence anchor (the specific photo, code section, or invoice that proves it).

Where pros consistently leave money

From thousands of reviewed estimates, the same omissions repeat:

• Drip edge — frequently omitted entirely on older estimates, almost always code-required now.
• Ice and water shield — omitted or under-measured; code-driven in cold and many mixed climates.
• Second-layer tear-off — paid as one layer when two or three were removed.
• Ridge ventilation and intake — ventilation balance is a code and manufacturer-warranty requirement; estimates routinely zero it out.
• Starter and ridge cap — priced as cut field shingle rather than the manufactured accessory the manufacturer requires for warranty.
• Steep and high charges — not applied where pitch or stories warrant.
• Detach-and-reset of solar, satellite, gutters, lightning protection.
• Decking — re-nail to code and sheet replacement where rotted/delaminated.
• Disposal/dumpster, permit, and minimum charges — small but legitimate and frequently dropped.

For each, your basis is either (a) the manufacturer's published installation instructions, (b) the building code section in effect at the time of installation, or (c) documented field conditions in your production photos. Those three sources are facts about your scope — exactly the kind of statement a contractor is allowed to make to a carrier. You are not arguing the policy; you are stating what the roof required and what you built.

Worked example

A representative under-scoped file. Carrier paid a total RCV of $9,800 on a 28-square architectural replacement, with a $1,000 deductible and 25 percent depreciation held back.

Initial estimate omissions found on comparison:

• Drip edge, 210 LF (code-required) — line-item pricing applied.
• Ice & water shield, 3 squares at eaves (code-required) — pricing applied.
• Second layer tear-off, 28 squares (photo evidence of two layers) — pricing applied.
• Ridge vent, 42 LF, with the old "ridge cap only" line corrected.
• Starter strip, 110 LF, reclassified from field shingle.
• Steep charge on the rear 9 squares (8/12 pitch documented).

Add those legitimate, documented items and the supplement on this single old file lands in the low-to-mid four figures of additional RCV — before you even address the unreleased depreciation. Across a backlog of a few hundred files, the math is obvious. Note the honesty here: these are real, installed, code-or-field-justified items, not padding. A supplement built on invented quantities or duplicated lines will get you flagged, denied, and remembered by the carrier.

Step 3 — Recover the depreciation you already earned

Bucket 2 is the easiest dollars in the building because there is no scope argument at all. On an RCV policy, the carrier owes the held-back depreciation once the work is complete and documented. If you never sent the closeout, go send it.

The depreciation-release checklist

For each job missing its final payment, assemble:

1. Certificate of completion — dated, signed, identifying the property and scope completed.
2. Final invoice — matching the approved scope plus any approved supplement, itemized.
3. Completion photographs — the finished roof from multiple angles, plus any accessory work.
4. Material documentation — supplier invoices confirming what was installed.
5. Lien waiver as applicable in your state and contract.

The homeowner submits this closeout package to the carrier; the carrier releases the recoverable depreciation. Your role is producing a clean, complete packet and handing it over. You are not negotiating — you are finishing the billing.

Why this gets missed

Depreciation release falls through the cracks because it happens weeks or months after the crew leaves, when the job feels "done" operationally even though it is not done financially. The fix is a closeout gate: no job is marked complete in your system until the completion certificate, final invoice, and completion photos are filed and the depreciation status is confirmed as either released or submitted. Build the gate and Bucket 2 stops accumulating.

Step 4 — Deductibles: collect what is owed, advertise nothing

The deductible is the homeowner's contractual responsibility under their policy. If a closed job has an uncollected deductible, that is collectible revenue. Build a clean aging report of deductibles billed-but-unpaid and work it like any accounts-receivable item: statement, reminder, payment plan if needed.

The hard line: you may not waive, absorb, rebate, discount-to-cover, or "handle" the deductible, and you may not advertise or imply any of those things. In many states that is insurance fraud and a deceptive trade practice, and the Federal Trade Commission and state attorneys general treat "free roof / we pay your deductible" advertising as exactly that. Recovering an owed deductible is collections; promising to erase one is a crime. Keep those two things in separate universes.

Step 5 — Build the documentation packet that survives review

Whether the recovery is a supplement, a depreciation release, or a re-documentation request, it travels as a packet. A packet that gets paid has a predictable shape.

Anatomy of a packet that gets paid

1. Cover summary — one page: property, claim number, date of loss, the specific items being documented, and the total. Factual, scope-only language.
2. Itemized estimate — the standard estimating-platform export, every line with quantity and pricing basis, no invented numbers.
3. Evidence index — each supplemental line cross-referenced to a numbered photo, code citation, or invoice. This is the single biggest driver of approval: an adjuster who can verify a line in five seconds approves it; one who has to hunt kicks it back.
4. Code citations — the specific code section and edition for every code-driven item.
5. Photo log — captioned, dated, geotagged where possible, organized by elevation.
6. Manufacturer documentation — install instructions for accessory items priced as manufactured components.

Packet-completeness scoring

Score every packet before it goes out, on a simple rubric: is every line item anchored to evidence? Is every code item cited to a section and edition? Are photos captioned and dated? Is the pricing basis a real database line, not a manual override? A packet that scores below your threshold gets fixed before submission, not after a denial. Denials cost weeks; a five-minute completeness check costs minutes.

The language guardrail

Scrub every document for prohibited language. The packet states what was installed, what code required, and what the field conditions were. It never says the claim "should be approved," never quotes coverage, never promises an amount, never mentions the deductible being handled. Contractor-side facts only. If a sentence reads like advocacy for the homeowner against the carrier, cut it.

Where RoofPredict does the heavy lifting

Everything above is doable by hand, and plenty of companies grind through it on spreadsheets. The reason most never finish is volume: a few hundred old files, each needing a line-by-line comparison, an evidence hunt, and a packet, is hundreds of hours of skilled labor. That is exactly the work RoofClaim — the claim revenue-cycle side of RoofPredict — is built to compress.

Opportunity detection on your old estimates

This is the core of the recovery program. In RoofClaim you upload the old claim documents for a job — the carrier estimate, your contract, production photos, supplier invoices, any denial letters. The system OCRs and auto-classifies each document (carrier estimate vs. contractor estimate vs. photos vs. denial vs. invoice), then maps the carrier estimate's line items against a roofing knowledge base and flags the gaps: scope-gap items that were installed but not paid, code-required items missing for that jurisdiction, and missed supplements — each flag carried with an evidence anchor and a pricing basis. Instead of manually building the three-column comparison from Step 2 for every file, you review a pre-built gap list with the supporting photo, code section, or invoice already attached to each line. A reviewer who used to clear three or four old files a day clears a stack.

Be clear about what this is and is not: it surfaces documentable gaps in scope and code coverage with evidence; it does not, and cannot, promise a carrier will pay them. The decision is always the insurer's. It is a documentation accelerator, not a magic-approval button.

Recoverable-depreciation autopilot

For Bucket 2, RoofClaim runs a recoverable-depreciation workflow: it tracks which completed jobs still have depreciation held back, drives the completion-evidence and final-invoice checklist, and flags the files where the closeout packet is ready to go but was never sent. The deductible-tracking and supplement-aging views give you the AR-style aging reports from Steps 3 and 4 without building them by hand, with a follow-up cadence so a submitted supplement does not sit untouched at the carrier for sixty days.

Locked, compliant templates

Every output — supplement packet, depreciation-release letter, deductible invoice, missing-docs letter, audit report — generates from LOCKED, UPPA-gated, contractor-documentation-only templates. The language guardrail from Step 5 is built into the template, so the cover summary states scope facts and never drifts into coverage interpretation, payout promises, or deductible language. Packet-completeness scoring is built in, so a packet flags its own missing evidence before it leaves the building. The claim-inbox triage pulls carrier emails into the right job so a "we need completion photos" reply does not get lost in someone's inbox for a month.

The honest limit, again: RoofClaim documents your scope and surfaces the gaps with evidence and pricing. It does not negotiate, does not handle the claim, and does not interpret the policy. It keeps you on the contractor side of the line by design, which is the whole point — the speed is only valuable if it is also clean.

Reading the carrier estimate like an estimator, not a victim

Recovery hinges on one skill: being able to read a carrier estimate and instantly see what is missing, mispriced, or quantity-shorted. Most contractors look at the bottom-line total and either accept it or get angry at it. Neither pays the bill. You need to read it the way the person who wrote it did — line by line, against the actual roof.

The structure of a carrier estimate

Most carrier estimates come out of the same estimating platform you use, which is a gift, because you can compare apples to apples. The document has a header (claim number, date of loss, insured, deductible, policy type — RCV or ACV), then groups of line items organized by area (the roof, then often gutters, then detached structures), and a summary that walks from RCV down to ACV by subtracting depreciation, then subtracts the deductible to reach the net claim paid. Three numbers tell you the recovery shape before you read a single roof line:

• RCV total vs. your contract total. If your contract is meaningfully above the carrier RCV and you built to code, the delta is your supplement target.
• Depreciation amount and whether it is recoverable. If it says "recoverable depreciation" and there is no final/depreciation payment in your ledger, that is Bucket 2 money waiting on a closeout packet.
• Deductible and whether it was collected. Uncollected and owed equals Bucket 3.

Reading the roof lines against reality

Now go line by line on the roof section. For each, ask three questions: Is the quantity right? Is the right line item used? Is the item present at all? Quantity errors are the most common and the most defensible — an estimate that pays 24 squares of removal when you tore off and your measurement report shows 28 squares is a four-square shortfall with a clean basis. Wrong-line errors are the next tier: starter strip paid as field shingle, ridge cap paid as field shingle, a single tear-off layer when the cross-section photo shows two. Missing items are the third tier: drip edge, ice-and-water, ventilation, steep and high charges, soft metals.

The discipline that separates a paid supplement from a denied one is that you only flag what you can prove with a number and an anchor. "The roof was bigger than they paid" is an argument. "Removal: estimate 24 SQ, measurement report and tear-off photos show 28 SQ, +4 SQ" is a fact. Carriers pay facts.

Pricing basis: use the database, never the override

When you add a line, the price has to come from the same regional pricing database the carrier uses, for the same period as the loss. A manual price override — a number you typed in — is the fastest way to get a line denied and your whole packet scrutinized. If the database price for that item in that region and period is what it is, that is your number. This is also a compliance point: you are stating a standard, verifiable price, not negotiating a figure. The moment you start hand-setting prices to hit a target total, you have stopped documenting and started arguing, and arguing about price is the carrier's job to push back on and frequently drifts toward the adjusting line.

Causation and the date-of-loss problem on old files

Old claims carry a specific risk that fresh ones do not: the further you are from the date of loss, the harder it is to tie the damage to the covered event. On a supplement to an already-approved claim this matters less — coverage is already established, you are documenting scope on an accepted loss. But on a re-documentation or a previously-denied file, causation is the whole ballgame, and it is also the place where contractors most often wander across the line into interpreting coverage. Stay on the factual side.

What you can document factually about causation

You can state observable facts: directional damage consistent with wind from a documented direction, hail bruising with the mat fracture and granule loss patterns photographed and measured, the spatial damage pattern across slopes, collateral indicators (dented soft metals, damaged vents, spatter marks on oxidized metal), and the condition of the roof relative to its age. You can reference public weather data for the address and date — the NOAA Storm Events Database and Storm Prediction Center reports establish that a hail or wind event occurred in that area on or near the date of loss. Those are facts about the roof and the weather, and a contractor is allowed to document and present them.

What you cannot do

You cannot tell the homeowner the damage "is covered," cannot conclude the carrier "wrongly denied" it, and cannot promise a reinspection will reverse the decision. The line is precise: you document the physical evidence and the weather facts, you hand that documentation to the homeowner, and the homeowner asks the carrier to reinspect. The carrier's reinspecting adjuster makes the coverage call. You supplied better facts; you did not adjudicate the claim.

Why date-of-loss data ages badly

Two seasons of additional weathering, foot traffic, and a partial repair can muddy a hail pattern that was crisp at the time of loss. This is the strongest argument for the monthly review in your prevention motion — the documentation you capture within weeks of the event is dramatically stronger than anything you reconstruct two years later. For the backlog sweep, it is also why re-documentation files sit in the long-shot tier: if your production photos from the original job captured the damage clearly, you may have a case; if they did not, no amount of current-day inspection will recover a two-year-old denial cleanly.

A field guide to the high-value missing items

It is worth going deeper on the specific line items that drive most recovery dollars, because knowing the basis cold is what lets your coordinator build defensible packets fast.

Tear-off layers

The most valuable single correction on many files. An estimate written from aerial data or a quick inspection routinely assumes one layer. If you removed two or three, you removed two or three, and your cross-section photo at the eave or a photo of the layered debris in the dumpster proves it. Basis: documented field condition. Quantity: the full roof square count per additional layer. This one item alone frequently exceeds a thousand dollars on an average home.

Drip edge

Metal drip edge at eaves and rakes is required by the IRC in current editions and by most adopted state and local codes. Older estimates omit it constantly. Basis: code section and edition in effect at installation. Quantity: total eave and rake linear footage. Pair the code citation with a finished-edge photo and it is close to automatic.

Ice-and-water shield

Code-required at eaves in regions subject to ice damming, and frequently required in valleys and at penetrations regardless of climate. Estimates omit it or under-measure the coverage. Basis: code section for the jurisdiction, plus manufacturer requirements. Quantity: squares at eaves per the required upslope coverage, plus valleys and penetrations.

Ventilation

Balanced intake and exhaust ventilation is both a code requirement (the IRC attic ventilation ratio) and a shingle-manufacturer warranty condition. Estimates routinely pay "ridge cap" while omitting actual ridge vent, or pay no exhaust at all. Basis: code ratio and manufacturer install instructions. Document the installed ridge vent length and any added intake.

Starter and ridge cap

Manufacturers require manufactured starter strip and manufactured hip-and-ridge cap for the warranty to hold; cutting field shingles to fabricate them voids coverage and is not equivalent labor or material. Estimates pay these as field shingle constantly. Basis: manufacturer installation instructions. Reclassify to the manufactured line item at the correct linear footage.

Steep and high charges

Pitch above a threshold (commonly 7/12 and steeper, with another tier at very steep) and multi-story access carry legitimate labor modifiers. If you have a measurement report showing the pitch and stories, the charge is mechanical. Basis: documented pitch and height. Estimates omit these on jobs where the adjuster could not or did not get on the roof.

Decking re-nail and replacement

Many codes require re-nailing the deck to current fastening schedules on a full replacement, and any rotted, delaminated, or storm-damaged sheathing must be replaced. Basis: code fastening schedule plus documented field condition with photos of replaced sheets. Quantity: per sheet replaced and the re-nail line for the full roof where code applies.

Soft metals and accessories

Dented gutters, downspouts, valley metal, vents, and flashing damaged by the same hail event are part of the loss. Detach-and-reset of solar arrays, satellite dishes, and lightning protection is real labor. Basis: photos of the damaged or detached items and the install. These small lines add up fast across a backlog.

What the recovered dollars actually add up to

It helps to do the arithmetic at the portfolio level, honestly and without inventing industry statistics — just your own file math. Take a company that completed roughly 300 insurance roofs over the past 30 months. Suppose, conservatively from a triage pass:

• 60 of those files show ACV paid but no depreciation release on record. The held-back depreciation averages, say, a few thousand dollars per file. That is Bucket 2, and it is the cleanest money in the building because there is no scope argument — only a closeout packet that was never sent.
• 90 files have a documentable scope or quantity gap (a missed layer, omitted drip edge, mispriced starter, an absent steep charge) averaging a low four-figure supplement each, on real installed-and-coded items.
• A smaller set has uncollected-but-owed deductibles in AR.

You do not need to publish a number to your team for this to be motivating; you need to run the triage and let the actual ledger show the total. The point is that the recoverable pool on a mature storm book is almost always large enough to fund a dedicated coordinator several times over, which is exactly why the program pays for itself in the first wave and turns into margin after that. And because the roofs are already built and paid for, nearly all of it is margin — there is no material cost, no crew cost, no acquisition cost attached to a dollar of recovered depreciation or a defensible supplement on a finished job.

Contrast that with the cost of the alternative use of the same effort: generating, canvassing, and closing brand-new claims to produce the same revenue. New work carries lead cost, sales labor, production cost, and material cost against every dollar. Recovery carries a few hours of file review. On a pure return-on-effort basis, working your own backlog beats almost anything else your office could spend that time on.

Turning a one-time cleanup into a monthly revenue motion

A backlog sweep recovers a pile of money once. The bigger win is never building a backlog again. Two things make recovery permanent.

The closeout gate

No job closes financially until: completion certificate filed, final invoice issued, completion photos uploaded, depreciation status confirmed (released or submitted), and deductible status confirmed (collected or in AR). Wire this into your production system as a hard gate. Bucket 2 and Bucket 3 dry up because nothing slips past closeout unbilled.

The monthly supplement review

Once a month, every job from the prior period gets a scope comparison before it is archived — the same line-by-line check from Step 2, run while the photos are fresh and the crew remembers the conditions. Supplements written within weeks of completion get approved faster and cleaner than ones dug up two years later, and the documentation is far stronger. The backlog sweep is remediation; the monthly review is prevention.

Staffing it

You do not need a dozen people. One detail-oriented coordinator who owns the closeout gate, runs the monthly comparison, and assembles packets can carry a substantial book, especially when the gap detection and packet assembly are tooled rather than manual. Many companies promote from production — someone who has been on roofs, knows what a two-layer tear-off looks like in a photo, and can spot a missing drip edge at a glance. That field knowledge is what separates a defensible packet from a padded one.

Working with adjusters without crossing the line

Recovery means re-engaging with carriers and their adjusters on files they thought were finished. How you do that determines whether you build a reputation as a clean, documentation-driven contractor whose packets get approved, or a problem the carrier flags. Both reputations are sticky.

Be the contractor whose packets are easy to approve

An adjuster reviewing a supplement is making a risk decision: approve it and move on, or kick it back and create work for themselves. You win by making approval the lower-effort path. That means: every line anchored to a photo, code section, or invoice the adjuster can verify in seconds; pricing straight from the standard database with no overrides; quantities tied to a measurement report; and a cover summary that states scope facts in plain, non-adversarial language. When an adjuster learns that your packets are always clean and never padded, your future supplements get a lighter review. That trust is a business asset worth protecting on every single file.

Keep the homeowner as the principal

On every carrier interaction, the structure stays the same: you provide documentation and an estimate about your scope; the homeowner is the party to the claim and the one who submits and follows up; the carrier decides. When you communicate with an adjuster, you communicate facts about what you built and what code required — not arguments about what the policy should cover. If a conversation starts heading toward "you owe my customer X" or "this should be covered," that is the homeowner's position to take, not yours, and pressing it for a fee is the public-adjusting line. Many state insurance departments publish exactly where that line sits; the Texas Department of Insurance and Florida's Department of Financial Services both have public guidance distinguishing a contractor's permitted activities from licensed public adjusting. Read your own state's version and operate inside it.

Follow-up cadence

A submitted supplement or depreciation packet is not done — it is in flight. Carriers are busy and packets sit. Build a cadence: a status check at a sensible interval, a polite resubmission if a packet was lost, and a record of every touch. The homeowner is the one who follows up on the claim status; your role is to keep the documentation current and complete and to re-supply anything the carrier says is missing. A clean packet with disciplined follow-up gets resolved; a clean packet that nobody tracks ages out and becomes a write-off all over again.

How recovery fits the rest of your acquisition engine

Recovery is not a standalone project — it sits inside the same revenue cycle as your new-customer work, and the same platform that ranks roofs and runs your outreach is where the claim side lives. The connection matters operationally. Every recovered job is also a warm reference, a fresh set of completion photos for your portfolio, and a homeowner who just watched you finish the billing correctly and professionally. That is a referral and a review waiting to happen, in a neighborhood where you already have storm exposure data and a ranked list of nearby due roofs.

In practical terms, the claim file in RoofClaim is linked to the home, which is linked to the targeting and outreach side of RoofPredict — the ranked due-roof audience, the tracked mail and microsites, the field routes, and the lead pipeline with two-way sync to the CRMs your office already runs. So a recovered job is not a dead end; it is a node in a service area you can keep working. The recovery program produces cash now from finished work, and it strengthens the data and the relationships that drive the next wave of new work in the same blocks. Run together, the new-acquisition engine and the recovery engine compound: one fills the pipeline, the other finishes the billing, and both feed the same record of every home and every claim.

The mistakes that get recovery programs killed

A few patterns reliably turn a recovery program from a profit center into a liability:

• Padding. Inventing quantities, duplicating lines, or claiming items you did not install. It gets caught, it gets denied, and it gets your company flagged with that carrier on every future claim. Document only what you actually built and what code actually required.
• Drifting across the legal line. The moment your packet or your salesperson starts negotiating coverage, promising approval, or talking about handling the deductible, you have stopped being a contractor and started practicing unlicensed public adjusting. Stay on scope facts.
• Advertising deductible help. "Free roof," "we pay your deductible," "no out-of-pocket" — these are not marketing edges, they are regulatory exposure. Collect what is owed; advertise nothing about waiving it.
• Working the long shots first. Thin-documentation denials are emotionally tempting and operationally exhausting. Work the fast money first; the wins fund the patience for the hard files.
• No evidence anchors. A supplement line with no photo, code section, or invoice behind it is a guess, and adjusters treat it like one. Anchor everything.
• Letting packets sit. A submitted supplement with no follow-up cadence ages out. Track it like AR and work the cadence.

A 30-day plan to recover your first wave

If you want this running inside a month, here is the sequence:

1. Days 1–3: Pull the trailing 24–36 months of storm/claim jobs into one list. Mark every file with ACV-paid-but-no-final-payment — that is your Bucket 2 fast-money list.
2. Days 4–7: Build the depreciation-release packets for the fast-money list (completion cert, final invoice, completion photos). Hand them to homeowners to submit. This funds the rest of the program.
3. Days 8–14: Triage the remaining files by recovery-potential score. Pull carrier estimates and production photos for the top tier.
4. Days 15–24: Run the line-by-line scope comparison on the top tier, build evidence-anchored supplement packets, run the completeness check, submit.
5. Days 25–30: Stand up the permanent motion — wire the closeout gate into production, schedule the monthly supplement review, assign the coordinator. Stop the backlog from ever rebuilding.

Run that sequence and you will recover real money from work you already did, with documentation you can defend, on the right side of the legal line.

Closing: finish the billing on work you already earned

The roofs are already on. The crews are already paid. The customers already trust you. The only thing standing between your company and a meaningful pile of recovered revenue is the unglamorous work of pulling old files, comparing scope line by line, anchoring every gap to evidence, finishing the closeout packets you never sent, and handing clean documentation to the homeowner so they can collect what their policy already owes.

Do it by hand and it is hundreds of hours. Do it with RoofClaim's opportunity detection — upload the old documents, review a pre-built gap list with evidence and pricing already attached, generate the supplement and depreciation-release packets from locked compliant templates, and track the recoverable depreciation, deductibles, and supplement aging in one place — and a backlog that felt impossible becomes a coordinator's monthly routine. Either way, the rule never changes: document your scope, write an accurate estimate, hand it to the homeowner, and let the insurer decide. Stay on that side of the line, work the fast money first, and go collect the revenue you already earned.

FAQ

What does it mean to recover revenue from old roofing claims that were never supplemented?

It means going back through completed storm and insurance jobs to find money that was earned but never collected: under-scoped carrier estimates where code-required and installed items were left out, recoverable depreciation that was never released because the closeout packet was never sent, deductibles billed but never collected, and accessory items dropped at closeout. The roof is already built, so recovering this revenue is paperwork and documentation, not new sales.

Is a contractor allowed to file or handle the supplement for the homeowner?

No. A contractor may document damage, prepare an accurate itemized repair estimate for their own scope, and state facts about that scope to the carrier. A contractor may not negotiate or handle the claim, interpret policy or coverage, or promise an approval or amount — that is unlicensed public adjusting in most states. The safe model is: you document and estimate your scope, you hand the packet to the homeowner, the homeowner submits, and the insurer decides.

How far back can I go to recover old claims?

Practically, most companies have clean records for the trailing three to five years; start with the trailing 24 to 36 months. The actionable window depends on whether the claim is still open at the carrier and on your state's policy suit-limitation clause (often one to two years). Depreciation that was never released is frequently still recoverable long after your internal file closed, because the claim itself never finished at the carrier.

What is recoverable depreciation and why is it the easiest money to recover?

On a replacement-cost-value policy, the carrier pays actual cash value up front and holds back depreciation (often 20 to 40 percent) until the work is complete and documented. If your office never sent the completion certificate, final invoice, and completion photos, that depreciation is still sitting at the carrier. There is no scope argument — it is owed once the work is documented — so it is the fastest, cleanest recovery: finish the closeout packet and the homeowner submits it for release.

Can I waive or pay the homeowner's deductible as part of recovering a claim?

No. Waiving, absorbing, rebating, or advertising that you will 'pay' or 'handle' the deductible is insurance fraud and a deceptive trade practice in most states. You can, however, collect a legitimately owed deductible that was never invoiced — that is normal accounts-receivable collection. Recovering an owed deductible and promising to erase one are completely different things; keep them separate.

What items are most commonly left off the original carrier estimate?

The repeat offenders are drip edge, ice-and-water shield, second-layer tear-off priced as one layer, ridge ventilation and intake, manufactured starter and ridge cap priced as cut field shingle, steep and high charges, detach-and-reset of solar and satellite, decking re-nail or replacement, and disposal, permit, and minimum charges. The basis for adding them is always the manufacturer's install instructions, the applicable building code, or documented field conditions in your photos.

How do I document a supplement so the carrier actually pays it?

Build an evidence-anchored packet: a one-page factual cover summary, the itemized estimate with a real pricing basis for every line, an evidence index cross-referencing each supplemental line to a numbered photo, code citation, or invoice, the specific code section and edition for code-driven items, a captioned and dated photo log, and manufacturer install documents for accessory items. Score it for completeness before sending. An adjuster who can verify a line in seconds approves it; one who has to hunt kicks it back.

Can a denied claim be recovered?

Sometimes. Many denials are documentation failures — missing date-of-loss photos, unclear directional damage, an inspection that called storm damage wear-and-tear. If you have better evidence the original inspection missed, the homeowner can ask the carrier to re-open or reinspect, and you supply the improved documentation. You are providing facts and photos, not arguing coverage. Work these last; thin-documentation denials are the lowest-probability files.

How does RoofPredict's RoofClaim help with old-claim recovery?

You upload the old claim documents (carrier estimate, your contract, production photos, invoices, denial letters); RoofClaim OCRs and classifies them, then maps the carrier estimate against a roofing knowledge base and flags scope-gap, code-required, and missed-supplement items with an evidence anchor and pricing on each. A recoverable-depreciation workflow tracks which completed jobs still have depreciation held back and drives the closeout checklist, with deductible tracking and supplement aging. Packets generate from locked, compliance-gated, contractor-documentation-only templates. It accelerates documentation; it does not negotiate, interpret coverage, or promise the carrier will pay.

How do I stop building a backlog of unsupplemented claims in the first place?

Two controls. First, a closeout gate: no job closes financially until the completion certificate, final invoice, and completion photos are filed and the depreciation and deductible statuses are confirmed. Second, a monthly supplement review: run the line-by-line scope comparison on every completed job before it is archived, while photos are fresh and the crew remembers the conditions. Supplements written within weeks of completion approve faster and document stronger than ones dug up years later.