Why Supplements Get Rejected (and How to Avoid It): A Roofer's Documentation Playbook

You wrote a clean estimate, the homeowner filed, and the carrier paid the original scope. Then you sent a supplement for the items the first estimate missed, and it came back denied, partially paid, or sitting in limbo for three weeks while your crew is already on the next job. If that pattern feels familiar, you are not unlucky. You are running into the same six or seven failure points that sink most supplements, and almost all of them trace back to one thing: the documentation didn't carry the weight the estimate was asking it to carry.

Before going further, a line that matters legally and that every reputable shop should internalize. A roofing contractor can inspect a roof, document conditions, and write an accurate repair estimate for the work they intend to perform. You can state facts about your own scope to a carrier. What you cannot do, unless you hold a public adjuster license, is negotiate or "handle" the claim on the homeowner's behalf, interpret their policy or coverage, promise a specific approval or payout, tell anyone their deductible is waived, or advertise a free roof. Those acts are unlicensed public adjusting in most states and they will get you fined, sued, or both. The homeowner files. The insurer decides coverage. Your job is to document thoroughly and write a defensible estimate. Everything below lives strictly on that document-and-estimate side, because that is the side where you actually have leverage and where supplements are won or lost.

With that framing set, let's get into why supplements get rejected and exactly how to keep yours from joining the pile.

What a supplement actually is (and why the framing changes everything)

A supplement is not a second bite at the apple. It is a correction to an incomplete scope. The original estimate, whether the carrier's desk adjuster or field adjuster wrote it, captured a slice of the real work. A supplement adds the line items that the first pass missed, mispriced, or under-quantified, supported by documentation that proves those items belong.

The psychology of the reviewer matters here. The person reading your supplement is not looking for reasons to pay. They are looking for reasons not to. Every line you add is a small claim that has to stand on its own evidence. If a line item can be questioned, it will be. The supplements that get paid are the ones where the reviewer reads the line, looks at the photo, checks the measurement, sees the code citation, and has nothing left to push back on. The supplements that get rejected are the ones that ask the reviewer to take your word for it.

So reframe the whole exercise. You are not "asking for more money." You are submitting a documented correction with evidence attached to every claim. That reframe drives every habit below.

The cost of a sloppy supplement

Think about what a bounced supplement actually costs you. Say your average supplement adds $2,800 in legitimate scope. If your approval rate is 55 percent and you submit 40 supplements a month, you are leaving roughly $50,000 a month on the table compared to a shop running at 90 percent. Across a year that is the difference between a healthy margin and a thin one. None of that money is extra. It is work you are already doing or already accounting for, simply not getting paid for because the paper didn't hold.

The other cost is time. A supplement that gets kicked back triggers a re-inspection request, a phone queue, a re-submission, and a follow-up cycle that can eat two to four weeks. Multiply that across a storm season and your office is drowning in rework instead of closing files. Clean supplements are about more than revenue. They are about cycle time and the sanity of whoever runs your estimating desk.

The seven reasons supplements actually get rejected

Most denials are not mysterious. They cluster into a short list of repeatable failures. Learn to recognize them and you can pre-empt them before you ever hit submit.

1. The photo doesn't prove the line item

This is the single biggest killer. You add a line for a damaged item, but the photo attached to it is a wide shot of the whole roof slope, or it's blurry, or it has no scale reference, or it simply doesn't show the thing you're claiming. The reviewer cannot connect the dollar amount to a visible condition, so they deny it. A line item without a photo that unambiguously shows the condition is a guess, and guesses get denied.

2. The measurement doesn't match the report

You claimed 34 squares but your measurement report says 31.2. You billed for 180 feet of ridge but the report shows 156. The moment a reviewer catches one number that doesn't reconcile, they start distrusting every number, and the whole supplement slows down. Quantity mismatches are an instant credibility hit.

3. The line item is missing a required code citation

Many of the items that drive real supplement dollars, drip edge, ice-and-water shield, ventilation, decking, and so on, are tied to building code requirements. If you add a code-driven item but don't cite the specific code section that requires it for that jurisdiction, the reviewer has no basis to approve it and will deny or hold it. "It's code" is not a citation. The section number is.

4. The price doesn't match the carrier's pricing database

