How to Write a Roof Supplement That Gets Approved the First Time

A roof supplement is the difference between the price an insurance carrier first put on a loss and the price it actually takes to put the roof back the way the policy says it should be. The first estimate a desk adjuster writes is rarely wrong on purpose. It is built from a scope that someone keyed in fast, often from a ladder-assist or a drone flight, sometimes from nothing but the homeowner's phone photos. It misses things. Your job on a supplement is not to argue that the adjuster is dumb or dishonest. Your job is to hand the carrier a clean, photo-backed, code-cited document that makes approving the money the path of least resistance.

The phrase that keeps roofers up at night is "first time." Anybody can get a supplement approved eventually if they file it four times and escalate to a manager. The expensive part is the back-and-forth: the re-inspections, the reassigned files, the homeowner calling you twice a week asking why the job hasn't started, the production calendar slipping because you are still waiting on a $1,900 approval that should have cleared in 48 hours. Getting it right on the first submission is mostly a documentation problem, partly a pricing problem, and almost never a "fight the carrier" problem. Below is the workflow used by supplement desks that clear most of their files on the first pass, the line items that get missed, the code citations that hold up, and the specific mistakes that turn a two-day approval into a three-week war.

A note before anything else: the contractor documents the conditions found on the roof and prepares an estimate to repair them. The insurer reviews that documentation and decides what the policy covers. The homeowner owns the claim and the relationship with their carrier. Nothing here is a promise about what a given carrier will pay, and no contractor should ever tell a homeowner their deductible will disappear or their roof will be "free." Write the supplement clean and let the documentation do the work.

What a roof supplement actually is

A supplement is a formal request to amend an already-approved claim scope. The carrier has accepted that a covered loss occurred and has issued an initial estimate. You are not opening a new claim or disputing coverage. You are saying: given the loss the carrier already accepted, here are additional or corrected line items, with the conditions and code requirements that justify them.

That framing matters because it changes the tone of everything you submit. A supplement is not an appeal. An appeal challenges a coverage decision. A supplement fills in scope. When roofers blur the two, they end up writing combative letters about coverage that was never in question, and the file lands on a desk adjuster who now feels attacked over something they did not decide. Keep the lane clean: coverage is settled, you are correcting the scope of repair.

Three things have to be true for a supplement line to survive review:

1. The condition exists and is documented. A photo, a measurement, a manufacturer requirement, or a code section establishes that the work is necessary.
2. It flows from the accepted loss or from doing the accepted work correctly. Replacing a roof legitimately triggers underlayment, drip edge, and disposal. A pre-existing satellite dish does not.
3. The price is defensible at the carrier's own pricing. Almost every large carrier estimates in Xactimate. If your number matches the current price list for that ZIP and the line is real, there is nothing left to argue.

Miss any one of those and you have given the adjuster a reason to deny, partially approve, or kick the file back for more information. The whole craft of first-time approval is making sure all three are airtight before you hit submit.

Why first submissions get rejected (the real reasons)

Before the workflow, understand what you are up against. Desk adjusters carry heavy file loads. They are not reading your supplement like a contract attorney. They are scanning for reasons it is easy to say yes, and reasons they are obligated to say no. The denials that eat your week almost always trace back to one of these:

• No photo tying the line item to the loss. You billed for 12 feet of ridge replacement; there is no photo showing damaged ridge. The adjuster can't approve what they can't see.
• A code item with no code citation. You added ice-and-water shield as a code upgrade but didn't cite the section of the adopted code that requires it for that jurisdiction and roof slope. "Code says so" is not a citation.
• Pricing that doesn't match the carrier's price list. You used your retail number or an old Xactimate release. The adjuster's system flags the variance instantly.
• Line items that duplicate the original scope. You re-billed the full tear-off the carrier already paid. Now the whole supplement looks padded and gets scrutinized line by line.
• Generic, unlabeled photos. Forty roof pictures with no captions, no slope or elevation labels, no overview-to-detail sequence. The adjuster cannot reconstruct what they are looking at.
• A missing or stale measurement report. Your squares don't reconcile with the carrier's, and there's no current aerial or hand-measure to settle it.
• Trade items with no justification. Detach-and-reset of solar, HVAC line work, or interior items with no explanation of why the roof work requires them.

