How to Improve Your Roofing Supplement Approval Rate

Most roofing companies treat the supplement as the annoying paperwork after the sale: the adjuster wrote a scope that was too low, somebody on staff fires off a list of missing line items, the carrier knocks half of them out, and everyone moves on resigned to leaving money on the table. The shops that run this well see it completely differently. To them the supplement is a documentation discipline that, done right, recovers thousands per job and gets approved on the first pass instead of the third. The gap between a 40 percent supplement approval rate and an 85 percent one is almost never luck or a friendlier carrier. It is process.

The approval rate is the percentage of your supplemented line items (or supplemented dollars) that the carrier actually approves. Raising it is a craft. It comes down to writing supplements the way a desk reviewer wants to receive them, backing every line with the kind of proof a person sitting in an office weeks later can verify, citing the code and manufacturer requirements that justify each upgrade, and never including the kind of junk that trains a reviewer to distrust your whole packet. Get those right and the same roofs that used to fight you start clearing on the first submission.

A hard line first, because it governs everything below. You are a roofing contractor. You inspect the roof, you document its condition, you write an accurate estimate for the work you will perform, and you supplement that estimate when the approved scope is missing items the job genuinely requires. You do not negotiate or adjust the claim, you do not interpret the homeowner's policy or coverage for them, you do not promise a payout or an approval, and you do not do anything with the deductible. The homeowner owns the claim and files it; the carrier decides coverage. In most states, stepping over that line is unlicensed public adjusting, which is a real legal problem, not a gray area. Everything below lives strictly inside the contractor lane, and the spots where that lane narrows are flagged.

What a supplement actually is, and what it is not

A supplement is a request to add or correct line items on a claim that has already been at least partially approved, because the approved scope does not reflect what the job actually requires to be built correctly, to code, and to manufacturer specification. It is a scope and pricing correction, supported by evidence.

That definition matters because it tells you what a legitimate supplement is made of, and it is not the same thing as disputing whether the loss is covered at all. Those are two different animals:

• A coverage dispute is about whether the peril is covered, whether the damage is storm versus wear, whether the date of loss is right. That fight is largely the homeowner's and their carrier's, and you support it with documentation but you do not run it.
• A supplement assumes coverage already exists and corrects the amount and scope of the approved work. This is squarely your lane as the contractor, because you are the one who has to build a roof that meets code and manufacturer requirements.

The reason the distinction is worth dwelling on: most denied supplements are denied because they smell like a coverage fight or a money grab rather than a clean scope correction. A line item that says "the deck won't pass fastening requirements once the old roof is off, here is the IRC section and here are the photos" is a scope correction a reviewer can approve in two minutes. A line item that says "additional overhead and profit" with no basis is a money grab that gets struck and makes the reviewer suspicious of everything around it. Approval rate is, to a large degree, the discipline of submitting only the first kind.

Approval rate versus recovery, and why you track both

Do not confuse a high approval rate with maximum recovery. You can hit a 95 percent approval rate by only ever supplementing the three safest items on every job, and leave real money unrecovered. You can also chase a huge recovery number by throwing everything at the wall and tank your approval rate while training carriers to distrust you.

The shops that win track two numbers per job and per estimator:

• Approval rate: approved supplemented dollars divided by submitted supplemented dollars. This measures the quality of what you submit.
• Average supplement recovery per job: the actual approved supplement dollars per claim. This measures whether you are leaving money behind.

A healthy operation has both trending up at once, which only happens when you submit more legitimate, well-documented items and fewer junk ones. The rest below is how.

Why supplements get denied: the real reasons

Before building the system, understand what you are building against. Carrier desk reviewers and re-inspecting adjusters knock out supplement line items for a fairly small set of recurring reasons. Almost every one of them is preventable on your side.

The denial reasons you control

1. No documentation. The single most common. You listed a line item but provided no photo, no measurement, no code reference, nothing the reviewer can verify from an office. Unverifiable items get denied by default, because the reviewer cannot approve what they cannot see.
2. No justification for an upgrade. You added ice-and-water shield, a higher-grade ridge, additional decking, but never cited why the job requires it (code, manufacturer instruction, or an observed condition). "I always include it" is not a justification a reviewer can sign off on.
3. Pricing that does not match the carrier's database. Most carriers price against a regional estimating database. If your unit prices are materially above the prevailing regional pricing for the same line item without explanation, the reviewer adjusts them down. Fighting that with opinion instead of a documented reason loses.
4. Duplicate or already-included items. You supplemented for something the original scope already covered under a different line, or you double-listed. This reads as sloppy or padded and it poisons the reviewer's trust in the rest.
5. Items that are genuinely optional or cosmetic, dressed as required. Upgrading to a premium shingle the homeowner wants is not a supplement; it is a homeowner upgrade they pay for. Listing it as required gets it struck and damages credibility.
6. Vague, non-specific line descriptions. "Misc. roofing labor," "additional materials," "extra flashing as needed." A reviewer cannot approve a number attached to a shrug.
7. Math and measurement errors. Squares that do not reconcile with the diagram, waste factors that look invented, quantities that exceed the roof area. Errors anywhere make the reviewer distrust everywhere.

