Roofing Claim Revenue Cycle Management, Explained

Most roofing companies that do storm work track their money in two buckets: did we sell the job, and did we collect the check. Everything in between gets lumped into a vague pile called "waiting on insurance." That pile is where margin goes to die. A job can be sold, built, and signed off and still bleed three weeks of cash flow, a supplement that never got written, and a depreciation balance the homeowner forgot to release. Revenue cycle management is the discipline that turns that murky middle into a tracked, staffed, repeatable process — the same way a hospital or a dental practice manages the gap between treating a patient and getting paid.

The term comes straight out of healthcare, where "RCM" describes every step from the moment a patient is scheduled to the moment the last dollar of a claim is collected. Roofing borrowed almost nothing from that playbook, and it shows. The average residential storm roofer loses real money to slow file movement, missed line items, depreciation that sits uncollected for 90+ days, and a back office that finds out a claim stalled only when the homeowner calls angry. The roofers who win the long game treat each insurance-related job as a file that moves through defined stages, with a person responsible at each stage and a number attached to each handoff.

A hard line first, because it governs everything below. A roofing contractor can inspect a roof, document damage with photographs and measurements, and prepare an accurate repair estimate for their own scope of work. The contractor can state facts about that scope to the carrier — what they found, what it costs to fix correctly to code. What a contractor cannot do, unless they hold a public adjuster license, is negotiate or "handle" the claim on the homeowner's behalf, interpret the homeowner's policy or coverage, promise a specific approval or payout, promise the deductible will be waived or absorbed, advertise a "free roof," or represent the homeowner against their insurer. That last cluster is unlicensed public adjusting, and it is illegal in most states. So when this piece talks about "managing the claim cycle," it means managing your documentation and your estimate through the cycle — being fast, accurate, and thorough on the parts that are legally yours. The homeowner files. The insurer decides coverage. You document and you build. Keep that wall clean and the rest of the system is safe.

What "revenue cycle management" actually means for a roofer

In healthcare, RCM has a clean definition: the financial process that tracks revenue from a patient's first contact through the final payment, including eligibility, coding, claim submission, denial management, and collections. Strip out the medical vocabulary and the skeleton maps onto roofing almost perfectly.

Here is the translation:

Healthcare RCM stage	Roofing equivalent
Patient scheduling & eligibility	Inspection booked; confirm the homeowner has a claim or is filing one
Charge capture / coding	Damage documentation + line-item estimate built to match the loss
Claim submission	Homeowner files; your estimate and photos support their claim
Adjuster review	Carrier inspection; you meet the adjuster on the roof
Payment posting	First insurance check (ACV) received and applied
Denial / underpayment management	Supplement: documenting missed or underpriced line items
Patient responsibility / collections	Deductible collected; recoverable depreciation released after completion

The point of borrowing the framework is not vocabulary. It is the mindset that every file has a clock running on it, that a file stuck between stages is costing money, and that someone owns the movement at each step. A roofer who internalizes that stops asking "did this job close" and starts asking "where is every open file right now, and what is the next action that moves it forward."

The financial reality is blunt. A storm job's gross profit is set when you sell it, but the realized profit — what actually lands in your account — is set by how cleanly the file moves. Two companies can sell the identical $18,000 reroof. One collects the full amount in 38 days with a complete supplement. The other collects $14,200 in 96 days because they never wrote the supplement, ate a chargeback on a code item, and wrote off $1,100 of depreciation the homeowner never released. Same sale. Wildly different business.

The roofing claim revenue cycle, stage by stage

Below is the full cycle a typical residential storm file moves through. Treat each stage as a station on an assembly line: it has an entry condition, a defined set of actions, an owner, and an exit condition that triggers the next stage. Job numbers and named stages are how you keep 60 open files from turning into chaos.

Stage 1 — Inspection and qualification

Entry: A homeowner agrees to a roof inspection, usually after a wind or hail event, or because their roof is visibly aging.

Actions: You get on the roof, document the condition, and make an honest call about whether there is storm-related damage worth pursuing. This is a fork. If the damage is real and storm-caused, the homeowner may have a viable claim. If the roof is simply old and worn — no storm signature — that is a retail replacement, not a claim, and you should say so plainly. Conflating the two is how roofers get into trouble: filing a claim on an old, undamaged roof invites a denial and, worse, can look like encouraging insurance fraud.

What pros get wrong here: They qualify for "will this homeowner sign" instead of "is there a defensible claim." A signed contingency agreement on a roof with no real storm damage is a file that will stall at the adjuster and burn your reputation with that carrier's local adjusters, who talk to each other.