Notice that none of these are "the carrier is cheap." They are documentation failures. The carriers that have a reputation for being difficult are usually just carriers that enforce their documentation standards strictly, which means sloppy submitters get rejected and disciplined submitters sail through. Be the disciplined submitter.

The first-time-approval workflow, start to finish

Here is the sequence that produces clean supplements. It looks like a lot of steps. In practice a trained crew runs it in well under an hour per file once the roof has been properly inspected, and the time you spend up front is a fraction of the time you lose chasing a rejected file.

Step 1 — Read the carrier's estimate line by line before you touch the roof

The single most common mistake is supplementing blind. You inspect the roof, write up everything you'd want paid, and submit it without ever reconciling against what the carrier already approved. Then half your lines are duplicates and the adjuster treats the whole packet as padded.

Pull the carrier's estimate and read every line. Build a simple two-column reconciliation:

Now you know exactly what to supplement and, just as important, what not to. You will never re-bill the tear-off the carrier already paid. Every line in your supplement is genuinely additive. That alone removes the "this looks padded" reflex.

Step 2 — Inspect for documentation, not only for damage

Most roofers inspect to decide whether there's a claim. By the time you're writing a supplement, the claim already exists. Now you inspect to prove specific conditions. That's a different photo discipline.

The shift in mindset is real. A damage inspection asks one question: is there enough here to file? A documentation inspection asks a different question for every single line you intend to bill: can an adjuster who never set foot on this roof verify this condition from my photos alone? If the answer is no, the line will get questioned, and a questioned line is a kickback. So you shoot for the adjuster's eye, not your own. You already know the ridge is damaged; the photo has to make a stranger know it too.

For every condition you intend to bill, you need a sequence:

• Overview shot establishing which slope and elevation you're on (front/left/back/right, or a slope ID from your measurement report).
• Context shot showing the area with a recognizable feature (chimney, vent, valley) so the adjuster can place it.
• Detail shot of the actual condition — the lifted shingle, the rusted flashing, the exposed deck, the hail bruise with chalk circle.
• Measurement shot where quantity matters: a tape on the ridge, the drip edge run, the valley length.

Label everything. A photo titled "IMG_4471" is useless. A photo titled "Rear slope - damaged ridge cap, 14 LF, see chalk" does the adjuster's job for them, and adjusters approve faster when you've done their job. Test for hail with chalk and date your test square. Photograph the soft metals (gutters, downspouts, vents, fascia) because spatter and dents on soft metals corroborate a hail date even when the shingle bruising is subtle.

Step 3 — Get a real measurement report

Quantity disputes are the quietest killers of first-time approval. The carrier scoped 25 squares; you're billing 28. If you can't reconcile that gap with an authoritative measurement, the adjuster discounts your number and approves theirs.

Use a measurement source the carrier already trusts — an aerial measurement report or a documented hand measurement with a diagram. Your supplement should reconcile your squares against the carrier's and show the source. When the numbers come from a report the carrier's own desk uses, the quantity conversation is over before it starts. If you hand-measure, include the diagram, the pitch, and the waste-factor logic so nothing is a black box.

Step 4 — Price in the carrier's pricing environment

This is non-negotiable for first-time approval: price the supplement in the same estimating platform and price list the carrier uses, which for most large carriers means a current Xactimate release for the correct ZIP. Do not submit retail pricing and expect the desk to convert it. Do not use a six-month-old price list. The adjuster's software compares your unit prices to the current list, and any variance becomes a reason to kick it back.

