How to Build a Supplement From an Adjuster Scope Sheet (Line by Line)

The scope sheet the adjuster hands you after an inspection is the single most useful document in the whole file, and most roofers treat it like a verdict. It is not a verdict. It is a draft. It is the carrier's first written description of what they think it takes to repair the roof, priced in their software, and it was usually built in twenty minutes by someone standing on a ladder with a clipboard or a tablet, working from a unit-price database that does not know your roof's pitch, your decking, or your local code.

Your job is not to argue with the adjuster's number. Your job is to read what they wrote, lay it next to what the roof actually requires to be put back the way it was, and document every place those two things differ. That difference, written up with measurements, photos, and code citations, is your supplement. Done well, a supplement is not a negotiation and it is not a fight. It is a correction supported by evidence, and the carrier either accepts the evidence or tells you specifically why they don't, which gives you the next thing to document.

Before anything else, the line that keeps you out of trouble: you can inspect, measure, photograph, and write an accurate estimate to repair your own scope of work, and you can state facts about that scope to the carrier. You are not negotiating the claim, interpreting the homeowner's policy, promising an approval or a payout, or saying a word about their deductible. The homeowner files. The insurer decides coverage. You document. Keep that separation clean and everything below is firmly in your lane.

What follows is the actual workflow: how to read the scope sheet, how to decode the line items and the shorthand, how to reconcile it against your own measured scope, how to write the delta into a supplement, and what to do when it comes back partial.

What the scope sheet actually is (and what it is not)

When people say "scope sheet" they usually mean one of two artifacts, and sometimes both stapled together.

The first is the field scope or inspection notes the adjuster writes on site: a handwritten or tablet form listing what they observed, what they're allowing, and rough quantities. Damaged slopes, test square results, number of damaged shingles, accessories noted, sometimes a sketch.

The second is the carrier estimate that comes out of their estimating software a day or a week later. The overwhelming majority of property claims are written in Xactimate, so most of the time you are reading an Xactimate estimate: a line-item document with item codes, descriptions, quantities, unit prices, RCV (replacement cost value), depreciation, and ACV (actual cash value). That estimate is the scope sheet that matters, because it is the priced version the carrier will pay against.

Here is what the document is not:

• It is not a measurement report. The square count on the estimate may be a rough field estimate, a number off a desk review, or pulled from an aerial report the adjuster ordered. It is frequently low, and it is frequently the first thing worth checking.
• It is not a complete scope. Adjusters work fast and price what they see. Underlayment, drip edge, code items, detach-and-reset of attached features, and steep/high charges are commonly absent on a first estimate, not because they're disputed but because nobody wrote them down.
• It is not the carrier's final position. The estimate explicitly invites correction. That is the entire reason a supplement process exists. Carriers reopen and revise files routinely; an estimate is a starting figure that gets trued up against reality.

When you internalize that the scope sheet is a fast first draft of someone else's description of your work, the whole exercise becomes calmer. You are not fighting. You are completing the document.

Reading the document top to bottom before you touch a number

Resist the urge to jump straight to the bottom-line RCV. The number at the bottom means nothing until you understand how it was built. Read the estimate the way an estimator reads a competitor's bid: structurally.

The header block. Claim number, date of loss, policy type, the adjuster's name and contact, and often the cause of loss (hail, wind, etc.). The date of loss is load-bearing. Everything you document has to tie back to that storm event. The cause of loss tells you which damage mechanism the carrier has already accepted, which shapes what you document and how.

The coverage summary. This is usually a small table near the top or bottom showing RCV, less depreciation, less the deductible, equals the net ACV payment. You read this to understand the structure, not to interpret it. You do not explain depreciation or the deductible to the homeowner as if you're advising them on their policy. You note what's recoverable on the file (recoverable depreciation is released after the work is completed and invoiced) because it affects how the job gets documented and closed out, and you let the homeowner and carrier handle the money mechanics.

The line items. This is the body. Each line has a category code, a description, a quantity with a unit, and pricing. This is where the real work happens, and the next two sections are entirely about reading it.