If you override a unit price above the regional pricing the carrier uses without justification, expect a kickback. Estimating platforms publish regional price lists, and reviewers compare your line against theirs. Deviations need a documented reason, like a manufacturer quote or a genuine local market condition, rather than simply a higher number.

5. The supplement contradicts the original scope

If the first estimate already paid for a tear-off of architectural shingles and your supplement assumes a different roof type or a different layer count, you've created a contradiction. Reviewers read the original first. Internal inconsistency reads as either error or padding, and both get denied.

6. The narrative is missing or generic

A supplement with no explanation forces the reviewer to reverse-engineer your reasoning. A supplement with a copy-paste narrative that doesn't reference the specific roof reads as boilerplate. Either way you've made the reviewer's job harder, and a harder job means a slower, more skeptical review.

7. It was submitted to the wrong place at the wrong time

Wrong claim number, wrong adjuster, submitted before the original was finalized, submitted after a deadline, or sent through a channel the carrier doesn't monitor. Process errors kill technically perfect supplements all the time. The work was right; the routing was wrong.

Notice that not one of these is "the carrier is cheap." Carriers underpay, sure. But the rejections you control are documentation and process failures, and those are the ones worth fixing because they are entirely in your hands.

How to tell a real denial from a soft denial

Not every "no" is final, and reading the response correctly saves you weeks of wasted effort. There are three flavors of pushback, and each one calls for a different move.

A hard denial says the item is not covered or not part of the loss. That is a coverage decision, and coverage is the carrier's call, not yours. You do not argue coverage; you document conditions. If the denial rests on a factual error about what is on the roof, you correct the facts with evidence and resubmit the documentation. If it rests on an actual coverage position, that is between the homeowner and the carrier.

A soft denial is really a request for more information dressed up as a no. "Insufficient documentation to support this line" is not the carrier saying the work is wrong; it is the carrier saying you didn't prove it. That is the most common kind, and it is the easiest to flip, because the fix is a better photo, a reconciled quantity, or a code citation you left off the first time.

A short-pay approves the item but at a lower quantity or price than you submitted. Read the line that was paid against the line you submitted, find the specific number they changed, and supply the document that supports your number, usually the measurement report for a quantity or a quote for a price.

The discipline is to read the actual response language before you react. A shop that treats every kickback as a fight wastes energy on hard denials it can't move and under-responds to soft denials it could flip with a single photo. Sort the response first, then respond to what it actually says.

A quick diagnostic: which failure is yours?

When a supplement bounces, run it against this short diagnostic before you resubmit. It tells you which of the seven failures you hit so you fix the right thing.

Most shops skip this step and resubmit the same paper that got denied the first time, which is why the second submission usually dies the same way. Diagnose, then resubmit only the thing that was actually missing.

The documentation system that makes supplements stick

The fix for almost every rejection above is a documentation discipline that you run the same way on every single roof, whether or not you think you'll need a supplement. The shops with 90-percent-plus approval rates do not document reactively. They capture everything up front so that when a supplement is warranted, the evidence already exists. You cannot go back and re-photograph a roof after the crew has torn it off.

Here is the system, broken into the four capture phases of a job.

Phase 1: The inspection capture

This happens before you write anything. The goal is a complete visual and dimensional record of the roof as it exists, with enough rigor that someone who never set foot on the property can verify your scope.

Photo set (minimum):

• Four elevations of the house from the ground, showing the full structure and address visible where possible.
• Each roof slope, wide shot, so the reviewer can orient.
• Every area of damage, three ways: a wide shot showing where it is on the slope, a medium shot showing the damaged zone, and a tight shot showing the individual condition with a scale reference in frame.
• A chalk-circle or marker on test squares if you're documenting hail, with the marked square photographed wide and tight.
• All penetrations: pipe boots, vents, chimneys, skylights, satellite mounts. Each one, close up.
• All flashing: step, headwall, valley, drip edge condition.
• Ridge, hip, rake, and eave detail.
• The existing ventilation, counted and photographed.
• Decking condition wherever visible.
• Any pre-existing or unrelated conditions, photographed honestly. Documenting what is NOT storm-related protects your credibility on what is.

