How Much Revenue Roofing Contractors Leave on the Table Per Claim (and Where It Leaks)

Ask a roofing owner how a storm job went and you'll usually get a clean answer: "We got it approved, we built it, we got paid." Ask them what the carrier estimate left out, and the room goes quiet. That quiet is the money. The revenue a contractor leaves on the table per claim almost never shows up as a lost sale. It hides inside the job you already won — in scope you forgot to photograph, in line items the carrier's estimate never included, in code-required work nobody asked for, and in the supplement you decided wasn't worth the phone call.

The number is bigger than most owners think, and it's surprisingly consistent. Across residential storm work, the gap between what a careful contractor documents and what a rushed one settles for tends to land somewhere between $900 and $3,500 per replacement, with steep-slope, multi-layer, and code-upgrade jobs running higher. On a 200-claim year, leaving even $1,500 on each one is $300,000 — gross, off work you already sold and already roofed.

What follows is a line-item teardown of where that money leaks, how to plug each leak with documentation and accurate estimating, the legal lines you cannot cross while doing it, and how to stop sinking documentation labor into roofs that were never going to qualify in the first place. None of it requires you to negotiate a claim, interpret a policy, or promise anybody a payout. All of it is on the side of the work you're licensed and qualified to do: inspect, document, and write an accurate, code-aligned estimate to repair your own scope.

The honest definition of "left on the table"

Before counting dollars, separate three things people lump together, because only one of them is yours to chase.

1. Earned scope you failed to document. Real, physical, storm-related or code-required work that exists on the roof and the surrounding components, that you can photograph and measure, that a proper estimate would include — and that got dropped because nobody wrote it up. This is recoverable, defensible revenue. This is the leak worth fixing.
2. Coverage decisions that aren't yours. Whether a given line gets paid is the carrier's and the homeowner's business, governed by the policy. You document the condition and write the repair estimate. You do not decide what's covered, and you do not promise it will be.
3. Stuff that isn't there. Padding, phantom damage, inflated quantities. That's not leakage — it's fraud, and it's the fastest way to lose your license and your business. Everything here assumes you only document and estimate what physically exists.

The distinction matters because it also defines your legal lane. A roofing contractor may inspect a roof, document damage with photos and measurements, and prepare an accurate estimate to repair the work they would perform, and may state facts about that scope to the carrier. A roofing contractor may not, for a fee, negotiate or "handle" the claim, interpret the homeowner's policy or coverage, promise a specific approval or payout, promise a deductible will be waived or absorbed, advertise a "free roof," or represent the homeowner against their insurer. That last bundle is unlicensed public adjusting in most states, and it's prosecuted. We'll come back to the do-not-say list, because the same conversation where contractors leave money on the table is the conversation where they accidentally cross that line.

The safe and effective frame is simple: document thoroughly, write an accurate estimate, hand it to the homeowner. The homeowner files. The insurer decides coverage. Your job is to make sure that when the insurer decides, they're looking at a complete, photo-backed, code-aware scope instead of a thin one.

The per-claim leak, line by line

Here's where the dollars actually walk off the job. The ranges below are typical residential figures and will vary by region, pitch, material, and local labor and material costs — treat them as a structure for your own audit, not as quotes. Pull your last ten settled claims and check each line against your file.

1. Accessories and small components the field estimate skips

The single most common leak isn't dramatic. It's a dozen small line items that a thorough estimate includes and a rushed one doesn't: pipe boots, ridge and off-ridge vents, drip edge, valley metal, step and counter flashing, chimney flashing, exhaust caps, the painting of new exposed metal, and the detach-and-reset of components that have to come off to reroof and go back on. Individually they're $15 to $250 each. Stacked across a full replacement, a complete accessory schedule is frequently $600 to $1,400 more than a bare "tear-off, felt, shingles" estimate.

The fix is mechanical: a field checklist that forces every penetration and every linear-foot transition to be counted and photographed. If it's on the roof, it's on the estimate, with a photo. (Full checklist later.)

2. Steep and high charges, and access difficulty

Pitch and height drive real labor cost, and estimating platforms account for them — but only if the slope and stories are entered correctly. A 9/12 read as a 6/12 silently deletes the steep-slope labor modifier. Two-story and three-story access charges get dropped when the measurement comes off a flat aerial without story count. On a moderately steep two-story, correctly captured steep and high charges are commonly $400 to $1,200.