The summary tail. Overhead and profit (often listed as O&P), sales tax, and any general notes. Whether O&P appears at all is a function of carrier practice and job complexity, and it's an item that's frequently missing on roof-only estimates that arguably warrant it.

Make a photocopy or save a clean PDF before you mark it up. You will be annotating, and you want the original pristine for the file.

Reading the test square and the accepted cause of loss

Before you reconcile a single line, understand what the carrier has already accepted, because that decision shapes everything downstream. When an adjuster does a hail or wind inspection, they typically chalk a 10-by-10 test square on a representative slope and count impacts or damaged shingles inside it. That count, slope by slope, is how they decide whether a slope (or the whole roof) gets repaired or replaced. The scope sheet usually records it: "test square, front slope, 8 hits" or a note that all slopes met the threshold.

This matters for two reasons. First, if the carrier has accepted full replacement, you are no longer documenting whether there's damage — that's settled — you're documenting what it takes to replace the roof correctly. The whole reconciliation is a scope completeness exercise, not a damage argument, and that keeps you squarely on the documentation side. Second, the test square and accepted cause of loss tell you which collateral and code items legitimately come along with the replacement. A roof being replaced to code triggers the code items; a roof approved for hail brings the storm-related collateral (vents, flashings, and pipe boots disturbed or damaged in the same event) into scope.

What to capture from the test square section:

• Which slopes are approved, and for repair versus full replacement. If the front and back are replaced but the sides are repair-only, your scope and your supplement are split the same way, and you don't accidentally scope a full replacement the carrier didn't accept.
• The cause of loss the carrier wrote. Hail, wind, or both. You document facts consistent with that accepted cause; you don't try to reclassify it.
• The damage thresholds, if noted. These are the carrier's own criteria, and your photos should corroborate the condition they already accepted rather than reopen it.

A word on staying in your lane here: you are not adjusting the cause of loss, deciding coverage, or arguing the threshold. If the physical evidence on the roof is consistent with what the adjuster accepted, you document it and move on to scope. If you genuinely believe a slope was missed, the honest move is to document the condition with photos and let the carrier and homeowner take it from there through their own reinspection process — you don't push it as a coverage demand. The supplement you're building is about completing the scope of an already accepted loss, which is exactly the work a contractor is entitled to do.

Decoding Xactimate line items and the shorthand

Xactimate line items follow a consistent grammar once you see it. A typical roofing line looks like this:

RFG 240 - Laminated comp. shingle rfg w/out felt - 28.50 SQ

Break that down:

• RFG is the category (roofing). You'll also see RFG subitems for ridge, starter, hip, valley metal, and so on; DMO for demolition/debris; DRY sometimes for decking; and category prefixes like PNT, STL, or SDG when the roof scope touches paint, metal, or siding from collateral damage.
• 240 is the selector/item number that maps to the specific material and labor combination in the price database.
• The description spells out exactly what's included. "w/out felt" is the tell that underlayment is a separate line you should look for. If you don't find it, that's a gap.
• 28.50 SQ is quantity and unit. SQ is squares (100 sq ft). Other units you'll see: LF (linear feet, for ridge/hip/eave/rake/drip edge), EA (each, for vents/boots/accessories), SF (square feet), HR (hours), and SQ for shingles and felt.

A few specific items earn their own attention because they're where scope sheets most often fall short:

"R&R" means remove and replace. "D&R" means detach and reset. "w/o" or "w/out" means a component is excluded from that line and lives (or should live) on its own line. "+" pricing notes and asterisks usually point to a price list footnote. When you see a quantity that's a suspiciously round number (exactly 20 SQ, exactly 100 LF of ridge), treat it as a field estimate that needs your measured number, not a measured fact.

Building your own measured scope first

You cannot find what's missing from the adjuster's scope until you have a complete, accurate version of your own. The supplement is the difference between two documents, so build the second document properly.

Work from a real measurement, not a guess. An aerial measurement report (the kind that gives you total squares, ridge LF, hip LF, valley LF, eave LF, rake LF, and predominant pitch) is the cleanest source because it produces a number you can defend on paper. If you measured by hand, document how. Either way, you now have authoritative quantities for every linear and area component.