Scale references matter. A coin, a tape measure, a chalk line, an adjuster's flag, or a pen in the frame turns "that might be hail" into "that is a measurable impact mark." A tight photo with no scale is nearly worthless to a reviewer because they cannot judge size or depth.

Timestamp and geotag everything. A photo with embedded date and GPS coordinates is dramatically harder to dispute than a bare image. Most modern phones and inspection apps do this automatically; confirm it is turned on.

Phase 2: The measurement capture

Get a measurement report and treat its numbers as your single source of truth. Whether you use an aerial measurement service or a hand measurement, every quantity in your estimate and every supplement must reconcile to it. Total squares, ridge length, hip length, valley length, rake, eave, step flashing count, penetration count, and pitch all flow from here.

The discipline: if a number in your estimate does not appear in or derive from your measurement report, you cannot defend it. Reviewers love quantity disputes because they're easy wins for the carrier. Remove that opening by making every quantity traceable.

Keep the measurement report in the file and reference it in your supplement narrative by its actual values. When you write "ridge cap, 156 LF per attached measurement report," you've closed the door on the most common quantity pushback.

Phase 3: The teardown capture

This is the phase most shops skip and the one that costs them the most. Conditions that are invisible until you tear off, rotten decking, double or triple layers, deteriorated underlayment, hidden flashing failures, are exactly the conditions that justify the highest-value supplements. And they are gone forever the moment the new roof goes on.

Build teardown documentation into the crew's job, not the salesperson's. Before the crew loads the dumpster, they shoot:

• Decking condition across the whole deck, wide, with any rot, delamination, or sagging shot tight with a scale.
• The number of existing layers, photographed at a cut edge where the layers are countable.
• Underlayment condition and type.
• Any flashing or penetration condition that wasn't visible from on top of the old roof.
• Decking thickness and spacing if you'll be claiming a re-deck or re-nail to code.
• A measuring tape across replaced decking sections so the square footage of replacement is provable.

A five-minute teardown photo routine is often worth more in approved supplements than anything else on the job. Make it non-negotiable and put it in the crew's checklist with the dumpster delivery.

Worked example of teardown value. Say a tear-off reveals 8 sheets of delaminated decking that were not visible from on top of the old roof. At a typical replace-and-renail line, that is decking material, labor, and disposal across roughly 256 square feet. If the crew photographs each rotten sheet wide and tight with a tape across it, plus a photo of the deck section before and after replacement, that is a clean, provable line. If the crew doesn't photograph it, the new roof goes on, the evidence is buried, and the carrier has every reason to deny a line for work nobody can see anymore. Same labor, same material, same cost to you. The only difference is whether the camera came out before the dumpster filled up.

Who shoots what. Decide in advance whether the salesperson, the foreman, or a dedicated production person owns teardown photos, and make it the same person every time. The failure mode is everyone assuming someone else got the shot. Put a name next to "teardown photos" on the job checklist and require the photos to be uploaded before the crew leaves the site, not at the end of the week when half of them are forgotten or mislabeled.

Phase 4: The completion capture

After the work is done, photograph the finished installation, including the code-required items you're billing for: the drip edge installed, the ice-and-water shield at the eaves, the ventilation installed, the valley detail. If you're supplementing for a code item, a photo of that item correctly installed closes the loop. The reviewer can see you did the work the code requires, which makes paying for it the path of least resistance.

Code-driven line items: where the dollars and the denials both live

The biggest, most defensible supplement dollars usually come from code-required upgrades. They are also where shops get sloppiest, because they treat "it's code" as self-evident. It isn't, to a reviewer. Here's how to make code items bulletproof.

Cite the section, the jurisdiction, and the trigger

A code line item needs three things: the specific code adopted by that jurisdiction (which edition of the IRC or the state amendment), the exact section number, and the condition that triggers it. "Drip edge required per IRC R905.2.8.5" is a claim a reviewer can verify. "Drip edge per code" is not.

Different jurisdictions adopt different code editions and add their own amendments, so confirm what your specific county or city has on the books before you cite. Citing the wrong edition is as bad as citing nothing because it tells the reviewer you didn't check.

Common code-driven items and the logic behind them