Owner: Sales rep / inspector.

Exit condition: A documented determination — storm damage present (proceed toward a claim the homeowner files) or not (offer retail or walk).

Stage 2 — Documentation

Entry: Storm damage confirmed at inspection.

This is the single highest-leverage stage in the cycle, and it is the one most roofers rush. The quality of your documentation determines how much of your estimate survives the adjuster, how strong your supplement is later, and whether the file moves in 30 days or 90. Documentation is also squarely inside the contractor's legal lane: you are recording facts about the roof condition and your scope, not opining on coverage.

A complete documentation package for one roof includes:

• Date-stamped, geotagged photos of every slope, every penetration, and every elevation. Wide shots for context, tight shots for individual hits.
• A hail/wind damage test square on each slope — a chalked 10' x 10' area with hits circled and counted, photographed. This is the industry-standard way to show density of impact.
• Collateral damage photos: dented gutters, downspouts, soft metals (vents, flashing, AC fins), window screens, fascia. Collateral damage corroborates that hail of a damaging size actually fell.
• Accurate measurements — total squares, pitch, ridge/hip/valley/eave/rake linear footage, penetration counts, layers. An aerial measurement report or a careful hand measurement; either way, it must be defensible.
• Code documentation for anything your local code requires on a reroof (ice-and-water shield coverage, drip edge, ridge ventilation, decking re-nail). Pull the actual code citation.
• A test-square diagram and a roof diagram noting where each photo was taken.

What pros get wrong: Soft metals and code items. The hits on the shingles are obvious; the dented furnace cap, the bent ridge vent, and the code-required ice-and-water shield are where supplements live. If it is not photographed and noted now, you will be fighting to add it later.

Owner: Inspector / documentation specialist.

Exit condition: A complete, organized photo and measurement package attached to the job file.

Stage 3 — Estimate construction

Entry: Documentation complete.

You build a line-item estimate of what it costs to repair the roof correctly, to code, in your market. Most storm-active roofers build this in Xactimate, the estimating platform carriers use, because pricing the loss in the same line-item language the carrier speaks removes friction. Your estimate is a fact about your scope and your cost — it is not a coverage opinion and it is not a demand. The homeowner submits it in support of their claim; the carrier decides what they will pay.

A defensible estimate:

• Uses current Xactimate price-list pricing for your ZIP, not last year's, and not made-up numbers.
• Itemizes every component — tear-off by layer, felt/synthetic, ice-and-water by code-required footage, shingles, ridge, starter, drip edge, valley metal, pipe jacks, vents, flashing, and the labor for each.
• Includes code-upgrade line items with the code citation attached. If your jurisdiction requires a full ice-and-water replacement or a decking re-nail to current standards, that is a real cost of building the roof correctly.
• Accounts for steep and high charges, two-story access, and detach-and-reset of anything mounted (satellite, solar — with the right specialty subcontractor noted).
• Flags waste correctly — hip-and-ridge and starter generate waste that a flat percentage misses.

What pros get wrong: Underpricing their own estimate to "match" what they assume the carrier will pay. That is backward. Build the estimate to the true, correct cost of the work. If the carrier's number is lower, that gap is exactly what the supplement stage exists to document — line by line, with evidence.

Owner: Estimator.

Exit condition: A complete line-item estimate ready to hand to the homeowner and to reconcile against the carrier's estimate.

Stage 4 — Carrier inspection (the adjuster meeting)

Entry: Homeowner has filed; the carrier schedules a field adjuster (or, increasingly, a virtual/drone inspection).

You — or your designated representative — meet the adjuster on the roof. Your job is to walk them through what you documented: show the test squares, the collateral damage, the code requirements. You are presenting facts. You are not arguing coverage, you are not telling the adjuster what the policy "should" do, and you are not promising the homeowner anything about the outcome.

Field notes that matter:

• Be on the roof before the adjuster if you can, so you are showing, not scrambling.
• Bring your test-square chalk, a tape, and your photo set on a tablet.
• Hand the adjuster a clean copy of your line-item estimate and your code citations. Many adjusters appreciate a contractor who hands them organized facts — it makes their write-up faster.
• Take your own photos of the adjuster's marked test squares.
• Note what the adjuster agrees to verbally versus what shows up on their estimate; those often differ, and the difference is your supplement.

