The Roofing Supplement Manager's Tools and Workflow: A Practitioner's Operating System

Most roofing companies discover they need a supplement manager the same way: a production manager who used to write three supplements a month is suddenly writing thirty, the spreadsheet tracking them has gone stale, and a $40,000 stack of recoverable depreciation has quietly aged past the point anyone remembers to chase it. The supplement function stops being a side task and becomes a job. The question owners ask next is the right one but usually framed wrong. It isn't "what software should I buy." It's "what is the actual workflow, what does each step produce, and where do tools remove the friction?"

This is the operating system for that role. It walks the full lifecycle of a supplement from the moment a claim file lands on the desk to the day the final recoverable depreciation check clears, with the specific documents, checkpoints, and aging cadences a competent supplement manager runs. It is written for contractors who restore their own work and document their own scope, and it stays on the right side of the line: a roofer documents damage, prepares an accurate repair estimate, and hands facts to the homeowner and the homeowner's carrier. The roofer does not negotiate the claim, interpret the policy, or promise an outcome. Hold that line and the supplement function is a clean, defensible, repeatable revenue cycle. Cross it and you have a licensing problem. We will return to that line because it shapes how every template is written.

What a supplement manager actually owns

Strip away the title inflation and the supplement manager owns one thing: making sure the approved scope of repair matches the real, code-required, manufacturer-required scope of repair, and that every dollar of that gap is documented well enough that an adjuster can approve it without a fight. That's it. Everything else is in service of that.

The role sits between three groups who do not naturally talk to each other. The sales rep who sold the job and wrote the original estimate. The production crew who actually tears off and installs and discovers what's really under the deck. And the carrier's desk adjuster who is processing 80 files this week and has never seen the roof. The supplement manager's job is to capture what production found, translate it into estimate line items priced to the carrier's own pricing database, anchor each line to evidence and an authority (code section, manufacturer spec, photo), and assemble it into a packet so complete the adjuster's path of least resistance is approval.

A useful way to think about the role is as a documentation and estimating function, not a negotiation function. The distinction matters legally and it matters operationally. When you frame the job as "build an airtight evidence packet," your supplement manager spends their time on photos, measurements, code citations, and clean Xactimate line items. When you frame it as "win the negotiation," they spend their time on phone calls and arguments, which is both less effective and, when done for a fee on the homeowner's behalf against the insurer, a regulated activity in most states.

The legal line, stated plainly, because it governs every tool you buy

Before any workflow, fix this in your head. In nearly every state, adjusting an insurance claim for a fee on behalf of the policyholder against their carrier is public adjusting, and it requires a license. A roofing contractor is not a public adjuster. What a contractor may do is well established: inspect the property, document damage with photographs and measurements, prepare an accurate estimate to repair the damage to their own scope of work, and communicate factual information about that scope to the carrier. The contractor may state what it costs to do the job right, cite the code that requires it, and show the photos that prove the condition.

What the contractor may not do, the do-not-say list every supplement manager and sales rep should have memorized:

• Do not negotiate, adjust, or "handle" the claim for the homeowner. You document; the homeowner files; the insurer decides coverage.
• Do not interpret the policy or tell a homeowner what is or isn't "covered." Coverage is the carrier's determination.
• Do not promise a specific payout, a specific approval, or that a supplement "will" get paid.
• Do not promise the deductible is waived, absorbed, eaten, or "taken care of." The deductible is the homeowner's obligation and rebating it is illegal in most states.
• Do not advertise or imply a "free roof."
• Do not represent the homeowner against the insurer.

The safe frame, repeated until it's reflexive: document thoroughly, write an accurate estimate aligned to the carrier's pricing, hand it to the homeowner, and let the homeowner file and the insurer decide. Every template your team uses, every email, every microsite, every letter should read like contractor documentation, not like advocacy. This isn't a disclaimer to bolt on at the end. It's the design constraint for the whole system, and the rest of this discussion assumes it.

The supplement lifecycle: seven stages

A supplement is not an event, it's a pipeline. Mapping it as discrete stages is what lets you build checklists, set aging timers, measure cycle time, and figure out where files die. Here is the lifecycle most disciplined shops converge on:

1. Intake and triage — the claim file lands, gets logged, gets a complete-or-not assessment.
2. Document classification and extraction — every document gets identified and its key fields pulled out (carrier estimate, RCV/ACV, deductible, depreciation, coverage dates, prior payments).
3. Scope-gap analysis — line-by-line comparison of the carrier estimate against the real required scope, producing a list of missing or under-scoped items, each with a reason.
4. Estimate build and pricing — the gap becomes Xactimate-aligned line items priced to the carrier's region/pricing date.
5. Packet assembly — narrative, line items, photo report, code citations, manufacturer documentation, measurements, and the cover communication, bundled into one submittable packet.
6. Submission and aging — the packet goes to the carrier; a follow-up cadence starts; status is tracked relentlessly.
7. Recoverable depreciation release — after completion, the completion-evidence and final-invoice package goes in to release the held-back depreciation, and the deductible gets collected.

Most shops are competent at stages 4 and 5 and leak money at 1, 2, 6, and 7. Intake is sloppy, so files are missing documents nobody notices until week three. Aging has no cadence, so supplements sit in a desk adjuster's queue with no follow-up. And recoverable depreciation, which is money already earned, simply doesn't get chased because no one owns the timer. Let's go stage by stage.

Stage 1: Intake and triage

Intake is where you win or lose three weeks of cycle time. A file that enters incomplete generates a back-and-forth that adds a week per round trip. The goal of intake is a single yes/no: is this file complete enough to work, and if not, exactly what is missing?

Build a required-documents checklist and run every new file against it before it enters the work queue. The minimum set for a residential storm claim:

• The carrier's loss estimate (the adjuster's scope and pricing).
• The declarations page or at least the deductible amount, coverage type (RCV vs ACV), and effective dates.
• The original signed contract or scope of work from your sales rep.
• Date of loss and claim number.
• Front-of-house and full elevation photos, plus the production/inspection photo set.
• Roof measurements (an aerial measurement report or hand measurements with a diagram).
• Any prior payment documentation or prior supplement history on the file.

What "triage" adds on top of completeness is a quick read of the file's character so you know how to staff it. A few questions that change how you work the file:

• RCV or ACV settlement? RCV claims hold back recoverable depreciation you'll chase later; ACV claims (or non-recoverable depreciation) won't. This determines whether stage 7 exists for this file.
• What pricing date and region did the carrier use? Estimates priced six months ago in a market where material costs moved will read differently than current pricing. Note it.
• Is there obvious missing scope on the face of it? A carrier estimate that pays for shingles but not for a single accessory (no drip edge, no starter, no ridge, no ice-and-water in a cold climate) tells you the gap before you've opened the photos.

Intake checklist as a gate, not a suggestion

The discipline that separates shops doing 30 supplements a month cleanly from shops drowning in them is that intake is a hard gate. A file that fails the checklist doesn't enter the queue; it goes back to the rep with a specific missing-items request, same day. The reason this matters: every document you discover is missing at stage 5 costs you a full cycle. Discovering it at stage 1 costs you an email.

A simple table your intake person fills out per file makes the gate concrete:

If any row is N and it's required, the file is blocked and the missing-items email goes out before lunch.

Stage 2: Document classification and extraction

Once a file is complete, someone has to read every document and pull out the numbers the rest of the workflow depends on. Done by hand, this is tedious and error-prone, and the errors are expensive: a deductible keyed wrong flows into a wrong invoice; a depreciation figure misread means you chase the wrong recoverable amount.

The fields worth extracting and standardizing on every file:

• RCV (replacement cost value) and ACV (actual cash value) totals.
• Total depreciation and the split between recoverable and non-recoverable.
• Deductible amount.
• Net claim / prior payments already issued.
• Date of loss, claim number, policy number, carrier and desk adjuster contact.
• Pricing profile (region and price list date) if shown.

The reason to standardize these into one structured record per claim isn't bookkeeping neatness. It's that the recoverable depreciation figure is the single number that most often gets left on the table, and you can't chase what you never recorded. A file where "recoverable depreciation: $11,240" is captured at intake is a file that gets a depreciation-release timer; a file where it's buried in a PDF is a file that gets forgotten.

This stage is also where document misclassification causes quiet damage. A denial letter filed as a "general correspondence," a contractor estimate confused with the carrier estimate, an invoice that's actually a prior supplement — each one corrupts the scope-gap analysis downstream. Whatever tool or process you use, the output of stage 2 should be: every document correctly labeled, and a clean structured summary of the money fields at the top of the file.

Stage 3: Scope-gap analysis, the heart of the job

