Best Supplement Software for Roofing Claims: An Honest Contractor's Buyer Guide

If you run the production or supplement side of a restoration roofing company, you already know where the money leaks. A storm job comes in at a carrier estimate that's $4,200 light on the actual scope. The crew adds a layer of synthetic underlayment the estimate never paid for. Drip edge gets installed on a slope the estimate skipped. The depreciation on the gutters never gets recovered because nobody pulled the final invoice and the completion photos together inside the window. By the time anyone notices, the file is closed, the homeowner has moved on, and you've eaten the difference.

The phrase people type into Google when they're tired of eating that difference is best supplement software for roofing claims. It's a fair search. The wrong tool will bury your team in another login that nobody opens by Thursday. The right tool turns the documentation grind — the part that actually decides whether you get paid for work you already did — into something repeatable, page-cited, and fast enough that a supplement coordinator can run forty open files instead of twelve.

What follows is a working buyer's guide written from the contractor's side of the table. We'll define what "supplement software" actually means (the category is muddier than the marketing implies), walk the real document workflow a supplement coordinator runs, compare the tools roofers actually shortlist — Xactimate, Symbility, the AI estimate-review startups, CompanyCam, AccuLynx, JobNimbus, Roofr — honestly about what each is good at and who it's for, and lay out a vendor-neutral checklist so you can score whatever you demo against your own files.

One hard line up front, and it runs through everything below: a roofing contractor documents their own scope, their own field evidence, their own invoices. The homeowner files the claim. The insurer decides it. No software, and nothing written here, turns a contractor into the homeowner's representative or a substitute for a licensed public adjuster or attorney. We'll come back to that boundary in detail, because it's the part most "supplement software" pitches get dangerously sloppy about.