What pros get wrong: Treating the adjuster as an adversary. The field adjuster is a busy professional documenting a loss for their employer. A contractor who is organized, factual, and respectful gets cleaner write-ups. A contractor who lectures the adjuster about coverage gets a reputation and slower files.

Owner: Sales rep / claims coordinator.

Exit condition: Carrier issues a scope and an ACV (actual cash value) estimate.

Stage 5 — Scope reconciliation

Entry: Carrier's estimate received.

Now you line up the carrier's estimate against yours, line by line. This is pure clerical comparison, and it is where money is found or lost. You are looking for:

• Line items you have that they missed — ice-and-water by code, drip edge, a second layer of tear-off, soft metals, detach-and-reset.
• Quantities that are short — they wrote 28 squares; you measured 31. They wrote 40 LF of ridge; you measured 64.
• Pricing that is below the current price list for your ZIP.
• Code items omitted that your jurisdiction actually requires.

Build a reconciliation table. One row per discrepancy, with the carrier's value, your value, the delta, and the evidence (photo number, code citation, measurement). That table is your supplement.

Owner: Estimator / supplement specialist.

Exit condition: A documented list of discrepancies, each with evidence.

Stage 6 — Supplement

Entry: Reconciliation shows the carrier's scope is short.

A supplement is a request to the carrier to revise their estimate to reflect the true, complete, code-compliant cost of the repair — supported by evidence. It is not a negotiation tactic and it is not padding. Every supplemented line must be a real component of building the roof correctly, with documentation behind it. This stays inside the contractor's lane as long as you are documenting the cost of your own scope, not arguing the homeowner's coverage.

A clean supplement package:

1. A cover sheet referencing the claim number, the property, and the date of loss.
2. The reconciliation table — carrier value, your value, delta, evidence per line.
3. Supporting photos for each supplemented item.
4. Code citations for each code-upgrade item.
5. Your revised line-item estimate.

What pros get wrong, repeatedly:

• They skip the supplement entirely because the back office is overwhelmed. This is the single most expensive mistake in storm roofing. An unwritten supplement is a 100% write-off of money that was owed for real work.
• They supplement without evidence, which trains adjusters to ignore them.
• They supplement late, after the job is built and the photos are gone. Document for the supplement before you tear off.
• They talk about the deductible. Never. The deductible is the homeowner's responsibility, full stop. Any suggestion that you will absorb it, eat it, or make it disappear is insurance fraud in most states and will end a company.

Owner: Supplement specialist.

Exit condition: Carrier issues a revised estimate (approved supplement) or a written denial of specific items.

Stage 7 — Production

Entry: Scope agreed (or agreed-enough to build), materials ordered, homeowner scheduled.

The roof gets built. From a revenue-cycle standpoint, production is also a documentation stage: photograph the decking once the old roof is off (this is where you catch — and document — rotten or non-code decking that becomes a legitimate supplement), photograph code items as installed, and capture the completed roof. Those photos support both the final invoice and any post-production supplement.

Owner: Production manager.

Exit condition: Job complete, final photos captured, certificate of completion signed.

Stage 8 — Invoicing and depreciation release

Entry: Job complete and documented.

Most storm checks come in two parts. The carrier first pays ACV (actual cash value) — the depreciated value of the roof — and holds back recoverable depreciation until the work is proven complete. Once you submit proof of completion (final invoice, completion certificate, photos), the carrier releases the recoverable depreciation. The homeowner pays their deductible. That is the structure, and it is the homeowner's money and the homeowner's claim — your role is to invoice your work accurately and submit clean completion proof.

This stage is where uncollected money piles up. Recoverable depreciation does not release itself. If nobody submits the completion paperwork, that money sits — sometimes for months, sometimes forever, because depreciation can expire if not claimed within the policy's timeframe (often 180 days to a year, varying by policy and state).

Owner: Back office / billing.

Exit condition: Final invoice sent, completion documents submitted to the carrier, depreciation release requested.

Stage 9 — Collections and reconciliation

Entry: Invoice out, depreciation requested.

Collect the deductible from the homeowner, collect the depreciation release from the carrier, and reconcile the total received against your estimate. Close the file only when the math ties out: ACV + recoverable depreciation released + deductible collected = your agreed contract amount, with any approved supplements added.

Owner: Back office.

Exit condition: Full payment received, file reconciled and closed.

The metrics that actually run the cycle

You cannot manage what you do not measure, and "we're busy" is not a metric. Here are the numbers a roofing revenue cycle lives and dies on. Track them per file and in aggregate.

Days in cycle (and days per stage)

