Why Roofing Restoration Claims Get Underpaid: The Scope Gaps That Cost You

You finished the job. The roof is tight, the crew is paid, the homeowner is happy. Then you line up the carrier's scope sheet against your actual costs and the math is ugly: the claim paid for a roof, but not for the roof you built. A few hundred here for missing flashing, a thousand there for ridge vent that got replaced with a price for ridge cap, drip edge that isn't on the sheet at all, and a steep/high line that never made it in. None of it is fraud. None of it is a coverage denial. It's scope. The work was covered; the estimate just didn't describe the work.

That is what an underpaid restoration claim almost always is. Not a fight over whether the storm caused damage, and not a fight over whether the policy responds. It's a fight over how much of the necessary, covered repair the written scope actually captured. Carrier estimates are built fast, often from aerial measurements and a desk review, sometimes from a field adjuster who spent eleven minutes on the roof. The line items that get dropped are the same ones every single time. Once you can name them, photograph them, and write them into an accurate, defensible repair estimate, the gap between what the claim paid and what the roof cost stops being a surprise.

Before going further, one boundary that matters and that this whole piece will hold to: a roofing contractor documents damage, measures, and writes an accurate estimate to repair their own scope of work. The contractor states facts about that scope to the carrier. The contractor does not, for a fee, negotiate or adjust the claim, interpret the homeowner's policy or coverage, promise a payout or an approval, promise a deductible is waived, advertise a "free roof," or represent the homeowner against their insurer. That last set is unlicensed public adjusting in most states, and it's the fastest way to turn a legitimate supplement into a regulatory problem. The homeowner files the claim. The insurer decides coverage. The contractor's job is to make the repair scope so well-documented and so accurately priced that there's nothing left to leave out. Everything below lives on that side of the line.

What "underpaid" actually means on a roofing claim

There's a useful distinction that gets blurred all the time, and blurring it is how good contractors end up arguing the wrong point.

A claim can come up short for three structurally different reasons:

1. Coverage shortfall. The policy genuinely doesn't respond to part of the loss — a wind/hail exclusion, a cosmetic-damage endorsement on metal, a roof-payment schedule (ACV-by-age) on an older roof, a separate wind/hail deductible. This is a policy question. It is the homeowner's and the carrier's to resolve. A contractor who starts arguing coverage here has stepped over the line.
2. Pricing shortfall. The line items are present but the unit prices are stale, the wrong waste factor was applied, or the labor/material split doesn't reflect the market. This is a price-list and methodology question.
3. Scope shortfall. The work that must be done to return the roof to pre-loss condition — and to do it to code — simply isn't fully described on the estimate. Items are missing. Quantities are low. The right line exists but the wrong one was used.

The third bucket is where the money quietly lives, and it's the one a contractor is squarely entitled to address, because it's a factual question about the work, not a legal question about the policy. When people say "restoration claims are underpaid," they usually mean scope. The carrier didn't deny anything. They paid for an incomplete description of the job.

The reason scope shortfalls dominate is mechanical. Carrier estimates are produced under time pressure, frequently off aerial measurement reports and photos, by adjusters carrying enormous file loads after a storm. The estimating software does exactly what it's told — it doesn't add a starter course or a code-required item unless someone puts it there. So the same handful of items fall through the cracks on file after file. Predictable gaps are good news: predictable means catchable, and catchable means you can build a documentation routine that closes them before the first estimate is even written.

The scope gaps that show up over and over

What follows is the working list of line items and quantities that most commonly go missing or get underpaid on a residential restoration roof. None of these are exotic. They're the ordinary anatomy of a real reroof. The skill isn't knowing they exist — it's proving each one with evidence on the specific house, in the specific estimate, so it isn't a generic "add this" request but a documented fact about this roof.

Tear-off, layers, and what's actually under there

The number of existing layers changes the tear-off line and sometimes the decking. An estimate written for one layer when there are two underpays the removal and disposal. You find this out on the roof, not from an aerial report, which is why a tear-off photo sequence — showing the layer count at the eave and at a mid-field cut — is worth more than any verbal description.

Decking condition is the companion item. If sheathing is delaminated, rotted at the eaves, or boards are spaced (plank decking) where code now requires a solid nailable surface, re-decking or re-nailing is part of returning the roof to a code-compliant, workmanlike condition. That's a documented field finding with photos and a moisture reading, not an assumption.