Use this as a starting framework, not gospel, because adopted editions and amendments vary by state and locality. The point is the structure: every code item gets a section, a trigger, a quantity, and a photo.

The ventilation calculation that wins arguments

Ventilation supplements get denied constantly because shops claim "inadequate ventilation" without showing the math. The code generally requires a net free ventilation area of 1/150 of the attic floor area, or 1/300 when the intake-exhaust balance and vapor-barrier conditions are met. So show it.

Worked example. The attic floor area is 1,800 square feet. At the 1/300 ratio (balanced intake and exhaust), required net free area is 1,800 / 300 = 6 square feet, or 864 square inches. Split roughly half intake, half exhaust: about 432 square inches each. The existing roof has three static box vents at 50 square inches NFA each, totaling 150 square inches of exhaust, plus no functional intake. You are short by hundreds of square inches on both sides. Lay that calculation out in the narrative with the existing-vent photos, and the upgrade stops being an opinion and becomes arithmetic. Arithmetic is hard to deny.

A note on balance, because reviewers who know ventilation will check it. The 1/300 ratio only applies when intake and exhaust are reasonably balanced and the other code conditions are met; otherwise the 1/150 ratio governs and your required area doubles. Show which ratio you used and why. If you're claiming the more favorable 1/300, demonstrate the balanced intake-and-exhaust design in your scope so the number holds up. Claiming 1/300 while installing exhaust-only is the kind of internal inconsistency that gets the whole ventilation section pulled.

Decking and re-nail: the most disputed code lines

Decking replacement and deck re-nailing draw more scrutiny than almost any other code item, because they are high-dollar and because they rely on conditions the reviewer can't see for themselves. Win them with teardown evidence and a clear trigger.

For decking replacement, the trigger is a deck that is deteriorated, delaminated, or non-nailable, meaning it won't hold fasteners to manufacturer or code spec. Your evidence is teardown photos with a scale, the square footage replaced traceable to a measured area, and a note on why the existing deck failed (rot, delamination, spacing too wide for the new material). "Replaced bad decking" with no photo and no square footage is an automatic denial.

For deck re-nailing or re-fastening, the trigger is usually a local high-wind amendment that requires a specific fastening schedule when a roof is replaced. This one is purely jurisdictional: some areas mandate it, many don't. Cite the exact local amendment, not a general code section, and photograph the existing fastening pattern if you can. If your jurisdiction doesn't have the amendment, don't claim the line; an unsupportable re-nail line poisons the credibility of the legitimate lines around it.

Starter strip, ridge cap, and the "it was assumed" trap

Some of the most commonly omitted lines in carrier originals are starter strip and ridge cap shingles, because desk estimators sometimes assume they're bundled into the field shingle price when they are separate manufacturer components with their own coverage and cost. When the original omits them, the supplement is straightforward: cite the manufacturer's installation requirement that calls for dedicated starter and ridge components, give the linear footage from the measurement report, and attach the spec. "Manufacturer requires dedicated starter course and hip-and-ridge cap per installation instructions; 224 LF starter and 156 LF ridge per attached measurement report" is a clean, hard-to-deny line because it rests on the manufacturer's own document, not your opinion.

Writing the estimate so it survives review

The estimate itself, line by line, is where good documentation either gets converted into approval or thrown away. A few writing habits separate clean estimates from messy ones.

One condition, one line, one photo

Wherever practical, tie each line item to a specific documented condition and a specific photo. Avoid lumping several distinct repairs into one vague line. Granularity reads as honesty and makes partial approvals cleaner, because the reviewer can approve the lines they accept without nuking the whole thing.

Quantities reconcile to the report, always

Say it on the line: "per attached measurement report." Every quantity in the estimate should be traceable to either the measurement report or a photographed count. If you can't trace it, don't bill it until you can.

Pricing that matches the database, with documented exceptions

Use the regional price list as your baseline. When a price genuinely needs to be higher, a specialty material, a documented local labor condition, a manufacturer quote for a specific component, attach the quote or the justification right to the line. An overridden price with no backup is the fastest path to a kickback.

A real narrative, written for this roof

The supplement narrative is a short, factual explanation of why each added line belongs, referencing the specific conditions and the specific documents attached. It is not a sales pitch and it is not boilerplate. Three to six sentences per significant item, referencing the photo number and the measurement, is plenty. The narrative's job is to make the reviewer's approval the easiest action available.