The total clock from inspection to final payment, and — more useful — the clock per stage. If files routinely sit 18 days between "carrier estimate received" and "supplement submitted," you have found your bottleneck. Healthcare RCM teams obsess over "days in accounts receivable"; roofers should obsess over days-per-stage, because that is where you find the specific handoff that is leaking time.

Supplement capture rate

What percentage of your storm files get a supplement written, and what is the average supplement dollar amount and approval rate? A shop that supplements 30% of eligible files is leaving money on the table compared to one that supplements 85% with evidence. Track both the attempt rate (did we even write it) and the approval rate (did it hold up).

Recoverable depreciation collected vs. released-eligible

Of all the depreciation that became collectible (job done, paperwork submittable), how much did you actually collect? This number should be near 100%. If it is 80%, one in five completed jobs is leaking its depreciation tail.

Cycle write-off rate

Dollars written off per closed file — chargebacks, uncollected depreciation, eaten code items, missed supplements. This is the truest measure of back-office health.

Stuck-file count

How many open files have had no forward action in 14 days? This is your early-warning system. A growing stuck-file count means the cycle is clogging before it shows up in cash flow.

Here is a simple monthly scoreboard worth keeping:

Metric	Healthy target	Red flag
Avg. days in cycle (inspection → final pay)	Under 45	Over 75
Supplement attempt rate (eligible files)	80%+	Under 50%
Avg. days, carrier estimate → supplement filed	Under 5	Over 14
Recoverable depreciation collected	97%+	Under 90%
Stuck files (no action 14+ days)	Under 10% of open	Over 25%
Write-off per closed file	Trending down	Trending up

These are reasonable operating targets, not industry-published figures — calibrate them to your own baseline once you start measuring, and chase your own trend line rather than someone else's number.

A worked example: one file, two outcomes

Make it concrete. Same house, same storm, two different back offices.

The job: A 31-square architectural shingle reroof after a hail event. True replacement cost, built to code: $19,400, which includes $1,250 of ice-and-water shield required by local code, $480 of soft-metal replacement (gutters and a furnace cap), and a detach-reset on a satellite dish.

Company A (no revenue cycle discipline):

• Documented the shingle hits but not the soft metals or the code items.
• Built the estimate to "about what insurance usually pays" — $16,800.
• Carrier wrote an ACV scope at $14,100 with $2,700 recoverable depreciation, total RCV $16,800. Deductible $1,000.
• No reconciliation, no supplement.
• Built the job. Found rotten decking, ate the $600 because nobody documented it for a supplement.
• Homeowner moved out of state before paperwork went in; depreciation release sat for five months and the back office forgot it. Lost $2,700 of recoverable depreciation.
• Collected: $13,100. Built a $19,400 roof. Realized margin: negative before overhead.

Company B (managed cycle):

• Documented hits, soft metals, code items, and shot the decking during tear-off.
• Built the estimate to true cost: $19,400, with code citations.
• Carrier's first scope came in at $16,800, same as above.
• Reconciliation found: ice-and-water shorted by code ($1,250), soft metals omitted ($480), satellite detach-reset omitted ($90), decking documented during production ($600), and a square count short by 1.5 squares.
• Filed a supplement with photos and code citations. Carrier approved $19,250 of it.
• Submitted completion paperwork the day the job finished; depreciation released in 21 days.
• Collected the $1,000 deductible at completion, as agreed up front.
• Collected: ~$19,250 plus deductible. Built the same roof. Realized the margin they sold.

The difference is not sales skill. Both companies sold the job. The difference is six thousand dollars of cycle discipline on one file — documentation, reconciliation, a written supplement, and somebody actually submitting the completion paperwork on time.

The compliance wall — the do-not-say list

Everything above only works if you stay on the right side of the line. The fastest way to blow up a storm roofing company is to drift into unlicensed public adjusting. Print this list and put it where your reps and your back office can see it.

Never say or do any of the following (in person, in ads, on your website, or on a yard sign):

• "We handle the claim for you" / "we deal with the insurance company." You document and you build. The homeowner files and communicates with their carrier. Handling the claim for a fee, without a PA license, is unlicensed public adjusting.
• "We'll get your claim approved" / "you're definitely covered." You do not decide coverage and you cannot promise an outcome. The carrier decides.
• "We'll waive your deductible" / "your deductible is covered" / "no out-of-pocket." Deductible manipulation is insurance fraud in most states. The deductible is the homeowner's legal responsibility and you collect it.
• "Free roof." Same problem. It implies the deductible vanishes and a guaranteed approval. Banned.
• Interpreting the policy. "Your policy covers X" or "they owe you Y under your coverage" is interpreting coverage — a licensed activity.
• Negotiating on the homeowner's behalf against the insurer. Stating facts about your scope to an adjuster is fine. Advocating for the homeowner's claim as their representative is public adjusting.
• Promising a specific payout number. You can state your estimate's cost. You cannot promise what the carrier will pay.

