Roofing Claim Revenue Leakage: Where It Actually Hides

Most roofing companies that work insurance restoration are leaking money they already earned. Not money they hope to win in a dispute, and not money they would need a license they do not have to chase. Earned money. Work that was scoped, materials that were installed, depreciation that was recoverable on the carrier's own estimate, supplements that were factually justified and simply never finished. The roof got replaced, the homeowner is happy, the crew moved on, and somewhere between the kitchen-table inspection and the final depreciation release, ten to thirty cents of every legitimate restoration dollar quietly walked out the back door.

That range is not a marketing number, and it is not a promise that you are leaking exactly that much. It is the practical band production and supplement managers describe when they go back and audit a year of closed files honestly. Some shops leak almost nothing because they have a disciplined, documented revenue cycle. Plenty of shops leak far more than they think because the leaks are invisible by design: each one is small, each one feels like a one-off, and none of them show up as a line on a profit-and-loss statement that says "revenue we earned and never collected."

The goal here is to make those leaks visible. We will walk the claim from first contact to final invoice and name every place revenue commonly escapes, with concrete examples, the documentation that prevents each one, and the workflow that catches them before the file closes. Throughout, one boundary stays fixed: you are a contractor documenting your own scope, your own observations, and your own invoices. The homeowner files the claim and the insurer decides it. Nothing here involves representing the insured, interpreting their policy, or negotiating a settlement. It is about not leaving earned money on the table through sloppy paperwork and dropped follow-through.

What "revenue leakage" means on a restoration claim

Revenue leakage is the gap between the revenue a job legitimately should have produced and the revenue you actually collected. On a cash retail job that gap is small, because you wrote a price, the customer agreed, and they paid it. On an insurance restoration job the gap is wide open, because the revenue arrives in stages, depends on documentation you control, and gets released by a third party on a timeline that outlasts most contractors' attention spans.

A restoration claim pays in pieces:

• Actual Cash Value (ACV) first: the depreciated value of the covered scope, usually paid after the carrier approves the estimate.
• Recoverable depreciation second: the difference between ACV and Replacement Cost Value (RCV), released after the work is completed and you submit proof of completion and a final invoice. This is your money on the carrier's own estimate, and it is one of the most-leaked categories in the entire industry.
• Supplements throughout: additional scope discovered during the job that was not on the original estimate, documented factually and submitted for the carrier's review.
• Overhead and profit (O&P) where the trade-and-complexity facts support it, typically expressed as a percentage on the carrier's estimate.

Every one of those pieces has a place where it can fall out. The original scope can be incomplete. The supplement can be justified but never submitted, or submitted and never followed up. The depreciation can be earned but never invoiced because nobody tracked completion. Each gap is a leak. Add them up across a year of files and you have the difference between a shop that is quietly bleeding and a shop that runs a tight revenue cycle.

A useful mental model: treat every claim like accounts receivable, because that is what it is. You would never let a retail invoice sit uncollected for ninety days without a phone call. A claim file is an invoice with extra steps, and the extra steps are exactly where shops get lazy.

The eight places roofing claim revenue actually leaks

Here is the map. We will take each leak in the order it tends to appear in the life of a file, from the first inspection to the final dollar.

#	Leak	Where it happens	Typical cause	What plugs it
1	Missed scope at inspection	Kitchen-table / roof inspection	Rushed, undocumented field visit	Standardized photo + measurement checklist
2	Soft initial estimate	Estimate build	Copy-paste templates, missing line items	Line-item discipline tied to field evidence
3	Code and manufacturer items omitted	Estimate / supplement	Not documented at time of tear-off	Local code citations + spec sheets in file
4	Abandoned supplements	Production	No owner, no tracking, no deadline	Supplement pipeline with status + due dates
5	Unrecovered depreciation	Closeout	Completion never proven, final invoice never sent	Completion trigger + invoice automation
6	Photo and document gaps	Throughout	Evidence scattered across phones and trucks	Centralized, page-cited evidence index
7	O&P left undocumented	Estimate review	Trade complexity not captured factually	Trade-count and complexity documentation
8	Slippage and aging files	Whole cycle	No audit trail, no follow-up cadence	Status tracking from inspection to check

Now the detail on each.

Leak 1: Missed scope at the inspection