This is the work that actually generates supplement dollars, and it's where expertise shows. Scope-gap analysis is a line-by-line comparison of what the carrier's estimate pays for against what the job actually requires — by code, by manufacturer instruction, and by physical reality discovered on the roof — and a documented reason for every gap.

The gaps fall into recognizable categories. Train your supplement manager to scan for these in order, because the same items go missing on the majority of carrier estimates.

Missing accessories and components

The carrier pays for field shingles but omits the parts that make the system work. The usual suspects:

• Starter strip at eaves and rakes (often omitted or under-counted).
• Hip and ridge cap priced as field shingle rather than as the correct cap product.
• Drip edge at eaves and rakes — frequently missing entirely, and code-required in most jurisdictions.
• Ice-and-water barrier at eaves, valleys, and penetrations in cold climates where code requires it.
• Pipe jacks, boots, and flashing — counted short or omitted.
• Ridge ventilation and the cut for it, where the existing system has it.

Code-driven items

These are the most defensible supplements because they're not opinion, they're law. When the local building code requires something to legally re-roof, replacing the roof requires it, and the estimate should pay for it. Common code-driven supplements:

• Drip edge, required at eaves and rakes under the IRC in most adopted versions.
• Ice barrier in regions where the IRC's cold-climate provisions apply.
• Decking renailing or re-fastening to current code where the existing nailing pattern doesn't meet current requirements.
• Detached structures and matching provisions where applicable.

The rule for code items: cite the specific section, and cite the locally adopted code. "IRC requires drip edge" is weaker than "IRC R905.2.8.5 as adopted by [jurisdiction] requires drip edge at eaves and rake edges." The supplement manager should keep a reference of the relevant code sections for the markets the company works, and verify local adoption, because amendments vary.

Labor and access realities

Steep and high roofs cost more to work safely, and the carrier's base labor rate may not reflect it:

• Steep charges for pitches above the threshold in the pricing database.
• High charges / multi-story access.
• Detach and reset of items like solar, satellite, gutters, where reuse isn't possible.
• Removal and disposal quantities that match the actual roof area and layers, not a default.

Quantity and measurement corrections

The carrier's squares, waste factor, and accessory counts may simply be wrong relative to an accurate measurement. A roof with significant hips and valleys carries more waste than a simple gable; if the carrier used a flat waste factor on a cut-up roof, the difference is a defensible, measurable supplement backed by your aerial report.

What "each gap needs a reason" means in practice

For every line you add, you should be able to fill in this sentence: "This item is required because ____, and here is the evidence: ____." The reason is one of code / manufacturer instruction / physical condition / measurement, and the evidence is a citation, a spec sheet, a photo, or a diagram. A supplement line with a reason and an anchor gets approved. A supplement line that's just a higher number gets pushback. The entire art of stage 3 is converting "I think this should be more" into "this is required, here's the authority, here's the proof."

Stage 4: Estimate build and pricing

Now the gap list becomes estimate line items. The non-negotiable here: price to the carrier's own pricing methodology and region, using the appropriate price list date. Submitting line items priced to a different region or a stale list invites a line-item reduction and makes you look like you don't know the system. The supplement manager works in the same estimating environment the adjuster uses, matches the pricing profile, and lets the numbers be the carrier's own numbers wherever possible. When your line item is the carrier's database price for the carrier's region, there's nothing to argue about.

A few estimating disciplines that reduce friction:

• Match the price list region and date to the original carrier estimate unless there's a documented reason current pricing applies.
• Use the correct line codes, not approximations. Hip/ridge cap has its own code; don't price it as field shingle and don't expect the adjuster to.
• Show your math on quantities — tie squares and accessory counts to the measurement report so the quantity isn't a judgment call.
• Keep options and overhead/profit clean. If a job legitimately involves multiple trades and warrants overhead and profit under the carrier's own rules, document the trades; don't assert O&P as a default.

The output of stage 4 is a supplement estimate that, read cold by an adjuster, is line items they recognize, priced the way they price, in quantities they can verify. That's the goal: make approval the easy choice.

Stage 5: Packet assembly

A supplement is judged as a packet, not as a number. The desk adjuster who can approve it in five minutes because everything they need is in front of them, labeled and ordered, will approve it. The one who has to email you back for the photo that proves the drip edge condition will set it aside. Packet completeness is the highest-leverage habit in the whole workflow.

A complete residential supplement packet, in order:

1. Cover summary / narrative. A short, factual statement of what's being supplemented and why, written as documentation, not argument. "Production tear-off revealed [condition]. The attached items are required by [code/manufacturer/measurement]. Supporting evidence is included." No promises, no coverage interpretation, no payout language.
2. The supplement estimate with each line, priced as above.
3. Photo report, captioned, each photo tied to the line item it supports. A drip-edge photo next to the drip-edge line. A close-up of the existing ridge venting next to the ridge-vent line.
4. Code citations for each code-driven item, with the specific section and locally adopted version.
5. Manufacturer documentation where an item is required by installation instructions (e.g., starter and cap requirements, ventilation requirements).
6. Measurement report / diagram supporting quantities.
7. Any prior estimate(s) for reference so the adjuster sees the delta clearly.

A packet-completeness score

The practical way to enforce this is to score every packet before it goes out. A simple rubric: each required element is worth points, and a packet below a threshold doesn't get submitted. This sounds bureaucratic until you watch it cut your back-and-forth in half. The score is a proxy for "will the adjuster have to ask for something," and every "ask" is a week.

A workable completeness rubric:

Set the bar (say, 85 of 100, with all "Yes" elements present) and hold it. The score also gives you a coaching tool: a supplement manager whose packets routinely score low on "captioned photo for each line" has a photo-discipline problem you can name and fix.

Stage 6: Submission and aging, where money quietly dies

You submitted a clean packet. Now what? In most shops, nothing — until someone remembers. That gap is where supplements go to die in a desk adjuster's queue. The fix is an aging cadence: every submitted supplement has a status and a next-touch date, and nothing falls past its date without a follow-up.

A reasonable follow-up cadence for a submitted supplement, adjusted to carrier responsiveness:

• Day 0: Submit packet. Log submission, confirm receipt.
• Day 5–7: First status check. Confirm it's been assigned and is in review. Factual, brief.
• Day 12–14: Second follow-up if no movement. Ask specifically whether anything else is needed to complete review.
• Day 21: Escalation check — confirm the file isn't stuck on a single missing item, and whether a reinspection is being scheduled.
• Every 7 days thereafter: Keep a light, factual touch until resolution.

The content of every follow-up stays inside the line: you're confirming status, confirming receipt, and asking what's needed to complete the carrier's review. You are not arguing coverage or demanding approval. "Following up on the supplement submitted [date] — can you confirm it's in review and whether you need anything further from us to complete it?" is a contractor documenting a file. It is not adjusting a claim.

Aging buckets and the reinspection fork

Track supplements in aging buckets the way you'd track receivables: 0–14 days, 15–30, 31–45, 45+. The 45+ bucket is your problem list, and it usually means one of two things: the file is stuck on a missing item (your fault, fix it) or it's headed for a reinspection (the carrier wants to re-examine the roof). A reinspection isn't a loss; it's a chance to walk the adjuster through the documented conditions in person. Prepare for it like a packet: the same photos, the same code citations, the same measurements, ready to show on the roof.

Stage 7: Recoverable depreciation release and deductible collection

This is the most-forgotten money in roofing, and it isn't a supplement in the scope sense — it's collecting money the carrier already agreed to pay. On an RCV policy, the carrier pays ACV up front and holds back the recoverable depreciation until you prove the work is complete. That held-back amount is yours to collect once you submit completion evidence and a final invoice. Shops leak enormous sums here simply because no one owns the timer between "job complete" and "depreciation requested."

The recoverable depreciation release is a documentation task with a short, fixed checklist:

• Completion evidence: photos of the finished roof, dated; a certificate of completion if the carrier uses one.
• Final invoice reflecting the actual total of the completed work (the approved RCV scope plus any approved supplements), itemized.
• Proof the deductible is accounted for as the homeowner's payment — because the deductible must be the homeowner's obligation, and your invoice and collections must reflect that it was charged and paid, not waived or absorbed.
• The release request itself, sent factually: the work is complete, here is the evidence and the final invoice, please release the recoverable depreciation per the settled claim.

The deductible is not optional and not yours to erase

Worth its own line because it's where well-meaning shops get into legal trouble. The deductible is the homeowner's responsibility. You charge it, you collect it, and your paperwork shows it was paid. You do not waive it, rebate it, "work it into the job," or advertise that you'll make it disappear. In most states, eating a homeowner's deductible is insurance fraud or an illegal rebate, and "free roof" advertising is specifically targeted by regulators and several state statutes. Your depreciation-release packet should make it affirmatively clear the deductible was collected from the homeowner. This protects you, and it keeps the whole revenue cycle clean.