The denial reasons that are coverage, not supplement

Some "denied supplements" were never winnable as supplements because they are coverage decisions:

• A policy roof payment schedule or ACV roof endorsement that caps the roof payout regardless of scope. No line item overcomes a policy term.
• A cosmetic damage exclusion on the policy. If the endorsement is there, the carrier has a contractual basis, and your path is proving functional (not cosmetic) damage at the inspection stage, not supplementing later.
• The deductible, which is the homeowner's money and obligation, period. You never touch, waive, rebate, absorb, or "work with them on" the deductible. In many states that is insurance fraud and it has ended roofing companies.

Knowing which bucket a denial falls in keeps you from burning effort re-submitting a supplement against a policy term that no amount of documentation will move, and from accidentally crossing into coverage advocacy that is not your job.

The foundation: a supplement is only as strong as the original inspection

Here is the truth that the supplement-software vendors will not lead with: most supplements are won or lost days before anyone writes one, at your inspection. If your field documentation is thin, no clever line-item list saves the supplement. If your documentation is airtight, half your supplement writes itself because the evidence is already sitting in the file.

A supplement-ready inspection captures, on every job:

• Accurate measurements and a roof diagram. Squares per slope, pitch, ridge and hip linear footage, valley footage, eave and rake footage, number of penetrations, layers, and ventilation count. Most supplements are scope and quantity corrections; you cannot correct a quantity you never measured.
• Per-component condition photos. Not only the field shingles, but every component. Photograph the flashing, the pipe boots, the drip edge (or its absence), the valley metal, the ridge, the decking where visible, the ventilation, the gutters, and the soft-metal collateral. Every one of these is a potential supplement line, and each needs a before-photo to justify replacement.
• Decking and substrate notes. Whether you can see deck condition, spacing, prior repairs, or fastening problems that will surface at tear-off. Decking and re-decking are among the most-supplemented and most-denied items precisely because they are under-documented.
• Code-relevant conditions. Missing drip edge, no ice-and-water in a climate that requires it, inadequate ventilation, multiple layers, a deck that will not meet current fastening spec. Photograph each, because each is a code-driven supplement waiting to be justified.
• The dated storm and event context where the loss is storm-related: the date of loss, the warning and reported hail size, and a sense of whether this specific roof actually sat in the damaging part of the event. This is corroborating context for why the claim exists, not proof of any individual line item, and you never present it as proof of loss.

Walk a roof once with this list and you will see that a clean supplement is mostly assembled in the field, not invented at a desk. The estimator's job becomes translating documented conditions into correctly-priced, code-cited line items, which is exactly the kind of supplement that gets approved.

A field-capture checklist your crews can run

• Full measurements and diagram (slopes, pitch, ridge/hip, valley, eave/rake, penetrations, layers)
• Wide, mid, and macro photos of every roof component, captioned with location
• Drip edge present/absent at eaves and rakes (photographed)
• Ice-and-water present/absent at eaves and valleys (photographed)
• Ventilation type and count, with condition
• Visible decking condition, spacing, prior repairs
• Flashing, valleys, pipe boots, counterflashing condition
• Number of existing layers (governs tear-off vs. overlay)
• Soft-metal collateral and storm-facing slope emphasis (storm claims)
• Date of loss confirmed and event context recorded

The supplement line items that get approved (and how to justify each)

This is the operational core. The following are the line items that legitimately recover the most money on roofing supplements, organized by the justification that makes each one approvable. The pattern is always the same: an observed condition or a code/manufacturer requirement, backed by a photo or measurement, expressed as a specific line item at regional pricing.

Nothing below is a trick. Every item is something the job genuinely requires that the original adjuster scope routinely misses, usually because the adjuster spent eleven minutes on the roof and could not see what tear-off would reveal.

Code-driven items (the most defensible category)

