How to Track Roof Supplements So They Don't Die in the Pile

Ask any production manager who has run a restoration roofing company for more than a season what kills supplement revenue, and you will rarely hear "the carrier denied it." You hear something quieter and more expensive: it got forgotten. The supplement got written, attached to an email, sent to a desk adjuster who never replied, and then it sat. Nobody owned the follow-up. Three weeks turned into three months. By the time someone noticed the job in the won column with an open balance, the adjuster had moved files, the homeowner had cashed the first check, and the documentation that would have supported the ask was buried under sixty newer claims.

That is how most supplements die. Not in a fight. In silence.

The money involved is not small. On a typical hail or wind reroof, the legitimate, code-and-scope-supported difference between the carrier's first estimate and a fully documented repair estimate often runs four to five figures. Multiply that by the share of jobs where the gap never gets pursued, and a mid-size company is leaving real margin uncollected every single month. The work to capture it is already done by the time you are supplementing. The roof is built or about to be. The only thing standing between you and the balance is whether your shop has a reliable way to keep every open item moving until it resolves.

This is a tracking problem before it is anything else. You can have the best estimator in the state, but if your pipeline leaks supplements out the bottom through inattention, the estimating talent is wasted. What follows is a complete operating system for tracking roof supplements so they do not die: how to define the stages, how to age them, what cadence keeps them alive, how to score a packet before it goes out, what to document on the repair side, and where most shops quietly lose the thread.

Before going further, a hard line that shapes everything below. A roofing contractor can inspect a roof, document conditions, and write an accurate repair estimate for their own scope of work. A contractor can state facts about that scope to a carrier. What a contractor cannot do, unless separately licensed as a public adjuster, is negotiate or "handle" the claim on the homeowner's behalf for a fee, interpret the homeowner's policy or coverage, promise a specific payout or approval, advertise that a deductible will be waived or absorbed, or represent the homeowner against their insurer. That last cluster is unlicensed public adjusting in most states, and it carries fines and license consequences. Everything in the workflow below lives on the safe side of that line: you document thoroughly, you write an accurate estimate aligned to the actual scope, and the homeowner files and the insurer decides. Track the work, not the outcome.

Why supplements die: the five failure modes

Before building a system, name the enemy. Supplements rarely die for one dramatic reason. They die from a handful of predictable, boring failures that compound. Map your own lost-supplement list against these and you will recognize most of them.

1. No owner. The single most common cause. A supplement is sent and then belongs to no one. The estimator thinks the production manager is following up. The production manager thinks the office handles carrier email. Nobody is wrong, because nobody was ever assigned. An unowned supplement is a dead supplement on a timer.

2. No next action with a date. Even owned supplements die when the system has no concept of "what happens next, and when." The supplement is "sent" and then the record just sits in a status that never forces a touch. Without a scheduled next action, the only thing that moves the supplement is somebody happening to remember it, which does not scale past about ten open items.

3. Incomplete packets that invite a stall. A supplement missing a photo, a measurement, a code citation, or a line-item justification gives the adjuster a reason to set it aside and ask for more, or to do nothing. Every round of "please send the documentation for line 14" adds two to three weeks. Half-built packets are the slow-motion version of dying.

4. Lost recoverable depreciation. This is the quiet killer that costs the most. The carrier approves the supplement, the job gets built, and then nobody closes out the recoverable depreciation because the completion documentation never got assembled and submitted. The depreciation is sitting there, already approved, waiting for a final invoice and proof of completion that nobody files. It is the most winnable money in the business and it dies more than any other category because it feels "done."

5. Aging blindness. The shop has no aging report. Leadership cannot see, on one screen, which supplements have gone untouched for 14, 30, or 60 days. Without that visibility, the oldest and most at-risk items are invisible until a quarterly reconciliation surfaces a pile of stale balances that are now nearly impossible to recover.

Notice that four of the five are tracking and process failures, not estimating or merit failures. The supplement was usually justified. It just was not managed. That is good news, because process problems are fixable with a system.

The mental model: a supplement is a pipeline, not an email

The core mistake is treating a supplement as a one-time transmission. You write it, you send it, you wait. In that model the supplement has only two states in anyone's head: "sent" and "paid," with a long fog in between where nothing is visible and nothing is required.