The single largest source of leakage is also the earliest: what you never wrote down because you never looked, or looked and did not document. If a damaged item is not captured during your inspection, it is not on your estimate. If it is not on your estimate, it is not in the claim. And if it is not in the claim, the only way it ever gets paid is through a later supplement that is harder to justify because you have no contemporaneous evidence it existed.

The classic missed items, all of them legitimate parts of a roof system:

• Step flashing and counterflashing at wall intersections
• Pipe jacks, boots, and their condition
• Drip edge and rake edge
• Valley metal and the valley treatment method
• Ridge and hip cap, especially on systems requiring specific cap shingles
• Ridge vent, off-ridge vents, turbines, and their replacement
• Ice-and-water shield where code or manufacturer specs require it
• Decking condition and the per-sheet replacement that emerges at tear-off
• Chimney flashing, crickets, and saddles
• Skylight flashing kits
• Detached structures that share the loss: detached garages, sheds, gazebos
• Soft metals, gutters, downspouts, and fascia where the same event caused damage
• Interior damage from the same event where it is your scope to document

The leak is not that these items are controversial. Most are routine. The leak is that a rushed inspector who shoots fifteen blurry photos from the eave and writes "replace roof" hands the estimator nothing to build a complete estimate from. The fix is procedural, not technical.

The documentation that plugs it: a standardized inspection checklist that the field tech cannot skip, paired with a required photo set. Photograph every slope, every penetration, every flashing detail, every transition, and every accessory, with at least one wide establishing shot and one tight detail shot per item. Capture test squares for hail with a measured reference. Note decking type and apparent condition. Record the manufacturer and approximate roof-age range if you can read it from the existing system, because age range and system type drive which code and manufacturer requirements apply. The output of a good inspection is not a price; it is an evidence package complete enough that an estimator who never set foot on the roof could build a full, defensible scope from it.

A practical rule: if a junior estimator looks at the photo set and has a question they cannot answer from the file, the inspection was incomplete and the tech goes back before the file moves forward. That single gate eliminates a large share of downstream leakage.

Leak 2: The soft initial estimate

Even with a complete inspection, revenue leaks when the estimate is built lazily. The most common pattern is the template estimate: a saved scope from a prior job, lightly edited, that omits anything the field package would have supported. Templates are fine as a starting structure and dangerous as a finished product.

Where estimates go soft:

• Quantity rounding down. Squares, linear feet of flashing, and accessory counts get estimated from memory instead of measured. Underclaiming square count on a complex roof is pure leakage.
• Waste factor. Cut-up roofs, steep slopes, and complex hip-and-valley systems carry legitimate waste that a flat template factor understates.
• Detach-and-reset versus replace. Items like gutters, satellite dishes, solar attachments, and detector-style accessories carry different line items depending on whether they are reset or replaced. Defaulting to the cheaper line when the facts support replacement is leakage.
• Steep and high charges. Pitch and height drive labor cost and are standard estimating line items, frequently omitted on template builds.
• Layers. Removal of multiple existing layers is additional labor that gets forgotten when the inspector did not note layer count.

The documentation that plugs it: tie every line item to field evidence and to a measurement source. If your measurements come from an aerial measurement report, the report is the evidence for quantities. If steep and high charges apply, the pitch and story-height from the report or field notes are the evidence. Build the estimate as a factual representation of what the roof requires, item by item, and keep the supporting fact attached to each line. The discipline is simple: no line item without a reason, and no roof requirement without a line item.

Leak 3: Code and manufacturer items that nobody documented at tear-off

This is a quieter leak and a large one. Modern roof systems are governed by the building code your jurisdiction has adopted and by manufacturer installation requirements that condition the warranty. When code or a manufacturer spec requires something the carrier's original estimate did not include, that item is a legitimate part of restoring the roof to a code-compliant, warrantable condition. The catch: the requirement has to be documented as a fact, with a citation, at the moment it applies.

Common examples, depending entirely on your local adopted code and the specific product:

• Ice barrier (ice-and-water shield) in climates where the adopted residential code requires it at eaves to a specified point, or where the manufacturer requires it for the warranty.
• Drip edge where the adopted code requires it at eaves and rakes.
• Decking and fastening requirements when re-sheathing or re-nailing is required to meet current code or to substrate the new system properly.
• Underlayment type and coverage specified by the manufacturer for the chosen product and slope.
• Ventilation required to maintain the manufacturer's warranty for the installed system.
• Starter and ridge cap specified as dedicated accessory products by the manufacturer rather than field-cut from field shingles.