Code upgrades are the strongest supplements you can write because the justification is not your opinion, it is the building code the jurisdiction enforces. A reviewer who strikes a properly-cited code item is overruling the building department, which they are reluctant to do when the citation is specific.

The operating rule: cite the specific section, not "code requires it." "Per IRC R905.2.8.5 and the [jurisdiction] amendment, ice barrier is required at eaves" is approvable. "Code stuff" is not. Pull the actual adopted code for the jurisdiction (the state or local amendments to the International Residential Code), and keep the citations in a reusable reference so estimators are not re-researching each time.

Manufacturer-requirement items

Nearly as strong as code: items required by the shingle or accessory manufacturer's published installation instructions, because failing to follow them voids the warranty. A reviewer understands that a roof built outside the manufacturer's spec is a defective roof.

• Starter strip (manufacturer-required, not field shingles cut down) at eaves and often rakes.
• Specified underlayment type and coverage where the manufacturer's instructions or warranty require it.
• Ridge cap that is the manufacturer's hip-and-ridge product, not three-tab cut up, where the system requires it.
• Ventilation balance the manufacturer specifies for warranty validity.
• Fastener type, count, and placement per the manufacturer's wind-rating requirements.

Attach the manufacturer's published installation instruction page for each. These are public documents; keep a folder of them per product line you install.

Access, detach-and-reset, and labor-reality items

These are the items adjusters under-scope because they cannot see them from a quick look or do not think about real-jobsite labor.

• Detach and reset of items that must come off and go back on: satellite dishes, solar attachments (with appropriate licensed handling), gutters where they obstruct the eave, antennas, lightning protection.
• Steep / high charges where pitch or height genuinely require them, backed by your measured pitch and story count.
• Multiple-layer tear-off labor when more than one layer exists (measured and photographed).
• Flashing and counterflashing at walls and chimneys that must be replaced rather than reused.
• Pipe boots, vents, and accessories that are not reusable once the roof is removed.
• Disposal / dumpster sized to the actual tear-off, including extra layers.

Each of these needs the same backing: a photo or a measurement that establishes the condition or quantity. "Steep charge because the roof is steep" loses; "steep charge, measured 10/12 pitch, see pitch photo" wins.

Pricing-correction items

Sometimes the line item is in the scope but priced below what the work actually costs in your region. This is the trickiest category and the easiest to lose, because it can read as "I want more money." The discipline:

• Price against the same regional database structure the carrier uses, and only flag genuine, documentable gaps.
• When a price truly does not reflect local cost, justify it with a concrete, current basis (a documented material invoice or quote for that specific item), not an assertion.
• Do not pad. A reviewer who catches one padded price re-scrutinizes every number you submitted, which lowers your approval rate across the whole packet and on future jobs.

How to write the supplement so a reviewer approves it fast

The person approving your supplement is usually a desk reviewer or a re-inspecting adjuster who was never on the roof, is working a stack of files, and has to be able to justify every approval they grant up their own chain. Write for that person. Make approving you the path of least resistance.

The structure of a clean supplement packet

1. A short cover summary. Claim number, date of loss, property, and a two- or three-sentence statement of what the supplement corrects and why ("the approved scope omits code-required drip edge and ice barrier, under-counts decking, and prices starter at a cut-shingle rate; documentation and code citations attached"). Tight and factual.
2. An itemized line-item list, each line specific, each tied to its justification, each priced to the regional database. No "misc." lines.
3. A justification per line. Code section, manufacturer instruction page, or the observed condition with the photo reference number.
4. Labeled, organized photos. Captioned with location and what they prove, numbered so the line items can reference them.
5. The measurements / diagram the quantities derive from, so the reviewer can reconcile squares and footages.
6. The estimate itself, clean and reconciled.

The whole packet should let a reviewer verify each item without picking up the phone. Every phone call you force is a delay and a chance for a no.

Writing rules that move approval rate

• One line, one justification, one proof. If you cannot name the code section, manufacturer requirement, or photographed condition that backs a line, do not submit that line. This single rule does more for approval rate than anything else.
• Be specific in descriptions. "R&R drip edge, aluminum, eaves and rakes, 210 LF per diagram" beats "drip edge as needed."
• Reconcile every quantity to the diagram. If your squares, ridge footage, and valley footage do not add up to the measured roof, fix it before submitting. Math errors cost you credibility on the correct items.
• Lead with the strongest, most defensible items (code and manufacturer) so the reviewer's first impression of the packet is rock-solid.
• Keep it focused. A tight packet of twelve airtight items beats a forty-item dump where the reviewer has to wade through six junk lines to find the good ones. The junk lines actively lower the approval odds of the good ones.
• Submit it through the homeowner's claim properly. The supplement is part of the claim the homeowner owns. You provide the documentation and estimate; the request flows through the claim. You are correcting your scope, not negotiating the homeowner's coverage.
• Mirror the carrier's format. Use the same estimating platform and structure the carrier uses so line items map cleanly and the reviewer is not translating your format into theirs.