What you absolutely can do (and should do better than anyone):

• Inspect and honestly assess storm damage.
• Photograph and document thoroughly.
• Build an accurate, code-compliant, line-item repair estimate for your scope.
• State facts about your scope and findings to the field adjuster.
• Write an evidence-backed supplement for the true cost of your work.
• Hand the homeowner clean documentation so they can file and manage their claim.
• Collect your deductible and invoice your completed work accurately.

The mental model: you are the roof expert and the documentation expert. The homeowner is the policyholder who files and decides. The carrier decides coverage. Stay in your lane and you can be aggressive, thorough, and fast on the parts that are yours — which is exactly where the money is anyway.

State licensing varies, so check your own. Several states require a registration or license specifically for contractors doing roofing work tied to insurance claims, and many have explicit statutes against deductible rebating and against contractors acting as public adjusters. Your state Department of Insurance (in Texas, the Texas Department of Insurance) is the authority; read your state's rules before you write a word of claims-adjacent advertising.

Building the system: roles, software, and handoffs

A managed revenue cycle is mostly an org-chart problem and a handoff problem. The work is not hard; the coordination is where it falls apart. Here is how the better shops structure it.

Roles

In a small shop, one person may wear several of these hats — but the functions still need to exist and someone needs to own each.

• Inspector / sales rep — owns Stages 1–2 (qualify and document) and represents you at the adjuster meeting (Stage 4).
• Estimator — owns Stages 3 and 5 (build the estimate, reconcile against the carrier).
• Supplement specialist — owns Stage 6. In shops doing real volume, this is a dedicated role or an outsourced service, because supplementing well is a specialized skill and it pays for itself many times over.
• Production manager — owns Stage 7, including the production-phase documentation that feeds post-build supplements.
• Back office / billing — owns Stages 8–9: invoicing, depreciation release, deductible collection, reconciliation, file closeout.
• Cycle owner — somebody (often the owner or an ops manager) who watches the whole board, hunts stuck files, and owns the metrics. This role is the difference between a system and a pile.

Software

You do not need an enterprise stack. You need three things that talk to each other or at least share a job number:

1. A CRM with stage tracking. The job moves through named stages, with the current stage, owner, and last-action date visible at a glance. Roofing-specific CRMs (JobNimbus, AccuLynx, and similar) are built around exactly this pipeline; a general CRM works if you configure the stages.
2. An estimating platform — Xactimate for claims work, because pricing in the carrier's own price list removes friction.
3. A measurement/documentation source — aerial measurement reports plus an organized photo system, so the documentation package is consistent and defensible.

The non-negotiable is that every file has a current stage and a last-action date. That single discipline surfaces stuck files automatically. If your CRM cannot tell you "show me every file with no action in 14 days," you cannot manage the cycle — you can only react to it.

Handoffs

Most leakage happens at handoffs, not within stages. The estimator finishes and the file sits because nobody told the supplement specialist. The job finishes and the completion paperwork sits because production thinks billing has it and billing thinks production has it. Fix this with explicit exit conditions: a stage is not done until its exit artifact exists and the next owner has been pinged. Make the handoff a tracked event, not an assumption.

Where the cycle starts: working the right roofs in the first place

Every word above assumes a file already exists — a homeowner agreed to an inspection. But the economics of the whole cycle are set before the cycle begins, by which roofs you bother to inspect. Run a clean revenue cycle on the wrong roofs and you are just being efficient at chasing dead files: a new roof with no storm damage will stall at the adjuster no matter how good your back office is, and an old roof the storm never touched is a retail conversation, not a claim.

The roofs worth a claims-track inspection are the ones where two things line up: the roof is old enough to be near or past its service life, and it actually took a damaging storm. Age without a storm is a retail replacement. A storm without age (a two-year-old roof in a hail swath) might have damage, but it is a tougher, more scrutinized file. The sweet spot — and the cleanest files — sit where an aging roof met real wind or hail.