Starter course and ridge — the two most-missed shingle lines

Starter strip along eaves and rakes is the single most commonly omitted shingle line on residential estimates. It's required by manufacturer installation instructions for a valid installation, it's a real material with a real labor component, and it is routinely absent from the carrier scope or buried inside a generic shingle quantity that doesn't account for it.

Ridge cap is the close second. Three-tab fields used to get capped with cut three-tab; architectural fields use a dedicated hip/ridge cap product that costs meaningfully more per linear foot. When the estimate prices ridge as "cut from field shingles" but the roof is architectural and the manufacturer's system calls for a matched cap product, the line is underpriced. Hip and ridge length is also frequently undercounted on cut-up roofs because the aerial sketch missed a hip.

Drip edge, flashing, and the metal nobody sketches

Drip edge at eaves and rakes is code in current model codes and is frequently missing from carrier scopes entirely. It's inexpensive per foot, but across a whole perimeter it adds up, and leaving it off the estimate means leaving it off the payment for a code-required component you're installing anyway.

Flashings are a category, not a line: step flashing at wall-to-roof transitions, headwall/apron flashing, counterflashing where it ties into masonry or siding, valley metal, pipe jack/boot flashings, and chimney flashing. Each is a separate item with its own quantity. Reusing old step flashing is usually not acceptable practice on a full reroof, and "detach and reset" versus "replace" is a real pricing difference you should be documenting per condition.

Vent components — turtle/box vents, ridge vent, turbines, and the pipe boots above — are their own cluster of small misses. Ridge vent in particular gets dropped or gets priced as if the existing vent is reusable when it isn't.

Underlayment, ice-and-water, and the code line that's hard to argue with

Underlayment type and quantity matter. Synthetic versus felt is a pricing line. The big one is ice-and-water shield (self-adhered membrane) at eaves, valleys, and penetrations where the local code and climate require it. In cold-climate jurisdictions the code calls for an ice barrier extending a specified distance up-slope from the eave — commonly to a point measured inside the exterior wall line — and that's a quantity calculation tied to roof geometry and overhang, not a guess. Valley lining and penetration flashing membrane are related items that get folded away.

Steep and high — the access modifiers

Steep-slope and high-roof (two-story-plus / difficult access) labor modifiers exist because the work genuinely costs more, and they are constantly omitted on the carrier estimate because the desk reviewer can't see pitch and stories from a flat aerial. Pitch is measurable from the field with a pitch gauge and provable in a photo. Roof height is provable. These modifiers apply to the affected squares, and getting them on the estimate for the correct quantity is ordinary, defensible scope.

Detach-and-reset, accessories, and the stuff on top of the roof

Anything mounted on or through the roof that has to come off and go back on is a line: satellite dishes, solar attachments, gutters and gutter guards where they interfere, antennas, dead-mount brackets, and so on. Gutters and downspouts damaged by the same storm event, where covered, are their own scope. Detach-and-reset of these is real labor.

Cleanup, protection, and the items that aren't shingles

Magnetic nail sweep, tarping/temporary protection if the roof was opened, dumpster/haul-off sized to the actual layer count, and landscape/property protection are legitimate cost components. Permit fees where the jurisdiction requires a permit for a reroof are recoverable and frequently left off.

Here is a compact reference of the usual suspects. Treat it as a pre-estimate checklist, not a menu — every line you claim has to be true on the actual roof and backed by a photo or a measurement.

Why the carrier estimate is structurally short — and why that's not personal

It helps to stop reading underpayment as bad faith and start reading it as a process artifact. The carrier's first estimate is a starting document produced under constraints:

• It's often built from aerial measurement reports. Those reports are excellent for area, eaves, rakes, hips, valleys, and pitch — and blind to layer count, deck condition, flashing condition, accessory mounts, and anything under the surface. A scope built purely off aerial geometry will be geometrically correct and physically incomplete.
• The adjuster carries volume. After a hail or wind event, field and desk adjusters are processing enormous numbers of files. The estimate that gets written is the fast, defensible-on-its-face version, not the exhaustive one.
• The price list is a snapshot. Estimating platforms publish regional price lists that update periodically. Between updates, and especially in a tight post-storm market, the published unit cost can lag the real cost of labor and material. That's a pricing-shortfall conversation, distinct from scope.
• Defaults don't add code or system items. Estimating software adds what's entered. It will not insert starter, drip edge, an ice barrier, or a steep modifier on its own. If nobody enters them, they're simply not there.