Replace that with a pipeline. A supplement is a record that moves through defined stages, where every stage has an owner, an entry condition, a next action, and a clock. The job of the system is to never let a record sit in a stage past its allowed age without forcing a human touch. When you think of it as a pipeline, "the supplement is taking a while" stops being a vague worry and becomes a specific, answerable question: which stage is it stuck in, who owns that stage, what is the next action, and how many days has it been there?

The rest of this is the implementation of that model.

Stage 1: define the supplement lifecycle stages

You cannot age what you have not staged. Before any tracking can work, every supplement needs to live in exactly one of a small set of named stages. Keep the list short enough to be honest and long enough to be useful. Here is a lifecycle that holds up across carriers and job types.

A few notes on this list. "Depreciation release" gets its own stage on purpose, because it is the single most-forgotten phase and burying it inside "approved" or "build" is exactly how it dies. Giving it a named stage with its own owner and its own clock is the difference between collecting it and writing it off.

"Closed-lost" requires a documented reason. Do not let supplements quietly evaporate. If one resolves with no recovery, somebody writes one sentence on why. Those sentences become your best training data for what to stop doing.

The "Identified" stage matters more than it looks. Plenty of legitimate items never even become supplements because the gap got noticed in the field and then forgotten before anyone wrote it up. Capturing the identification as its own tracked stage means the finding does not depend on the estimator's memory surviving until they are back at a desk.

Stage 2: build the aging report

Stages tell you where a supplement is. Aging tells you whether it is in trouble. The aging report is the heartbeat of the whole system, and if you build nothing else from this, build this.

The concept is borrowed straight from accounts-receivable aging, and for good reason: an open supplement is functionally a receivable that has not been invoiced yet. You want every open supplement bucketed by how long it has sat in its current stage without a meaningful touch.

Use buckets that map to action thresholds, not arbitrary calendar lines:

The power is not in the buckets themselves but in two rules attached to them. First, age is measured from the last meaningful touch, not the creation date and not a passive status change. A meaningful touch is a documented contact or action that advanced the supplement: a call to the adjuster, a resubmission, a request answered. Opening the record to look at it is not a touch. This distinction is what stops a shop from gaming its own aging report by clicking around.

Second, every item in "Stale" or worse must have a next action with a date before it can leave the morning review. You do not get to acknowledge that a supplement is 22 days untouched and then move on. The act of seeing it in the stale bucket obligates you to schedule the next touch. The aging report is not a passive dashboard; it is a forcing function.

Run this report daily for the at-risk and critical buckets, and weekly for the full pipeline in a standing supplement meeting. The daily scan takes five minutes and is the highest-leverage five minutes in the production office.

A worked example of an aging review

Picture a Monday-morning report with 38 open supplements. The buckets show 19 fresh, 8 watch, 6 stale, 4 at-risk, 1 critical. You ignore the 27 fresh and watch items entirely; they are on schedule. You spend the meeting on the 11 that are stale or worse.

The critical item is 71 days in "Submitted" with no carrier acknowledgment. That is a red flag that the submission never actually landed, or landed with someone who left. The action is not to wait another week; it is to confirm receipt through a different channel today and, if it never arrived, resubmit with a fresh transmittal and restart the clock with a clean record.

Two of the at-risk items are sitting in "Depreciation release" at 41 and 47 days. The jobs are built. The only thing missing is the final invoice and completion photos. That is pure collection work and it is nearly free money; it goes to the top of the day's task list.

Three of the stale items are in "Under review" at 18 to 24 days with no response to the last touch. The action is a documented follow-up call to each desk adjuster and, where appropriate, a polite written confirmation of what was submitted and when. Each gets a next-action date seven days out.

That is the entire discipline. The report surfaces the eleven that matter, you assign a dated next action to each, and the other twenty-seven take care of themselves. Run that loop every week and supplements stop dying.

Stage 3: the follow-up cadence

A cadence is the default schedule of touches that a supplement gets at each stage so that nothing relies on memory. Cadence is what converts "we should follow up" into a thing that actually happens on a date. The exact numbers below are a starting template; tune them to your carriers' real response patterns, but keep the principle that every stage has a defined next-touch interval.