Here is the difference in practice.

Weak narrative: "Adding ridge cap, drip edge, and ice and water. These are standard items that were missed. Please approve."

Strong narrative: "Adding ridge cap shingles, 156 LF, per attached measurement report page 2; original estimate omitted ridge cap entirely (see line audit). Adding drip edge at eaves and rakes, 224 LF, required per IRC R905.2.8.5 as adopted by [county]; photos 14 and 15 show no existing drip edge. Adding ice barrier at eaves, 96 LF, required per [jurisdiction] amendment; eave length per measurement report. All quantities reconcile to the attached report; installed-condition photos attached on completion."

The second one gives the reviewer nothing to push on. Every number is sourced, every code item is cited, every condition is photographed. That is what a 90-percent approval rate looks like on paper.

The line audit: how to find every missing item

The line audit is the step that turns a vague sense of "they shorted us" into a specific, defensible list of supplement lines. Done well, it is the highest-leverage 20 minutes in the whole process. Here is how to run it.

Put your complete scope and the carrier's original side by side, line by line. For each item on your scope, ask three questions. Is it on their estimate at all? If yes, is the quantity right? If the quantity is right, is the price right? Anything that fails one of those three questions is a candidate supplement line. Work top to bottom so nothing gets skipped.

The categories you'll typically find:

• Outright omissions. Items entirely absent from the original: drip edge, starter, ridge cap, ice barrier, detach-and-reset of items, code upgrades. These are usually your strongest lines because the original simply doesn't address them.
• Quantity shorts. The item is there but at a lower quantity than your measurement report supports. These resolve fast when you cite the report.
• Price shorts. The item and quantity are right but the unit price is below the regional list or below a documented cost. Address with the database value or a quote.
• Wrong assumptions. The original assumes a roof type, layer count, pitch, or access condition that doesn't match reality. These need a photo or measurement that establishes the actual condition.

Write each candidate line with its category noted, because the category tells you what evidence it needs. An omission needs proof the item belongs (code or manufacturer requirement plus a photo). A quantity short needs the measurement report. A price short needs the database value or a quote. Match the evidence to the category and you'll never submit a line you can't back.

Reading the estimating platform's report language

Most carriers run estimates through a recognized estimating platform that publishes regional price lists and flags overrides. Learn to read what that platform shows. When a line carries a note that the price was overridden, the reviewer sees it highlighted, so your justification needs to be attached right there. When a line is at the database default, it sails through. The practical takeaway: minimize unjustified overrides, attach documentation to the ones you keep, and let the database baseline carry everything it can. The fewer flags on your estimate, the faster and friendlier the review.

A repeatable supplement workflow, start to finish

Put the pieces together into a process your team runs the same way every time. Consistency is what turns one good estimator's instinct into a shop-wide approval rate that does not depend on a single person.

1. Inspect and capture fully. Run the Phase 1 photo set and pull the measurement report. Do this before you ever write a number. No exceptions, even on jobs you don't expect to supplement.
2. Write the complete scope first. Build the full, correct estimate from the measurement report and your photos, not the partial one you think the carrier will accept. You can only supplement against a complete picture of the real work.
3. Audit the carrier's original line by line. When the original estimate comes back, compare it to your complete scope item by item. Every gap, missing items, short quantities, mispriced lines, omitted code items, is a candidate supplement line.
4. Build the supplement with evidence attached to every line. For each gap: the line, the quantity sourced to the report, the price sourced to the database (or justified), the code citation where it applies, and the photo that proves the condition.
5. Capture teardown and completion photos. Phases 3 and 4 feed the supplement for anything not visible at inspection. Get them before the dumpster leaves and after the install is done.
6. Write the per-roof narrative. Short, factual, referencing the attached documents by number and the code sections by section.
7. Submit to the right place at the right time. Correct claim number, correct adjuster or supplement desk, after the original is finalized, through the channel the carrier actually monitors, before any deadline.
8. Track and follow up on a schedule. Log the submission date, set a follow-up at the carrier's stated turnaround, and have one person own the follow-up so supplements don't die in silence.

A pre-submit checklist