None of that requires a villain. It does mean the first estimate is a draft of the work, and the contractor who can hand over a complete, evidence-anchored description of the actual repair is doing the carrier's file a favor, not picking a fight. That framing also keeps you on the right side of the line: you're not arguing the homeowner's coverage, you're correcting the description of the work you're going to perform.

The documentation that makes a supplement undeniable

A supplement that gets paid is a supplement that's boring to read. Every requested item is right there with a photo, a measurement, a citation, and a price. No persuasion, no adjectives, no "please reconsider." Just a corrected description of the work with the evidence attached so the desk reviewer can approve it without leaving their chair.

The difference between a 30% supplement approval rate and an 80% one is almost never how hard you push. It's whether the file makes approval easy. Build the documentation at inspection and tear-off, before you ever know you'll need it, because you can't go back and photograph a roof you already replaced.

The inspection photo set, organized so it proves scope

Shoot for a named, repeatable set every time. Disorganized photos are nearly worthless in a supplement; a labeled set is a paper trail.

1. Address verification — the house number and a street-context shot, so every later photo is unambiguously this property.
2. Full elevations — all four sides, showing stories (proves high/2-story), wall transitions, and accessory mounts.
3. Overall roof planes — each slope, oriented, so geometry and shingle type are visible.
4. Pitch — a pitch gauge on the deck, in frame, proving steep modifier eligibility.
5. Test square (damage density) — a marked 10x10 area with hail hits or wind damage circled, with a reference object for scale. This documents damage; it is a factual record, not a coverage opinion.
6. Penetrations and accessories — every pipe boot, vent, dish, solar mount, counted and shown.
7. Flashing conditions — step, headwall, valley, chimney, each with a condition note.
8. Eave and rake edges — showing presence/absence of drip edge and starter, and overhang depth (feeds the ice-barrier calc).
9. Layer count — a cut at the eave and a mid-field cut showing how many layers exist.
10. Decking — once exposed, any rot, delamination, spacing, or fastener failure, with a moisture meter reading in frame where relevant.

Tie each photo group to the line item it supports. A reviewer who can see the missing drip edge and read the code distance next to the eave-overhang measurement has no reason to kick it back.

The measurement and code packet

Alongside photos, the file needs hard numbers:

• Measurements — squares, eave LF, rake LF, hip LF, ridge LF, valley LF, penetration count, story count, predominant pitch. Whether from an aerial report or hand measurement, this is the quantity backbone for every line.
• Code references — the specific adopted code edition in the jurisdiction and the sections that drive your code items (ice barrier distance, drip edge requirement, deck/fastening, re-cover limits). Cite the section, don't paraphrase it. "Required by [adopted code] [section]" reads very differently than "this should be included."
• Manufacturer instructions — the install document that makes starter and matched ridge cap a requirement for a valid, warrantable installation, not a preference.
• The unit-price basis — if you're addressing a pricing shortfall, show the basis (current published price list version, or documented local market quotes) rather than asserting a number.

The estimate itself

Your repair estimate should be written line-by-line in the same structure and order the carrier uses, so they line up side by side and the gaps are self-evident. Match line codes where you can. Where you're adding an item, label it clearly, attach the evidence, and price it to the same basis. Where a quantity differs, show your measurement. The goal is an apples-to-apples document where the only differences are the documented, missing scope — nothing for a reviewer to untangle.

And a hard rule on language: the estimate and any cover note describe the work and its cost. They never opine on the homeowner's coverage, never state what the carrier "owes" the policyholder, never promise an approval, and never reference the deductible as something to be handled. You are the contractor pricing the repair. That's the whole role, and it's a strong one.

A worked example: where a real roof loses money

Abstract lists don't land, so here's a representative single-family reroof to show how the gaps stack. The numbers are illustrative — use your own current price basis — but the structure is exactly what plays out on real files.

Assume a 28-square architectural-shingle roof, two stories, predominant 7/12 pitch, two existing layers, cut-up with several hips, in a cold-climate jurisdiction with an ice-barrier requirement.

The carrier's aerial-built first estimate captures: field shingles (28 sq), one-layer tear-off, felt underlayment, a generic ridge allowance, and standard pipe boots. It looks complete at a glance. Here's what an evidence-backed scope adds, and roughly where the money sits:

Notice the pattern: not one of these is a coverage argument. Every single line is a factual correction to the description of the work, each backed by something you can point at. Add them up across a few dozen jobs a year and the difference between catching them and eating them is the difference between a restoration division that funds itself and one that bleeds margin while everyone congratulates themselves on "winning" the claim.

Notice too what's not in that table: nothing about the deductible, nothing about what the homeowner is "owed," nothing promising the supplement will be approved. The deductible is the homeowner's responsibility under their policy and stays that way. Your job ended at an accurate, complete, well-evidenced estimate.

The supplement workflow, step by step

A repeatable process beats heroics. Here's a clean sequence from inspection to a closed supplement that any production or supplement manager can run.

1. Inspect with the full photo set and measurements. Do this before any contract conversation about claims is finished, and capture the test square, pitch, layers, flashings, penetrations, and elevations every time — even when you think the roof is simple.
2. Pull the adopted code and manufacturer instructions for this jurisdiction and product. Identify the code-driven items (ice barrier, drip edge, deck/fastening) up front so they're in the first estimate, not a later supplement.
3. Write your repair estimate in the carrier's structure. Line-by-line, matched codes where possible, every quantity tied to a measurement, every code/system item tied to a citation or install doc.
4. Compare to the carrier estimate and build a delta list. For each gap, attach the specific photo(s), the measurement, and the code/manufacturer reference. The output is a clean, item-by-item document, not a letter.
5. Submit on the documentation side. Provide the corrected scope and evidence to the homeowner and, as the contractor performing the work, to the carrier as a factual description of the repair. The homeowner remains the claimant. You do not negotiate coverage; you supply scope and price.
6. Track aging and follow up on a cadence. A supplement that sits for weeks with no follow-up dies of neglect. Set a follow-up rhythm (for example, a touch every few business days) and log each contact, so nothing stalls silently.
7. Document completion for recoverable depreciation. On ACV-first claims, the recoverable depreciation releases after the work is done and documented — typically a final invoice plus completion evidence (photos, sometimes a certificate of completion). Build that release packet as part of closeout, not as an afterthought weeks later when the homeowner has stopped answering.
8. Close the deductible properly. The deductible is collected from the homeowner. It is not waived, rebated, absorbed, or "taken care of." Invoice it, collect it, and keep the record clean. This is both a compliance line and, in many states, the law.

The two places this process leaks are the front (incomplete documentation at inspection, which you can never recover) and the middle (supplements that age out without follow-up). Fix those two and most of the underpayment problem fixes itself.

Reading the carrier estimate line by line

Most contractors skim the carrier estimate for the bottom number and a couple of obvious omissions. The estimators who consistently get paid read it the way an auditor reads a ledger — top to bottom, line by line, asking three questions of every line and noting every line that should exist and doesn't. The three questions:

1. Is the right line item here at all? Does a line exist for this component? Starter, drip edge, ice barrier, ridge cap, each flashing type, each modifier.
2. Is it the right item? Ridge priced as cut-from-field on an architectural roof is the wrong item. Felt where the spec needs synthetic is the wrong item. A reset where the condition requires replacement is the wrong item.
3. Is the quantity right? Eave LF, rake LF, hip and ridge LF, valley LF, penetration count, affected squares for modifiers, membrane SF for the ice barrier. Aerial sketches miss hips on cut-up roofs and under-count valleys constantly.

Reading this way, the estimate stops being a number and becomes a map of what was and wasn't seen. A line that's present but priced as the wrong product is a different conversation from a line that's missing entirely, which is different again from a line whose quantity is short — and each gets handled differently. The present-but-wrong item needs the manufacturer spec or the field photo that shows what's actually on the roof. The missing item needs the code citation or install instruction that makes it required plus the measurement. The short quantity needs your measurement against theirs. Sorting the gaps into those three buckets before you write a word is what turns a vague "this is underpaid" feeling into a clean, itemized delta a reviewer can act on.

There's a sequencing benefit too. Reading line by line in the carrier's own order means your estimate naturally mirrors theirs, which is exactly the side-by-side structure that makes a supplement easy to approve. You're not handing the reviewer a separate document to reconcile — you're handing them their own estimate with the corrections slotted into the right rows.

ACV, RCV, and depreciation — getting the money flow right