Then walk the roof and the elevation and write down everything required to replace the roof to its pre-loss condition and to current code:

1. Field area in squares, including waste. Note the pitch by slope; anything 7/12 and up triggers steep charges, and you record the actual pitch, not a guess.
2. Tear-off including the number of existing layers. Two layers is two tear-off lines or a layer multiplier. Note decking condition if visible; rotten or delaminated decking is its own documented item, never assumed.
3. Underlayment type and area. If code or manufacturer instructions require synthetic or a specific weight, note it.
4. Ice & water barrier where required by code (eaves, valleys, low-slope sections). This is jurisdiction-specific and code-driven.
5. Edge metal (drip edge) in LF at eaves and rakes, separately if the profiles differ.
6. Starter course in LF at eaves and rakes.
7. Ridge and hip cap in LF, with the actual cap product (not field shingles cut down, if the manufacturer specifies a cap).
8. Flashings: step flashing, counter flashing, headwall/sidewall, chimney, skylight, valley metal. Note which are damaged or which code/manufacturer instructions say must be replaced rather than reused.
9. Penetrations: every pipe jack, every B-vent, every exhaust cap, counted individually.
10. Ventilation: ridge vent LF, box vents EA, turbines, power vents — whatever's up there, replaced like-for-like.
11. Accessories and attached features that must be detached and reset to do the work, priced as D&R.
12. Access, height, and steep surcharges driven by the measured pitch and story count.
13. Debris removal/dumpster and any tarp or temporary repair already performed.
14. Code upgrade items triggered by the local building code (covered in its own section below).

This is your scope. It's complete, it's measured, and every line has a quantity you can show. Now you compare.

The line-by-line reconciliation

This is the heart of the work. Put the adjuster's estimate and your measured scope side by side and reconcile them line by line. There are exactly four outcomes for any given line, and naming them keeps you organized:

• Match — same item, same quantity (within reasonable waste). Leave it.
• Short quantity — same item, but their number is lower than your measured number. Document the correct quantity.
• Missing item — your scope has a required line theirs doesn't. Document the item and why it's required.
• Wrong treatment — they wrote "reuse" or "D&R" where the correct treatment is "replace" (or vice versa). Document the correct treatment with the reason.

Build a simple reconciliation table. Many supplement coordinators keep it in a spreadsheet, but a printed grid on a clipboard works fine:

The "supplement reason" column is what separates an approved supplement from a rejected one. Every line needs a reason that is a fact, a measurement, a code requirement, or a manufacturer instruction — never an opinion and never "because that's how we do it." "Required by IRC R905.2.8.5" is a reason. "Should have more" is not.

Work the whole roof before you write anything up. A supplement that arrives in dribs and drabs — one line today, three more next week — wears out the file handler and looks disorganized. Reconcile completely, then submit once, complete.

The labor and access lines nobody prices on a first pass

The missing material lines are the obvious ones. The lines that quietly get left off — and that are harder to recover later because they're easy to wave away — are the labor, access, and overhead items. They're real costs of doing the work correctly, and they belong on the estimate when the conditions trigger them. Document them the same way: with a measured or observed condition behind each.

Steep charges. Standard roofing labor pricing assumes a walkable pitch. Once a slope hits roughly 7/12 and steepens from there, the labor cost climbs in tiers, and the price database has separate steep-charge lines for each tier. The trigger is the measured pitch, slope by slope — which is why a pitch gauge photo on the actual slope is the cleanest evidence. A roof with 8/12 mains and a 5/12 garage gets the steep charge on the mains only, in the squares those slopes actually contain. Don't apply it blanket; apply it to the slopes that earn it, and show the measurement.

High charges. Separate from steep, this covers the added labor and safety setup for work above one story. A two-story or one-and-a-half-story home triggers it on the affected area. The evidence is simply the story count visible in the elevation photos.