Submitted stage cadence. After a supplement is sent, the clock starts on acknowledgment, not approval. Confirm receipt within 3 business days. If you have no acknowledgment by day 3, that is a problem to solve immediately, because an unacknowledged submission may simply not exist on the carrier's side. Once acknowledged, set the next touch for roughly 7 to 10 business days out depending on the carrier's typical turnaround.

Under-review cadence. During review, a touch every 7 to 10 business days is the right rhythm for most carriers, more frequent if the adjuster has gone quiet past their own stated timeframe. Each touch is documented: who you contacted, by what channel, what was said, and what the next step is. The goal of each touch is to either advance the supplement or surface the specific obstacle blocking it.

Request-for-information cadence. If the carrier asks for more documentation, that is a same-week response, ideally same-day. Nothing burns goodwill and timeline like sitting on an information request for two weeks. A fast, complete response to a request is one of the cheapest ways to keep a supplement alive and to signal that your shop is organized.

Depreciation-release cadence. Once a job is complete, the recoverable depreciation packet should go out within days, not weeks. Set a hard internal rule: completion triggers an immediate task to assemble the final invoice and completion evidence, and that task does not get to age past your "Watch" threshold. The longer a completed job's depreciation sits, the colder it gets.

The escalation ladder. Cadence also defines when an item moves up the chain. A reasonable ladder: the supplement writer owns touches through the first follow-up; if the item goes stale, the supplement manager takes a documented touch; if it reaches at-risk, it gets manager review and a decision about a more senior contact or a different channel; if it reaches critical, leadership is aware and personally involved in the next move. The point of escalation is not blame. It is to make sure the people with more leverage and more options get involved before the window closes, not after.

Write the cadence down. An undocumented cadence is just a hope. A documented cadence is a checklist that anyone on the team can execute, which is what lets the system survive turnover and growth.

Stage 4: packet completeness scoring

The fastest way to keep a supplement from dying is to send a packet so complete that the adjuster has nothing to ask for. Every missing element is an excuse to stall. So before a supplement leaves "Drafting," it should pass a completeness check, scored against a fixed rubric. A supplement that scores below threshold does not get submitted; it goes back for the missing pieces.

Think of the score as a gate, not a grade. Here is a practical rubric for a roofing supplement packet. Adjust the weights to your market, but keep every category present.

Score it simply: count the elements that apply to this specific supplement and confirm each is present. Anything below complete-for-the-applicable-elements is not ready. The discipline of scoring before sending eliminates the entire category of "send, get asked for the photo, wait three weeks, resend" delays that quietly age supplements into the danger zone.

A note on what belongs in the packet and what does not. The packet documents the condition and the scope of work to repair it. It states facts: this is the roof, this is the damage pattern, this is the code that applies in this jurisdiction, this is the manufacturer's install requirement, this is the line-item scope and quantity to restore it correctly, and here is the photo for each. The packet does not argue coverage, does not interpret the homeowner's policy, and does not assert what the carrier must pay. You are documenting and estimating your scope; the coverage determination is the insurer's to make. Keeping the packet strictly factual is both the compliant approach and, not coincidentally, the more persuasive one, because facts with photos are harder to brush aside than arguments.

Stage 5: the documentation foundation

Everything upstream depends on the quality of what was captured in the field. A tracking system cannot resurrect documentation that was never taken. The single most common reason a supplement is weak is that the field documentation was thin, and you cannot reshoot a roof that has already been replaced. Get this right at inspection and the rest of the pipeline runs smoothly.

Photograph the condition, not only the roof. A wide shot of a roof proves the roof exists. It does not justify a line item. For each supplemented item you want a tight, in-focus shot of the specific condition, ideally with a reference for scale and a marker, plus a context shot showing where on the roof it sits. Test squares for hail, chalk-circled hits, drip edge and flashing conditions, decking exposure, ventilation, and any code-driven detail all want their own documented frames.

Capture metadata. Date-stamped and location-tagged photos are dramatically more defensible than loose images that could have come from anywhere. Use a field tool that embeds the capture date and GPS so the documentation carries its own provenance.

Document code requirements in their jurisdiction. Code-required items are some of the strongest supplements because they are not a matter of opinion; the local code adopted from the model residential code mandates them. But you have to cite the actual applicable provision and confirm it is adopted in that jurisdiction. A code citation that names the section turns a contestable line into a defensible one.