A worked example: a $4,200 supplement that clears on the first pass

A 28-square hip roof, hail claim, dated and confirmed event. The IA approved a tear-off and re-roof but wrote a thin scope: field shingles, basic underlayment, and a flat allowance for accessories. Here is how a disciplined estimator turns the under-scope into an approvable supplement.

Observed and documented at inspection:

• No existing drip edge at eaves or rakes (photographed).
• No ice-and-water at eaves in a jurisdiction whose amendment requires it (photographed underlayment).
• Starter was original field-shingle cut-downs; manufacturer requires a starter product.
• Ridge was three-tab cut up; the system shingle requires the manufacturer's hip-and-ridge.
• Two existing layers (photographed at a lifted edge), so the disposal and tear-off labor in the scope under-counted.
• Three pipe boots and two box vents, not reusable.

The supplement, each line backed:

No padding, no vague labor lines, no overhead-and-profit grab, nothing touching coverage or the deductible. Every line maps to a photo or a code/manufacturer page, every quantity reconciles to the diagram. A reviewer can approve all of it from the desk in minutes because there is nothing to question and nothing to call about. That is what an 85-percent-approval packet looks like: boring, specific, and impossible to argue with.

Where RoofPredict fits, honestly

Most of what raises a supplement approval rate is the documentation discipline above, plus one thing that happens even earlier: only carrying claims on roofs that genuinely qualify in the first place. A supplement on a roof that should never have been filed is a fight you do not win, and it drags your approval rate and your reputation with the local adjuster pool down with it. The front-end targeting is where RoofPredict fits, and it is worth being precise about what it does and does not do, because overstating it would be the fastest way to get a contractor in trouble.

RoofPredict gives you two things per address before anyone climbs a ladder. First, a roof-age estimate expressed as a range (for example, a roof that reads as roughly 17 to 23 years old), derived from aerial imagery over time. Second, storm modeling at the level of the individual roof rather than the ZIP or county: it models hail and wind physics per roof to estimate which specific roofs in a storm's path most likely took meaningful impact, instead of only showing where the storm passed. A hail map tells you where it hailed; the per-roof modeling estimates which roofs the storm most likely wore out.

Where that helps the supplement side of the business:

• It concentrates your claims on roofs that genuinely qualify. Ranking doors by age range and per-roof storm exposure means your reps inspect the roofs most likely to have real, documentable functional damage, so the claims you carry into the supplement stage are the strong ones. The cleanest way to keep approval rate high is to never file the weak claims.
• The age range corroborates context. A defensible age range supports the picture that a roof was at a vulnerable age, which strengthens the legitimacy of a storm claim that your physical inspection documents. It supports the documentation; it never replaces it.
• It enriches your own list, not a bought lead. RoofPredict appends roof-age and storm signals to a contractor's own CRM or mailing list and ranks routes; it is not a lead-buying service and it does not file or handle anything.

Now the honest limits, because they matter and because pretending otherwise crosses lines:

• The age output is a range, not a date, and the storm modeling is odds, not proof. Neither is evidence of damage on a specific roof, and neither belongs in a supplement as a line-item justification. You justify line items with code sections, manufacturer instructions, and photographed conditions, never with a model. Presenting modeled data as proof of loss is exactly the kind of overstatement that gets claims and contractors in trouble.
• It does not write, file, negotiate, or approve any supplement or claim, and neither do you in the negotiating sense. It is front-of-funnel targeting and list enrichment. The homeowner owns the claim; the carrier decides coverage.
• It does not replace the inspection. It tells you which roofs are worth the ladder; your chalk, camera, measurements, and code knowledge build the supplement.

Used that way, the data does the part it is good at (pointing your crews at the roofs most likely to verify and to qualify) and your documentation does the part only documentation can do (justifying every supplemented line). That division is also what keeps everything inside the contractor lane.

Building a supplement system that scales

A single well-written supplement is a skill. A consistently high approval rate across a whole company is a system. The shops that recover the most, on the most jobs, with the least friction, build the following.