When a line legitimately isn't in the price list, or the listed price clearly doesn't reflect the actual cost of the work, that's where you use a documented price justification — a written quote from your supplier, an invoice, or a manufacturer requirement. But that should be the exception. The default is: match the carrier's price list exactly, and the only thing left for them to evaluate is whether the line is real. You've already proven it is with photos and codes.

Step 5 — Cite code, don't claim it

Code upgrade items are where the most money is left on the table and where the most amateur mistakes happen. "Code requires ice and water shield" is not a citation. A citation names the adopted code, the edition, the section, and ties it to the specific condition on this roof. More on the exact citations below — this is worth its own section.

Step 6 — Write a cover narrative that an adjuster can approve in one read

The supplement packet needs a short cover document that does three things, in plain language:

1. States that coverage is not in dispute and this is a scope supplement on claim #_____.
2. Lists each supplemented line in a table with the reason and the documentation reference (photo number, code section, measurement page).
3. Totals the supplement and references the attached estimate.

Keep it tight. The adjuster doesn't want a five-page essay; they want a map to the evidence. A clean cover narrative might be one page. Every line in it points to a photo, a code, or a measurement. There is nothing to research and nothing to dispute — they can verify each line in seconds and approve.

Step 7 — Submit complete, and submit once

A partial submission is a rejected submission with extra steps. If you're missing the measurement report, wait for it. If three photos are blurry, reshoot them. The fastest path to first-time approval is a packet with zero open questions. Every time an adjuster has to email you for "one more thing," your file goes back to the bottom of their queue and you've lost days.

A complete packet contains, at minimum:

• The supplement estimate in the carrier's pricing platform
• The cover narrative / line-item justification table
• A labeled photo report in overview-to-detail sequence
• The measurement report with square reconciliation
• Code citations for any upgrade items, with the adopted code reference
• Any supplier quotes or invoices for non-standard pricing
• The original carrier estimate for reference

Step 8 — Follow up on a schedule, not on emotion

A submitted supplement is not a closed one. The mistake here is bimodal: either you forget about it for three weeks while the homeowner stews, or you call the adjuster every morning until you've made yourself the file they dread opening. Neither moves the money. What moves it is a predictable cadence.