Record measurements you can defend. Quantities drive a large share of supplement value, and "about" is not a defensible quantity. An aerial or measured diagram that supports your squares, lineal footage of edges, and penetration counts removes an entire class of pushback.

Build the completion file as you go. This is the part that saves recoverable depreciation later. From the day the job is scheduled, treat completion evidence as a deliverable: progress photos, a completed-work set, and the final invoice. If you assemble this during the build instead of trying to reconstruct it weeks after the crew has left, the depreciation release becomes a five-minute task instead of an archaeology project.

The theme across all of these is that documentation is a tracking artifact, not only evidence. Each photo, each measurement, each citation is a thing your system can confirm is present or flag as missing. That is what makes packet scoring possible and what keeps incomplete packets from leaking into the carrier's hands and stalling.

Where RoofPredict fits: RoofClaim as the supplement tracking spine

Everything above can be run on a whiteboard and a spreadsheet, and small shops do exactly that. It works until volume outgrows attention. Somewhere around a few dozen open supplements at a time, the manual version starts leaking, because the aging math, the cadence reminders, and the packet checks all depend on a human remembering to look. The whole point of a system is to remove the dependence on memory. That is the specific problem RoofPredict's RoofClaim module is built to solve.

Here is what the contractor actually does with it, mapped to the workflow above.

Claim intake linked to the home. A supplement does not float free; it is attached to a specific property with its roof profile and history already on file. When you open a claim record, the home's documented context travels with it, so the supplement writer is not starting from a blank page.

Document upload, auto-classification, and OCR. You upload the carrier estimate, the contractor estimate, field photos, denial or partial-approval letters, and invoices. The system classifies each document and runs OCR so the line items and figures are readable data, not loose images in a folder. That is what makes the next piece possible.

Opportunity detection on the estimate. This is the part that directly attacks the "incomplete packet" failure mode. RoofClaim maps the carrier's estimate line items against a roofing knowledge base and flags missing scope, code-required items that are absent, and missed supplement opportunities, each surfaced with an evidence anchor and pricing context. Instead of relying on the estimator to catch every gap by eye, the system surfaces the candidates and points to the evidence supporting them. You still review and decide; the tool makes sure the obvious gaps do not slip past because someone was rushing.

Packet-completeness scoring, built in. The completeness rubric from earlier is not a checklist you have to maintain by hand. RoofClaim scores packet completeness so a supplement that is missing its photo anchor, its measurement support, or its line justification is flagged before it goes out, not after the adjuster asks. That is the gate that keeps half-built packets from leaking into review and stalling.

Supplement aging plus a follow-up cadence. The aging report and the cadence ladder described above run automatically. Open supplements are bucketed by age in stage, stale and at-risk items surface to the right owner, and the follow-up cadence schedules the next touch so nothing relies on anyone remembering. The aging blindness failure mode disappears because the report is always current and always in front of the people who can act on it.

Recoverable-depreciation autopilot. Because this is the most-forgotten money, it gets dedicated handling. The recoverable-depreciation workflow runs a completion-evidence and final-invoice checklist, so when a job finishes, the system knows exactly what is needed to release the depreciation and prompts for it rather than letting an already-approved balance quietly die. Deductible tracking sits alongside it so the math on every job stays clean.

Claim-inbox triage. Carrier email is where supplements go to get lost. RoofClaim triages the claim inbox so a desk adjuster's reply or request lands against the right claim and the right next action, instead of sitting unread in a shared mailbox that no single person owns.

A few honest limits, because the point is to be useful, not to oversell. The system surfaces opportunities and evidence; it does not decide what is legitimate for your specific job, and you should never submit a flagged item you cannot stand behind. Pricing context is a baseline, not a guarantee of approval. And every template RoofClaim produces, the supplement packets, depreciation-release letters, deductible invoices, missing-docs letters, and audit reports, is built on locked, compliance-gated, contractor-documentation-only language. The tooling is deliberately constrained to keep you documenting your scope and estimating accurately, not negotiating the claim or interpreting coverage. That constraint is a feature. It keeps a busy production office from drifting across the public-adjusting line on a deadline.

The recoverable depreciation playbook