Standardize the line-item library

Maintain a living reference of your common supplement line items, each with its standard justification text, the code section or manufacturer instruction that backs it, and the proof a field rep needs to capture. When an estimator writes a supplement, they are assembling from vetted, pre-justified components rather than re-researching the IRC every time. This both speeds writing and raises consistency, which raises approval rate.

For each library entry, store:

• The exact line description and unit.
• The justification category (code, manufacturer, observed condition, pricing).
• The specific citation (code section number, manufacturer instruction reference).
• The field proof required to use it (which photos and measurements).
• Notes on which carriers or jurisdictions push back, and what resolved it.

Build the code reference per jurisdiction

Code adoption varies by state and locality. Build and maintain a per-jurisdiction reference of the adopted code edition and the local amendments that matter for roofing (drip edge, ice barrier triggers, layer limits, ventilation, fastening). When you cite the exact adopted section for that jurisdiction, code supplements approve cleanly. When you cite generic "IRC" without the local adoption, reviewers in jurisdictions with amendments push back.

Separate the roles cleanly

In a scaled operation, the field rep documents, a dedicated estimator/supplementer writes, and a reviewer checks before submission. The field rep is trained on exactly what to capture (the checklist above). The estimator writes from the library. A second set of eyes catches math errors, duplicate items, and any line that lacks proof before it ever reaches the carrier. That internal review is the cheapest approval-rate gain available, because the items most likely to get denied are the ones a teammate would have flagged in thirty seconds.

Track the metrics and feed them back

Log, per supplement: submitted dollars, approved dollars, which line items were denied, and the stated reason. Review denials monthly. Patterns emerge fast: a particular line item that keeps getting denied for weak justification, a particular estimator who pads pricing, a jurisdiction where your code citations are wrong. Each pattern is a fixable process gap. Approval rate is a measured, managed number, not a vibe.

Train against the do-not-say list

Every person who touches a claim, from the canvasser to the estimator, gets trained on the lane. This is compliance, and it protects the business more than any single supplement.

The do-not-say / do-not-do list, taught explicitly:

• Do not offer to "handle," "negotiate," "fight," "work," or "manage" the insurance claim. You document and estimate; the homeowner files and owns it.
• Do not promise an approval, a specific payout, or a settlement amount. You cannot control the carrier's decision and promising one is both unkeepable and, in some framings, deceptive.
• Do not do anything with the deductible: not waive, not rebate, not absorb, not "eat," not "help with." In many states this is insurance fraud and it has put roofers out of business.
• Do not advertise or imply a "free roof" or "no out-of-pocket." The deductible is the homeowner's obligation.
• Do not interpret the homeowner's policy or coverage for them. Recognize coverage terms so you know which battles are winnable, but do not advise the homeowner on their policy.
• Do not represent the homeowner against their insurer. That is public adjusting, and it requires a license you almost certainly do not hold.
• Do not call modeled storm or age data "proof" of damage. It is context and targeting, never evidence of loss on a specific roof.

The safe frame, said out loud to homeowners early: "I inspect and document the condition of your roof and give you an accurate estimate for the repair. You file and own the claim with your insurer, and your insurer decides coverage. If the approved scope is missing things the job actually needs to be built to code, I supplement those items with documentation. If you want someone to represent you to the carrier, that is what a licensed public adjuster is for." That sentence keeps the homeowner's expectations and your role correctly aligned and keeps you out of trouble.

The mistakes that quietly tank a supplement approval rate

Even good shops bleed approval rate in predictable ways. These are the ones that cost the most.

Submitting unjustified items to "see what sticks"

Throwing extra line items at the wall feels like upside, but it is the single fastest way to lower your approval rate and, worse, to train carriers to scrutinize your whole packet. A reviewer who strikes three junk items starts second-guessing your nine good ones. Submit only what you can back. The discipline to leave a marginal line out of the packet protects the strong lines around it.

Thin or disorganized documentation

The item might be legitimate, but if the photo is blurry, uncaptioned, or missing, the reviewer cannot verify it and defaults to no. Document like a desk reviewer in an office will evaluate it weeks from now without ever having seen the roof, because that is exactly what happens.

Citing "code" without a section

Generic code references get pushed back; specific, adopted-section citations get approved. The difference is a few minutes of building a jurisdiction reference once, versus losing the same legitimate code supplements over and over.

Pricing above the database without basis

Prices materially above the regional database with no documented reason get cut and make the reviewer distrust your numbers. When a price is genuinely justified, attach the concrete basis. When it is not, price to the database.