This is where RoofPredict fits into the front of the cycle. It reads aerial imagery to estimate a roof-age range per address (a range, not an install date — re-roofs are invisible to county "year built" records), and it models storm physics per roof rather than just telling you a ZIP code got hailed. A hail map shows you where it hailed; modeling impact roof by roof gets you closer to which roofs in that swath likely took a damaging hit, paired with whether each roof was old enough for that hit to matter. You can also enrich a list you already own — past customers, old estimates, a mailing list — with roof-age and storm signals, so your inspectors spend their windshield time on the addresses most likely to produce a defensible, fully collectible file instead of a stall.

Two honest limits, because the data only earns trust if the limits are stated. Roof age comes back as a range, not a precise date — useful for ranking and routing, not a substitute for getting on the roof. And storm modeling gives you odds, not proof: it tells you which roofs most likely took a damaging hit, which is exactly what you want for prioritizing inspections, but the actual damage determination still happens with your eyes, your chalk, and your camera on the roof. Used that way — to point the front of the cycle at the right doors — better targeting compounds through every downstream stage: cleaner qualification, stronger documentation, fewer stalled files, faster collections.

A 30-day plan to install a revenue cycle in your shop

You do not roll this out all at once. Sequence it.

Week 1 — Make the cycle visible.

• Define your stages (use the nine above or adapt them) in your CRM.
• Put every open storm file into a stage. Yes, all of them. This first audit alone usually surfaces five to fifteen stuck files holding real money.
• Add a "last action date" to every file.

Week 2 — Fix the back of the cycle first (fastest cash).

• Pull every completed job with unreleased recoverable depreciation. Submit the completion paperwork on each. This is money you already earned; collect it.
• Pull every open file with no action in 14+ days and assign a next action and an owner to each.

Week 3 — Install the supplement habit.

• For every file at "carrier estimate received," build the reconciliation table.
• Write supplements with evidence on every one that is short. If you do not have the in-house skill, this is the stage most worth outsourcing or hiring for; it pays for itself on the first file.

Week 4 — Lock the front of the cycle.

• Standardize your documentation package so every inspector produces the same complete photo-and-measurement set (test squares, soft metals, code items, decking shots during production).
• Tighten qualification so you stop opening files on roofs that will stall — point inspections at roofs that are both old enough and storm-hit.
• Set up your monthly scoreboard and pick the one metric you will move next month.

Then run it. The system is not finished in 30 days; 30 days is how long it takes to make the cycle visible and stop the most obvious bleeding. The compounding comes from running the scoreboard month after month and chasing your own bottleneck each time.

The line items adjusters most often miss — and how to document each

Reconciliation gets faster once you know where the gaps usually are. The same handful of items go short or get omitted on file after file, because they are the parts a quick adjuster write-up glosses over. None of these are tricks. Each is a real cost of building the roof correctly, and each needs its own piece of evidence to hold up. Keep a running checklist so your estimator hunts for them every time.

Commonly missed item	Why it gets missed	Evidence that holds it
Ice-and-water shield (code footage)	Adjuster prices the old felt-only roof, not current code coverage	The code citation for required eave/valley coverage in your jurisdiction, plus your measured linear footage
Drip edge	Often omitted entirely on older scopes	Code requirement + photo of existing (or absent) drip edge
Second-layer tear-off	Adjuster assumes one layer	Photo at an edge or vent showing two layers
Steep / high charges	Defaulted to standard pitch and one story	Pitch measurement and a two-story elevation photo
Soft metals (gutters, vents, furnace cap, AC fins)	Eyes go to the shingles	Tight collateral-damage photos of each dented component
Detach-and-reset (satellite, solar, lightning rods)	Not visible from the ground	Photo of the mounted equipment; specialty sub noted for solar
Ridge ventilation to code	Scoped as box vents when code or design calls for ridge vent	Code/design citation + ridge linear footage
Decking replacement / re-nail	Hidden until tear-off	Photo of rotten or non-code decking taken during production
Valley metal	Lumped into shingle line	Measurement of valley linear footage + photo
Waste factor on starter and ridge	Flat percentage misses these	Itemized starter and hip-and-ridge quantities

The pattern is consistent: the missed money is in the components you cannot see from the driveway and the code items a generic price list does not assume. An estimator who works this checklist on every file turns reconciliation from a guess into a routine, and turns the supplement from an occasional scramble into a standard step.

Denials and underpayments: read them, do not fight them blind

When a carrier denies an item or a whole claim, the denial comes with a reason. Read it before you react, because the reason tells you exactly what evidence is missing — and whether the gap is even yours to address.

Common reasons you will see on roofing files:

• "No storm-related damage observed." The carrier's adjuster did not see what you saw, or you did not document it well enough. The fix is evidence: your dated test squares, your collateral damage, and the storm date tied to that property. This is a documentation problem, and documentation is your lane.
• "Damage is from wear / age, not a covered peril." This is the qualification fork coming back to bite. If the roof genuinely took storm damage, your dated photos and collateral evidence are the answer. If it was actually old and worn with no storm signature, the carrier is right and you should never have opened a claim file — that was a retail roof.
• "Cost exceeds policy limits" or coverage questions. Stop. This is a coverage and policy-interpretation matter, and it is squarely the homeowner's and the carrier's to work out — not yours. You can hand the homeowner your clean documentation so they can pursue it; you cannot interpret their policy or argue their coverage.
• Underpayment (partial scope). This is the most common outcome and the one fully inside your lane: the carrier covered the loss but priced it short. That is a reconciliation-and-supplement problem, handled with the line-item evidence above.

The discipline here is sorting denials into two bins fast: documentation/pricing gaps you can address with evidence about your scope, versus coverage decisions that belong to the homeowner and the carrier. Pour your effort into the first bin. Hand the second bin to the homeowner with good documentation and stay out of it.

Cash flow inside the cycle

Even a perfectly managed file has a cash-flow shape, and the shop has to fund the gap. Materials and a chunk of labor get spent during production, but the recoverable depreciation does not land until after completion and paperwork. That gap — often the largest single piece of the job's value — is real working capital you front.

Three honest ways shops manage it, none of which involve touching the homeowner's deductible:

1. Sequence the carrier payments correctly. The ACV check should arrive before or around production start. Do not order materials and schedule a crew on a file where the first carrier payment has not posted; that is how a shop funds a roof entirely out of pocket and then waits 60 days.
2. Collect the deductible at the agreed milestone. The deductible is the homeowner's responsibility and a normal part of your contract. Collect it on the schedule you set up front — never waive it, never advertise that it disappears.
3. Submit depreciation-release paperwork the day the job closes. Every day that paperwork sits is a day your largest receivable is parked. The cheapest cash-flow improvement in the whole cycle is a back office that fires completion documents the moment the crew rolls off the roof.

Map your own cycle's cash shape once — dollars out at production versus dollars in at each carrier milestone — and the funding gap stops being a surprise that shows up as a tight payroll week.

Reading the cycle as a board, not a list

The operational shift for most owners is to stop thinking of jobs as a list and start seeing them as a board where every card sits in a column (a stage) and every card has an age (days since last action). When you look at the board instead of the list, the problems announce themselves: a column with too many cards is an understaffed stage, an old card in any column is a stuck file, and a column where cards arrive faster than they leave is your bottleneck.

Run a ten-minute board review twice a week. Three questions only: Which column is backing up? Which cards have not moved in 14 days, and who owns the next action? Did any card skip its exit artifact (a stage marked done with no photo set, no reconciliation table, no completion paperwork)? That short, boring meeting is what converts a pile of jobs into a managed cycle. It is also where you catch the file that is about to lose its depreciation window before the window closes, not after.

What separates the shops that own this

The roofers who run a tight revenue cycle are not smarter or better at sales. They have simply decided that the murky middle — the part between the handshake and the final check — is a business process worth staffing, measuring, and improving, instead of a black box labeled "waiting on insurance." They document like the supplement depends on it, because it does. They reconcile every carrier estimate, because that is where money is found. They submit completion paperwork the day the job ends, because depreciation does not release itself. And they stay rigorously on the documentation-and-estimate side of the legal line, because the company that drifts into handling claims or erasing deductibles does not get to have a long game at all.

Point that disciplined cycle at the right roofs — old enough and genuinely storm-hit — and the whole machine runs cleaner, because you are not spending it on files that were never going to collect. That is the entire game: the right roofs in the front, a measured cycle in the middle, and a clean compliance wall around all of it.

If you want help with the front of that cycle — ranking which roofs in your area are old enough and likely storm-hit enough to produce a defensible, fully collectible file — that is what RoofPredict was built for. Book a demo and bring a street you already know, so you can judge for yourself whether the targeting holds up before you point a single inspector at it.

FAQ

What is roofing claim revenue cycle management?