A lot of perceived underpayment is really a misread of how a replacement-cost claim pays out in stages, so it's worth being precise about the mechanics, because they change what "underpaid" even means at each step.

On a replacement-cost-value (RCV) policy, the carrier typically issues the first payment at actual cash value (ACV) — the replacement cost minus depreciation minus the deductible. Depreciation here is the carrier's estimate of the wear the old roof had used up. That first check looks small, and contractors who don't understand the structure read it as the carrier lowballing the whole loss. It usually isn't. The recoverable portion of that depreciation is held back and released after the work is completed and documented, which is why the closeout packet matters so much: the depreciation isn't lost, it's pending proof of completion.

Three things to keep straight:

• ACV first, recoverable depreciation later. The held-back depreciation comes back on an RCV policy once you submit the final invoice and completion evidence. Miss that step and real, owed money simply never gets released.
• Non-recoverable depreciation is different. Some depreciation may be non-recoverable depending on policy terms and the roof's situation — that's a policy matter the homeowner and carrier work out, not something a contractor argues.
• The deductible comes out once. It's the homeowner's, collected by you, and it doesn't get "made up" elsewhere.

Where this intersects with scope: depreciation is applied to the scope that's on the estimate. If a line item was never written, there's no depreciation held against it — but there's also no payment for it, recoverable or otherwise. Fixing scope before the estimate is finalized means the RCV total is correct, the ACV is calculated against the right base, and the recoverable depreciation that releases at completion reflects the actual job. Scope accuracy and the money-flow mechanics aren't separate problems; the second one only works if the first one is right.

A clean way to explain this to a homeowner — staying entirely on facts and never interpreting their coverage — is to say: the first check reflects the depreciated value today, a portion of that depreciation is recoverable after the work is documented as complete, and the deductible is your responsibility under your policy. You're describing the mechanics, not promising an outcome, and that distinction is exactly the compliance line.

Cold-climate, coastal, and high-wind scope items that get dropped

Geography drives code, and code drives scope. The items that go missing on a cold-climate roof aren't the same ones that go missing on a coastal high-wind roof, and a desk reviewer working a national file volume won't always apply the local requirement. Knowing your jurisdiction's adopted code and its local amendments is what lets you write — and defend — these.

Cold-climate jurisdictions

The headline item is the ice barrier: a self-adhered membrane required at eaves extending up-slope to a point measured a set distance inside the exterior wall line, with the exact distance set by the adopted code. Because the requirement depends on overhang depth and roof geometry, the membrane square footage is a calculation, not a flat allowance — and it's frequently either dropped or under-quantified on an aerial-built estimate that never measured the overhang. Valley membrane and penetration membrane ride along with it. In heavy-snow areas, additional fastening or underlayment requirements may apply per local amendment.

Coastal and high-wind jurisdictions

High-wind zones drive enhanced fastening (more nails per shingle, ring-shank fasteners), sealed or taped deck requirements in some jurisdictions, and specific starter and perimeter detailing because the edges are where wind uplift starts. There may be product approval or wind-rating requirements that change the material line itself. Drip edge and perimeter metal specifications can be more stringent. None of these show up on a generic national-default estimate unless someone enters them with the local code basis.

Everywhere: the re-cover and re-decking triggers

Most codes limit how many roof layers are permitted and prohibit re-covering over certain conditions, which forces a full tear-off and sometimes deck work. Spaced plank decking that no longer provides a continuous nailable surface for modern shingles can trigger re-decking or re-sheathing as part of a code-compliant install. These are field-discovered, code-driven items — exactly the kind that belong in the file with a photo and a code section, not as a verbal add later.

The practical move: keep a short, jurisdiction-specific code sheet for each area you work, listing the adopted edition and the sections that drive your common code items. Then the cold-climate ice barrier, the coastal fastening schedule, and the re-cover limit are in your first estimate by default, cited, instead of remembered on file forty.

Building a standard estimating template so approval rates stop being a coin flip

The single biggest lever on supplement approval rate across a multi-estimator shop isn't talent — it's standardization. When every estimator builds scope their own way, your approval rate is the average of your best and worst estimators, and your worst estimator is leaving money on every file. A standard line-item template per roof type fixes this without micromanaging anyone.