Because recoverable depreciation is where the most money dies, it deserves its own detailed workflow. Recoverable depreciation is the portion of the claim the carrier holds back on the first payment and releases after the work is completed and documented. On a replacement-cost policy, it is money that is, in effect, already yours to collect once you prove the job is done. It dies not because anyone disputes it but because the completion paperwork never gets assembled and sent.

Here is the sequence that keeps it from dying.

1. At approval, flag the recoverable amount. The moment a supplement or claim is approved, the system records the recoverable depreciation amount and the conditions to release it. Now it is a tracked balance, not a surprise you find at year-end.
2. At job scheduling, open the completion file. Completion evidence becomes a deliverable from day one. Progress and finished-work photos are captured during the build, not reconstructed after.
3. At completion, trigger the release task immediately. Job done is the trigger. The release task enters the pipeline at the "Watch" cadence so it cannot quietly age. This is the rule that single-handedly recovers the most lost money.
4. Assemble the release packet. Final invoice, proof of completion, and the completion photos, packaged on a clean transmittal that references the claim. With the completion file built during the job, this is minutes of work.
5. Submit and track to zero. The release item gets the same aging and cadence treatment as any other supplement until the balance is collected and the job moves to closed-won.

The whole playbook is one idea executed reliably: treat the depreciation release as a tracked supplement in its own right, with its own stage, owner, clock, and cadence. The companies that lose it are the ones that treat "approved" as the finish line. The finish line is a zero balance.

The weekly supplement meeting

Systems live or die on the standing meeting that runs them. Thirty minutes a week, same time, with the aging report on the screen. The agenda is fixed and short.

• Critical and at-risk first. Walk every item 30 days and older. For each, confirm the owner, the next action, and the date. Nothing 30-plus leaves the meeting without a dated next action.
• Depreciation releases. Walk every open release. These are collection items; they should resolve fast and they should embarrass the room if they are aging.
• Stale items. Quick pass on the 15-to-29-day bucket to confirm each has a scheduled touch.
• Last week's commitments. Did the dated next actions from last week actually happen? This is where accountability lives. If touches were promised and not made, that is the real problem to solve, more than any single supplement.
• Closed-lost review. Read the one-sentence reasons on anything that closed lost. Look for patterns. If three items died for the same reason, fix that reason.

What you do not do in this meeting is relitigate the merits of every line item or turn it into a coverage debate. The meeting is about motion: is every open supplement moving, who is moving it, and when is the next touch. Merits get worked at the desk, not in the standup.

Metrics that tell you the system is working

If you cannot measure the pipeline, you cannot improve it. A handful of metrics tell you whether your tracking system is actually keeping supplements alive or just giving you a nicer-looking dashboard while they die anyway.

The two most diagnostic numbers are the percentage of open supplements with a scheduled next action and the days-from-completion-to-release. If the first is high, your cadence is real and supplements are not dying of neglect. If the second is low, you are capturing the depreciation that most shops leak. Watch those two and the rest tends to follow.

A word on how to read these numbers over time. Any single week's snapshot is noisy; a big job closing or a slow carrier can swing a metric without meaning anything. Track the trend across four to six weeks instead. If average age in stage is creeping up week over week, that is the early warning that the cadence discipline is slipping before any supplement actually dies, and it is far cheaper to fix a slipping habit than to recover a stale pile. Pair the numbers with a quick read of the closed-lost reasons, because two shops can have identical collection rates while one is losing winnable items to neglect and the other is correctly walking away from items it could never document. The metrics tell you whether the machine is running; the closed-lost reasons tell you whether it is running on the right fuel.

Resist the urge to add more metrics than these. A dashboard with twenty numbers gets glanced at and ignored; six numbers that each map to a clear action get used. The test of a good metric here is whether a bad reading points at a specific person and a specific habit to change. If a number moves and nobody knows what to do differently, it is decoration, not measurement.

Edge cases and what pros get wrong

A few situations break the simple version of the system, and the experienced operators handle them differently.

The adjuster goes silent past their own timeframe. The mistake is to keep sending the same email into the void. The move is to change channels and document it: a phone call, a portal message, a polite written confirmation of what was submitted and when, and if the silence continues past the carrier's stated turnaround, a professional escalation to a supervising contact. Persistence with a paper trail, not nagging.