The Building Codes adopted by states and localities derive largely from the International Residential Code published by the International Code Council, but adoption and amendments vary jurisdiction to jurisdiction. That variability is exactly why the documentation has to be specific: cite the code edition and section your jurisdiction has adopted, or the manufacturer's published installation instruction page, and attach it to the file. "Code requires it" is an argument. "The adopted 2021 IRC Section R905.1.2 as amended by our jurisdiction requires an ice barrier here, see attached" is a fact, and facts are what survive review.

The documentation that plugs it: maintain a current reference of your jurisdiction's adopted code and the manufacturer installation instructions for the systems you install. When a tear-off reveals a condition that triggers a requirement (for example, decking that will not hold the specified fastener, or an eave configuration that triggers the ice barrier requirement), photograph it, cite the requirement, and document it at that moment. Tear-off is a one-time window. Once the new roof is on, the evidence of what the old substrate required is gone unless you captured it.

Leak 4: Abandoned supplements

Supplements are where shops lose the most money relative to how recoverable it is. A supplement is additional scope, discovered during the work, that was not on the approved estimate, documented factually and submitted for the carrier's review. Decking that turns out to need replacement once the old roof is off. A satellite mount that has to be reset. A second layer that was not visible until tear-off. These are normal. They are not aggressive. They are the difference between an estimate written before anyone could see the substrate and the reality of the completed job.

The leak is rarely that supplements get denied. The leak is that they never get finished. The pattern is brutally consistent:

1. The crew discovers additional scope at tear-off.
2. Someone takes a photo, maybe.
3. The job gets finished and the crew moves to the next address.
4. The supplement is supposed to get written "when there is time."
5. There is never time.
6. The file closes on the original estimate and the supplement revenue evaporates.

A worked example. A shop completes 120 restoration jobs in a year. On 70 of them, real additional scope appears at tear-off: decking, an extra layer, a reset, code-triggered items. The average legitimate supplement on those jobs is worth, say, several hundred to a couple thousand dollars in earned revenue. If even 40 percent of those supplements never get written or never get followed up to release, the shop has left a meaningful five-figure sum uncollected for the year, on work it already performed. Nobody stole it. It leaked because no one owned the supplement pipeline.

The documentation and workflow that plugs it:

• Capture at the moment of discovery. The crew or super photographs the additional condition with a wide and a tight shot, notes what it is, and flags the job as having a pending supplement before they leave. A discovery that is not captured on-site is usually a discovery that is lost.
• Assign an owner. Every pending supplement has a named person responsible for writing and tracking it. "The team" is not an owner.
• Track status with a due date. Discovered, drafted, internally reviewed, submitted, under carrier review, approved, invoiced, paid. A supplement sitting in any status past its due date is an aging receivable and gets worked like one.
• Submit factual documentation, not arguments. The submission is a request for the carrier to review the attached factual documentation: photos, measurements, the relevant code or manufacturer citation, and the line items those facts support. You are documenting what the job required. The carrier reviews it and decides. You are not telling them what they owe.
• Follow up on a cadence. A submitted supplement with no response is not a closed matter; it is a receivable awaiting action. Work it on a schedule until it resolves one way or the other.

The boundary matters here and it is simple to hold. You document your own scope and your own field observations and you request review of the factual documentation. If the dispute is about coverage, causation, policy interpretation, or whether the homeowner is entitled to something, that is not your lane: route it to the homeowner and, where appropriate, a licensed public adjuster or attorney. The homeowner files and the insurer decides. You keep your supplements on the factual contractor-documentation side, and that is precisely where the recoverable money is.

Leak 5: Unrecovered recoverable depreciation

If abandoned supplements are the most-leaked discretionary revenue, unrecovered recoverable depreciation is the most painful, because it is your money on the carrier's own approved estimate. There is no argument to win. The carrier already agreed to the RCV. They withheld the depreciation pending proof that the work was actually completed. Complete the work, prove it, send the final invoice, and they release it. Fail to prove and invoice, and it stays withheld forever.

How the leak happens:

• The job gets completed but completion is never formally documented (final photos, certificate of completion, final invoice).
• The final invoice never gets generated because the file moved to "done" in the field while it was still "open" on the books.
• Nobody connected the production milestone ("roof complete") to the billing action ("submit proof and invoice for depreciation release").
• The homeowner's mortgage company is holding insurance funds in escrow and the release paperwork never got completed.
• The depreciation deadline in the policy passes while the file sits.

This is the leak that makes owners physically wince when they find it, because it is the most recoverable and the most senseless. The work was done. The roof is on. The money was approved. It simply was never invoiced.

The documentation and workflow that plugs it:

• Make completion a trigger, not a status. The moment a job is marked complete in production, it should automatically generate a depreciation-recovery task: assemble final photos, completion certificate, and final invoice, and submit.
• Standardize completion proof. Final photos of every slope and key detail, signed completion documentation, and the final invoice matching the approved scope. Carriers release depreciation against proof; make the proof package the same every time so nothing gets forgotten.
• Track the depreciation balance as a receivable. For every approved claim, the withheld recoverable depreciation is a known dollar figure. Put it on an aging report. A completed job with unrecovered depreciation is past-due AR and gets worked until the check clears.
• Handle mortgage escrow proactively. When a mortgage holder is endorsed on the insurance check or holding funds, the release process has its own paperwork and its own timeline. Start it early, not at the end.
• Watch the policy deadline. Recoverable depreciation often must be claimed within a defined period after the loss or after ACV payment. Knowing that window per file prevents the worst version of this leak: earned money lost to a calendar.

A shop that simply closes this one leak, with no other changes, often recovers more in a quarter than the cost of the system they used to do it.

Leak 6: Photo and document gaps

Every leak above shares a root cause: evidence that exists but is not organized, or evidence that should exist and does not. The photos are on three different crew phones. The measurement report is in an email. The signed contract is in a filing cabinet. The carrier estimate is a PDF nobody extracted line items from. The tear-off photos are gone because the super's phone storage filled up. When the evidence is scattered, two things happen: legitimate scope goes unclaimed because no one can prove it, and the supplements that do get written take three times as long because someone has to reassemble the file from scratch.

The documentation that plugs it: a centralized, per-claim evidence index where every document and photo lives in one place, tied to the claim, and tagged to the line item or condition it supports. The standard to aim for is page-cited, structured evidence: a carrier estimate is treated as more than a PDF; it becomes a set of extracted line items you can compare against your own scope; a code requirement is not a memory, it is a cited page; a tear-off condition is not a vague recollection, it is a photo with a timestamp and a location. When every gap in the claim is linked to the specific evidence that supports closing it, supplements get written in minutes instead of hours and nothing legitimate goes unclaimed because the proof was lost.

This is also where comparing your scope against the carrier's estimate becomes an internal QA step rather than a dispute. You extract the line items from the carrier's estimate, line them up against your own field-supported scope, and the differences become a checklist of documentation tasks: here is an item on our scope that is not on theirs, here is the field evidence and the code or manufacturer citation that supports it, route it for review. That is internal estimate comparison and factual documentation. It is not negotiation and it is not coverage interpretation.

Leak 7: Overhead and profit left undocumented

Overhead and profit is a standard component of restoration estimating where the complexity of the job supports it, typically expressed as a percentage applied to the estimate. The facts that support O&P are things like the number of trades coordinated on the loss and the complexity of managing the project. The leak is not that O&P is mysterious; it is that the facts supporting it are never documented, so the line is omitted or applied inconsistently.

The documentation that plugs it: capture the trade count and complexity facts as part of the file. If the loss involves roofing plus gutters plus interior plus detached structures, that is a multi-trade coordination fact. If the job is complex to schedule and supervise, document why. You are not arguing entitlement; you are recording the factual characteristics of the project that standard estimating practice ties to O&P, and letting the carrier review the estimate against those documented facts.

Leak 8: Slippage and aging files

The last leak is the one that quietly amplifies all the others: files that age out without anyone watching. A claim has a lot of moving parts and a long timeline, and without a tracking system, files slip into limbo. The ACV got paid but the work never got scheduled. The supplement got submitted but nobody followed up. The depreciation is recoverable but the file shows "complete" with no invoice. Each of these is a file aging silently, and aging files are where recoverable money goes to die.