The fix: verify pitch on site (a pitch gauge or a phone level on a rafter, not an eyeball from the driveway), record story count, and confirm the aerial measurement report's slope matches what you measured. Photograph the pitch gauge reading.

3. Layers, decking, and what's under the shingles

Multiple existing layers mean more tear-off labor and disposal. Damaged or deteriorated decking that has to be replaced to install properly is real, code-relevant work — but it has to be discovered and documented during tear-off, with photos, because nobody can see it from the estimate desk. Decking replacement and the labor to install it is one of the most-missed legitimate items precisely because it's invisible until the roof is open.

Document it the day you find it: wide shot showing location, tight shot showing the rot or delamination, a tape for dimension, and a note of the count. Missed decking and second-layer tear-off routinely runs $300 to $1,500 depending on the find.

4. Code-required upgrades (the big, legitimate, under-claimed bucket)

This is where the largest defensible dollars hide, and where contractors are most timid because they don't know their own code. When you re-roof, the current building code governs the new installation, not the code in force when the house was built. Depending on your jurisdiction's adopted edition of the International Residical Code (IRC) and any local amendments, that can require:

• Ice-and-water shield at eaves, valleys, and penetrations in cold-climate zones (IRC R905.1.2 underlayment provisions).
• Drip edge at eaves and rakes (IRC R905.2.8.5) — a code requirement in current editions, not an upgrade.
• Synthetic or specified underlayment meeting current standards.
• Ventilation brought to the required net free area (IRC R806).
• Decking re-nailing or replacement to meet current fastening requirements, common in high-wind-adopted jurisdictions.
• Sheathing nailing patterns and, in some coastal jurisdictions, secondary water barrier requirements.

These are not optional add-ons you're inventing. They're what the code says you must build, and an installation that ignores them isn't compliant. The way to capture them is to know your adopted code edition cold, cite the section, document the existing non-compliant condition with a photo, and include the upgrade as a line item because the law requires it to be built that way. Code items, where they apply, commonly add $500 to $2,500 to a residential replacement.

One discipline that pays for itself: keep a one-page reference of your jurisdiction's adopted IRC edition and the local amendments, with section numbers. When a code line appears on your estimate, the section citation is right there. Check your building department's website or your state's code adoption page; the ICC publishes which states have adopted which editions.

5. Detach-and-reset and adjacent trades

Satellite dishes, solar attachments, gutter guards, lightning protection, antennas, and snow guards usually have to be detached to reroof and reset after. Gutters and downspouts that interfere with eave work, fascia and soffit damaged by the same storm, and the cleanup and tarping during the project are all legitimate, documentable line items that bare estimates skip. Together these are commonly $200 to $900.

6. Waste factor and starter/ridge specifics

Waste percentage on cut-up, hip, and complex roofs is real material you buy and dispose of. Hip roofs and roofs with lots of valleys carry higher waste than a simple gable. Starter course and ridge cap as separate line items (not absorbed into field shingle counts) reflect product you actually install. Underclaimed waste and separate starter/ridge run $150 to $700 on a complex roof.

7. The supplement you never filed

Everything above, when discovered after the initial estimate is written — most commonly the decking and code conditions found at tear-off — is the basis for a supplement: a documented request to revise the estimate to reflect actual conditions. The supplement isn't a negotiation tactic; it's an accurate revision of the estimate based on physical findings, supported by photos and measurements. Contractors leave enormous money on the table simply by not writing supplements, because it feels like extra paperwork on a job they're ready to close out. A properly documented supplement on a job that surfaced hidden conditions frequently recovers $800 to $2,500.

Putting the per-claim number together

These overlap — you don't add every row on every job — but the pattern is clear. On a typical replacement, $900 to $3,500 of legitimate, documentable scope routinely goes uncaptured. The contractors who capture it aren't more aggressive. They're more organized, and they document before they tear off and again after.

Why the leak happens: the four failure modes

If the money is this real, why does anyone leave it? Four reasons, in order of how much damage they do.