Detach and reset (D&R). Anything attached to the roof that has to come off to replace it, and go back on afterward, is D&R labor — not free, not assumed. Gutters where the drip edge or starter requires it, satellite dishes, lightning protection, snow guards, and solar where applicable. Solar in particular is a meaningful D&R cost that's almost never on a first estimate, because the adjuster doesn't price the third-party detach/reset of a live electrical system. You document that the array exists and must be detached and reset to replace the roof beneath it; you don't perform or price the electrical work yourself unless you're licensed for it — you note it as required scope.

Debris and access. Dumpster or trailer haul-off, and any site access constraint (a long carry, no driveway access, tight lot) that changes the labor. Tarping or a temporary repair already performed after the loss is its own line, with the date and a photo, because it's work that was actually done.

Overhead and profit (O&P). Often shown as a percentage applied to the subtotal. Whether it appears is a function of carrier practice and the complexity of the job — historically tied to whether the work involves coordinating multiple trades. It's frequently absent on roof-only first estimates that arguably warrant it. This is one to handle factually and carefully: you note the trades and coordination the job actually requires and let the carrier apply their O&P policy. You don't argue entitlement or characterize it as owed; you document the job's complexity and the carrier decides.

The through-line on all of these: each is a real cost triggered by a real, observable condition — pitch, height, an attached system, a haul-off, a multi-trade job. Document the condition, not the dollar entitlement, and the line stands on the same footing as a missing material line.

Worked example: a hail file from scope sheet to supplement

Let's run a real-shaped example end to end. Numbers are illustrative; the method is what matters.

The file. Hail date of loss, a one-and-a-half story home, laminated architectural shingles, all slopes approved for replacement after the adjuster's test squares. The carrier's Xactimate estimate arrives.

The adjuster's scope sheet shows:

• RFG laminated comp shingle: 24.00 SQ
• RFG tear-off, 1 layer: 24.00 SQ
• RFG ridge cap: 40 LF
• RFG pipe jack: 2 EA
• RFG dumpster/debris: 1 EA
• No felt line. No drip edge. No starter. No ice & water. No steep charge. Flashing not listed.
• RCV total before your review: a figure that looks reasonable until you read it.

Your measured scope (from the aerial report and the roof walk):

• 28.50 SQ field area including waste
• One layer tear-off confirmed; decking sound
• Predominant pitch 8/12 on the main slopes (steep charge applies), with a one-story garage at 5/12
• 64 LF ridge + hip cap measured
• 110 LF eave + 70 LF rake drip edge
• 180 LF starter at eaves and rakes
• Eaves require ice & water barrier under the local amended code
• 4 pipe jacks, 1 B-vent cap, 2 box vents
• Step flashing at a sidewall, bent during tear-off inspection, not reusable

The reconciliation produces this supplement:

1. Shingle quantity correction: 24.00 → 28.50 SQ. Reason: aerial measurement report. Evidence: report page with the diagram.
2. Tear-off quantity correction: matched to the corrected 28.50 SQ.
3. Underlayment, added: 28.50 SQ synthetic. Reason: shingle line written w/out felt; roof cannot be installed over bare deck. Evidence: photo of bare deck during the test-square inspection plus manufacturer install requirement.
4. Drip edge, added: 180 LF. Reason: required by code at eaves and rakes; cite the adopted code section. Evidence: code citation + edge photos showing no existing serviceable drip edge.
5. Starter course, added: 180 LF. Reason: manufacturer installation instructions require a manufactured starter. Evidence: the manufacturer's published install guide.
6. Ice & water barrier, added: at eaves per the local amended code. Reason and evidence: cite the adopted/amended section; photo of eave condition.
7. Ridge/hip cap correction: 40 → 64 LF. Reason: measured ridge plus hips. Evidence: measurement report linear breakdown.
8. Steep charge, added: for the 8/12 slopes. Reason: measured pitch exceeds the standard threshold. Evidence: pitch gauge photo on the slope.
9. Pipe jack correction: 2 → 4 EA, plus the B-vent and box vents. Reason: field count. Evidence: a labeled photo of each penetration.
10. Step flashing, replace not reuse: Reason: existing flashing damaged/bent and not serviceable. Evidence: close-up photos.

Every line carries a quantity and a reason rooted in a measurement, a code, or a manufacturer instruction. There's nothing to argue with because there's no argument in it — just corrected facts the carrier can verify. That is what an approvable supplement looks like.