Owning the timer

The operational fix for forgotten depreciation is autopilot: the moment a job is marked complete in production, a recoverable-depreciation task fires with the completion-evidence checklist attached and the dollar figure already populated from intake. No one has to remember; the system remembers. A shop that does this collects depreciation in days; a shop that doesn't collects it in months, or never. Across a year of volume, that timing difference is one of the largest swings in collected revenue the supplement function controls.

The toolset: what each tool is actually for

Now the tools. The mistake is buying software and reverse-engineering a workflow from its menus. Build the workflow first — the seven stages above — then ask which tool removes the most friction from which stage. Here's the honest mapping of tool categories to the work.

Estimating platform

The carrier-aligned estimating environment is non-optional; it's the language the claim is written in. Your supplement manager lives here for stages 3 and 4. The tool's job is to let you price line items to the carrier's region and price list so your numbers are their numbers. There's no clever substitute. The skill is in the operator, not the software — the platform doesn't know your roof has cut-up valleys or that local code adopted the ice-barrier provision; you do.

Measurement / aerial reports

An accurate measurement report is the backbone of every quantity argument. It converts "I think it's more squares" into a diagram with numbers. Use it at intake to sanity-check the carrier's squares and at stage 5 as packet evidence. The honest limit: aerial measurements are very good but not infallible on complex or obstructed roofs; verify on site where it matters.

Document management and classification

Stage 2 lives or dies on whether documents are correctly identified and the money fields are extracted reliably. Whether you do this with a person and a disciplined naming convention or with software that classifies and OCRs the documents, the requirement is the same: every document labeled, every key figure captured in a structured record. The failure mode of skipping this is the forgotten recoverable depreciation and the mis-keyed deductible.

A tracking system with aging and a cadence

Stages 6 and 7 are pure follow-up discipline, and discipline at volume requires a system with statuses, next-touch dates, and aging buckets. A spreadsheet works at low volume and silently fails at high volume because nobody updates it. Whatever you use, it must answer two questions instantly: "which supplements are past their follow-up date" and "which completed jobs have recoverable depreciation not yet requested."

Photo and field documentation

The photos are the evidence, and most supplement weakness traces to weak field photography. Your crews and inspectors need a consistent capture standard: every condition that will become a line item gets a wide shot and a close-up, dated, ideally tied to the line it supports. A field app that lets crews capture and tag photos against the job, with voice notes for context, turns the roof into documentation instead of a memory.

Where RoofPredict fits the supplement workflow

Most of the tools above are point tools — an estimator here, a measurement service there, a spreadsheet for tracking, a separate app for photos — and the supplement manager spends real hours stitching them together and re-keying numbers between them. RoofPredict's RoofClaim is built as the claim revenue-cycle layer that runs the seven-stage lifecycle as one connected workflow, on locked, UPPA-gated, contractor-documentation-only templates. Concretely, here's what your supplement manager actually does inside it, stage by stage.

At intake, a claim is created and linked to the specific home, so the claim file inherits the property's roof profile and storm-exposure record instead of starting from a blank folder. The intake gate runs against the required-documents checklist automatically.

At classification, you upload the claim documents — carrier estimate, contractor estimate, photos, denial letters, invoices — and RoofClaim auto-classifies and OCRs them, pulling the money fields (RCV, ACV, recoverable vs non-recoverable depreciation, deductible, prior payments) into a structured record at the top of the file. That's the step that stops recoverable depreciation from getting buried and deductibles from getting mis-keyed. There's a claim-inbox email triage so documents that arrive by email get routed into the right file instead of sitting in someone's inbox.

At scope-gap analysis, this is the capability that does the most work: opportunity detection maps the carrier estimate's line items against a roofing knowledge base and flags missing scope, code-required items, and missed supplements — each flag carrying an evidence anchor and pricing. So instead of your supplement manager scanning every estimate cold for the same twenty commonly-omitted items, the system surfaces "no drip edge line — code item" and "ridge priced as field shingle — component gap" with the anchor and a price already attached. The supplement manager's judgment still governs — they confirm each flag against the real roof and the local code adoption — but the blank-page scan is gone.