Failure mode 1: The estimate is written from the driveway. A field rep walks the perimeter, eyeballs the pitch, counts squares from an aerial, and writes "replace roof." Nobody gets on the roof, nobody opens it, nobody counts penetrations. Everything in the line-by-line section above is invisible from the driveway. This is the biggest single cause.

Failure mode 2: Photos are taken to prove the sale, not the scope. The rep shoots three pictures of obvious hail bruising to convince the homeowner, then stops. When the file needs to support a complete scope, there's no photo of the decking, no pitch gauge shot, no flashing condition, no penetration inventory. You can't put a line item on an estimate you can't back up.

Failure mode 3: Nobody on the team knows the adopted building code. Code-required upgrades are the largest defensible bucket and the most-skipped, purely from ignorance. A crew that doesn't know their jurisdiction requires drip edge and ice-and-water shield doesn't write them, even though the law requires them to install them.

Failure mode 4: Documentation labor gets spread across roofs that never qualified. This is the quiet one. A rep spends two hours documenting a roof that turns out to be five years old with no real storm exposure — time that should have gone to the roof down the street that's twenty years old and took two hail events. Bad targeting costs you more than knocks. It dilutes your documentation quality on the roofs that actually deserved a thorough file. We'll deal with this one head-on.

The documentation system that captures the scope

Everything legitimate you can recover comes down to one thing: a photo and a measurement for every line item, captured in a repeatable order so nothing gets skipped. Not more aggression with the carrier. A better file.

The two-pass rule

Document the roof twice: once at inspection, once at tear-off. The inspection pass supports the initial estimate. The tear-off pass captures everything that was invisible until the roof was open — decking, layers, deck nailing, hidden flashing rot. The tear-off pass is where most supplements are born, and it's the pass most crews skip because they're in production mode and want to dry the roof in.

Build it into the workflow: no shingles get loaded until the tear-off photos exist. Make it the foreman's job, make it a gate, and the supplement basis stops walking off the roof.

The inspection-pass photo checklist

Shoot these every time, in this order, so it becomes muscle memory:

1. Address and context — house number, full elevation of each side (proves the property and the slopes).
2. Overview of each roof plane — wide shots establishing layout.
3. Pitch gauge reading — the gauge on the slope, legible.
4. Story count / access — a shot that makes height obvious.
5. Every penetration — each pipe boot, vent, exhaust cap, individually.
6. Every transition — valleys, step flashing, counter flashing, headwall, sidewall, chimney.
7. Drip edge / eave / rake condition.
8. Ridge and ridge vent.
9. Damage detail — tight shots with a reference (chalk circle, marker, coin or tape for scale) on representative impacts or wear.
10. Collateral — soffit, fascia, gutters, and any detach-reset items (dish, solar, guards).
11. A test square (where appropriate) — a measured area with marked hits, to show density.

The tear-off-pass checklist

1. Layers exposed — count visible, photo showing the count.
2. Decking condition — wide location shot, tight rot/delamination shot, tape for dimension, count.
3. Existing deck nailing pattern (relevant where code requires re-nail).
4. Hidden flashing condition once shingles are off.
5. Anything that contradicts the original estimate — this is your supplement file.

Measurements that hold up

Use a real aerial measurement report (or a careful hand measurement) for squares, ridge, hip, valley, eave, and rake linear footage, and confirm the pitch and story count match what you photographed. The estimate's quantities should trace to the measurement report, and the measurement report should match the photos. When all three agree — photos, measurements, estimate — the file defends itself.

Write the estimate in the carrier's language

Most carriers price from a standard estimating platform (Xactimate is the dominant one) using regional unit pricing. You don't need to argue pricing; you need your scope to be complete and your quantities correct, expressed in line items that map cleanly to the platform's items. An estimate that's complete and correctly quantified, with a photo behind each line, is the strongest thing you can hand a homeowner to submit. If your estimate and the carrier's estimate differ, the difference should be explainable line by line, with a photo — that's a documentation conversation, not a negotiation.

The legal line: capturing scope without becoming a public adjuster

Here's where good contractors get themselves in trouble. The same diligence that captures revenue can slide into unlicensed public adjusting if you start talking about the wrong things. Keep the diligence; drop the language. State unfair-claims and public-adjuster statutes vary, but the safe operating rules are consistent.

You MAY:

• Inspect the roof and document conditions with photos and measurements.
• Prepare an accurate, code-aligned estimate to repair the scope you would perform.
• State facts about your scope and the physical conditions to the carrier or adjuster.
• Meet the adjuster on the roof and point out conditions you documented.
• Hand the homeowner a complete file so they can file and submit.

You MAY NOT (the do-not-say list):

• Negotiate, adjust, "handle," or "fight" the claim for the homeowner for a fee.
• Interpret the policy or tell the homeowner what is or isn't covered.
• Promise a specific approval, payout, or that "the claim will go through."
• Tell anyone their deductible will be waived, absorbed, eaten, discounted, or "taken care of" — promising to absorb a deductible is illegal in many states and is insurance fraud.
• Advertise or imply a "free roof" or "no out-of-pocket."
• Represent the homeowner against their insurer.
• Sign or submit claim paperwork on the homeowner's behalf as their representative.

The difference between the two columns is the difference between a licensed contractor doing thorough work and an unlicensed public adjuster — and crossing it can cost you your license, trigger fines, and void the very work you did. Train every rep on the do-not-say list the same week you train them on the photo checklist. The phrasing that keeps you safe and still wins is plain: "I document everything thoroughly and write you an accurate estimate for the repair. You file it with your insurer, and they decide what's covered. If they approve the scope, we build it right and to code." That sentence captures the intent behind every "will my claim get approved" question without making a single promise you're not allowed to make.

A quick script for the deductible question

Homeowners will ask you to make the deductible disappear. The honest, legal answer: "The deductible is between you and your insurer — it's part of your policy, and I can't waive it or absorb it; that's actually illegal. What I can do is make sure the estimate is complete and accurate so nothing legitimate gets left out." You just turned a trap question into a trust-builder.

The adjuster meeting: how to be useful without crossing the line

When the carrier's adjuster comes out, the contractor who shows up with a complete photo-and-measurement file is doing exactly what they're allowed to do — and is far more useful than one who shows up empty-handed. The safe posture on the roof is to point out physical conditions you documented and the code requirements that govern the new installation, and to let the photos and the measurement report speak. You're presenting facts about scope, not arguing coverage.

Practical moves that stay on the right side of the line:

• Be on the roof with the adjuster, not in the driveway. Walk the same planes. Point at the conditions in your photos and show them in person.
• Hand over a clean file, not a stack of loose phone pictures. Organized by elevation and plane, each photo labeled, the measurement report attached, the estimate itemized.
• Cite code by section, not by opinion. "Current adopted code requires drip edge at eaves and rakes, section R905.2.8.5" is a fact. "You guys always leave this off" is an argument you don't need.
• Talk scope, never coverage. If the adjuster's estimate is missing a line, the conversation is "here's the condition and here's the photo," not "you owe my customer this." The carrier decides coverage; you supply the documentation.
• Don't speak for the homeowner against the carrier. The moment you're negotiating the settlement on the homeowner's behalf for a fee, you've stepped into public adjusting. Stay the contractor with the best-documented file in the room.

The well-documented file does most of the work. When every line has a photo and a measurement, and the code lines carry section numbers, there's rarely much to argue — the scope is just complete, and a complete scope is hard to trim.

Tie documentation quality to how reps get paid

Process that isn't measured decays. If your reps are paid purely on signed contracts, nobody's incentive is aligned with file quality — they're rewarded for the signature, not the scope. Without redesigning anyone's whole comp plan, you can attach accountability to the file: make a complete photo set and a code-checked estimate a condition of the job moving to production, track per-rep capture rates in your monthly audit, and recognize the reps whose files defend themselves. When file quality is visible and measured, it improves; when it's invisible, it's the first thing that slips on a busy week.

A worked example: two contractors, one storm, the same street

Two crews work the same hail-struck neighborhood. Same shingle, same labor market, same carriers.

Contractor A writes from the driveway. Aerial squares, "replace roof," three damage photos, done in twenty minutes. The estimate: tear-off, felt, shingles, a flat allowance for "flashing and accessories," no pitch verification, no penetration inventory, no code lines, no tear-off documentation, no supplement. Settles at roughly $11,200. Moves on.