Build a base template for each common roof configuration you run — for example, architectural single-layer, architectural over two layers, three-tab, low-slope/flat sections — that pre-lists every line that should be considered, in the carrier's order, with the evidence requirement noted next to each. The template doesn't decide quantities or confirm conditions; it makes sure no estimator forgets to ask the question about starter, drip edge, ice barrier, ridge cap product, each flashing, each modifier, layers, decking, accessories, and permit. Each line on the template carries a note: "required by [code/manufacturer ref]; quantity = [measurement source]; evidence = [photo group]."

What this does in practice:

• It moves expertise from heads to the system. Your best estimator's checklist becomes everyone's checklist.
• It makes files consistent. A reviewer who sees the same clean, complete structure from your shop every time starts trusting your files, and trusted files move faster.
• It surfaces training gaps. When you can see which lines a given estimator routinely omits, you know exactly what to coach.
• It standardizes the evidence. Because the template names the required photo group per line, the inspection photo set and the estimate template reinforce each other — the inspector knows what to shoot because the estimate knows what it needs.

The template is not a license to add lines that aren't true on the roof. Every templated line still has to be confirmed against the actual conditions and backed by the actual photo before it goes on the estimate. The template guarantees the question gets asked every time; the field evidence answers it. That combination — ask every question, prove every answer — is what turns scope completeness from a personal skill into a company process.

What pros get wrong

Even experienced restoration shops lose money to a short list of avoidable habits.

• Treating the carrier estimate as the scope of work. It's a draft. Building your job and your budget around it guarantees you eat every missing line.
• Photographing for the file instead of for the line item. A thousand unlabeled roof photos prove nothing. Ten photos tied explicitly to ten line items prove ten line items.
• Writing supplements as arguments. Persuasion language ("we strongly believe," "please reconsider") signals a weak file. Evidence language ("drip edge required per [code section]; eave+rake = X LF; see photos 8–9") gets approved.
• Skipping code research until the supplement. Code items belong in the first estimate. Adding them late looks like an afterthought and slows everything down.
• Crossing the public-adjusting line to "help." Negotiating the claim, interpreting the homeowner's coverage, promising approval, or telling the homeowner the deductible is handled feels like service and is a regulatory hazard. Stay on documentation and estimate. It's a stronger position anyway, because facts don't need permission.
• Letting supplements age. No follow-up cadence means files stall and depreciation never gets released. The work is done; the money's sitting there because nobody touched the file.
• Inconsistent estimating across estimators. When every estimator builds scope differently, your supplement approval rate becomes a coin flip. A standard line-item template per roof type fixes it.

Where RoofPredict's RoofClaim does the heavy lifting

Most of the work above is a documentation-and-estimating discipline problem, and that's exactly what RoofPredict's integrated claim revenue-cycle side, RoofClaim, is built to make repeatable instead of heroic.

Start with claim intake linked to the home. The claim isn't a loose folder; it's attached to the specific property you already have a roof profile and storm-exposure record for. You upload the claim documents — the carrier estimate, your estimate, photos, denial letters, invoices — and they're auto-classified and OCR'd, so a multi-page carrier scope becomes structured, searchable line items instead of a flat PDF you squint at.

Then the part that maps directly to everything above: opportunity detection. RoofClaim takes the carrier's estimate line items and compares them against a roofing knowledge base, then flags missing scope, code-required items, and missed supplements — with evidence anchors and pricing attached. That's the starter strip that isn't there, the ridge priced as cut-from-field on an architectural roof, the absent drip edge, the under-quantified ice barrier, the missing steep modifier — surfaced as a delta list against the actual scope rather than something an estimator has to remember to check on file number forty of the week. The flags come with the why (the code item, the system requirement) and a pricing basis, which is exactly the evidence-anchored format a supplement needs to be approvable on sight.

For the back half of the cycle, RoofClaim runs a recoverable-depreciation autopilot — a completion-evidence and final-invoice checklist so the depreciation release packet gets built at closeout instead of forgotten — and deductible tracking that keeps the deductible recorded as the homeowner's responsibility (collected, never "waived"). Supplement aging with a follow-up cadence stops files from dying of neglect, and packet-completeness scoring tells you whether a given supplement actually has its photos, measurements, and citations before it goes out, so you're not submitting half-built files. There's also claim-inbox email triage so carrier correspondence doesn't pile up unread.