The documentation and workflow that plugs it: a single source of truth that tracks every claim from inspection to final check, with status and dates at each stage, and an audit trail of who did what and when. The questions it has to answer instantly: Which files have ACV paid but no work scheduled? Which supplements are submitted and awaiting response past their follow-up date? Which completed jobs have unrecovered depreciation? Which files are approaching a policy deadline? When you can answer those in seconds, leakage from slippage approaches zero, because nothing sits unwatched long enough to be forgotten.

A claim revenue-cycle workflow that plugs the holes

The leaks above are not independent; they are stages of one cycle. The way to stop leaking is to run the claim like a managed receivable from first contact to final dollar. Here is a workflow that closes every hole in sequence.

Stage 1 — Inspection (plugs Leak 1). Field tech runs the standardized checklist and captures the required photo set: every slope, penetration, flashing detail, transition, and accessory, plus decking notes and an approximate roof-age range. Output is an evidence package, not a price. Gate: an estimator must be able to build a full scope from the file without questions, or the tech returns.

Stage 2 — Estimate build (plugs Leaks 2, 3, 7). Estimator builds line-by-line from field evidence and measurements. Every line ties to a fact. Code and manufacturer requirements are cited and attached. Trade-count and complexity facts are recorded. No template ships unverified.

Stage 3 — Internal scope QA (plugs Leak 6). Extract the carrier estimate's line items and compare against your field-supported scope. Differences become a documentation checklist, each item linked to its supporting evidence. This is internal review, not negotiation.

Stage 4 — Production with live supplement capture (plugs Leak 4). At tear-off and during the job, crews capture any additional scope on-site with wide and tight photos and a note, and flag the job as having a pending supplement before leaving. Each pending supplement gets an owner and a due date the moment it is discovered.

Stage 5 — Supplement pipeline (plugs Leak 4). Each supplement moves through tracked statuses with due dates: discovered, drafted, internally reviewed, submitted, under review, approved, invoiced, paid. Submissions are requests to review attached factual documentation. Follow-up runs on a cadence. Anything aging gets worked like the receivable it is.

Stage 6 — Completion trigger and depreciation recovery (plugs Leak 5). Marking a job complete auto-generates the depreciation-recovery task: final photos, completion certificate, final invoice, submit. Withheld depreciation sits on an aging report until the check clears. Mortgage escrow and policy deadlines are tracked per file.

Stage 7 — Closeout and audit (plugs Leak 8). No file closes until someone confirms: original scope fully invoiced, all supplements resolved, depreciation recovered or formally accounted for, evidence index complete. The audit trail records the whole cycle so the next file is faster and the patterns are visible.

A closeout checklist you can use tomorrow

Before any restoration file is marked closed, confirm every line:

• Inspection photo set complete for every slope, penetration, flashing detail, and accessory
• Every estimate line item tied to field evidence and a measurement source
• All applicable code and manufacturer requirements cited and attached
• Carrier estimate line items extracted and compared to our scope
• All tear-off discoveries captured on-site with photos
• Every supplement written, submitted, and resolved (approved, invoiced, paid, or formally closed)
• Final completion photos captured for every slope
• Completion certificate signed and on file
• Final invoice submitted for the full approved scope
• Recoverable depreciation invoiced and tracked to payment
• Mortgage escrow release completed if applicable
• Policy deadlines checked and met
• Evidence index complete and page-cited
• Audit trail recorded

A file that passes every line on this list does not leak. A file that skips three of them probably leaks a few hundred to a few thousand dollars, and you will never see it on the P&L.

A worked example: finding the leak in one file

Walk a single representative file to see how the leaks compound and how documentation recovers them.

A homeowner has hail damage. Your tech inspects, shoots a solid photo set, and notes a complex hip roof, three penetrations, an older system, and decking of unknown condition under the existing roof. The carrier approves a replacement at RCV with ACV paid up front and recoverable depreciation withheld pending completion.

Now the leaks line up, and here is how each is plugged:

• Estimate build. The original carrier estimate counted the roof a half-square light and omitted steep charges on the steeper hip sections. Because your estimator built line-by-line from the measurement report rather than accepting the carrier count, the square count and steep charges are documented facts in your scope. Leak 2 plugged.
• Code item. The eave configuration and your adopted code trigger an ice barrier the original estimate did not include. Your estimator cites the adopted code section and attaches it. Leak 3 plugged.
• Tear-off discovery. With the old roof off, three sheets of decking are delaminated and will not hold the specified fastener. The crew photographs each sheet wide and tight, notes it, and flags a pending supplement before leaving the site. Leak 4 capture done.
• Supplement. The supplement manager writes the decking supplement with the on-site photos and the fastening requirement, submits it as a request to review the attached factual documentation, and tracks it to approval. Leak 4 plugged.
• Completion and depreciation. The job is marked complete, which auto-generates the depreciation task. Final photos, completion certificate, and final invoice go out the same week. The withheld depreciation, a four-figure sum on this file, is invoiced and tracked until the check clears. Leak 5 plugged.
• Evidence and audit. Every document lives in one page-cited index. The carrier estimate was extracted and compared, the differences were documented, the audit trail is complete. Leaks 6 and 8 plugged.

In the leaky version of this same file, the estimator accepts the carrier count, the ice barrier never gets cited, the decking photos die on someone's phone, the supplement never gets written, and the depreciation never gets invoiced because the field marked it done and the office never knew to bill it. Same roof. Same homeowner. The difference between the two versions is several thousand dollars of earned revenue, and the only variable is documentation discipline.

How RoofPredict fits the revenue cycle

RoofPredict is built around two linked capabilities, and both sit upstream and alongside the leakage problem rather than on top of it.

The first is targeting: telling you which roofs are due, house by house, by combining a roof-age range read from aerial imagery with storm physics modeled per roof. That is a range, not a date, and a forecast expressed as odds, not proof. It feeds the front of your business by helping crews focus on due and storm-hit roofs and enrich their own CRM and mailing lists, which lowers acquisition cost. It does not write your supplements. It gets the right inspections on the calendar.

The second is the part that touches leakage directly: RoofClaimRCM, the claim revenue-cycle and documentation layer. The idea is to do exactly what this map describes, but systematically. Every document the file touches, your inspection notes, the carrier estimate, code references, manufacturer specs, becomes verified, page-cited, structured data instead of scattered PDFs and phone photos. Every gap between your field-supported scope and the carrier's estimate becomes an evidence-linked, compliance-gated documentation opportunity, tracked from the kitchen table to the depreciation check to the material order. The supplement pipeline has owners, statuses, and due dates. Completion triggers depreciation recovery. Aging files surface before they slip. And every output that touches the insurer side is held behind human approval, because a person, not an automated step, should sign off on anything that leaves your shop for a carrier.

The boundary is enforced by design and worth restating plainly: the platform helps you document your own inspection, your own scope, your own invoices, and your own field evidence, and it helps you request factual review of that documentation. It does not represent the homeowner, interpret their policy, negotiate a settlement, or tell anyone what they are entitled to recover. Coverage disputes, causation disputes, denials, appraisal, and proof-of-loss questions route to a licensed public adjuster or attorney. The homeowner files and the insurer decides. RoofPredict keeps you on the contractor-documentation side, where the recoverable money actually lives.

Honest limits: this is a documentation and revenue-cycle discipline, not a magic recovery button. It will not conjure scope your field team never captured, and it will not approve a supplement the facts do not support. What it does is make sure that the scope you did earn, the supplements that are factually justified, and the depreciation that was already approved do not leak out through dropped follow-through and scattered paperwork. If your shop already runs a flawless cycle, you do not need it. Most shops do not, and the audit usually proves it.

Why the leaks are invisible: the organizational reasons revenue escapes

It helps to understand why these leaks persist in shops run by smart, hard-working people, because the causes are organizational, not personal. Once you see the structural reasons, the fixes stop feeling like nagging and start feeling like plumbing.

The field and the office speak different languages. The crew's job is to get the roof on safely and move to the next address. The office's job is to collect the revenue. Those two clocks run at different speeds. The crew finishes a job and mentally closes it; the office still has weeks of supplement and depreciation work ahead. Without a handoff that forces field discoveries into the billing system, the two halves of the cycle never reconcile, and the gap between them is exactly where money falls.