The partial approval that hides a stall. A partial approval feels like progress and so it stops getting worked. But the unapproved items are still open and still aging. The fix is to split the record: the approved portion moves toward build and collection, and the still-open items keep their own stage, clock, and cadence so they are not forgotten in the glow of the partial win.

The job that built before the supplement resolved. Production runs ahead of paperwork constantly. The risk is that once the roof is on, the open supplement loses urgency because the customer is happy and the crew is gone. The discipline is to keep the supplement and especially the recoverable depreciation tracked to zero regardless of build status. Build completion is a trigger to push the paperwork, not permission to drop it.

Treating every gap as a supplement. Newer estimators sometimes flag everything and submit padded packets, which trains adjusters to distrust the shop and slows every future supplement. The opposite of dying-by-neglect is dying-by-credibility. Send only what you can document and stand behind. A tight, fully-evidenced packet with five solid items beats a sprawling one with fifteen shaky ones, every time.

Forgetting the deductible math. The homeowner is responsible for their deductible; that is not money you collect from the carrier and it is not money you can advertise away. The error pros avoid is letting deductible confusion muddy the supplement tracking. Keep deductible tracking clean and separate, state it plainly to the homeowner, and never represent that it will be waived, absorbed, or made to disappear. That representation is both a compliance problem and a trust problem.

Losing the thread at staff turnover. A supplement manager leaves and takes the entire mental map of forty open claims with them. This is why the system has to live in a shared, durable record with stages, owners, cadences, and documentation, not in one person's head and inbox. The test of a real tracking system is whether a new hire can open it on day one and immediately see what is open, who owns it, and what happens next. If the answer is no, you have a person, not a system, and people leave.

A 30-day implementation plan

You do not have to build this all at once. Here is a sequenced rollout that gets the highest-leverage pieces working first.

Week 1: stage and inventory. Put every open supplement into the lifecycle stages. Just getting an honest count of what is open and where it sits usually surfaces several items everyone had forgotten, which is the first win. Assign an owner to every open item.

Week 2: build the aging report and run the first meeting. Bucket everything by age in stage. Hold the first weekly supplement meeting and work the stale-and-older items. Expect the first meeting to be uncomfortable; that discomfort is the cost of having ignored the pile.

Week 3: install the cadence and the packet gate. Write down the follow-up cadence and the completeness rubric. From here forward, no supplement leaves drafting without passing the gate, and every open item has a scheduled next action.

Week 4: attack the depreciation backlog. Pull every completed job with open recoverable depreciation and run the release playbook on each. This week often pays for the entire effort, because it collects money that was already approved and simply never claimed.

From there it is maintenance: the daily five-minute scan of at-risk and critical, the weekly meeting, and the discipline of never letting an item sit past its allowed age without a dated touch.

The bottom line

Supplements do not die because carriers are ruthless. They die because the work of tracking them is boring, easy to defer, and invisible until the money is already gone. The shops that collect their full, legitimate, documented scope are not the ones with the most aggressive estimators. They are the ones with the most reliable system: every supplement in a named stage, every stage with an owner and a clock, an aging report that forces a touch before anything goes critical, a cadence that does not depend on memory, a packet gate that keeps incomplete documentation from stalling out, and a dedicated playbook for the recoverable depreciation that everyone else forgets.

Build that, run the weekly meeting, watch the two diagnostic metrics, and the supplement pile stops being a graveyard and starts being a pipeline. The roofs are already built. The documentation is already done. The only thing left is to make sure nothing dies in the gap between approved and collected, and that gap is entirely within your control.

If you want the tracking spine handed to you instead of built by hand, RoofPredict's RoofClaim module runs this exact workflow: claim intake tied to the home, document upload with OCR and auto-classification, opportunity detection that flags scope gaps and missing code items with evidence and pricing, packet-completeness scoring, supplement aging with a built-in follow-up cadence, recoverable-depreciation autopilot, deductible tracking, and claim-inbox triage, all producing compliance-gated, contractor-documentation-only templates. It keeps you on the document-and-estimate side of the line while making sure no supplement dies of neglect. Start with the part that is bleeding the most money today, the recoverable depreciation sitting in your closed jobs, and let the system close the rest.

FAQ