Contractor B gets on the roof. Pitch gauge confirms 8/12 (the aerial said 6/12 — that alone restores the steep-slope labor). Story count noted. Every penetration photographed and itemized: eleven pipe boots and vents. Valley metal, step and counter flashing, chimney flashing — each on the estimate with a photo. Drip edge and ice-and-water shield included with the IRC section cited, because the jurisdiction's adopted code requires them. At tear-off, the crew finds two layers and four sheets of delaminated decking — photographed, measured, and written into a supplement with the original estimate cross-referenced. Detach-and-reset for a satellite dish. The complete, documented scope lands at roughly $14,400.

The difference is $3,200 on one roof. Contractor B didn't pad anything — every dollar is a photographed, measured, code-cited, physically-present line item. He didn't negotiate, didn't promise a payout, didn't touch the deductible. He documented better and wrote a complete estimate. Across a 150-claim season, that gap is $480,000 of gross revenue, on roofs both contractors had already won.

Now scale the failure mode. If Contractor A also spent documentation hours on roofs that didn't qualify — the five-year-old roofs, the homes with no real storm exposure — then his thin files on the good roofs aren't even his worst problem. His best reps' time bled out on the wrong houses.

The leak before the claim: documenting the wrong roofs

Every hour a rep spends inspecting and documenting a roof that was never going to qualify is an hour stolen from a roof that would have. This is the failure mode nobody puts on a spreadsheet, because it doesn't show up as a line item — it shows up as thin files, rushed photos, and skipped tear-off documentation on the roofs that actually deserved the full two-pass treatment.

The math is brutal when you look at it. If a rep can do four thorough inspections a day, and two of them are on roofs that were too new or too lightly hit to ever support a real scope, you've cut your documentation capacity in half — and the half you kept is rushed because the rep is behind. The fix isn't working faster. It's pointing the rep at the right roofs before they leave the truck.

What "the right roof" actually means

Two things make a roof worth a thorough file: age and storm exposure. A roof that's old enough to be near or past its service life, that also took real wind or hail, is where complete documentation pays off — there's genuine scope to capture and a real basis for a claim the homeowner can file. A five-year-old roof that caught the edge of a cell is usually a short, polite inspection, not a two-pass documentation project.

The trouble is you can't see either one from the curb reliably. Year-built data (from a county record or a real-estate site) tells you when the house was built, not when the roof was last replaced — re-roofs are invisible to those sources, so a 1998 house might have a 2019 roof. And a regional hail map tells you the storm passed through the ZIP, not which specific roofs it actually wore out; hail and wind hit individual roofs unevenly depending on orientation, slope, and the storm's path.

Where RoofPredict fits

This is the gap RoofPredict is built for, and it's worth being precise about what it does and doesn't do. RoofPredict scores the roofs in an area on two axes that matter for exactly this decision:

• Roof age as a range, estimated from aerial imagery — not a property record's year-built, and not an exact install date. It's a range (for example, 18–22 years), because that's the honest resolution of the signal. A range is enough to separate "worth a thorough file" from "too new to bother."
• Storm exposure modeled per roof, not per ZIP. Instead of a flat hail map that says "it hailed here," it models wind and hail impact roof by roof — the difference between where the storm passed and which roofs it actually wore out.

Used honestly, that means a rep walks out of the truck already knowing which addresses on the street are old enough and storm-worn enough to justify the full two-pass documentation, and which ones are a quick courtesy look. It also enriches a contractor's own CRM or mailing list with roof-age and storm signals, so the past customers and old estimates already in your book that are now due float to the top instead of sitting forgotten.

Honest limits, because that's how a tight trade compares notes: it's a range and a probability, not proof. The age is an estimate, not a roof's birth certificate. The storm score is the odds a roof was worn out, not a guarantee of damage — you still have to get on the roof and document what's physically there. What it does is make sure the documentation hours your reps have go to the roofs most likely to deserve them, instead of getting sprayed across a whole ZIP. It points the file-building labor at the right doors. The file-building itself is still yours to do well.

That's the connection back to the per-claim leak: the revenue you capture per claim is downstream of which claims you spend your documentation effort on. Better targeting upstream means better files downstream, which means more legitimate scope captured per job and fewer thorough inspections wasted on roofs that were never going to qualify.

The estimate itself: where quantities quietly shrink