Misclassifying a coverage dispute as a supplement

Re-submitting a supplement against a policy term (a roof payment schedule, a cosmetic exclusion) that no scope correction can move wastes everyone's time and dings your relationship with the carrier. Recognize coverage terms and stop supplementing against them.

Letting the homeowner think you are running their claim

The moment a homeowner believes you will "handle the insurance," you have set an expectation you cannot legally meet and invited a complaint when it does not go their way. Set the role straight at the first conversation and keep it there.

Crossing the UPPA / deductible line

This is the one that ends businesses, not claims. Negotiating the claim, promising approval or payout, advertising a free roof, or doing anything with the deductible can constitute unlicensed public adjusting and, with the deductible, insurance fraud, in many states. Courts have treated even labeling yourself a claims specialist as a public-adjusting violation. Stay the documentation-and-estimate expert. Let the homeowner own and file the claim, the carrier decide coverage, and a licensed public adjuster or counsel represent the homeowner if they choose.

Carrier behavior, timing, and the re-supplement loop

Approval rate is not only about what you submit; it is shaped by how carriers process supplements and how you handle the back-and-forth. Understanding the rhythm keeps you from losing legitimate dollars to fatigue or a missed reply.

How supplements actually get processed

When your packet reaches the carrier, it usually does not go back to the original field adjuster. It lands with a desk reviewer or a claims handler who evaluates it against the file and the carrier's pricing database. That person approves the items they can verify and justify up their chain, partially approves some, and denies the rest with a stated reason. You then get a revised estimate showing what moved and what did not.

Two practical consequences follow. First, the reviewer is paper-bound: they live and die by what is in the file, which is exactly why the self-verifying packet wins, you are handing them everything they need to say yes without leaving their desk. Second, a partial approval is normal and expected, not a failure. The question is whether the denied items were denied for a fixable reason (weak documentation, missing citation) or an unfixable one (a policy term, or an item that was never justified).

Reading the revised estimate and deciding whether to re-supplement

When the revised estimate comes back, do not reflexively re-fire the denied items. Triage them:

• Denied for fixable reasons (no photo attached, generic code reference, quantity did not reconcile): correct the defect and re-submit only those items, with the fix obvious. A second pass that supplies the missing proof for a legitimate item has a high success rate, because you are removing the exact reason given.
• Denied as a coverage term (roof payment schedule, cosmetic exclusion, deductible): stop. No scope correction moves a policy term, and re-submitting wastes the relationship.
• Denied because they were never justified in the first place: let them go, and learn the lesson, that item should not have been in the packet. Re-submitting an unbacked item a second time just confirms to the reviewer that your packets need scrutiny.

The discipline of re-submitting only the fixable, legitimately-backed items, with the defect cleanly corrected, is what separates a second pass that recovers money from one that annoys the carrier and lowers your standing for the next claim.

Timing and the homeowner's patience

Supplement review takes time, sometimes a week, sometimes several, and a homeowner left in silence assumes the worst. Keep them informed without ever stepping into running their claim: a short, honest update that the revised estimate came back, what was approved, and that you are re-submitting two items with corrected documentation keeps them steady and keeps your name attached to competence rather than silence. You are reporting on your scope work, not negotiating their coverage.

One timing trap to avoid: many policies hold recoverable depreciation until the work is completed and invoiced. A homeowner looking at an ACV check may think the claim was "shorted" when the depreciation is simply being held back until completion. Recognizing this stops you from chasing a "missing" amount that is not a supplement issue at all, and stops the homeowner from panicking over a number that is working exactly as the policy intends.

Estimating-platform discipline that protects your numbers

The estimating platform is where your supplement either reconciles cleanly or trips over itself. A few habits inside the software protect your approval rate more than any single line item.

• Build from an accurate diagram, not a guess. Quantities that derive from a measured roof diagram reconcile; quantities pulled from memory create the math errors that make reviewers distrust the whole packet. Measure once, accurately, and let every line draw from it.
• Use the carrier's pricing structure and region. Pricing against the same regional database the carrier uses means most of your unit prices already match, so the only prices a reviewer questions are the genuinely-flagged ones you have documented. Pricing in a different structure forces the reviewer to translate, which invites adjustments.
• Keep waste factors defensible. A waste factor that reflects the actual roof geometry (hips, valleys, cut-up planes) holds up; an inflated blanket waste percentage gets trimmed and casts doubt on your other quantities. Tie waste to the diagram, not to habit.
• Avoid the catch-all line. A single large "miscellaneous" or "additional labor" line is the easiest thing in any estimate to deny, because it cannot be verified. Break it into specific, named, quantified items, each with its own backing.
• Reconcile before you export. Squares, ridge and hip footage, valley footage, eave and rake footage, and penetration counts should all tie back to the diagram before the packet leaves your office. A thirty-second reconciliation pass catches the errors that would otherwise cost you credibility on correct items.