Notice what this supplement does not do. It does not claim a payout amount, it does not tell the homeowner their claim is approved, it does not mention the deductible, and it does not characterize the adjuster as wrong or adversarial. It documents the correct scope and hands the carrier the evidence. The carrier decides.

Photo and documentation discipline that carries the file

A supplement line without evidence is a request the carrier can decline without explanation. A supplement line with a labeled photo and a quantity is a fact they have to address. Photos are the work.

Shoot in a consistent order and shoot more than you think you need:

• Overview/context first. A few wide shots of each elevation and the full roof, so the file handler can orient. House number or address marker in one of them ties the photos to the property.
• Each damaged slope with the test square circled or marked if the adjuster's chalk is still visible. You're corroborating the accepted cause of loss, not relitigating it.
• Each missing or short item documented specifically: the bare deck for underlayment, the eave line for drip edge and ice & water, every penetration counted for pipe jacks, the bent flashing close-up for replace-vs-reuse.
• Measurement evidence: a pitch gauge on the slope for the steep charge, a tape on a representative dimension if you measured by hand.
• Date-stamped and geotagged where your phone or documentation app supports it. A timestamp tying photos to the inspection date strengthens everything.

Write captions. "Sidewall step flashing, bent during inspection, not serviceable" beats an uncaptioned photo every time, because the file handler reading it in an office three states away can't see what you saw on the roof.

Keep the package tight: a cover summary, the reconciliation table, the corrected estimate, the measurement report, and a labeled photo set, organized in the same order as your line items. A file handler who can find the evidence for line 7 in five seconds approves faster than one who has to hunt.

Writing the cover summary the file handler reads first

The person reviewing your supplement is processing a queue. They open your file, and the first thing they should see is a short cover summary that tells them exactly what changed and why, in the order it appears on the estimate. A good cover summary is not a letter and it is not a pitch — it's a map. It lets the reviewer approve the easy lines fast and spend their attention only on the ones that need it.

Keep it to one page. Structure it as a numbered list that mirrors your reconciliation table:

1. A one-line header: property address, claim number, date of loss, and that this is a supplement to the carrier's estimate of [date].
2. A single sentence stating the basis: "The following corrections are supported by an aerial measurement report, the adopted local building code, and the manufacturer's installation instructions, with photos attached."
3. The numbered lines, each in the same plain form: item — correction — reason — evidence reference. For example: "Shingle quantity corrected from 24.00 to 28.50 SQ per aerial measurement report, page 2."
4. A closing line that stays in your lane: "This supplement documents the scope required to repair the accepted loss. Coverage and payment remain between the homeowner and the carrier."

Notice what's absent. No adversarial language. No "you missed," no "you should have," no characterization of the adjuster. No dollar demands, no payout figures, no mention of the deductible, no claim that anything is owed. Just the corrections and where to verify each one. A reviewer who reads a calm, organized, evidence-referenced summary treats the whole file as credible. A reviewer who opens an angry letter treats the whole file as a fight, and fights get slow-walked.

The tone you're aiming for is the tone of a good estimator handing over a clean bid: here is the work, here is why each line is there, here is how to check it. That's it.

Code citations that hold up

Code-driven items are the strongest supplement lines because the requirement doesn't depend on anyone's judgment — it's law in the jurisdiction. But a code line only holds up if you cite the right code, adopted in the right place.

The model code most roofing work references is the International Residential Code (IRC), Chapter 9 (Roof Assemblies), with sections like R905 covering specific roof-covering requirements — drip edge, underlayment, ice barrier, and fastening among them. But the model code is not what's enforced. What's enforced is the code your jurisdiction adopted, which edition, and with what local amendments. A county may adopt the 2021 IRC; a city inside it may amend the ice-barrier requirement based on local climate. Cite the adopted local code, with the section number, rather than a vague "the IRC says."

How to do this cleanly:

1. Confirm the adopted code for the property's jurisdiction — the building department publishes which code edition is in force and any amendments. The ICC maintains the model codes; your local AHJ (authority having jurisdiction) controls what's actually adopted.
2. Cite the specific section that triggers your item. For an ice barrier, that's the ice-barrier provision; for edge metal, the drip-edge provision; for fastening, the fastening table.
3. Attach or reference the text. A file handler shouldn't have to look it up. Quote the operative sentence.
4. Tie it to a photo showing the existing non-compliant or absent condition.

Manufacturer installation instructions function the same way and are often even cleaner: most shingle manufacturers' published install guides require a manufactured starter strip and specify underlayment, and installing otherwise voids the warranty. "The roof must be installed to the manufacturer's specification to carry the warranty" is a factual, documentable basis for a starter line or an underlayment line, and the install guide is public and attachable.

Do not overreach on code. Cite only what's actually adopted and actually triggered by this roof. A wrong or aspirational code citation costs you credibility on the whole file.

Where roof-due and storm-modeled data fits

Most of the pain in supplementing isn't the supplement itself — it's that you're doing this work on roofs that were never the best use of your time, or you're discovering only at the adjuster meeting that the storm exposure was marginal. The supplement workflow is sharpest when you walked into a roof you already knew was old enough and storm-exposed enough to be worth the file.

That's the part RoofPredict speaks to. It reads aerial imagery to estimate roof age as a range per address (not an exact install date — re-roofs don't show up in tax records, so anyone claiming a precise date is guessing), and it models storm physics per roof — hail trajectory and wind, scored house by house — rather than just telling you a ZIP code got hailed. A hail swath map shows you where it hailed. Modeling the storm on each individual roof gets you closer to which roofs the storm likely actually wore out.

Where that helps the documentation side, concretely:

• Aiming the inspections. You prioritize roofs that are both old enough and storm-exposed enough to plausibly warrant a careful inspection and, where the damage supports it, a thorough scope. You spend your documentation effort where it's most likely to be justified, instead of writing files on borderline roofs.
• Corroborating the date of loss. Per-roof storm modeling and storm history give you another factual reference point that the property was exposed to the hail or wind event the claim is built around. It supports your documentation of the loss; it does not replace the physical evidence on the roof, and it never proves a specific roof was damaged.
• Pre-screening the list. Before you ever order an aerial measurement or send an inspector, you've already filtered to the roofs where the age-plus-storm signal is strongest, so more of your inspections turn into real, documentable scopes.

Honest limits, because they matter: roof age is a range, not a birthday. Storm modeling produces odds, not proof — it tells you which roofs were most likely affected, and the actual damage still has to be on the roof and in your photos. None of this is a substitute for physically inspecting, measuring, and documenting the roof, and none of it touches the claim itself. It just gets you onto the right roofs with the right expectations, so the supplement you build from the adjuster's scope sheet is one you were always going to be able to support.

What pros get wrong

A lot of supplements fail for reasons that have nothing to do with the merits. The roof needed the work; the documentation just didn't earn it. The recurring mistakes:

Treating the scope sheet as final. The single biggest error. The estimate is a draft that invites correction. Roofers who accept the first number leave correct, supportable scope on the table.

Submitting before reconciling completely. Piecemeal supplements — one line, then three more, then two more — train the file handler to see you as disorganized and slow the whole file. Reconcile the entire roof, then submit once.

Lines without reasons. "More squares" with no measurement attached. "Add starter" with no manufacturer instruction cited. Every line needs a fact behind it: a measurement, a code section, a manufacturer requirement, or a photo of the condition.

Weak or wrong code citations. Citing the model code generically, or citing a code that isn't adopted locally, or citing a section that isn't actually triggered. One wrong citation undermines the credibility of your whole package.

Photos without captions or order. A pile of forty unlabeled images is not documentation; it's homework you've handed the file handler. Caption and order them to match your line items.

Round-number quantities. Submitting your own suspiciously round numbers (exactly 30 SQ, exactly 100 LF) reads as an estimate, not a measurement. Use your real measured figures, including the decimals.

Crossing the legal line. This is the one that can actually hurt you. The list of things that turn documentation into unlicensed public adjusting in many states:

• Don't negotiate, handle, manage, or adjust the claim for a fee. You document and submit your scope; you don't represent the homeowner against their carrier.
• Don't interpret the policy or coverage. Whether something is covered is the carrier's call and the policy's language, not yours.
• Don't promise an approval, a payout amount, or a settlement figure. You can document scope; you can't guarantee outcome.
• Don't say anything about the deductible — not waived, not absorbed, not covered, not "don't worry about it." In many states that's fraud, full stop.
• Don't advertise or imply a "free roof."

The safe frame, every time: you inspected, you measured, you photographed, you wrote an accurate estimate to repair your own scope of work, and you handed it over with the evidence. The homeowner files. The insurer decides. You're the contractor documenting the work, and that role is both legally clean and exactly where your expertise actually lives. (None of this is legal advice; UPPA rules vary by state, so confirm your state's line with counsel if you're building a supplement operation at volume.)

Handling the partial approval and the kickback

Most complete, well-documented supplements come back at least partially approved. Some come back with questions or a flat decline on specific lines. Neither is a problem if you've documented properly, because a partial response tells you exactly what's still open.

When a line is approved, confirm the corrected quantity and pricing carried through and move on. When a line is declined or questioned, the response should tell you why, and the why is your next documentation task:

• "No photo of the condition." You missed a shot or didn't caption it. Send the specific photo, labeled.
• "Code not applicable here." Either you cited the wrong adopted code, or there's a genuine disagreement about what's triggered. Re-confirm the adopted local code and section, and send the operative text.
• "Reuse is acceptable." They believe the flashing or accessory is serviceable. Send the close-up showing it isn't, with a caption explaining the damage.
• "Quantity not supported." They want the measurement basis. Send the page of the measurement report that produces your number.

Keep the tone factual and the file moving. You're not winning an argument; you're closing gaps in the documentation one at a time until the scope and the evidence line up. If a real disagreement remains after you've documented everything, that's a coverage question between the homeowner and the carrier — and depending on the policy, there are formal processes (like appraisal) that the homeowner and insurer can invoke. That's their mechanism, not yours; you stay on the documentation side of it.

Then, when the work is done, the close-out matters as much as the supplement: a final invoice matching the approved scope is what releases any recoverable depreciation on the file. Document the completed work the same way you documented the scope — photos of the installed components, especially the items you supplemented in — so the completion is as clean as the estimate.

A repeatable workflow you can hand to a coordinator

The whole thing scales once it's a checklist instead of a feel. Hand this to a supplement coordinator and the output gets consistent:

1. Intake the scope sheet. Save a clean PDF of the carrier estimate. Confirm claim number, date of loss, and accepted cause of loss.
2. Order or pull the measurement. Get authoritative quantities for every area and linear component. Note the pitch by slope.
3. Build the measured scope. Walk the 14-point list above. Every required line, every measured quantity.
4. Reconcile line by line. Four outcomes per line — match, short, missing, wrong treatment. Fill the reconciliation table, with a fact-based reason for every non-match.
5. Document the evidence. Ordered, captioned photos; the measurement report; code citations with the adopted section and operative text; manufacturer install instructions where they apply.
6. Assemble one complete package. Cover summary, reconciliation table, corrected estimate, measurement report, photo set — in line-item order.
7. Submit once, complete. No dribbling lines in over two weeks.
8. Work the response. Confirm approvals; for each declined line, send the specific evidence the response asked for.
9. Close out clean. Final invoice matching approved scope; completion photos of the installed items.

Keep your reconciliation tables. Over a season they tell you which line items this carrier and this region routinely leave off a first estimate, and you start anticipating the gaps before you even read the next scope sheet. That institutional memory — "this carrier always omits starter and undercounts ridge" — is worth more than any single supplement.

The honest limits

A supplement built this way isn't a guaranteed approval, and nobody should sell it as one. It's a complete, measured, evidenced correction of a fast first draft, submitted in a form the carrier can verify. Carriers still decline lines, still disagree about code applicability, still take time. What this method does is make every one of your lines defensible, so when something comes back, you know it's a documentation gap to close rather than a weak position to defend.