Two honest limits, because the whole point is staying credible. First, every template in RoofClaim — the supplement packets, depreciation-release letters, deductible invoices, missing-docs letters, audit reports — is locked and UPPA-gated to the contractor-documentation side. They describe and price your work. They do not negotiate the claim, interpret the homeowner's policy, promise an approval, or touch the deductible as something to be erased, because doing any of that would be public adjusting and the templates are built specifically to keep you out of that territory. Second, the opportunity detection surfaces and prices candidate scope gaps from the documents and the roof; a human still has to confirm each one is true on this specific roof and attach the field evidence. It makes the catch reliable and fast. It doesn't replace the inspection.

Targeting the right roofs before a claim ever exists

Underpaid claims are a back-end problem. The front-end version of the same discipline is making sure you're working the roofs most likely to have a legitimate, well-supported restoration story in the first place — which is where the targeting side of RoofPredict comes in, and it's worth a paragraph because the two halves reinforce each other.

RoofPredict scores every home in a service area by roof-age band (recent / mid-life / due / overdue) plus per-roof storm exposure plus an opportunity score, and produces a ranked, house-by-house target audience with a "why this home" evidence chain. Honest about the method: that scoring is roof-age plus storm-exposure heuristics, not a magic prediction — roof age is estimated as a range, not an exact install date, and a storm-exposure flag is odds that a roof saw a damaging event, never proof of damage on that specific roof. What it does well is point your inspectors at the overdue, storm-exposed roofs first instead of knocking randomly. You turn that ranked list into tracked direct mail (personalized proofs, per-piece delivery tracking, cost quoted up front), personalized microsites and PDF reports per home with lead capture, per-home QR codes for mail and doors, and door-knock routes with a mobile field app for your canvassers. Leads flow into a pipeline (new → contacting → appointment → inspected → won/lost) with an immutable first-touch source, and that pipeline syncs two-way with the CRM you already run — JobNimbus, AccuLynx, ServiceTitan, HubSpot, CompanyCam, and others — so the claim work in RoofClaim and the production work in your CRM aren't two disconnected worlds.

The through-line: target the roofs with a real age-and-storm story, document them completely at inspection, write an accurate code-aligned estimate, and let RoofClaim catch the scope gaps the carrier's draft left out — all on the documentation-and-estimate side of the line, every time.

A pre-submission checklist you can actually use

Print this. Run it on every file before scope goes out.

• Address-verified photo set, labeled and tied to line items
• All four elevations (story count proven)
• Each roof plane photographed, oriented, shingle type visible
• Pitch gauge photo (steep modifier basis)
• Test square with damage marked and a scale reference
• Layer-count photos (eave cut + mid-field cut)
• Decking condition photos + moisture reading where relevant
• Every penetration and accessory counted and shown
• Flashing conditions documented (step, headwall, valley, chimney)
• Eave/rake photos showing drip-edge and starter presence/absence + overhang depth
• Measurements: squares, eave/rake/hip/ridge/valley LF, penetration count, stories, pitch
• Adopted code edition + cited sections for each code item (ice barrier, drip edge, deck/fastening)
• Manufacturer install instructions on file (starter + matched ridge cap)
• Estimate written in carrier structure, matched line codes, evidence attached per item
• Delta list against carrier estimate, each gap evidenced
• Pricing basis documented (current price-list version or local quotes)
• Depreciation-release / completion packet planned for closeout
• Deductible recorded as homeowner responsibility (collected, not waived)
• No coverage interpretation, payout promise, approval promise, or deductible-handling language anywhere in the file

That last checkbox is the one that protects the business. The rest get you paid for the roof you actually built.

The bottom line

Restoration claims come back underpaid because the carrier's first estimate is a fast draft built largely from aerial geometry, and the same dozen items — starter, ridge cap, drip edge, ice barrier, flashings, steep and high modifiers, second-layer tear-off, decking, accessory detach-reset, permit — fall out of it every time. None of that is a coverage fight. It's a description-of-the-work problem, and the contractor owns the document side of that problem completely: photograph it at inspection, measure it, cite the code, write an accurate estimate in the carrier's structure, and attach the evidence so approval is the path of least resistance. Stay strictly on documentation and price — never negotiate the claim, interpret the homeowner's coverage, promise an approval, or touch the deductible — and the scope gaps stop being a surprise at the end of the job and start being a line you caught at the beginning. Catch them reliably across every file, and the restoration division stops leaking the margin it was supposed to earn.