Run this before every supplement leaves the building.

• Every line item has a quantity that reconciles to the measurement report.
• Every code-driven line cites the specific section and the adopting jurisdiction.
• Every claimed condition has a photo that unambiguously shows it, with scale where size matters.
• Every overridden price has a documented justification attached.
• The supplement does not contradict the paid original scope.
• Teardown photos are attached for any hidden-condition line.
• The narrative references this specific roof, these photos, these measurements.
• The claim number, adjuster, and submission channel are correct.
• The original estimate is finalized and you're inside any deadline.
• A follow-up date is logged and owned.

If any box is unchecked, the supplement is not ready. A supplement that goes out incomplete doesn't only risk that line; it costs you credibility on the whole file.

Timing and routing: the boring failures that cost the most

The single most frustrating denial is the one where the work was right and the routing was wrong, because you did everything correctly on the roof and lost anyway on a clerical detail. A few rules eliminate most of these.

Submit after the original is finalized, not before. Sending a supplement while the original estimate is still in flux creates version confusion, and your supplement may be evaluated against a scope that then changes underneath it. Wait for the original to settle, then audit and supplement against the final version.

Use the right claim number and the right adjuster or desk. Storm claims get reassigned constantly. The adjuster who wrote the original may not be the one handling supplements. Confirm the current handler and the current claim number before you send, and address the submission to the channel the carrier actually monitors, whether that's a supplement desk, a portal, or a named adjuster.

Know the deadlines. Some carriers and some policies impose time limits on supplemental documentation. Find out the window for each carrier you work with and build it into your tracking so a clean supplement never dies because it arrived a day late.

Send it in a format the reviewer can actually open and verify. The estimate, the measurement report, the photo report with captions tying photos to lines, and the narrative, packaged so the reviewer can move from a line to its proof in one click. A reviewer who has to hunt for the photo that supports a line is a reviewer who denies the line.

Tracking and follow-up that actually closes files

The last failure is silence. A supplement sits in a queue, nobody follows up, and three weeks later it's stale and forgotten. Fix it with ownership and a cadence.

Log every supplement with its submission date, the carrier's stated turnaround, the claim number, the dollar amount, and the handler. Assign one person to own follow-up across all open supplements, not the salesperson who happened to write each one. Set the first follow-up at the carrier's stated turnaround and a recurring follow-up after that until the file closes. Record every contact: who you spoke to, what they said, what they committed to. A logged, dated follow-up history is also useful if a file later needs escalation, because it shows you ran a professional process rather than a series of angry phone calls.

The shops that win on supplements treat the queue like accounts receivable, because that's exactly what it is. Money you've earned, sitting in someone else's system, that closes only if somebody owns getting it closed.

The do-not-say list: staying on the right side of the line

Because supplements live next to the claim, it is easy to drift across a legal line without realizing it. Train your whole team, sales especially, on what you cannot say and do. This protects the company and it keeps your documentation clean of language that could be used against you.

Do not, for a fee or in advertising:

• Negotiate, adjust, or "handle" the claim on the homeowner's behalf. You document and estimate; the homeowner files and the carrier decides.
• Interpret the homeowner's policy or tell them what is or isn't covered. Coverage is the carrier's call, and reading policy for a fee is public adjusting.
• Promise a specific approval, payout amount, or that the claim "will go through." You can document conditions; you cannot promise outcomes.
• Tell anyone their deductible will be waived, absorbed, eaten, or made to disappear. In many states that is insurance fraud, full stop. The deductible is the homeowner's responsibility and it gets paid.
• Advertise or promise a "free roof." It invites the deductible problem above and misrepresents the transaction.
• Represent the homeowner against the insurer. That is the textbook definition of public adjusting, which requires a license you probably don't hold.

What you absolutely can do: inspect thoroughly, document conditions with photos and measurements, write an accurate repair estimate aligned to a recognized estimating standard, cite the codes that apply to your scope, and hand a clear, complete document to the homeowner so they can file. State facts about your scope to the carrier. That is the lane, and it is a wide one with plenty of room to win.

Keep this list posted where your estimators and salespeople can see it. The moment a supplement narrative starts arguing coverage instead of documenting conditions, you've left your lane, and you've handed the carrier a reason to question everything.