It also doesn't change the fundamental roles. You document. The homeowner files. The carrier decides coverage and pays against their accepted scope. Stay precisely in that lane and the supplement is the most credible document on the file — the one that's just the facts of what it takes to put the roof back, written down so plainly there's nothing to push back on but the evidence itself.

Get onto the right roofs, build your measured scope, reconcile it against the adjuster's scope sheet line by line, and let the documentation carry the file. If you want help aiming that effort — knowing which roofs in your area are old enough and storm-exposed enough to be worth the careful inspection in the first place — that's exactly the question RoofPredict is built to answer, house by house, before anyone gets on a ladder.

FAQ

What is an adjuster scope sheet, exactly?

It's the carrier's written description of what they think it takes to repair the roof. Usually it shows up in two forms: the field notes the adjuster writes on site, and the priced line-item estimate their software (most often Xactimate) produces afterward. The priced estimate is the one that matters, because it's what the carrier pays against. Treat it as a first draft of your scope, not a final verdict.

Is building a supplement from the scope sheet legal for a roofer to do?

Yes, when you stay on the documentation side. You can inspect, measure, photograph, and write an accurate estimate to repair your own scope of work, and state facts about that scope to the carrier. What you cannot do is negotiate or handle the claim for a fee, interpret the policy or coverage, promise an approval or payout, say anything about the deductible, or advertise a free roof. The homeowner files and the insurer decides coverage. UPPA rules vary by state, so confirm your state's specifics with counsel.

Why are line items missing from the first estimate?

Almost always because the adjuster worked fast and priced what they could see in a short inspection, not because anything is in dispute. Underlayment, drip edge, starter course, ice and water barrier, steep and high charges, and full flashing replacement are the usual omissions. They're missing because nobody wrote them down, which is exactly why a documented supplement corrects them.

How do I know the square count on the estimate is wrong?

Compare it to an authoritative measurement. An aerial measurement report gives you total squares, ridge and hip linear feet, eave and rake linear feet, and predominant pitch — defensible numbers you can show. If the estimate's square count is a suspiciously round figure, it's likely a field estimate. Submit your measured number with the report page that produces it as evidence.

What makes a supplement line get approved versus rejected?

A reason rooted in a fact. Every line needs a measurement, a code section, a manufacturer installation requirement, or a photo of the condition behind it. 'More squares per the aerial report' gets approved; 'should be more' gets rejected. Lines without evidence are requests the carrier can decline without explanation.

How do I cite code correctly on a supplement?

Cite the code your jurisdiction actually adopted, the specific section, and any local amendments — rather than the model IRC generically. Confirm the adopted edition with the local building department, quote the operative sentence, and tie it to a photo showing the existing condition. A wrong or aspirational citation undermines your whole package, so cite only what's adopted and actually triggered by this roof.

Should I submit lines as I find them or all at once?

All at once. Reconcile the entire roof first, then submit one complete package. Piecemeal supplements that trickle in over two weeks train the file handler to see you as disorganized and slow the file down. One organized submission — cover summary, reconciliation table, corrected estimate, measurement report, ordered photos — moves faster.

What do I do when the carrier declines a line?

Read why and close that specific gap. 'No photo of the condition' means send the labeled photo. 'Quantity not supported' means send the measurement page. 'Reuse is acceptable' means send the close-up proving the item isn't serviceable. A partial response is a roadmap, not a fight — you document the gap they named and resubmit that line.

Can I tell the homeowner the deductible is covered if I find enough supplement?

No. Say nothing about the deductible — not waived, not absorbed, not covered. In many states that's insurance fraud regardless of the math. Your role is to document an accurate scope and hand it over. How the deductible and payment work out stays strictly between the homeowner and their carrier.

Where does roof-age and storm data fit into supplementing?

It helps before the supplement, by aiming your inspections. Tools like RoofPredict estimate roof age as a range per address and model storm physics per roof, so you focus careful inspections on roofs that are old enough and storm-exposed enough to plausibly warrant a thorough scope. It's a targeting and corroboration aid, not proof of damage — the actual damage still has to be on the roof and in your photos, and the data never touches the claim itself.