Missed line items are the obvious leak. The sneakier one is line items that are on the estimate but carry the wrong quantity. A complete scope with shrunken numbers settles low without anyone noticing, because the estimate "looks complete." Walk your estimating discipline through these.

Squares. Field measurement and aerial reports both round, and a roof with several small planes adds up to more area than a quick read suggests. Trace your total squares back to the per-plane breakdown on the measurement report, and confirm the slope factor was applied — a flat (plan-view) area on a steep roof understates the actual surface you shingle. A single missed slope-factor adjustment on a steep roof can quietly drop a square or two.

Linear-foot items. Ridge, hip, valley, eave, rake, step flashing, and starter all price per linear foot. These are the quantities most often eyeballed instead of pulled from the measurement report. Hip-and-ridge cap especially gets shorted because people forget the off-ridges and the hips on a cut-up roof. Pull every linear quantity from the report; don't estimate them in your head.

Waste. Waste isn't padding — it's material you physically buy and throw away on cut-up roofs. A simple gable wastes little; a roof with five valleys and three dormers wastes a lot more. Match the waste percentage to the roof's actual complexity instead of defaulting to a flat number, and be ready to show the cut-up geometry in a photo if asked.

Layers and disposal. Two layers is roughly double the tear-off labor and disposal of one, and disposal is priced by weight and volume. If the estimate says one layer and the roof has two, both the labor line and the dumpster line are short. This is exactly what the tear-off pass exists to catch.

Quantity sanity check before you submit. Before anything goes to the homeowner, run a thirty-second sanity pass: does the square count match the measurement report, do the linear items match the report, does the layer count match the tear-off photos, and is there a photo behind every line. If those four agree, the estimate is internally consistent and defends itself line by line.

Worked numbers on a single plane

Say a measurement report lists a plane as 1,000 square feet in plan view at a 9/12 pitch. The slope factor for 9/12 is about 1.25, so the actual roof surface is roughly 1,250 square feet — 12.5 squares, not 10. Skip the slope factor and you've understated that one plane by 2.5 squares of shingles, underlayment, tear-off labor, and disposal. Stack that error across every plane on a steep roof and the "complete" estimate is quietly thousands of dollars light, with not one missing line item to point at. That's why the slope factor and the per-plane trace matter as much as the accessory checklist.

Commercial and steep-slope: the leak is bigger and the rules are the same

Everything above scales up on larger and commercial jobs, where the dollars per missed item are higher and the components are different. On low-slope and commercial work the under-claimed items shift to: tear-off and disposal of multiple membrane plies, insulation and tapered insulation, cover board, fasteners and plates per the wind-uplift requirement, flashing at curbs and parapets, pitch pans, edge metal and coping, drains and overflow scuppers, walkway pads, and the detach-and-reset of rooftop equipment. The documentation principle is identical — photo and measurement behind every line, captured before and after — but the per-line dollars are larger, so a thin commercial file leaves far more on the table than a thin residential one.

Steep-slope and complex-architecture residential (think 10/12-plus, turrets, multiple dormers, and heavy cut-up) carries the same multiplier: more access and safety labor, more waste, more linear-foot transitions, more detail flashing. The mistake is using a simple-gable mental model to estimate a complex roof. Let the measurement report and the photo inventory drive the numbers, not your gut.

Building the audit into a number your team feels

The Week 1 audit (below) produces a single figure that changes how a team behaves: your annualized leak. Make it concrete. If your audit of ten settled claims shows an average miss of $1,400 and you settle 180 claims a year, that's roughly $252,000 of gross revenue per year, on work you already sold and already built. Put that number on the wall. It reframes the photo checklist and the tear-off gate from "more paperwork" into "the most profitable hour of the day," and it's the difference between a process that sticks and one the crew quietly abandons by week three.

A 30-day plan to stop the leak

You don't fix this with a memo. You fix it with gates in the workflow that make the right behavior the only behavior.

Week 1 — Measure your current leak.

• Pull your last ten settled claims.
• Score each against the seven leak categories above. For each, was it captured, partially captured, or missed?
• Total the missed and partial dollars. That number is your annualized leak when you multiply by your claim volume. It's usually sobering, and it's the number that gets the team to take the rest seriously.