None of this is glamorous, and that is the point. A supplement that reconciles to a measured diagram, prices to the regional database, and contains no catch-all lines is one a reviewer has almost nothing to push back on, which is the entire mechanism behind a high approval rate.

A pre-submission checklist you can hand to an estimator

Compress the whole system into something a supplementer runs before every packet goes out.

Documentation:

• Every line item has a photo, measurement, code section, or manufacturer instruction backing it
• Photos are captioned with location and numbered for line-item reference
• Measurements and diagram reconcile to the supplemented quantities

Line items:

• No vague descriptions ("misc.," "as needed," "additional")
• No duplicates or items already in the approved scope
• No optional/cosmetic homeowner upgrades dressed as required
• Strongest code and manufacturer items lead the packet
• Pricing matches the regional database, or has a documented basis attached

Code and manufacturer:

• Each code item cites the specific adopted section for this jurisdiction
• Each manufacturer item attaches the relevant install-instruction page

Lane discipline:

• The supplement corrects scope and quantity only, not coverage
• Nothing in the packet negotiates the claim, promises a payout, or touches the deductible
• No modeled age or storm data presented as proof of loss
• The supplement flows through the claim the homeowner owns

Internal review:

• A second person has checked math, duplicates, and unbacked items before submission
• Logged for tracking: submitted dollars, and later, approved dollars and denial reasons

Putting it together

A roofing supplement approval rate is not a number that happens to you; it is a number you engineer. You engineer it at the inspection, by documenting every component thoroughly enough that the supplement mostly writes itself. You engineer it in the writing, by attaching a code section, a manufacturer instruction, or a photographed condition to every single line, pricing to the regional database, and cutting anything you cannot back. You engineer it in the format, by handing the desk reviewer a tight, organized, self-verifying packet that makes approval the easy choice. And you engineer it in the system, by standardizing the line-item library, building per-jurisdiction code references, separating the field and estimating roles, and tracking denials until the patterns disappear.

The two highest-leverage moves are the simplest to state. First, only carry claims on roofs that genuinely qualify, so the supplements you write are on strong claims, which is where targeting the right roofs up front by age range and per-roof storm exposure earns its keep. Second, never submit a line you cannot prove, because the junk items are not only denied themselves, they lower the approval odds of every legitimate item around them and spend your credibility with the carrier.

Do all of that while staying strictly in the contractor lane, inspect, document, estimate, supplement to code, and let the homeowner own and file the claim and the carrier decide coverage, and your approval rate climbs because you have made approving you the path of least resistance. That reputation, the contractor whose supplements are documented right and whose word holds up, is the real asset. It is built one boring, specific, impossible-to-argue-with packet at a time.

FAQ

What is a good roofing supplement approval rate?

There is no single official benchmark, but the practical gap is wide: shops that submit unjustified items see roughly 40 to 50 percent of supplemented dollars approved, while disciplined operations that back every line with a photo, measurement, code section, or manufacturer instruction commonly clear 80 percent or more on the first submission. The difference is almost never a friendlier carrier; it is process. Track two numbers together, approval rate (approved dollars divided by submitted dollars) and average recovery per job, because you can game either one alone. Healthy operations push both up at once by submitting more legitimate items and fewer junk ones.

Why do roofing supplements get denied?

The most common reasons are all on the contractor's side and all preventable: no documentation to verify the item, no justification for an upgrade (no code section or manufacturer requirement cited), pricing above the regional database with no documented basis, duplicate items already in the approved scope, optional or cosmetic items dressed as required, vague descriptions like 'misc. labor,' and math or measurement errors that make the reviewer distrust everything. A separate bucket of denials are actually coverage decisions, not supplement problems: a policy roof payment schedule, a cosmetic damage exclusion, or anything touching the deductible. No line item overcomes a policy term, so recognizing which bucket a denial falls in saves wasted re-submissions.

How do I justify a code upgrade on a roofing supplement?