A workable rhythm: confirm receipt within 24 hours (a system that doesn't acknowledge your submission didn't receive it as far as you're concerned). Then give the desk a reasonable window — many carriers target a set number of business days for supplement review — before the first status touch. When you do follow up, reference the claim number, the date submitted, and ask one concrete question: "Is anything in the packet incomplete, or is it in queue for review?" That question is doing work. If something's missing, you find out now instead of in two weeks. If it's simply in queue, you've logged a polite, dated touch that keeps the file visible without making yourself a nuisance. Keep a log of every contact — date, person, substance — because if the file ever escalates, that log is the difference between "we've been chasing this for a month" and a documented timeline.

Photo discipline: the skill that decides most files

If there is one craft to obsess over, it's photography, because it's the documentation an adjuster actually consumes. Codes and pricing they can argue; a clear photo of a real condition with a measurement in frame ends most arguments before they start. A few principles that separate packets that approve from packets that get questioned:

Shoot a story, not a pile. The adjuster should be able to flip through your photos and walk the roof in their mind: pull up to the house, see the front elevation, climb to the front slope, here's the overview, here's the chimney, here's the failed step flashing at the chimney with a tape on it. A pile of forty context-free detail shots forces the adjuster to reconstruct geography they can't see, and what they can't place, they don't approve.

Put a reference in the frame. A hail bruise photographed against blank shingle could be anywhere on any roof. The same bruise photographed with a chalk circle, near a vent you also shot in the overview, with the slope identifiable, is anchored. Soft-metal damage — dents in gutters, downspouts, vents, fascia, even the AC condenser fins — is some of the most persuasive corroboration you have, because soft metals dent from hail in a way that's hard to fake and easy to date. Shoot them.

Caption every photo. "Rear slope — lifted/creased shingle, wind, photos support tab seal failure" tells the adjuster what they're looking at and which line it supports. Uncaptioned photos make the adjuster guess, and guessing slows approval. The caption is where you do the adjuster's interpretation for them, which is exactly what makes the easy yes easy.

Date and locate your test square. When you chalk a test square for hail, photograph it with the date and the slope/elevation noted. A dated, located test square is the backbone of a hail loss; an undated one floating with no slope reference invites doubt. The dated inspection is your proof of loss — treat it like the load-bearing document it is.

Capture the conditions that justify your code and access charges. Your steep charge needs a pitch you can show; your two-story charge needs an elevation photo; your ice-barrier citation is stronger with eave detail. Don't make the adjuster take your word on anything a camera can settle.

The line items that get missed (and survive review)

These are the items that legitimately belong on most full-replacement roof claims and routinely get left off the carrier's first estimate. Each one survives review when it's documented and priced correctly. None of these are tricks — they're the actual cost of doing the work to standard.

Starter course

The carrier's estimate prices field shingles by the square but frequently omits the starter strip at eaves and rakes. Manufacturers require a starter course for the warranty and for proper wind resistance. This is a real material with a real labor component, and it's one of the most commonly omitted lines. Document it with the manufacturer's installation instructions, which specify starter at eaves and rakes.

Ridge cap (vs. field shingle)

Many first estimates pay for ridge as if it were cut-up field shingle, or omit it entirely. Hip and ridge cap is a separate product at a separate price. Measure your ridge and hip linear footage from the measurement report and bill the actual cap product the system the roof requires.

Drip edge — both eaves and rakes

Drip edge at eaves is often included; rakes are often forgotten. The IRC requires drip edge at eaves and rake edges (IRC R905.2.8.5 in editions that carry it), so this is both a real material and a code item. Measure the full eave and rake perimeter.

Underlayment to manufacturer spec

The carrier may price 15# felt while the shingle manufacturer's instructions — and sometimes the code — call for synthetic underlayment or a specific weight. The manufacturer's published installation instructions govern the warranty, and installing to a lesser spec voids it. Cite the manufacturer's spec sheet.

Ice and water shield (eaves, valleys, penetrations)

In climates subject to ice formation, the IRC requires an ice barrier at eaves extending to a point at least 24 inches inside the exterior wall line (IRC R905.1.2 / R905.2.7.1 depending on edition). This is a code-driven line, not a betterment, in jurisdictions that have adopted and not amended out that provision. Valleys and penetrations frequently warrant it as well per manufacturer requirements. Cite the adopted code and the jurisdiction's amendments.

Step and counter flashing

Reusing old flashing is rarely acceptable and usually not to manufacturer or code standard. New step flashing at wall-to-roof intersections and counter flashing at masonry are real line items. Photograph the existing flashing condition and the wall-to-roof detail.

Pipe jacks, boots, and vent flashings

Every penetration needs a new flashing on a re-roof. These are cheap individually and add up, and they're constantly omitted. Count and photograph each penetration.

Valley metal

Open valleys require new valley metal; closed valleys require ice-and-water and proper weaving. Measure valley linear footage and document the valley type.

Detach and reset

Satellite dishes, solar attachments, lightning protection, antennas, and similar items mounted to the roof have to come off and go back on, or be reset by the appropriate trade. Solar in particular usually requires a licensed solar contractor to detach and reset, which is a documented sub-trade cost. Photograph every rooftop attachment.

Disposal and dumpster

Tear-off generates debris that has to be hauled and tipped. Disposal is a legitimate line tied to the square count and the number of layers. If the carrier paid two-layer tear-off, disposal scales accordingly.

Steep and high charges

Roofs over a certain pitch (commonly 7/12 and up) and over a certain height (typically two stories) carry steep and high access charges in the price list because the labor genuinely costs more. These are standard line items keyed to documented pitch and height, not add-ons you invent. Your measurement report's pitch and the elevation photos justify them.

Permit and related fees

Many jurisdictions require a permit for a re-roof. The permit fee is a hard cost you can document with the jurisdiction's fee schedule.

O&P where the job warrants it

Overhead and profit (commonly 10 and 10) applies when the job is complex enough to require general-contractor coordination of multiple trades. This is a carrier-by-carrier and job-by-job determination, not an automatic add. When your job genuinely coordinates three or more trades — roofing, gutters, solar detach/reset, interior, for example — O&P is defensible. Document the trades involved rather than asserting O&P as a right.

Worked example: a routine supplement that clears on the first pass

Consider a two-story home, 28.4 squares measured, 8/12 pitch, one layer of architectural shingle, hail loss the carrier already accepted. The carrier's first estimate paid the field shingle, 15# felt, eave drip edge, and tear-off at 25 squares. Here's a clean supplement:

Every line has a reference. Pricing matches the current price list for the ZIP. There is no re-billed work, no "code says so" without a section, no orphan photo. A desk adjuster can verify each line in under a minute and approve. That's what first-time approval looks like — it's boring, and boring is the goal.

Code citations that hold up

Code upgrade coverage depends on the policy (look for "ordinance or law" or "increased cost of construction" coverage and its limits) and on which code the jurisdiction has actually adopted and amended. You can't bill a code item the local jurisdiction amended out, and you can't bill one the policy's ordinance-or-law coverage doesn't reach. So the discipline is: cite the adopted code for the specific jurisdiction, with the edition, and tie it to the condition on this roof.

How to build a citation that survives:

1. Confirm what's adopted. The International Residential Code (IRC) is published by the ICC, but jurisdictions adopt specific editions (2015, 2018, 2021, 2024) and frequently amend them. Find the jurisdiction's adopting ordinance — usually on the city or county building department site — and the local amendments. The amendments are where pros get caught; a state or city may strike or modify the ice-barrier requirement.
2. Name the edition and section. "Per the 2021 IRC, Section R905.1.2, as adopted by [City/County] on [date]" beats "per code" every time.
3. Tie it to the roof's actual condition. Ice barrier applies where there's a history of ice forming along the eaves; drip edge applies at all eaves and rakes; underlayment requirements scale with slope. State the condition that triggers the section.
4. Reconcile against ordinance-or-law coverage. Code upgrades are typically covered under the policy's ordinance-or-law provision, which has its own limit (often a percentage of the dwelling coverage). The homeowner's declarations page governs that. You document the code requirement; the carrier and homeowner sort out the coverage limit.

The sections you'll cite most often on residential asphalt-shingle roofs:

Always verify the section number against the edition the jurisdiction adopted; section numbers shift between editions. The ICC publishes the model code; your authority is the locally adopted version. When a jurisdiction publishes its amendments, read them — that's the document that decides whether your code line lives or dies.

Where roof-due and storm-modeled data fits

Most of what's above is about a single file you already have. There's a second, quieter problem the best storm-restoration companies solve: choosing which roofs to inspect and document in the first place, and knowing the storm context for the roofs you do work. That's where targeting data earns its place in a supplement operation — not in writing the supplement itself, but in deciding where to point your crews and how to frame the storm history behind a loss.

RoofPredict gives a roofing company two things that matter here. First, it ranks addresses by which roofs are likely due — it reads aerial imagery to estimate a roof's age as a range, not an exact install date, and combines that with the home's characteristics so your canvassing and inspection effort lands on roofs that are genuinely aging out rather than on doors at random. Second, it models storm physics per roof — hail and wind exposure modeled at the individual address rather than a county-wide "a storm passed through here." That per-roof storm context is useful background when you're documenting a loss, because it tells you what the roof was actually exposed to and where on the structure to look hardest.

Be clear about the limits, because honesty is what keeps this lane clean. A roof-age range from imagery is an estimate, not a manufacturer install date — you still verify age on the roof and in the documentation. A storm model is odds and exposure, not proof that a specific shingle was damaged on a specific date; it is never a substitute for the chalk-tested test square, the soft-metal spatter photos, and the dated inspection that actually document the loss. RoofPredict does not write your supplement, file your claim, or decide coverage. What it does is make sure the crews are knocking the roofs the storm most likely wore out and the roofs aging out anyway, so the inspections you do run are on roofs that actually have something to document. The supplement still lives or dies on the photos, codes, measurements, and pricing you put in the packet.

Used that way, the data shortens the front of the funnel — fewer wasted inspections, better storm context per address — without ever standing in for the documentation. That's the only honest way to use it, and it's also the way that keeps you out of trouble with carriers and regulators who take a dim view of anyone treating a forecast or an age estimate as if it were proof of a loss.

Reading the carrier you're dealing with

Not every carrier behaves the same, and pretending they do costs you first-pass approvals. You don't need inside knowledge — you need to pay attention to the file in front of you and adjust within the rules.

Some desks are strict on pricing and lenient on narrative; others want a tight written justification for every line. Some carriers' first estimates are consistently thin on the same items — they'll pay field shingle and felt and almost nothing else — so you learn to expect the same starter, cap, drip-edge, and underlayment supplement on most of their files and you build it cleanly every time rather than acting surprised. Some carriers route supplements through a separate desk than the original estimate, which means your reconciliation table matters even more because the second adjuster may not have the first one's context.

The practical move is to keep a quiet, internal record per carrier: what they consistently omit, what documentation they consistently ask for, which pricing release they're on, how they prefer to receive packets, and their typical review window. None of that is adversarial. It's the difference between submitting a supplement tuned to how a given desk actually reviews and submitting a generic packet and hoping. Tuned packets approve the first time more often, full stop.

What you never do is treat a carrier's reputation as license to pad, or to skip documentation because "they always pay it anyway." The carrier that always pays it is the carrier most likely to install an automated check that flags the day you get sloppy. Clean every time is the only durable strategy.

Handling the partial approval and the kickback

Even disciplined submitters get partials. The adjuster approves nine of your twelve lines and questions three. The instinct is to fire back a frustrated email. Don't. Treat a partial as a documentation request and answer it surgically.

For each questioned line, send back exactly what resolves it and nothing else:

• "Need photo of X." Send the labeled photo and the line it supports. One photo, one line.
• "Code citation insufficient." Send the adopting ordinance and the section, with the edition and adoption date.
• "Pricing variance." Send the supplier quote or invoice, or show that your unit price matches the current price list and the carrier's was stale.
• "Duplicate of original scope." Show the reconciliation table proving it's additive, not a re-bill.

Keep the tone procedural. You're not winning an argument; you're closing open questions. The adjuster who gets a clean, specific response to a partial approves the rest far faster than the one who gets a wall of grievance.

If a line is genuinely denied on coverage grounds — say the carrier rules a condition pre-existing — that's no longer a supplement question; it's a coverage question that belongs to the homeowner and their carrier, and potentially their state's department of insurance or appraisal clause. Know the line. You document conditions and prepare estimates. You don't adjudicate coverage, and you never tell a homeowner what their carrier will or must pay.

The compliance guardrails you can't cross

Supplementing puts you close to regulated territory, and the companies that blow up do it here, not on the roofing. Keep these straight:

• You don't adjust claims. Negotiating or settling a claim on the homeowner's behalf can constitute public adjusting, which is licensed and regulated state by state. Documenting conditions and preparing a repair estimate is contractor work; advocating the homeowner's claim against the carrier may not be. Know your state's line and stay on the contractor side of it.
• Never promise a deductible will be waived or absorbed. Insurance deductibles are the homeowner's obligation. Rebating, absorbing, or "eating" a deductible is illegal in many states and is insurance fraud framing everywhere. Don't say it, don't imply it, don't put it in marketing.
• No "free roof." A roof paid through a claim is not free; the homeowner pays their deductible and their premiums reflect it. The phrase is a regulatory magnet and a trust-killer.
• Don't represent a forecast or an age estimate as proof of loss. Storm odds and roof-age ranges are targeting and context. The documented inspection is the proof. Conflating them is how you end up in a fraud conversation.
• The homeowner owns the claim. Every communication with the carrier should respect that the policyholder is the party to the contract. You support and document; you don't take over.

These aren't just legal niceties. Adjusters and Special Investigation Units flag patterns. A company known for clean, well-documented, compliant supplements builds a reputation that makes future approvals easier. A company known for padded packets and deductible games builds a file with the carrier's SIU. First-time approval, over a year of files, is partly a relationship — and the relationship is built on never giving them a reason to distrust your documentation.

Building a supplement operation that approves the first time at scale

One clean supplement is a skill. A hundred clean supplements a month is a system. The companies that turn first-time approval into a competitive advantage standardize the workflow so it doesn't depend on one heroic estimator.

Standardize the photo report. Build a required shot list per roof: every elevation, every slope overview, every penetration, every flashing detail, the test square, the soft metals, the measurements. Make it a checklist the inspector physically completes before they leave the roof. A missing photo is the most common cause of a kickback, and it's the easiest to eliminate with a checklist.

Build a code library by jurisdiction. For every market you work, keep the adopted code edition, adoption date, and local amendments on file. When a supplement needs an ice-barrier citation, the estimator pulls the verified citation instead of guessing. Update it when jurisdictions adopt new editions.

Reconcile before you write, every time. The two-column reconciliation against the carrier's estimate is the step most often skipped under deadline pressure, and it's the one that prevents the "padded" perception. Make it mandatory.

Price in the carrier's environment, with current releases. Keep your estimating platform on the current price list. A stale release is a self-inflicted variance flag.

Track your first-pass approval rate. You can't improve what you don't measure. Tag every supplement as first-pass approved, partial, or denied, and review the misses monthly. The patterns are almost always documentation gaps you can close: a recurring missing photo, a jurisdiction whose code you keep getting wrong, a carrier whose pricing release you keep lagging.

Feed the front of the funnel with real targeting. This is where roof-due and per-roof storm data pays off operationally. If your crews are inspecting roofs that are genuinely aging out and were genuinely in a storm's path, a higher share of inspections turn into real, documentable losses — and real losses produce clean supplements. Pointing crews at random doors produces a lot of inspections with nothing to document and a lot of weak supplements. Targeting is upstream of approval rate.

A simple first-pass scorecard

Review these monthly per estimator and per market:

The goal isn't to maximize supplement dollars per claim — that's how you drift into padding. The goal is to capture the legitimate scope the first estimate missed, with documentation so clean the carrier approves without a fight. Do that consistently and your production calendar stops slipping, your homeowners stop calling worried, and your reputation with carriers becomes an asset instead of a liability.

What pros get wrong

A few patterns separate the operators who clear files on the first pass from the ones who live in re-inspection limbo:

• They supplement everything instead of the right things. Throwing twenty marginal lines at the wall makes the desk scrutinize all twenty. Twelve airtight lines approve faster than twenty soft ones.
• They lead with attitude. The combative cover letter signals a problem file before the adjuster reads a single line. Procedural and specific beats aggrieved and vague.
• They skip the reconciliation. Re-billing approved scope is the fastest way to get the "padded" label that taints the whole packet.
• They cite code by vibe. "Code requires it" with no edition, section, or adoption reference gets struck on sight.
• They submit incomplete and hope. Every missing item is a round trip. Complete-and-once beats fast-and-partial on every measurable timeline.
• They treat targeting and proof as the same thing. Storm odds and age ranges tell you where to look; only the documented inspection proves what you found. Operators who conflate them either over-promise to homeowners or invite a fraud conversation. Keep the two jobs separate and you stay both effective and clean.

Get the documentation right, price it in the carrier's own environment, cite the actual adopted code, and reconcile against what's already paid. Do that and "approved the first time" stops being luck and becomes the default.

FAQ

What is the difference between a roof supplement and a roof claim appeal?

A supplement amends the scope of an already-approved claim — the carrier has accepted that a covered loss occurred, and you're adding or correcting line items the first estimate missed. An appeal challenges a coverage decision the carrier has made. They live in different lanes. Most missed scope is a supplement, not an appeal, and treating a supplement like an appeal (with combative coverage arguments) is a common reason files get stuck. Keep coverage settled and correct the scope.

Why do roof supplements get rejected on the first submission?

Almost always for documentation reasons, not because the carrier is cheap. The usual culprits are a line item with no photo tying it to the loss, a code item with no specific code citation, pricing that doesn't match the carrier's current price list, lines that duplicate the originally approved scope, unlabeled photos, and a missing or stale measurement report. Close those gaps before submitting and the bulk of first-pass rejections disappear.

Do I have to price a roof supplement in Xactimate?

If the carrier estimates in Xactimate — as most large carriers do — you should price your supplement in the same platform using the current price list for the correct ZIP. The adjuster's software compares your unit prices to that list, so any variance from a retail number or an old release becomes a reason to kick the file back. When a line legitimately isn't in the list or the listed price clearly doesn't reflect actual cost, document it with a supplier quote or invoice.

Which roofing line items are most commonly left off the carrier's first estimate?

Starter course, hip and ridge cap priced as cap (not field shingle), drip edge at rakes, underlayment to manufacturer spec, ice-and-water shield where code requires it, new step and counter flashing, pipe jacks and vent flashings, valley metal, detach-and-reset of rooftop attachments, disposal, steep and high charges, and permit fees. Each survives review when it's documented with photos, measurements, and the manufacturer or code requirement behind it.

How do I cite code so the upgrade item actually gets approved?

Name the specific code the jurisdiction adopted, the edition, the section, and the adoption date, then tie it to the condition on the roof. "Per the 2021 IRC Section R905.1.2 as adopted by [County] on [date], ice barrier is required at eaves on this 8/12 slope" holds up; "code requires it" does not. Check the local amendments — jurisdictions sometimes strike or modify provisions — and reconcile against the policy's ordinance-or-law coverage, which has its own limit.

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

No. A roof paid through a claim isn't free — the homeowner pays their deductible and the claim affects their premiums. Waiving, absorbing, or rebating a deductible is illegal in many states and is fraud framing everywhere. Don't say it, imply it, or market it. Your role is to document conditions and prepare an estimate; the homeowner owns the claim and the deductible is their obligation.

Does writing supplements make me a public adjuster?

It can cross that line depending on your state. Documenting roof conditions and preparing a repair estimate is contractor work. Negotiating or settling the claim on the homeowner's behalf, or advocating their claim against the carrier, may constitute public adjusting, which is licensed and regulated state by state. Know where your state draws the line and stay on the contractor side of it — document and estimate, don't adjudicate.

How should I respond to a partial approval?

Treat it as a documentation request, not an argument. For each questioned line, send back exactly what resolves it — the labeled photo, the adopting-ordinance citation, the supplier quote, or the reconciliation table proving the line is additive rather than a re-bill — and nothing else. Keep the tone procedural. A clean, specific response to a partial gets the remaining lines approved far faster than a frustrated email.

How can roof-age and storm data help with supplements?

It helps upstream of the supplement, not in writing it. Tools like RoofPredict rank which roofs are likely due using a roof-age range estimated from aerial imagery, and model hail and wind exposure per roof. That points crews at roofs genuinely aging out and genuinely in a storm's path, so a higher share of inspections turn into documentable losses. But a range is an estimate and a storm model is odds — never proof of a specific loss. The documented inspection still carries the supplement.

What's the single biggest factor in getting a supplement approved the first time?

Completeness. A packet with zero open questions — every line tied to a labeled photo, a current-price-list number, a specific code section, and a reconciled measurement — gives the adjuster nothing to research and nothing to dispute. Every missing item is a round trip that drops your file to the bottom of the queue. Submit complete and submit once; that does more for your first-pass rate than any pricing trick.