How the do-not-say list shows up in your paperwork

The legal line isn't only about what your salesperson says at the door; it leaks into documents, and a careless phrase in a narrative or a contract can create real exposure. Watch for it in three places.

In the supplement narrative. Keep the language factual and scope-focused. Write "the existing condition shows X; code section Y requires Z for this scope." Do not write "this should be covered" or "the policy provides for this," because those are coverage interpretations. You document conditions and cite codes; the carrier decides coverage.

In the homeowner agreement. A contract that ties the homeowner's obligation to "whatever insurance pays" or that promises to absorb the deductible is a problem in many states. The homeowner is responsible for their deductible, and your agreement should reflect a real price for real work, with the homeowner filing their own claim and deciding how to proceed.

In marketing. "Free roof," "we handle your claim," "we get your claim approved," and "no out-of-pocket" are exactly the phrases that draw regulatory attention. Market what you actually do: thorough inspection, clear documentation, an accurate repair estimate, quality installation. That's a strong, honest pitch that keeps you out of the public-adjusting and deductible-fraud zones entirely.

The through-line: your value is the quality of your documentation and your work, not your ability to influence a coverage decision you have no authority over. Selling the documentation keeps the whole operation clean.

What separates a 90-percent shop from a 55-percent shop

After looking at how high-approval shops operate versus the ones that struggle, the difference is almost never talent. It's system. The high-approval shop does five things relentlessly.

1. They document every roof completely, before they know if they'll need it. Reactive documentation is too late; the conditions are gone.
2. They reconcile every number to a measurement report. No untraceable quantities, ever.
3. They cite code with section numbers and jurisdiction, every time. "It's code" never appears in their files.
4. They write per-roof narratives, not boilerplate. Every supplement reads like it was written about that specific house, because it was.
5. They own the follow-up. One person, a logged date, a scheduled cadence. Supplements don't die in their office; they get answered.

None of that requires a bigger team. It requires a checklist that everybody runs and a culture that treats documentation as the product, not the afterthought. The estimate is downstream of the photos and the measurements. Get those right and the supplement writes itself.

Where roof-age and storm data fit before the supplement ever exists

Everything above is about winning the supplement once you're on the roof. But there's an earlier problem that quietly tanks approval rates: chasing the wrong roofs in the first place. If your crews are knocking doors on roofs that took no real storm exposure, or roofs too new to have a legitimate scope, you'll write thin estimates, fight harder for every line, and burn your documentation effort on jobs that were never strong to begin with.

This is the targeting problem, and it's where a tool like RoofPredict fits, on the document-and-estimate side, before you ever write a line. RoofPredict reads aerial imagery to give a roof-age estimate as a range per address (not an exact install date, a range, because imagery infers age, it doesn't read a receipt), and it models storm physics per individual roof so you can see which roofs in an area actually took meaningful hail or wind exposure versus which were spared. It expresses storm exposure as odds, not proof, because a model estimates likelihood; the roof itself is still the evidence you document on site.

Used honestly, that does two things for your supplement approval rate. First, it points your crews at the roofs most likely to have a real, documentable scope, the ones aging out plus the ones a storm genuinely wore, so the estimates you write start from stronger ground. Second, it lets you enrich your own CRM or mailing list with roof-age-range and storm-exposure signals so your route planning, door priority, and follow-up lists target the roofs where the work and the documentation will actually hold up.

The honest limits matter, and saying them out loud is part of staying in your lane. The age is a range, not a date. The storm exposure is a probability, not a guarantee. Neither replaces the on-roof inspection, the photos, the measurement report, or the code research. What it does is keep your team from spreading thin documentation across roofs that were never going to support a strong estimate, and concentrate that effort where it pays off. The supplement still has to be earned with evidence on the roof. Good targeting just makes sure the roof was worth climbing.

Putting it all together

Supplements get rejected for a short, predictable list of reasons: the photo doesn't prove the line, the numbers don't reconcile, the code citation is missing, the price isn't justified, the scope contradicts the original, the narrative is generic, or the submission was routed wrong. Every one of those is a documentation or process failure you control.