Week 2 — Build the photo and estimate gates.

• Adopt the inspection-pass and tear-off-pass checklists. Print them. Put them on a clipboard or in your field app.
• Make a rule: no estimate goes out without a photo behind every accessory and code line; no shingles get loaded without tear-off photos.
• Build a one-page reference of your jurisdiction's adopted IRC edition and local amendments, with section numbers, for the code lines.

Week 3 — Train the legal line.

• Run the team through the do-not-say list. Role-play the deductible question and the "will my claim get approved" question until the safe phrasing is automatic.
• Make clear that crossing into negotiating, interpreting coverage, promising payouts, or touching deductibles is a fireable, license-risking offense — not a sales technique.

Week 4 — Fix the targeting upstream.

• Stop spreading documentation hours evenly across every door. Rank the roofs by age range and per-roof storm exposure before reps roll out, so the thorough two-pass files land on the roofs that earn them.
• Enrich your existing CRM and mailing list with roof-age and storm signals, and work the past customers and old estimates that are now due first — that's revenue already sitting in your own book.

Ongoing — Audit monthly.

• Every month, pull a random five claims and re-run the Week 1 scoring. The leak should shrink. If a category keeps leaking, your gate for it is broken.

What pros get wrong (even the good ones)

• They confuse a sales photo with a scope photo. Three hail pictures sell the homeowner; they don't support eleven line items. Document the whole scope, not only the obvious damage.
• They skip the tear-off pass. Production mode wins, the roof gets dried in, and the decking-and-layers supplement basis is gone forever. Gate it: no loading shingles until the tear-off photos exist.
• They don't know their own code. The biggest defensible bucket is the one they're most timid about, purely from not knowing the adopted edition. Learn it once; cite it every time.
• They treat supplements as confrontation. A supplement is an accurate revision based on physical findings, not a fight. Photo plus measurement plus the original estimate cross-referenced — it defends itself.
• They cross the legal line trying to help. "Don't worry about the deductible" feels like good customer service and is illegal in many states. The safe phrasing wins more trust anyway.
• They document everything evenly. Spreading thorough inspections across roofs that never qualified is the invisible leak. Point the labor at the roofs that are actually old and actually storm-worn.
• They never measure their own leak. The Week 1 audit is the cheapest, highest-ROI hour an owner can spend, and almost nobody does it.

The bottom line

The revenue a roofing contractor leaves on the table per claim is real, recoverable, and mostly self-inflicted — typically $900 to $3,500 per residential replacement, hiding in undocumented accessories, missed steep-and-high charges, invisible decking, unknown code requirements, skipped detach-and-reset, absorbed waste, and the supplement nobody bothered to write. None of it requires negotiating a claim, interpreting a policy, or promising a payout. All of it lives on the side of the work you're licensed to do: get on the roof, document it twice, know your code, write a complete and accurate estimate, and hand the homeowner a file that defends itself.

And the leak starts before the claim does — in which roofs you spend your documentation hours on. Point that effort at the roofs that are genuinely old enough and storm-worn enough to deserve it, and every downstream number gets better.

The owners who fix this don't run a more aggressive shop; they run a more disciplined one. They measure their leak instead of guessing at it, they gate the photos so the file is built before the roof is dried in, they know their adopted code well enough to cite it, and they keep their reps firmly on the documentation side of the legal line. The result isn't a riskier business — it's a calmer one that captures the full, legitimate value of every roof it touches and can prove every dollar of it with a photo. None of that depends on a storm season being kind, and none of it asks anyone to promise a payout or erase a deductible. It's just the work done all the way through.

If you want to stop spraying documentation labor across a whole ZIP and instead see which roofs in your area are actually due — by age range and the storms they've taken roof by roof — and to enrich your own customer list with those signals, that's exactly what RoofPredict is for. Book a demo and bring a roof you already know the story on; you decide whether we called it right.

FAQ

How much revenue do roofing contractors actually leave on the table per claim?

On a typical residential replacement, the gap between a thoroughly documented scope and a rushed one usually runs $900 to $3,500, with steep-slope, multi-layer, and code-upgrade jobs running higher. The money hides in undocumented accessories, missed steep-and-high charges, invisible decking, unknown code requirements, skipped detach-and-reset, absorbed waste, and unfiled supplements. It's recoverable because it's all legitimate, physically-present, documentable work — not padding.