At packet assembly, the outputs are generated on locked templates: supplement packets, depreciation-release letters, deductible invoices, and missing-docs letters, with the photos, citations, and line items assembled in order. Because the templates are UPPA-gated and contractor-documentation-only, the narrative reads as factual documentation, not advocacy — you physically can't generate a packet that promises a payout or interprets coverage, which keeps the whole team inside the legal line by default. Each packet gets a packet-completeness score so a thin packet gets caught before it's submitted, not after the adjuster bounces it.

At submission and aging, supplements move through aging with a built-in follow-up cadence and supplement aging views, so nothing sits silently in a desk adjuster's queue. At depreciation release, the recoverable-depreciation autopilot fires the completion-evidence and final-invoice checklist when a job is marked complete, with the recoverable figure already captured from intake — which is the single fix for the most-forgotten money in the cycle. Deductible tracking keeps the deductible visible as the homeowner's obligation so your invoicing and collections reflect that it was charged and paid.

The honest limits, because credibility matters more than a pitch: the opportunity-detection flags are a knowledge-base mapping, not a guarantee — a flagged item still has to be true on your roof and required by your locally adopted code, and the supplement manager has to confirm it. The system documents and estimates; it does not, and should not, negotiate the claim or promise an approval. What it removes is the re-keying, the forgotten timers, the blank-page scope scan, and the packets that go out incomplete. What it doesn't remove is the expertise — it makes a competent supplement manager faster and a small team able to handle volume that would otherwise need a bigger one.

How RoofClaim connects to the rest of the acquisition cycle

A point worth making because it's where the platform earns its keep beyond the supplement desk. The same claims that flow through RoofClaim started as homes somewhere upstream. RoofPredict scores every home in a service area by roof-age band and per-roof storm exposure, generates a ranked list of which roofs are due or overdue, and runs that list through tracked direct mail, personalized microsites with lead capture, QR codes, and door-knock routes for the field team. Those leads land in a lead pipeline (new → contacting → appointment → inspected → won/lost) with two-way sync to the major roofing CRMs — HubSpot, ServiceTitan, JobNimbus, AccuLynx, Jobber, Housecall Pro, Salesforce, Pipedrive, Leap, Roofr, SalesRabbit, CompanyCam, and more.

For a supplement manager, the relevant payoff is continuity: a won storm job arrives at the claim desk already linked to the property's roof profile and storm-exposure evidence, so the documentation that supports the supplement is partly assembled before the claim file even opens. The targeting honesty applies throughout — roof age is a range, not an exact date, and a storm-exposure score is odds of exposure, not proof of damage. The roof still has to be inspected and documented for real. But the contractor who runs targeting, mail, CRM, and claims on one platform isn't re-keying the same property three times, and the supplement function inherits a clean file instead of building one from scratch.

Building the workflow as a team, not a hero

A caution that matters at scale. Many shops run their entire supplement function on one talented person who keeps the whole process in their head. That works until that person is sick, leaves, or hits volume they can't carry. The fix is to make the workflow live in the system and the checklists, not in one head — so a new hire can be productive on the seven stages in weeks because the intake gate, the scope-gap flags, the packet rubric, and the aging cadence are all explicit and enforced by the tooling.

A few roles a mature supplement operation separates:

• Intake coordinator — runs the completeness gate, chases missing documents, keeps the queue clean. Often part-time or shared.
• Supplement estimator — does stages 3 and 4, the scope-gap and pricing work. This is the skilled seat.
• Follow-up / aging owner — works the cadence on submitted supplements and the depreciation-release timers. Discipline over expertise; can be a dedicated coordinator.

At low volume one person does all three. The value of naming them is that you can see which one is the bottleneck and staff it, rather than burning out your one estimator on intake chasing and follow-up calls that a coordinator could own.

A worked example: the $4,800 that was sitting in plain sight

Make it concrete. A typical residential hail claim comes in. The carrier's estimate pays for the field shingles, tear-off, felt, and a flat allowance, at an RCV of, say, $14,200, with $3,100 in recoverable depreciation held back and a $1,000 deductible. The sales rep is happy; it covers the job. The supplement manager runs the file.

Classification pulls the money fields: RCV $14,200, recoverable depreciation $3,100, deductible $1,000, RCV settlement. The recoverable-depreciation timer is set the moment the file is created.

Scope-gap analysis, against the carrier estimate:

• No drip edge line. Code-required at eaves and rakes under the locally adopted IRC. Add it, cite the section. (~$350)
• Ridge cap priced as field shingle. Re-priced to the correct hip/ridge cap code at the carrier's region. (~$280 delta)
• No starter strip at rakes. Manufacturer-required for the warranty; add per installation instructions. (~$210)
• No ice-and-water at the valleys, in a climate where it's required. Cite the provision. (~$520)
• Steep charge missing on the two sections above the pitch threshold, per the measurement report. (~$900)
• Waste factor low for a cut-up roof; corrected against the aerial diagram. (~$640)
• Two pipe boots and a furnace cap found at tear-off, photographed, omitted from the original. (~$220)
• Detach-and-reset of gutters that couldn't be worked around. (~$480)
• Removal/disposal quantity corrected to actual layers and area. (~$1,200)

That's roughly $4,800 of documented, defensible gap — every line with a reason (code, manufacturer, measurement, physical condition) and an anchor (citation, spec, photo, diagram). None of it is a negotiation. It's the carrier's own pricing, applied to items the job actually requires, proven with evidence. The packet scores above the threshold because every added line has a captioned photo and every code line has a citation. It goes out clean, gets worked on the aging cadence, and the recoverable depreciation gets requested the week the job completes — with the deductible collected from the homeowner and shown as paid. That's the whole job, done right, on the right side of the line.

A 30-day plan to stand up the function

If you're building this from scratch, sequence it so you get value fast and don't try to boil the ocean.

Week 1 — Define the gate and the fields. Write the intake checklist and the standard money-fields record. Start running every new file through the gate by hand. You'll immediately stop losing weeks to incomplete files.

Week 2 — Build the scope-gap habit and the packet rubric. Make the commonly-omitted-items list and the packet-completeness rubric. Score the next ten packets before they go out. Your back-and-forth drops.

Week 3 — Install the aging cadence. Put every submitted supplement on a status and a next-touch date. Pull every completed job from the last 90 days and check which ones never had recoverable depreciation requested. That sweep alone usually pays for the whole effort.

Week 4 — Tool the friction points. Now that the workflow is explicit, add tooling where the friction is worst — usually classification/extraction and the aging/depreciation timers — so the process survives volume and turnover. This is where a connected claim revenue-cycle platform replaces the spreadsheet and the stitched-together point tools.

The order matters: workflow first, tools second. A tool layered onto a vague process just digitizes the chaos. A tool layered onto explicit stages, gates, rubrics, and cadences makes a good process fast and a small team capable of real volume.

The standard to hold

The whole function comes down to a standard you can state in a sentence: every supplement is documentation, not advocacy — accurate scope, priced to the carrier's own numbers, with a reason and an evidence anchor on every line, assembled into a packet so complete that approval is the adjuster's easy choice, followed up on a cadence so nothing dies in a queue, and finished by collecting the recoverable depreciation the moment the job is done. Hold that standard, keep the team inside the legal line, and the supplement desk stops being the place revenue leaks and becomes the place it gets recovered.

If you want the seven stages to run as one connected workflow — intake linked to the home, documents auto-classified and OCR'd, scope gaps flagged with evidence and pricing, packets assembled and scored on UPPA-locked templates, supplements aged on a cadence, and recoverable depreciation on autopilot — that's exactly what RoofPredict's RoofClaim is built to do, sitting on top of the same platform that targets the due roofs, runs the mail and field outreach, and feeds clean storm jobs into the pipeline in the first place. See how it maps to your volume at https://roofpredict.com/.

FAQ

Is a roofing supplement manager the same as a public adjuster?

No, and the distinction is legally important. A supplement manager documents damage, prepares an accurate repair estimate for the contractor's own scope of work, and communicates factual information about that scope to the carrier. A public adjuster negotiates and adjusts the claim on the homeowner's behalf against the insurer, for a fee, which requires a license in nearly every state. A contractor's supplement manager must stay on the documentation-and-estimate side: document thoroughly, write an accurate estimate, hand it to the homeowner, and let the homeowner file and the insurer decide coverage. They do not interpret policy, promise a payout, or represent the homeowner against the carrier.

What documents do I need before a supplement file is ready to work?

At minimum: the carrier's loss estimate, the deductible amount and coverage type (RCV vs ACV), the signed contract or scope of work, the date of loss and claim number, the inspection and production photo set, an accurate roof measurement report or diagram, and any prior payment or supplement history. Run every new file against this checklist as a hard gate. A file missing any required item should go back to the rep with a specific missing-items request the same day, because every document discovered missing later costs you a full cycle of back-and-forth.