FAQ

Why does my carrier estimate keep missing line items like starter and drip edge?

Because most carrier first-estimates are built quickly, often from aerial measurement reports and a desk review, and the estimating software only includes what someone enters. Aerial reports are blind to layer count, deck condition, and flashing condition, and defaults don't add starter, drip edge, an ice barrier, or steep modifiers on their own. The fix is to document each item with a photo, a measurement, and a code or manufacturer citation, then write it into your estimate in the carrier's own structure so the gap is self-evident.

Is requesting a supplement the same as adjusting or negotiating the claim?

No, and keeping them separate is what keeps you compliant. A contractor supplies a corrected, evidence-backed description of the work to be performed and its price. That is a factual statement about your scope. Adjusting or negotiating the claim, interpreting the homeowner's policy, or promising an approval is a different activity that is unlicensed public adjusting in most states. Stay on the documentation-and-estimate side: the homeowner files, the insurer decides coverage, and you describe and price the repair.

What documentation makes a roofing supplement most likely to be approved?

A labeled photo set tied to specific line items, hard measurements (squares plus eave, rake, hip, ridge, and valley linear footage, penetration count, story count, pitch), the adopted code edition with cited sections for code-driven items, manufacturer install instructions for items like starter and matched ridge cap, and a pricing basis. Write the estimate in the carrier's structure with matched line codes so it lines up side by side. The aim is to make approval require no effort from the reviewer.

What is the difference between an underpaid claim from scope versus from coverage?

A scope shortfall means the necessary, covered work simply isn't fully described on the estimate — missing items or low quantities. That is a factual question about the work and squarely the contractor's to address. A coverage shortfall means the policy genuinely doesn't respond to part of the loss, such as an exclusion or an age-based payment schedule. Coverage is a policy question between the homeowner and the carrier, not something a contractor should be arguing.

How do I prove a steep or high-roof modifier belongs on the estimate?

Pitch is measurable in the field with a pitch gauge and provable with a photo of the gauge on the deck. Roof height and story count are provable with elevation photos. These modifiers exist because steep and multi-story work genuinely costs more, and they're often omitted because a desk reviewer can't see pitch or stories from a flat aerial image. Document the pitch and stories, then apply the modifier to the affected squares with the photo as the basis.

When does recoverable depreciation get released, and how do I make sure it does?

On an actual-cash-value-first claim, the recoverable depreciation typically releases after the work is completed and documented, usually with a final invoice plus completion evidence such as photos and sometimes a certificate of completion. The common failure is finishing the job and never building that release packet, so the money sits unclaimed. Build the completion packet as part of closeout and follow up on a set cadence so the file doesn't stall.

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

No. The deductible is the homeowner's responsibility under their policy, and it must be invoiced and collected. Promising it is waived, absorbed, rebated, or handled — or advertising a free roof — is prohibited in many states and can constitute insurance fraud or an unfair practice. Keep the deductible recorded as the homeowner's obligation, collect it, and keep the documentation clean.

How does RoofPredict's RoofClaim help close scope gaps?

RoofClaim links the claim to the home, auto-classifies and OCRs the uploaded claim documents, then runs opportunity detection that compares the carrier's line items against a roofing knowledge base and flags missing scope, code-required items, and missed supplements with evidence anchors and pricing. It also runs a recoverable-depreciation autopilot, deductible tracking, supplement aging with a follow-up cadence, and packet-completeness scoring. Every template is locked to the contractor-documentation side, and a human still confirms each flagged item is true on the specific roof.

Should code-required items go in the first estimate or wait for a supplement?

Put them in the first estimate. Research the jurisdiction's adopted code edition before you write the estimate and include the code-driven items — ice barrier, drip edge, deck and fastening requirements — from the start, with the section cited. Adding code items later as a supplement looks like an afterthought, slows the file, and gives a reviewer a reason to question them. Front-loading them with citations makes the whole file cleaner.

Why do experienced restoration shops still lose money on scope?

Usually for a few repeatable reasons: treating the carrier estimate as the scope of work instead of a draft, photographing for the file rather than tying photos to specific line items, writing supplements as persuasive arguments instead of evidence, researching code only at supplement time, letting supplements age without a follow-up cadence, and estimating inconsistently across estimators. Fixing the front (complete documentation at inspection) and the middle (a follow-up rhythm) recovers most of the lost margin.