The fix is a system you run identically on every roof: capture a complete photo set and measurement report at inspection, document teardown conditions before the dumpster leaves, write a complete scope first and audit the carrier's original against it, attach evidence to every single line, cite code with section and jurisdiction, write a factual per-roof narrative, submit to the right place at the right time, and own the follow-up. Stay strictly on the document-and-estimate side, never drifting into negotiating the claim, interpreting coverage, promising a payout, erasing a deductible, or offering a free roof.

Do that, and your approval rate climbs because you've stopped asking reviewers to take your word for anything. You've handed them a file where every line is already proven. That's the whole game.

If the upstream targeting is also a leak, point your crews at the roofs most likely to carry a real scope before you write the first estimate. RoofPredict can tell you which roofs are due, by roof-age range and per-roof storm exposure, so your documentation effort lands where it actually converts. See how it ranks the roofs in your area at https://roofpredict.com/.

FAQ

What is the number one reason roof supplements get rejected?

Photos that don't prove the line item. When a reviewer can't connect a dollar amount to a clearly visible condition in an attached photo, they deny it. Every line should have a photo that unambiguously shows the condition you're claiming, with a scale reference where size or depth matters.

How many photos should I take to support a supplement?

Enough to document each claimed condition three ways: a wide shot showing where it is on the slope, a medium shot of the damaged zone, and a tight shot of the individual condition with a scale reference in frame. Add elevations of the house, every penetration and flashing detail, ventilation, and decking. There's no fixed number; the test is whether someone who never visited the property could verify your scope from the photos alone.

Why does a quantity mismatch tank a whole supplement?

Because the moment a reviewer catches one number that doesn't reconcile to your measurement report, they start distrusting every number. Tie every quantity to the measurement report and say so on the line, for example 'ridge cap, 156 LF per attached measurement report,' so there's nothing to dispute.

How do I cite building code correctly on a supplement line?

Provide three things: the specific code edition adopted by that jurisdiction (and any state or local amendments), the exact section number, and the condition that triggers the requirement. 'Drip edge per IRC R905.2.8.5 as adopted by the county' is verifiable. 'Drip edge per code' is not and will be denied or held.

Can a roofing contractor negotiate the insurance claim for the homeowner?

No, not unless you hold a public adjuster license. You can inspect, document conditions, write an accurate repair estimate for your scope, and state facts about that scope to the carrier. You cannot negotiate or handle the claim, interpret the policy, promise an approval or payout, waive a deductible, or represent the homeowner against the insurer. Those acts are unlicensed public adjusting in most states.

How do I justify a ventilation upgrade so it doesn't get denied?

Show the math. Code generally requires net free ventilation area of 1/150 of attic floor area, or 1/300 with balanced intake and exhaust. Calculate the required net free area from the attic square footage, count the existing vents' net free area, photograph the existing condition, and lay the shortfall out in the narrative. A documented calculation converts an opinion into arithmetic, which is hard to deny.

When is the best time to capture teardown photos?

Before the crew loads the dumpster, every time. Hidden conditions like rotten decking, multiple layers, and failed underlayment justify the highest-value supplement lines, and they're gone forever once the new roof is on. Build a teardown photo routine into the crew's checklist so it happens on every job, rather than only the ones you think will need it.

Why does my overridden price keep getting kicked back?

Because reviewers compare your line against the regional pricing in their estimating database, and a price above that baseline with no justification reads as padding. Use the regional price list as your baseline, and when a price genuinely needs to be higher, attach the reason to the line, a manufacturer quote, a documented local labor condition, or a specialty material cost.

What should a supplement narrative actually say?

A short, factual explanation of why each added line belongs, written for that specific roof and referencing the attached documents by number and the code sections by section. Three to six sentences per significant item is plenty. Avoid boilerplate and avoid arguing coverage; the narrative's job is to make approval the easiest action available to the reviewer, not to pitch or to interpret the policy.

How can roof-age and storm data improve my approval rate?

Indirectly, by improving targeting before you ever write an estimate. A tool like RoofPredict gives a roof-age estimate as a range per address and models storm exposure per roof as odds, so crews focus on roofs aging out or genuinely worn by a storm. That means stronger, more documentable scopes from the start. It doesn't replace on-roof inspection, photos, or code research; the supplement still has to be earned with evidence.