What are the most commonly missed items on a carrier roof estimate?

The recurring gaps are: drip edge at eaves and rakes (often omitted and code-required), starter strip, hip and ridge cap priced as field shingle instead of the correct cap product, ice-and-water barrier where code requires it in cold climates, steep and high-roof labor charges, detach-and-reset of items like gutters, low waste factors on cut-up roofs, and removal/disposal quantities that default to less than the actual area and layers. Each should be added only with a documented reason — code, manufacturer instruction, measurement, or physical condition — and an evidence anchor.

How should supplement line items be priced?

Price to the carrier's own estimating methodology, matching the price list region and date used on the original carrier estimate unless there's a documented reason current pricing applies. Use the correct line codes rather than approximations, tie quantities to the measurement report so they aren't judgment calls, and let the numbers be the carrier's own database prices wherever possible. When your line item is the carrier's price for the carrier's region in a verifiable quantity, there's very little to dispute.

What is recoverable depreciation and why does it get left unpaid?

On a replacement-cost (RCV) policy, the carrier pays actual cash value up front and holds back the recoverable depreciation until you prove the work is complete. That held-back amount is money already agreed to — it just requires completion evidence and a final invoice to release. It gets left unpaid because no one owns the timer between job completion and the release request; the figure sits buried in a PDF and gets forgotten. The fix is to capture the recoverable figure at intake and fire a completion-evidence checklist the moment the job is marked complete.

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

No. The deductible is the homeowner's obligation. Waiving, rebating, or absorbing it is illegal in most states — treated as insurance fraud or an illegal rebate — and advertising a 'free roof' is specifically targeted by regulators and several state statutes. You charge the deductible, collect it from the homeowner, and your paperwork should affirmatively show it was paid. Your depreciation-release packet should make the collected deductible clear, which protects you and keeps the revenue cycle clean.

How often should I follow up on a submitted supplement?

Put every submitted supplement on a status and a next-touch date. A reasonable cadence: confirm receipt at submission, a first status check at day 5 to 7, a second follow-up around day 12 to 14, an escalation check at day 21, then a light weekly touch until resolution. Keep every follow-up factual — confirm it's in review and ask whether anything else is needed to complete the carrier's review. That's a contractor documenting a file, not adjusting a claim. Track supplements in aging buckets the way you'd track receivables so the 45-plus-day bucket becomes your problem list.

What makes a supplement packet 'complete'?

A complete packet, in order: a short factual narrative (documentation, not advocacy), the supplement estimate priced to the carrier's region and date, a captioned photo for every added line, a specific code citation for each code-driven item, manufacturer documentation for spec-driven items, a measurement report or diagram supporting quantities, and the prior estimate for reference. Score every packet against this before submitting and hold a threshold. The completeness score is a proxy for whether the adjuster will have to ask you for something — and every 'ask' costs you roughly a week.

Do I need expensive software to run a supplement function, or is a spreadsheet enough?

At low volume, a disciplined spreadsheet plus a carrier-aligned estimating platform and accurate measurements can work. The failure happens at volume and during turnover: the spreadsheet goes stale, recoverable depreciation gets forgotten, and the whole process lives in one person's head. Build the workflow first — intake gate, scope-gap habit, packet rubric, aging cadence — then add tooling where the friction is worst, usually document classification and the depreciation timers. A connected claim revenue-cycle platform earns its place when volume outgrows manual tracking, not before.

How does RoofPredict's RoofClaim help with the supplement workflow?

RoofClaim runs the supplement lifecycle as one connected workflow: claims link to the specific home, uploaded documents are auto-classified and OCR'd with the money fields extracted, and opportunity detection flags missing scope, code-required items, and missed supplements with evidence anchors and pricing. It assembles supplement packets, depreciation-release letters, deductible invoices, and missing-docs letters on locked, contractor-documentation-only templates, scores packet completeness, ages supplements on a follow-up cadence, runs recoverable-depreciation autopilot on job completion, and tracks deductibles as the homeowner's obligation. The honest limit: the flags are a knowledge-base mapping, not a guarantee — a supplement manager still confirms each one against the real roof and locally adopted code. It removes the re-keying, forgotten timers, and blank-page scope scan; it does not replace the expertise or negotiate the claim.