It is the discipline of treating each insurance-related roofing job as a file that moves through defined stages — inspection, documentation, estimate, adjuster meeting, scope reconciliation, supplement, production, invoicing, depreciation release, and collections — with an owner and a clock on each stage. The idea is borrowed from healthcare RCM, which tracks revenue from a patient's first contact to final payment. The goal is to stop losing money in the murky middle between selling a job and collecting the final check, where slow files, missed supplements, and uncollected depreciation quietly erase margin.

Is managing the claim cycle the same as handling a homeowner's insurance claim?

No, and the distinction is legally critical. Managing your revenue cycle means managing your own documentation and estimate through the process — being fast, accurate, and thorough on the parts that are legally yours as a contractor. Handling the homeowner's claim — negotiating with the carrier on their behalf, interpreting their policy or coverage, or promising an approval or payout — is public adjusting and is illegal without a license in most states. You document the roof and build an accurate estimate; the homeowner files and the insurer decides coverage.

What is a roofing supplement and is it legal for a contractor to write one?

A supplement is a documented request to the carrier to revise their estimate to reflect the true, complete, code-compliant cost of the repair — supported by photos, measurements, and code citations. It is legal and normal for a contractor to write one, because you are documenting the actual cost of your own scope of work, not arguing the homeowner's coverage. The line to respect: every supplemented item must be a real component of building the roof correctly with evidence behind it, and you never use a supplement to discuss or manipulate the deductible.

How do I document a roof so my estimate survives the adjuster?

Build a complete package per roof: date-stamped, geotagged photos of every slope and elevation; a chalked test square on each slope with hits circled and counted; collateral damage photos (dented gutters, soft metals, screens); accurate measurements (squares, pitch, ridge/hip/valley/eave linear footage, penetrations, layers); and code documentation with the actual citation for anything your jurisdiction requires. Photograph the decking during tear-off too. The items most often missed — and most often worth a supplement — are soft metals and code-required line items like ice-and-water shield.

Why is recoverable depreciation so often left uncollected?

Carriers typically pay actual cash value (ACV) first and hold back recoverable depreciation until the work is proven complete. That release does not happen automatically — someone has to submit the completion paperwork (final invoice, completion certificate, photos). When the back office is overwhelmed or the homeowner moves, that paperwork sits, and depreciation can expire if not claimed within the policy's window (often 180 days to a year, varying by policy and state). Submitting completion documents the day a job finishes is the single cheapest fix for this leak.

What metrics should a roofing company track to manage its claim revenue cycle?

Track days in cycle (inspection to final payment) and days per stage to find bottlenecks; supplement attempt and approval rates; recoverable depreciation collected versus eligible (should be near 100%); write-off per closed file; and stuck-file count (open files with no action in 14+ days). The stuck-file count is your early warning — a rising number means the cycle is clogging before it shows up in cash flow. Calibrate targets to your own baseline rather than chasing published industry figures.

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

No. Never advertise or promise that a deductible will be waived, absorbed, covered, or that there is no out-of-pocket cost, and never advertise a 'free roof.' Deductible manipulation is insurance fraud in most states. The deductible is the homeowner's legal responsibility and you collect it as part of your contract. This is one of the fastest ways a storm roofing company gets into serious legal trouble, so keep it off your ads, your website, your yard signs, and your reps' scripts.

Should I build my estimate to match what insurance usually pays?

No — that is backward and it costs you money. Build your line-item estimate to the true, correct, code-compliant cost of the work in your market, using current Xactimate price-list pricing for your ZIP. If the carrier's first estimate comes in lower, that gap is exactly what the reconciliation and supplement stages exist to document, line by line, with evidence. Underpricing your own estimate to 'match' the carrier just hands away margin you will never get back.

Where does RoofPredict fit in the claim revenue cycle?

At the very front, before a file even exists. The cleanest, most collectible claim files come from roofs that are both old enough to be near service life and were actually hit by a damaging storm. RoofPredict estimates a roof-age range per address from aerial imagery and models storm physics per roof — rather than only telling you which ZIP got hailed — so you point inspectors at the addresses most likely to produce a defensible file. You can also enrich your own list (past customers, old estimates) with age and storm signals. Honest limits: roof age comes back as a range, not an exact date, and storm modeling gives odds, not proof — the damage determination still happens on the roof.

How long should a roofing claim file take from inspection to final payment?

A well-run cycle often closes residential storm files in under 45 days; over 75 days is a red flag that something is stuck. The biggest time leaks are usually the gap between receiving the carrier's estimate and filing the supplement (target under 5 days) and the gap between job completion and submitting depreciation-release paperwork. Tracking days per stage, rather than only total days, is how you find the specific handoff that is leaking time, rather than guessing.