Nobody owns the back half of the claim. Most shops staff the front of the claim well: salespeople to sign the job, crews to build it. The back half, supplements and depreciation recovery, is treated as administrative overflow that someone handles "when there is time." There is never time, because it is nobody's primary job. The single highest-leverage structural change a shop can make is to give the back half of the claim a named owner whose entire performance is measured on it. The moment a person's compensation is tied to recovered supplements and released depreciation, the leakage that survived a decade of good intentions closes in a quarter.

The work feels finished before it is billed. The most psychologically dangerous moment in a restoration claim is the day the roof is complete. Everyone feels done. The homeowner is happy, the crew is gone, the job photos look great. But financially the file is only partway through: the depreciation is still withheld and the supplements may still be open. A completed roof that is not fully invoiced is a job that feels successful and is silently unprofitable. Naming completion as a billing trigger rather than an ending is the cultural fix.

Small leaks never trigger an alarm. A single dropped supplement worth a few hundred dollars never shows up as a crisis. It is too small to notice and too routine to investigate. The damage is cumulative: a hundred small, individually-ignorable leaks across a year of files add up to a number that would absolutely trigger an alarm if it appeared as one line. The only way to see cumulative leakage is to measure it deliberately, because it will never announce itself.

Evidence has a short shelf life. Tear-off conditions exist for a few hours. Decking that needed replacement, a hidden second layer, the eave configuration that triggered a code item: all of it is buried under the new roof by end of day. If the evidence is not captured in that window, the supplement that depends on it is not weak, it is impossible, because the fact it rested on no longer exists to be photographed. Most missed supplements are not missed at the writing stage; they are missed at the capturing stage, hours earlier, when nobody shot the photo.

Understanding these five causes reframes the whole problem. You are not trying to make people work harder or care more. You are trying to build a cycle where the right capture happens at the right moment, the back half of the claim has an owner, and completion triggers billing instead of relaxation. Discipline beats effort, every time.

Metrics that make leakage visible before it happens

You cannot manage what you do not measure, and most shops measure the front of the business (leads, closes, jobs built) while flying blind on the revenue cycle. A handful of metrics, reviewed weekly, turn invisible leakage into a dashboard a manager can act on.

Metric	What it tells you	Healthy direction
Supplement capture rate	Share of jobs with tear-off discoveries that got a supplement written	Approaching the share of jobs that genuinely had additional scope
Supplement cycle time	Days from discovery to submission	Short and shrinking; long times mean abandonment risk
Depreciation recovery rate	Share of approved recoverable depreciation actually collected	As close to full as the files allow
Days-to-invoice after completion	Days from job complete to final invoice submitted	Single digits
Aged file count	Files past expected duration at any stage	Trending toward zero
Evidence completeness	Share of files that pass the closeout checklist on first review	High and stable

The two that matter most are supplement cycle time and days-to-invoice after completion, because they are leading indicators. A supplement that is still unsubmitted three weeks after discovery is on the path to abandonment, and you can intervene now rather than discover the loss at year-end. A completed job that has gone two weeks without a final invoice is depreciation on the verge of leaking, and a single phone call recovers it. Lagging metrics like annual recovery rate tell you what already leaked; leading metrics like cycle time let you stop the leak while the money is still on the table. Review the leading indicators weekly and the lagging ones monthly, and leakage shifts from something you discover after the fact to something you prevent in real time.

How to audit your own leakage this month

You do not need any new tool to find out how much you are leaking. You need one afternoon and a sample of closed files. Pull twenty to thirty restoration files that closed in the last six months and check each against five questions:

1. Scope completeness. Did the final invoiced scope include every legitimate item the field evidence supported, or did flashing, accessories, or code items get dropped?
2. Supplement follow-through. Were there tear-off discoveries that never became written, submitted, resolved supplements?
3. Depreciation recovery. Was the recoverable depreciation actually invoiced and collected, or is it still withheld on a completed job?
4. Evidence integrity. Could you reconstruct the full claim from the file today, or is the evidence scattered or missing?
5. Timeline slippage. How long did each file sit at each stage, and did any age out near a policy deadline?

Tally the dollars attached to every "no." That number, annualized across your file volume, is your leakage. It is almost always larger than owners expect, and it is almost always recoverable through process rather than dispute, because it is earned money lost to paperwork, not contested money lost to a carrier.