Cite the specific adopted code section for that jurisdiction, not 'code requires it.' For example, reference the exact International Residential Code section and the local amendment that requires ice barrier at eaves, and attach a photo showing the existing underlayment lacks it. Code supplements are the strongest you can write because the justification is the building code the jurisdiction enforces, not your opinion, so a reviewer who strikes a properly-cited code item is overruling the building department. Build and maintain a per-jurisdiction reference of the adopted code edition and the amendments that matter for roofing (drip edge, ice barrier, layer limits, ventilation, fastening) so estimators cite the right section every time.

What line items should I supplement on a roofing claim?

Supplement only what the job genuinely requires that the adjuster scope missed, organized by justification: code-driven items (drip edge, ice-and-water shield, decking to fastening spec, tear-off where overlay is prohibited, ventilation, valley and step flashing), manufacturer-required items (starter strip, specified underlayment, manufacturer ridge cap, fastener type and count), access and labor-reality items (detach-and-reset, justified steep and high charges, multiple-layer tear-off, non-reusable boots and vents, correctly-sized disposal), and genuine pricing corrections backed by a documented basis. Each line needs a photo, measurement, code section, or manufacturer instruction attached. Anything you cannot back should be left out of the packet entirely.

How do I write a roofing supplement so it gets approved faster?

Write for the desk reviewer who was never on the roof and is working a stack of files. Lead with a short factual cover summary of what the supplement corrects and why, then an itemized list where every line has one specific description, one justification (code section, manufacturer instruction, or photographed condition), and one proof reference. Attach labeled, numbered photos and the measurements the quantities derive from so the reviewer can verify each item without a phone call. Mirror the carrier's estimating format, lead with your strongest code and manufacturer items, reconcile every quantity to the diagram, and keep it focused. A tight twelve-item packet of airtight lines beats a forty-item dump.

Can I supplement for decking replacement?

Yes, when the existing deck genuinely will not meet current code once the old roof is off, for example because the spacing or fastening will not pass the applicable sheathing requirement, or when the deck is deteriorated. Decking is among the most-supplemented and most-denied items precisely because it is under-documented. To get it approved, photograph the visible deck condition and spacing at inspection, note prior repairs, cite the specific code provision that the deck must meet once exposed, and reconcile the quantity to your diagram. A decking supplement with photos and a code citation approves; one with neither gets denied as unverifiable.

Is a higher-grade or premium shingle a valid supplement?

No, not if the homeowner simply wants a nicer shingle. That is a homeowner upgrade they pay for out of pocket, not a required scope correction, and listing it as required gets it struck and damages your credibility on the rest of the packet. Supplements correct scope and quantity that the job genuinely requires to be built to code and manufacturer specification. The exception is when a manufacturer system or a matching requirement legitimately drives a component (for example, the manufacturer's required hip-and-ridge product rather than cut three-tab), which is a requirement, not a preference, and is documented as such.

How is a supplement different from disputing a denial?

A supplement assumes coverage already exists and corrects the amount and scope of approved work, which is squarely the contractor's lane because you are the one who has to build the roof to code. Disputing a denial is a coverage question, whether the peril is covered, whether the damage is storm versus wear, whether the date of loss is right, which is largely the homeowner's and their carrier's matter, supported by your documentation but not run by you. Most denied supplements get denied because they smell like a coverage fight or a money grab rather than a clean, evidence-backed scope correction. Keep your supplements firmly in the scope-correction category.

Can I waive or help with the homeowner's deductible to win the job?

No. Never waive, rebate, absorb, 'eat,' or 'help with' the deductible, and never advertise or imply a free roof or no out-of-pocket. The deductible is the homeowner's money and obligation, and in many states doing anything with it is insurance fraud that has put roofing companies out of business. This is part of the broader lane discipline: you inspect, document, estimate, and supplement to code; the homeowner files and owns the claim; the carrier decides coverage. Negotiating the claim, promising a payout or approval, or touching the deductible can constitute unlicensed public adjusting and fraud. If a homeowner wants representation against their insurer, that is what a licensed public adjuster is for.

Does roof age or storm data help get a supplement approved?

Not as a line-item justification. Modeled roof-age ranges and per-roof storm modeling are useful for targeting which roofs to inspect and for corroborating why a claim exists, but a roof-age range is a range, not a date, and storm modeling is odds, not proof. Neither is evidence of damage on a specific roof, and neither belongs in a supplement as justification. You justify supplemented line items with code sections, manufacturer installation instructions, and photographed conditions, full stop. The main value of good front-end targeting is that it concentrates your claims on roofs that genuinely qualify, so the supplements you write are on strong claims, which is how you keep your approval rate high.