What "supplement software" actually means (and what it doesn't)

The first reason people waste a demo cycle is that "supplement software" describes at least four different jobs, and most vendors only do one of them well. Sort the category before you sit through a single sales call.

1. The estimating platform itself. This is Xactimate (Verisk) and, to a smaller degree, Symbility (now CoreLogic/Cotality). These are the systems carriers and most contractors actually write the estimate in, using line-item pricing that updates monthly by ZIP. When a roofer says "I need to write a supplement," they usually mean adding or correcting line items inside an estimate platform and resubmitting. Nothing else on your shortlist replaces this. The estimate of record lives here.

2. Estimate-review / scope-gap detection. A newer wave of tools ingests the carrier's estimate (and sometimes your photos and measurements) and flags line items that appear missing or under-quantified versus a typical scope for that roof. These are the tools most directly marketed with the word "supplement." They don't write the estimate of record; they tell you where it looks short so a human can investigate.

3. Field evidence capture. CompanyCam is the dominant example: time-stamped, geo-tagged, date-organized photos and notes that tie a piece of evidence to an address and a slope. A supplement lives or dies on whether you can prove the condition existed and the work happened. This is the proof layer, not the estimate layer.

4. The CRM / project system that holds the job together. AccuLynx, JobNimbus, Roofr, Leap. These run the pipeline, the documents, the job costing, and increasingly bolt on photo, measurement, and estimate features. They're where the file lives, even if the supplement math happens elsewhere.

Here's the trap: a vendor in bucket 2 will demo a slick "found you $3,800" screen, and you'll forget that the number is a suggestion, not a recovery. A vendor in bucket 4 will show you a tidy pipeline and let you assume the scope-gap detection is as deep as a dedicated tool's. The best supplement software for roofing claims for your shop depends entirely on which of these four jobs is your actual bottleneck — and for most growing restoration roofers, the bottleneck isn't writing the line item, it's documentation throughput: assembling the page-cited factual support fast enough, consistently enough, that legitimate scope doesn't die in the backlog.

A quick definition you can hand your team

A roofing supplement is a request to the carrier to revise an estimate because the documented scope of work differs from what the estimate of record pays for — usually because of missed line items, code-required items, under-measured quantities, or work conditions the desk adjuster couldn't see from the original inspection. The contractor's job is to document the difference factually: photos, measurements, manufacturer requirements, applicable code, and the contractor's own invoices and field observations. The homeowner submits; the carrier evaluates; if there's a coverage or causation dispute, it routes to people licensed to handle that. Software's job is to make the factual documentation faster, more complete, and harder to lose.

Where restoration roofers actually leak revenue

Before tooling, name the leaks. Most "10 to 30 percent of earned restoration revenue left on the table" estimates you'll hear are vendor figures — treat them as directional, not gospel. But the categories of leak are real and consistent across shops:

• Missed scope at first write. The desk estimate pays for shingles and felt and forgets starter, ridge, drip edge, ice-and-water where code requires it, or the second story access. Caught early, these are routine. Caught after closeout, they're gone.
• Code-required items never itemized. Your jurisdiction enforces a code edition that requires, say, ice barrier 24 inches inside the warm wall, or a specific re-nail/re-deck standard. If the estimate doesn't reflect the adopted code, that's a documentable, factual gap — if you can cite the adopted edition and section.
• Quantity under-measurement. Squares, ridge length, valley length, pitch, layers. A measurement report that disagrees with the estimate's quantities is the single cleanest supplement there is, because it's arithmetic, not argument.
• Unrecovered depreciation (the quiet one). On a replacement-cost-value policy, depreciation is typically held back and released after the work is completed and documented within the policy's window. Miss the window, or fail to submit the completion documentation, and recoverable depreciation just... evaporates. This is often the largest single leak in a high-volume shop because it's invisible — there's no "denial," just silence.
• Dead supplements. A supplement gets submitted, the desk adjuster asks for one more photo, and the request dies in someone's inbox for six weeks. Aging kills supplements. Throughput is a revenue problem disguised as an admin problem.
• O&P and access items that are legitimately part of the job but get dropped when the estimate is rushed.

Notice what every one of these has in common: the recovery hinges on factual documentation produced and assembled on time. That's the job the right software is buying down. Not "winning an argument with the adjuster" — producing clean, page-cited factual support and never letting a file age out.

The document workflow a good supplement coordinator runs

If you want to evaluate tools intelligently, you need a clear picture of the workflow they're supposed to accelerate. Here's the loop a disciplined restoration shop runs on every storm file. Score any tool you demo against how many of these steps it genuinely shortens.

1. Intake every document into one structured record. Carrier estimate (the ESX or PDF), the homeowner's declaration page summary only as needed for limits/coverage routing — not for you to interpret, your inspection notes, your measurement report, your photos, your signed scope/contract, and your own invoices. If these live in five places, you've already lost.
2. Convert documents to structured, page-cited data. Every claimed fact should point back to where it came from: "starter course not present in carrier estimate — Estimate of record, page 3, roofing line items" / "ridge length 142 LF — measurement report, page 2." Page citations are what make a packet reviewable in minutes instead of hours, and they're what keep your internal QA honest.
3. Run the internal scope comparison. Your documented scope versus the carrier estimate of record, line by line. This is a factual comparison of two documents — not an opinion about what's owed. The output is a list of differences, each tied to evidence.
4. Identify the documentation gaps. For each difference, what factual support is missing? A photo of the slope without starter? A code citation for the adopted edition? A manufacturer installation requirement? The output here is a request list — what evidence still needs gathering — not a demand letter.
5. Gather the missing evidence. Field photos, additional measurements, the manufacturer spec sheet, the adopted code section. Compliance-gated: a green coordinator shouldn't be able to mark a packet "ready" while required photos are missing.
6. Human review and approval before anything goes to the carrier. This is non-negotiable and it's where the UPPA boundary lives. A qualified person on your team reviews the factual packet. Anything that's actually a coverage or causation dispute — a denial, a peril argument, a policy-interpretation question — gets routed to a licensed public adjuster or attorney, not jammed into a supplement.
7. Submit the revision request with the factual documentation attached, through the estimate platform / carrier channel.
8. Track aging and follow-up. Every open supplement has a clock. Who owns it, what's it waiting on, how old is it. The single highest-ROI feature in any supplement tool is a board that makes an aging file impossible to forget.
9. Close the loop on depreciation. When work is complete, assemble final invoice + completion photos + certificate of completion and submit for depreciation release inside the policy window. This is its own mini-workflow and the most commonly dropped one.
10. Capture the outcome. What was requested, what was approved, cycle time, and why anything was denied. Outcome data is how you get better at step 1 next quarter — and how you spot which desk adjusters and carriers consistently underwrite which items.

A tool that only does step 3 (scope-gap detection) and calls itself "supplement software" is solving the easiest part of the loop. The throughput killers are steps 1, 2, 8, and 9. Keep that in mind through every demo.

How to actually read a carrier estimate (the skill no tool replaces)

Software speeds this up; it doesn't substitute for knowing where to look. When a carrier estimate (the ESX or its PDF print) lands, a good coordinator reads it in a fixed order, and you can teach this to a new hire in an afternoon:

• The cover and limits page first — RCV vs. ACV, deductible, and whether depreciation is recoverable or non-recoverable. This tells you whether there's a depreciation loop to close at all. (Read it for operational routing, not to interpret coverage for the homeowner.)
• The line-item roofing section — walk it against your measurement report top to bottom: remove/replace shingles, felt/underlayment, starter, ridge/hip cap, drip edge (eave and rake — they're often split), step and counter flashing, pipe boots, valley metal, ice barrier, and steep/access charges. Each line is either present-and-correct, present-but-under-quantified, or missing.
• The waste and pitch factors — a 28-square roof estimated at a 10 percent waste factor on a cut-up hip is under-measured before you read another line.
• The "RCV" column versus the "ACV paid" column — the gap is the depreciation that's recoverable on completion, and it's the number that quietly disappears if you miss the window.
• The general/labor minimum and access lines — second-story, steep, and detach-and-reset items are the most commonly dropped on a rushed first write.

The tools that earn their keep flag these mechanically — an estimate-review tool surfaces the missing starter, a measurement report surfaces the quantity gap. But the coordinator who knows the read order catches things no rules engine has been taught yet, and stays out of the trap of trusting a "we found $X" screen they can't explain to a desk adjuster.

A worked example: anatomy of a $3,900 supplement

Make it concrete. Single-family, 28 squares, hip roof, hail event documented in the area.

• Carrier estimate of record: pays for shingles, synthetic felt, ridge cap, and removal. Total roofing ~ $11,800.
• Your documented scope finds five differences:
  • Starter course not itemized — present on every eave per manufacturer requirement. Factual support: manufacturer installation instructions + eave photos. Worth roughly $300–$500.
  • Drip edge on rakes and eaves required by the adopted code edition; estimate paid for it on eaves only. Support: adopted code section + photos of both conditions. ~$250.
  • Ice & water barrier at eaves required by adopted code for your climate zone; not in estimate. Support: code section + climate zone reference. ~$600–$900 depending on eave length.
  • Ridge length under-measured — estimate shows 96 LF, measurement report shows 142 LF. Pure arithmetic. ~$350.
  • Steep/access for the second-story slope, documented by elevation photos and the measurement report's pitch data. ~$400.
• Plus depreciation recovery at completion on the now-corrected RCV.

None of those five is an argument. Each is a document pointed at another document: code edition, manufacturer spec, measurement arithmetic, a photo of a condition. That's the entire game. The supplement coordinator who can assemble that packet — page-cited — in 25 minutes instead of two hours is the difference between a shop that recovers this routinely and one that recovers it when someone happens to have time. That throughput delta is what you're actually shopping for.

The honest tool-by-tool rundown

Now the comparison. Pricing in this space is almost universally quote-based and changes constantly, so what follows is pricing posture, not numbers — and you should confirm current pricing and feature scope directly with each vendor, because it shifts. The goal here is to tell you, fairly, what each tool is genuinely good at and who it's for.

Xactimate (Verisk)

What it is: the estimating system of record for most of the property insurance industry. Line-item pricing by ZIP, updated monthly, that both carriers and contractors write to.

Genuinely good at: being the common language. If your estimate and supplement are written in Xactimate with correct line items and current pricing, you and the desk adjuster are looking at the same structure. For supplements specifically, getting fluent in Xactimate line items and the price list is the highest-leverage skill on your team — more than any add-on tool.

Who it's for: any restoration contractor doing meaningful claim volume. This is table stakes, not optional, and the others orbit around it.

Honest limits: it's an estimating tool, not a documentation-throughput or aging-management system. It won't intake your photos, build your evidence index, or remind you a supplement has aged 40 days. The learning curve is real and the licensing isn't cheap. Treat it as the foundation the rest of your stack supports, not as your supplement workflow by itself.

Symbility (CoreLogic / Cotality)

What it is: the other major estimating/claims platform, used by a meaningful share of carriers, particularly some national and Canadian books.

Genuinely good at: being the estimate platform when that's the carrier's system. If you work claims on carriers who run Symbility, you need to be able to operate in it.

Who it's for: contractors whose carrier mix includes Symbility books. For many U.S. residential roofers, Xactimate is the dominant one they'll touch, but knowing which platform a given carrier uses is part of the job.

Honest limits: same as Xactimate — it's the estimate layer, not the documentation, evidence, or aging layer.

The AI estimate-review tools (the "supplement finder" category)

What they are: a wave of newer software that ingests a carrier estimate (ESX/PDF), and sometimes your measurements and photos, and flags line items that look missing or under-quantified versus a typical scope. This is the category most aggressively marketed as "supplement software." (We're deliberately not over-indexing on any single brand name here because the field is moving fast and feature claims change month to month — evaluate the live product, not last year's demo.)

Genuinely good at: speed on step 3 of the workflow — the scope comparison. A good one turns "read the estimate line by line and remember what's usually missing" into a fast first-pass flag list, which is real time saved, especially for newer coordinators who don't have a veteran's mental checklist yet.

Who it's for: shops whose bottleneck is specifically spotting gaps — typically because the team is junior or volume outran the one person who knew where to look.

Honest limits, stated plainly:

• The output is a suggestion, not a recovery. "We found $3,800" means "here are items that might be missing"; a human still has to verify each one is actually applicable to this roof and this jurisdiction, gather the support, and put it through approval. Treating the number as money is how shops submit junk supplements that erode their credibility with desk adjusters.
• Many do the finding but not the documenting — they don't manage your photos, build the page-cited evidence index, gate on missing required photos, or track aging. You still need a system for steps 1, 2, 5, 8, and 9.
• Watch the UPPA line hard here. Some marketing in this corner drifts toward "maximize the homeowner's claim" and entitlement language. The defensible posture is: detect factual documentation gaps in the contractor's own scope, support them with evidence, route coverage/causation questions to a licensed professional. A tool that nudges you toward arguing what the homeowner is "owed" is handing you compliance risk, not leverage.

CompanyCam

What it is: the dominant field-photo platform in roofing — time-stamped, geo-tagged, address-organized photos and notes, with project galleries you can share.

Genuinely good at: the proof layer. Supplements are won on documentation, and CompanyCam is how a lot of shops make sure the photo of the missing starter course, the soft metal damage, or the completed ice-and-water actually exists, dated and located. It integrates with most of the CRMs below.

Who it's for: essentially every roofing shop. If you only adopt one new tool and you don't have organized field photos yet, make it this one. Evidence beats argument every time.

Honest limits: it's the evidence capture layer, not scope comparison or supplement-aging management. It makes your packets provable; it doesn't tell you what's missing from the estimate or that a file has aged out.

AccuLynx

What it is: a mature, roofing-specific CRM/project-management platform — pipeline, documents, production scheduling, job costing, with claim/insurance features and measurement and estimate integrations.

Genuinely good at: being the system of record for a serious residential roofing operation, retail and insurance both. Strong on production and job costing; insurance-job features are built in rather than bolted on. Good fit when you want one platform holding the whole job.

Who it's for: established shops that want a deep, roofing-native operating system and will use the production/job-costing depth.

Honest limits: it's a premium-posture platform (quote-based, not the cheapest), and like all the CRMs, its supplement support is "a place to hold the file and documents," not a dedicated scope-gap engine. It manages the job; the supplement-specific intelligence is still mostly your team's.

JobNimbus

What it is: a widely used roofing/contractor CRM and project-management tool — pipeline, tasks, documents, estimating, with a large integration ecosystem (including CompanyCam, EagleView, Beacon).

Genuinely good at: flexible, approachable workflow management at a friendlier price posture than the heaviest platforms, with strong integrations so you can assemble a stack around it. Popular with small-to-midsize shops scaling up.

Who it's for: growing shops that want pipeline + document management + integrations without the heaviest platform commitment.

Honest limits: same category caveat — it organizes the job and the documents; it's not a dedicated supplement scope-gap or depreciation-recovery engine. The aging-management discipline is something you configure with boards and tasks, not something it does for you out of the box.

Roofr

What it is: a newer roofing platform that's grown fast on the strength of fast, affordable measurement reports plus CRM, instant estimates, and proposals.

Genuinely good at: measurement-to-proposal speed and a clean, modern price posture — especially attractive to shops that lived in EagleView/HOVER for measurements and want it bundled with CRM and proposals.

Who it's for: retail-leaning and growing shops that prize measurement speed and a tidy sales workflow.

Honest limits: its center of gravity is sales/measurement/proposal, not deep insurance-supplement documentation and aging. For a heavy insurance-restoration book, it's part of a stack, not the supplement engine.

A note on Leap, EagleView, HOVER

You'll see these in the same conversations. Leap is strong on digital contracts/financing/sales-process and integrates with the CRMs. EagleView and HOVER are measurement/property-data tools — they produce the measurement report that powers the cleanest supplements (quantity arithmetic), but they're measurement vendors, not supplement software. Knowing the category each one lives in keeps you from expecting a measurement tool to manage your aging board.

The comparison table

Scope: how each tool relates to the four jobs of "supplement software." Confirm current details directly with each vendor — this is posture, not a spec sheet.

The honest read: no single product does all four jobs equally well. The right answer for most growing restoration shops is a small, deliberate stack — an estimating platform you're fluent in (Xactimate, plus Symbility if your carriers use it), a strong evidence layer (CompanyCam), a CRM that holds the job (AccuLynx/JobNimbus/Roofr to taste), and then a documentation-RCM discipline layered on top so the factual packet, the aging clock, and the depreciation loop don't depend on one heroic coordinator's memory.

Where RoofPredict fits — and where it honestly doesn't

We build RoofPredict, so read this section with the appropriate skepticism. We'll keep it factual and tell you the limits.

RoofPredict started on the targeting side: from aerial imagery and storm physics modeled per roof, it tells a contractor which roofs in an area are likely due — a roof-age range per address (a range, never an exact install date — re-roofs don't announce themselves) paired with the storms each roof has actually taken. That's the "which houses do I knock and mail" problem, and it's a different category from everything above; it's not measurement, not CRM, not estimating.

The piece relevant here is RoofClaimRCM — the claim revenue-cycle-management layer. It's built around exactly the throughput problem this whole article is about: turning every document in a file into verified, page-cited structured data, turning every gap into an evidence-linked, compliance-gated documentation opportunity, and tracking each one from the kitchen table to the depreciation check to the material order — with human approval guarding everything that touches the carrier.

What that means in the workflow terms above:

• It leans into steps 1, 2, 8, and 9 — the throughput killers most "supplement finders" skip. Intake into one structured record, page-cited extraction so every claimed fact points back to its source document, file-level aging so nothing rots in an inbox, and a dedicated depreciation-recovery loop so completion documentation goes out inside the window.
• Step 3 (the internal scope comparison) is framed as exactly that — a factual comparison of your documented scope against the carrier estimate of record, producing a list of differences each tied to evidence. Not an opinion about what's owed.
• Step 6 (human review) is enforced, not optional. Compliance gates mean a packet can't go out missing required photos, and anything insurer-facing routes through a person.

Now the honest limits, because the guardrails on this site are real:

• It is not a public adjuster and won't act like one. It documents the contractor's own scope and field evidence. It does not represent the homeowner, negotiate settlement, interpret coverage, or tell anyone what they're "entitled" to. Coverage and causation disputes — denials, peril arguments, appraisal, proof of loss — route to a licensed public adjuster or attorney. That's a deliberate design constraint, not a missing feature.
• It is not your estimating system of record. The estimate of record lives in Xactimate (or Symbility). RoofClaimRCM organizes the documentation around that estimate; it doesn't replace it.
• The targeting side is odds, not proof. Roof age is a range and storm impact is a probability that a specific roof was worn, not a guarantee. We say this plainly because pretending otherwise burns trust the first time a "due" roof turns out to be five years newer than modeled.
• It's quote-based, and for a very low-volume shop, disciplined boards in your existing CRM plus CompanyCam may be all you need. The RCM layer earns its keep when document volume and dollars-at-risk outgrow one person's memory.

If your bottleneck is spotting gaps, an estimate-review tool may serve you first. If your bottleneck is assembling and not losing the factual documentation — the page-cited packet, the aging file, the depreciation window — that's the specific problem RoofClaimRCM is built for, and that's the honest place it fits in your stack.

How to actually evaluate a tool: the demo checklist

Don't watch the canned demo and nod. Bring three of your own recent files — ideally one clean win, one that aged out and died, and one depreciation recovery — and make the vendor run your documents through their tool live. Score against this:

Documentation throughput (the real bottleneck)

• Can it intake all my file types — ESX/PDF estimate, measurement report, photos, my invoices, signed scope — into one structured record, without me retyping?
• Does every extracted fact carry a page citation back to the source document?
• How long does it take my coordinator to assemble a page-cited packet on a real file — measured, not promised?

Scope comparison (without crossing the line)

• Does it compare my documented scope to the carrier estimate of record and output differences each tied to evidence?
• Does it frame output as factual documentation, or does it use entitlement language ("what they owe," "maximize the claim")? Entitlement language is a red flag, not a feature.

Evidence and compliance

• Can it flag missing required photos/measurements and block a packet from being marked ready until they're there?
• Is there an enforced human-approval step before anything goes carrier-facing?

Aging and the depreciation loop

• Is there a board showing every open supplement's age and what it's waiting on, with an owner?
• Is there a dedicated depreciation-recovery workflow that assembles completion documentation and watches the policy window?

Outcomes and fit

• Does it capture requested vs. approved and cycle time so I can see whether it's working?
• Does it integrate with what I already run (estimating platform, CompanyCam, my CRM), or is it another island?
• What's the adoption reality — will my supplement coordinator actually open it Thursday afternoon?

The compliance gut-check (do this for every claims tool)

• Ask the rep directly: "Does this ever represent the homeowner, negotiate with the carrier, or tell a homeowner what they're entitled to?" The right answer is an unambiguous no — it documents the contractor's own scope and routes coverage disputes to licensed professionals. If they get cute, walk.

The UPPA boundary — the part most pitches get wrong

This deserves its own section because it's where well-meaning roofers and sloppy software get shops in trouble. Most states have an Unauthorized/Unlicensed Public Adjuster Act or equivalent statute. The short version: adjusting another person's insurance claim for compensation generally requires a license, and a roofing contractor is not licensed to do it by virtue of holding a roofing license. The homeowner files and owns the claim. The insurer decides it. The contractor documents their own scope of work.

What's clearly allowed (and what good software accelerates):

• Documenting your own inspection, estimate, scope, invoices, and field evidence.
• OCR and factual extraction of documents into structured data.
• Photo and measurement checklists.
• Internal QA of your own scope.
• Comparing the carrier estimate to your documented scope internally.
• Building an evidence index and a missing-document/photo request list.
• Human-reviewed factual packets and an audit trail.

What's not yours to do (route it to a licensed PA or attorney):

• Representing or acting for the insured.
• Negotiating the settlement.
• Interpreting coverage or telling a homeowner what they're entitled to recover.
• Recommending appraisal, litigation, complaint, or settlement-acceptance strategy.
• Pressure scripts, bad-faith threats, or anything fee-based on the claim proceeds.
• Deductible-waiver, rebate, or "free roof" messaging (its own separate legal problem in most states).

The language discipline that keeps you safe is small and learnable. Train your team — and demand it of your software — to write like this:

None of this weakens a legitimate supplement. A supplement built on "page 3 of the estimate omits starter course; here's the manufacturer requirement and the eave photo" is stronger than one built on "the homeowner deserves more," because the first is a fact pointed at a document and the second is an argument a desk adjuster can wave off — and one of them keeps your license clean. The best supplement software for roofing claims makes the factual version the path of least resistance. The worst makes the entitlement version one click away.

Building the stack: three realistic configurations

There's no universal answer, so here are three concrete stacks by shop profile. Adjust to your carrier mix and volume.

The lean retail-plus-storm shop (under ~$3M, light insurance volume)

• Estimating: Xactimate (you need fluency even at low volume).
• Evidence: CompanyCam. Non-negotiable; it's the cheapest leverage on this list.
• System of record: JobNimbus or Roofr — accessible, integrates with CompanyCam.
• Supplement discipline: a manual aging board with hard rules and a checklist for the depreciation window. At this volume, discipline beats another subscription. Revisit a dedicated RCM layer when files start aging out because nobody had time.

The growing restoration shop (volume outran one coordinator)

• Estimating: Xactimate + Symbility for the carriers that use it.
• Evidence: CompanyCam, with required-photo checklists enforced by process.
• System of record: AccuLynx or JobNimbus.
• Scope-gap help: an estimate-review tool if your coordinators are junior and missing items — but treat its output as suggestions to verify, not money.
• Throughput layer: this is where a documentation-RCM discipline (RoofClaimRCM or an equally rigorous internal SOP) starts paying for itself — page-cited packets, enforced aging, the depreciation loop. The leak you're plugging is files dying in the backlog and depreciation aging out, not failure to spot gaps.

The high-volume restoration operation (multiple crews, dedicated supplement team)

• Estimating: full Xactimate fluency across the team; Symbility as needed.
• Evidence: CompanyCam standardized, with photo SOPs by job type.
• System of record: AccuLynx (production/job-costing depth earns it at this scale).
• Documentation RCM: a dedicated layer is now a throughput and compliance necessity, not a nicety — structured page-cited data, compliance gates so no coordinator can submit an incomplete or out-of-bounds packet, file-level aging across hundreds of open supplements, and outcome analytics to see which items and which desks consistently underwrite. Human approval enforced at scale is the point.
• Compliance: a written UPPA-boundary SOP and the language table above posted at every coordinator's desk. At volume, one entitlement-language packet to the wrong carrier can become a regulatory headache.

The numbers to put on a board (so you know it's working)

You can't manage a leak you don't measure, and "we feel like we're recovering more" is not a metric. Whatever stack you land on, instrument these — most of them you can pull from your CRM and estimating platform with a spreadsheet before you buy anything fancier:

• Supplement capture rate — of insurance jobs in a period, what percentage had at least one documented, submitted supplement? A shop doing real restoration volume with a capture rate near zero isn't "clean," it's leaking.
• Average days-to-submit — from job intake (or closeout, for depreciation) to the supplement or depreciation request going out. This is your aging early-warning; when it creeps up, files are starting to die.
• Open-supplement aging buckets — count of open supplements at 0–15, 16–30, 31–60, and 60+ days. The 60+ bucket is money actively rotting. The goal is to keep it empty, not to celebrate a big "found" number.
• Requested vs. approved dollars — and the reason for any gap. A low approval rate isn't always bad documentation; sometimes it's junk supplements built on weak support, which is its own fixable problem.
• Depreciation-recovery rate — of jobs with recoverable depreciation, what percentage actually got the completion documentation submitted inside the window? This single number is often the biggest quiet leak in a high-volume shop.
• Cycle time by carrier and by desk — over a quarter, patterns emerge: which carriers and which desk adjusters consistently underwrite which items. That's not ammunition to argue with — it's intelligence that tells your coordinators where to front-load documentation so the first submission is complete.

The reason to track these before you buy is simple: they tell you which of the four "supplement software" jobs is actually your bottleneck, so you demo for the right problem. A shop with a healthy capture rate but a fat 60+ aging bucket and a low depreciation-recovery rate has a throughput problem, not a spotting problem — and buying a gap-finder won't fix it.

A 30-day plan to stop leaking

If you do nothing else after reading this, run this:

1. Week 1 — Measure the leak. Pull every supplement and depreciation file from the last 90 days. Count: how many supplements aged past 30 days without follow-up? How many depreciation recoveries got assembled outside the window? That's your number. It's almost never zero.
2. Week 1 — Standardize evidence. If you don't have organized, dated field photos, deploy CompanyCam this week and write a required-photo checklist by job type.
3. Week 2 — Write the workflow down. Take the 10-step loop above and turn it into your shop's SOP with owners and aging rules. Most shops have never written it down; that alone recovers money.
4. Week 2 — Post the language table. Train every coordinator on factual vs. entitlement language. Make the factual version the default.
5. Week 3 — Demo with your own files. Take three real files to two or three vendors and run the checklist above. Don't buy the demo; buy the result on your files.
6. Week 4 — Pick the smallest stack that plugs your specific leak. If the leak is spotting gaps, a scope-review tool. If it's assembling and not losing the documentation — the bigger leak for most growing shops — a documentation-RCM discipline. Layer it on your estimating platform and evidence layer; don't rip and replace.

The shops that recover legitimately earned restoration revenue consistently aren't the ones with the flashiest "we found $4,000" screen. They're the ones who turned the document workflow into a habit a junior coordinator can run, kept every claimed fact pointed at a page in a document, never let a file age out, and never once told a homeowner what they were "owed." Buy the tool that makes that easy — and confirm every vendor's current pricing and feature scope directly, because in this category it changes faster than any article can track.

FAQ

What is supplement software for roofing claims?

It's a loose category covering four different jobs: the estimating system of record (Xactimate, Symbility), scope-gap detection that flags possibly missing line items, field evidence capture (CompanyCam), and the CRM that holds the job (AccuLynx, JobNimbus, Roofr). Most tools do one of these well. A roofing supplement itself is a request to the carrier to revise an estimate because the documented scope differs from what the estimate of record pays for. The best tool for you depends on which of those four jobs is your actual bottleneck — for most growing shops it's documentation throughput, not spotting gaps.

What's the difference between Xactimate and a 'supplement finder' tool?

Xactimate is the estimating system of record — where the estimate and supplement are actually written, in line items priced by ZIP. A scope-gap or 'supplement finder' tool ingests a carrier estimate and flags items that look missing versus a typical scope. The finder produces suggestions; Xactimate produces the estimate everyone negotiates from. You generally need Xactimate fluency regardless; a finder is optional help for spotting gaps, mostly useful for junior coordinators.

Can roofing supplement software handle the insurance claim for the homeowner?

No — and any tool that implies it can is a compliance risk. The homeowner files and owns the claim; the insurer decides it; the contractor documents their own scope of work. Software that represents the homeowner, negotiates settlement, interprets coverage, or tells a homeowner what they're entitled to is drifting into unlicensed public adjusting, which most states regulate. Good software documents the contractor's own scope and routes coverage and causation disputes to a licensed public adjuster or attorney.

How does software actually help recover more supplement revenue?

By buying down the throughput bottleneck. The recovery hinges on factual documentation produced and assembled on time: page-cited extraction so every claimed fact points back to its source document, enforced photo/measurement completeness, a scope comparison tied to evidence, and — most overlooked — file-level aging so supplements don't die in an inbox and a depreciation loop so completion documentation goes out inside the policy window. It's not about winning arguments; it's about not losing legitimate, documented scope to the backlog.

Is CompanyCam supplement software?

Not exactly — it's the field evidence layer, and it's the single highest-leverage tool for supplements even though it doesn't detect gaps. Time-stamped, geo-tagged, address-organized photos are what make a supplement provable: the photo of the missing starter course, the soft-metal damage, the completed ice-and-water. It won't tell you what the estimate missed or that a file aged out, but supplements are won on documentation, and CompanyCam is how most shops make sure that documentation exists.

Do AccuLynx, JobNimbus, and Roofr do supplements?

They hold the file and its documents, and you can run supplement discipline inside them with boards, tasks, and integrations — but none is a dedicated scope-gap or depreciation-recovery engine out of the box. AccuLynx is deep on production/job-costing for established residential shops; JobNimbus is flexible and integration-rich at a friendlier price; Roofr leans toward fast measurement and proposals. They run the job; the supplement-specific intelligence and aging discipline is something you configure or layer on.

How much does roofing supplement software cost?

Pricing across this category is almost universally quote-based and changes often, so treat any number you see as outdated. Xactimate and Symbility are licensed and not cheap; CompanyCam is per-user subscription; CRMs range from accessible (JobNimbus) to premium quote-based (AccuLynx); scope-review tools and documentation-RCM platforms are typically quote-based. Confirm current pricing directly with each vendor and price the whole stack, not one tool in isolation.

What's the most common revenue leak in roofing supplements?

Two tie for worst, and both are invisible. First, dead supplements — a desk adjuster asks for one more photo and the request ages out in an inbox; aging kills supplements. Second, unrecovered depreciation — on a replacement-cost policy, depreciation is released after work is documented within the policy window, and miss that window and it just evaporates with no denial, just silence. Both are throughput problems, which is why aging boards and a dedicated depreciation loop matter more than a flashier gap-finder.

How do I keep supplements compliant with state public-adjuster laws?

Document your own scope, never the homeowner's claim. Stick to factual language: instead of 'the homeowner is entitled to' write 'the uploaded documents show'; instead of 'demand payment' write 'please review the attached factual documentation'; instead of interpreting coverage, 'route for qualified coverage review.' Keep an enforced human-approval step before anything goes carrier-facing, and escalate any coverage, causation, denial, appraisal, or proof-of-loss matter to a licensed public adjuster or attorney. A supplement built on a fact pointed at a document is both stronger and safer than one built on entitlement.

How should I evaluate supplement software before buying?

Bring three of your own recent files — a clean win, one that aged out, and a depreciation recovery — and make the vendor run them live. Time how long your coordinator takes to assemble a page-cited packet. Check that output is tied to evidence and uses factual, not entitlement, language; that it flags missing required photos and enforces human approval; that there's an aging board and a depreciation workflow; and that it integrates with your estimating platform, CompanyCam, and CRM. Ask point-blank whether it ever represents the homeowner or negotiates with the carrier — the right answer is no.