The roofing companies that win the restoration game over the next few years will not be the ones who chase the most aggressive claims. They will be the ones who stop leaking the legitimate revenue they already earn, file after file, by treating every claim as the managed receivable it is, documenting their own scope with discipline, and keeping every insurer-facing output on the factual, human-approved, contractor-documentation side of the line. The leaks are findable. The fixes are procedural. And the money is already yours, sitting in your own closed files, waiting to be invoiced.

FAQ

What is roofing claim revenue leakage?

It is the gap between the revenue a restoration job legitimately should have produced and what you actually collected. It hides in missed scope at inspection, soft estimates, omitted code and manufacturer items, supplements that get discovered but never submitted, and recoverable depreciation that is approved but never invoiced. It is earned money lost to paperwork and dropped follow-through, not money won in a dispute.

How much revenue do roofing contractors typically leak on claims?

Practically, shops that honestly audit a year of closed files describe a band of roughly 10 to 30 percent of legitimate restoration revenue leaking out. That is not a guarantee for your shop and not a fabricated benchmark; it is the range production and supplement managers tend to find. Disciplined shops leak almost nothing, while shops with no managed revenue cycle often leak more than they expect.

Where does the most claim revenue leak out?

Two places dominate: abandoned supplements, where additional scope is discovered at tear-off but never gets written or followed up, and unrecovered recoverable depreciation, which is your money on the carrier's own approved estimate that never gets invoiced because completion was never formally proven. Missed scope at the original inspection is the largest upstream source because it removes items from the claim before it is even built.

What is recoverable depreciation and why does it leak?

Recoverable depreciation is the difference between Actual Cash Value and Replacement Cost Value that the carrier withholds until you complete the work and prove it. It leaks when completion is never formally documented, the final invoice never gets generated, the production milestone is never connected to a billing action, or a policy deadline passes. The carrier already approved the RCV, so this is the most recoverable and most senseless leak.

How do I keep supplements from getting abandoned?

Capture additional scope at the moment of discovery on-site with wide and tight photos, assign every supplement a named owner, track it through statuses with due dates (discovered, drafted, reviewed, submitted, under review, approved, invoiced, paid), submit factual documentation rather than arguments, and follow up on a cadence. The most common failure is that nobody owns the pipeline, so legitimate supplements simply never get written.

Can a roofing contractor document claim items without acting as a public adjuster?

Yes. You document your own inspection, scope, invoices, and field evidence, and you request factual review of that documentation. That is contractor-side activity. What you cannot do without proper licensing is represent the homeowner, interpret their policy, negotiate a settlement, or tell them what they are entitled to recover. Coverage and causation disputes, denials, appraisal, and proof of loss route to a licensed public adjuster or attorney. The homeowner files and the insurer decides.

How do code and manufacturer requirements affect claim revenue?

When your jurisdiction's adopted building code or the manufacturer's installation instructions require an item the original estimate omitted, that item is a legitimate part of restoring the roof to a code-compliant, warrantable condition. Revenue leaks when the requirement is never documented as a fact with a citation at the moment it applies. Cite the adopted code section or the manufacturer's published installation page and attach it to the file, especially at tear-off, since that evidence window closes once the new roof is on.

What is the difference between a supplement and the original estimate?

The original estimate is built before anyone can see the substrate. A supplement documents additional scope discovered during the work that was not on the approved estimate, such as decking that needs replacement, a hidden second layer, or a reset that emerges at tear-off. Supplements are normal and factual, not aggressive. They are submitted as requests for the carrier to review the attached field documentation, and they are where a large share of recoverable revenue sits.

How can I audit my own shop's claim revenue leakage?

Pull twenty to thirty restoration files that closed in the last six months and check each for scope completeness, supplement follow-through, depreciation recovery, evidence integrity, and timeline slippage. Tally the dollars attached to every gap and annualize across your file volume. That figure is your leakage, and it is almost always recoverable through better process rather than through any dispute with a carrier.

Does RoofPredict help with claim revenue leakage?

Its RoofClaimRCM capability is a claim revenue-cycle and documentation layer that turns the file's documents into page-cited structured data, tracks the supplement pipeline with owners and due dates, triggers depreciation recovery at completion, and surfaces aging files, with human approval guarding everything insurer-facing. It keeps you on the contractor-documentation side of the line. It is a documentation discipline, not a magic recovery button: it will not conjure scope your team never captured or approve a supplement the facts do not support.