What is the most common reason roof supplements die?

Neglect, not denial. The most common cause is that no single person owns the follow-up, so the supplement is sent and then sits unworked until it is too old to recover. Four of the five top failure modes (no owner, no scheduled next action, incomplete packets, lost recoverable depreciation, and aging blindness) are tracking and process problems rather than merit problems, which means they are fixable with a system.

How often should I follow up on a submitted supplement?

Confirm the carrier received it within about 3 business days, because an unacknowledged submission may not exist on their side. During review, a documented touch every 7 to 10 business days is a reasonable rhythm for most carriers, more frequent if an adjuster goes quiet past their own stated timeframe. Respond to any request for information the same day if you can. Tune these intervals to your carriers' actual response patterns, but keep the rule that every stage has a defined next-touch interval.

What is a supplement aging report and why does it matter?

It is an accounts-receivable-style report that buckets every open supplement by how many days it has gone untouched in its current stage, typically Fresh (0-7), Watch (8-14), Stale (15-29), At risk (30-59), and Critical (60+). It matters because it surfaces the oldest, most at-risk items before they die, and because the rule that anything stale or worse must get a dated next action turns the report into a forcing function rather than a passive dashboard.

What is recoverable depreciation and why does it get lost so often?

It is the portion of a replacement-cost claim the carrier holds back on the first payment and releases after the work is completed and documented. It gets lost because it feels finished once the supplement is approved and the roof is built, so nobody assembles the final invoice and completion evidence needed to release it. Giving it its own tracked stage, owner, clock, and a completion-triggered release task is what keeps this already-approved money from dying.

What should be in a complete roof supplement packet?

An itemized estimate aligned to a standard pricing baseline, photo evidence anchored to each line item, measurements or a diagram supporting quantities, a code citation for any code-required item, a short written justification per line, date-stamped and location-tagged field photos, a reference to the original carrier estimate by line, manufacturer specs where install requirements drive scope, and a clear transmittal naming the claim and property. Score the packet against this list before sending so missing pieces are caught before an adjuster asks.

Can a roofing contractor negotiate the insurance claim for the homeowner?

No, not unless separately licensed as a public adjuster. A contractor may inspect, document conditions, and write an accurate repair estimate for their own scope, and state facts about that scope to the carrier. A contractor may not negotiate or handle the claim for a fee, interpret the homeowner's policy or coverage, promise a specific payout or approval, advertise that a deductible will be waived, or represent the homeowner against the insurer. Those activities are unlicensed public adjusting in most states. Document and estimate; the homeowner files and the insurer decides coverage.

How many open supplements can a shop track manually before it starts leaking?

Most shops start leaking somewhere around a few dozen open supplements at a time. Below that, a disciplined person with a spreadsheet and a whiteboard can hold it together. Above it, the aging math, cadence reminders, and packet checks all depend on someone remembering to look, and memory does not scale. That is the point where dedicated tracking software that automates aging, cadence, and completeness scoring pays for itself by stopping the leaks.

What metrics show whether my supplement tracking is actually working?

The two most diagnostic are the percentage of open supplements that have a scheduled next action (you want this near 100 percent, which means cadence is real) and the days from job completion to depreciation-release submission (you want this in the low single digits, which means you are capturing the most-forgotten money). Also watch average age in stage, recoverable-depreciation collection rate, packet completeness pass rate, and closed-lost rate with its top reasons.

How do I handle a partial approval so the open items don't get forgotten?

Split the record. A partial approval feels like a win and so the unapproved items often stop getting worked while they keep aging. Move the approved portion toward build and collection, and keep the still-open items in their own stage with their own clock and cadence so they continue getting follow-up touches until they resolve one way or the other.

How does RoofPredict's RoofClaim help track supplements?

It runs the whole tracking spine: claim intake linked to the home, document upload with OCR and auto-classification, opportunity detection that flags scope gaps and missing code items with evidence anchors and pricing, packet-completeness scoring that catches incomplete packets before they go out, supplement aging with a built-in follow-up cadence, recoverable-depreciation autopilot with a completion-evidence checklist, deductible tracking, and claim-inbox triage. Every template it produces is compliance-gated and contractor-documentation-only, keeping you on the document-and-estimate side rather than negotiating the claim.