What's the single most-missed line item on a roofing claim?

Accessory and component items as a group — pipe boots, vents, drip edge, valley and step flashing, chimney flashing, exhaust caps, and detach-and-reset — because a driveway estimate lumps them into a flat allowance instead of itemizing each one with a photo. Individually small, they commonly total $600 to $1,400 on a full replacement. The close runner-up is code-required upgrades, which carry the largest defensible dollars and get skipped purely from contractors not knowing their adopted building code.

Can a roofing contractor legally negotiate an insurance claim for a homeowner?

No. Negotiating, adjusting, or 'handling' a claim for a homeowner for a fee is unlicensed public adjusting in most states and is prosecuted. A contractor may inspect, document conditions with photos and measurements, prepare an accurate estimate to repair their own scope, and state facts about that scope to the carrier. The homeowner files and the insurer decides coverage. Stay on the document-and-estimate side and you keep both your license and the revenue you documented.

What is a roofing supplement and how much can it recover?

A supplement is a documented revision of an estimate to reflect actual conditions discovered after the initial write-up — most often decking damage, extra layers, or code conditions found at tear-off. It's not a negotiation tactic; it's an accurate correction supported by photos and measurements with the original estimate cross-referenced. A well-documented supplement on a job that surfaced hidden conditions frequently recovers $800 to $2,500. The most common reason contractors lose this money is simply never writing the supplement.

Why are code-required upgrades the biggest under-claimed bucket?

Because most teams don't know their jurisdiction's adopted building code. When you re-roof, current code governs the new installation — which in many areas requires drip edge, ice-and-water shield, specified underlayment, proper ventilation, and re-nailing or decking work. These aren't optional add-ons; the law requires you to build them. Contractors who don't know the adopted IRC edition don't write them. Keep a one-page reference of your adopted edition and local amendments with section numbers, document the existing non-compliant condition, and cite the section on the estimate.

Is it legal to tell a homeowner their deductible will be covered?

No. Promising to waive, absorb, eat, or discount a homeowner's deductible is illegal in many states and is treated as insurance fraud. Advertising a 'free roof' or 'no out-of-pocket' falls in the same bucket. The deductible is part of the homeowner's policy and is between them and their insurer. The safe and honest answer is that you can't touch the deductible, but you can make sure the estimate is complete and accurate so nothing legitimate gets left out.

Why document a roof twice instead of once?

The inspection pass supports the initial estimate, but everything invisible until the roof is open — extra layers, deteriorated decking, hidden flashing rot, deck nailing — only shows up at tear-off. The tear-off pass is where most supplements are born, and it's the pass crews skip because they're in production mode. Make it a gate: no shingles get loaded until the tear-off photos exist. That one rule stops the supplement basis from walking off the roof.

How does targeting the right roofs affect revenue per claim?

Documentation labor is finite. Every thorough inspection spent on a roof that was too new or too lightly hit to qualify is one stolen from a roof that would have supported a real scope — so the good roofs get thin, rushed files. Pointing reps at the roofs that are genuinely old enough and storm-worn enough before they leave the truck means the full two-pass documentation lands where it pays, and more legitimate scope gets captured per job.

Can't I just use the county year-built and a hail map to find the right roofs?

Those tell you less than you'd hope. Year-built data is when the house was built, not when the roof was last replaced — re-roofs are invisible to property records, so an old house can have a recent roof. A regional hail map tells you the storm passed through the ZIP, not which specific roofs it wore out, since hail and wind hit individual roofs unevenly. You need roof-age (as a range) and storm exposure modeled per roof, not per ZIP, to know which doors deserve a thorough file.

What does RoofPredict do, and what doesn't it do?

RoofPredict scores the roofs in an area by estimated roof age (as a range, from aerial imagery — not an exact install date) and by storm exposure modeled per roof rather than per ZIP, and it enriches your own CRM or mailing list with those signals so the customers and old estimates that are now due float to the top. It tells you which roofs are most likely worth a thorough inspection. It is not a lead-buying service, it doesn't handle claims, and it doesn't prove damage — the age is a range and the storm score is odds, not a guarantee. You still get on the roof and document what's physically there.