Roofing Claim AR: A Follow-Up Cadence for Pending Supplements That Actually Gets Paid

Every roofing company that touches insurance work has a number it does not like to say out loud: the dollars sitting in "pending supplement" that have been pending for sixty, ninety, a hundred and twenty days. The roof is on. The crew got paid. The material invoice cleared weeks ago. And somewhere in a carrier's queue is a request for the difference between what the original scope paid and what the job actually cost — drip edge that was never in the estimate, a second layer nobody priced, steep-and-high charges, code-required ice-and-water, ridge vent the adjuster missed. That money is real. It is also the slowest, most fragile receivable on your books, and the thing that decides whether it gets paid is almost never the merit of the line item. It is the cadence. It is whether somebody followed up on day 7 and day 14 and day 30 with the right document attached, instead of letting the file go quiet until the homeowner calls asking why their final invoice is higher than the deductible they were told about.

This is an operations problem dressed up as an insurance problem. The carrier is not refusing to pay a properly documented, code-supported, accurately priced supplement out of spite — most of the time the file is simply stalled: it landed in the wrong inbox, the desk adjuster changed, the estimate was attached as a photo instead of an ESX, the reviewer is waiting on a document you assumed they already had. A follow-up cadence is the system that surfaces those stalls before they age into write-offs. Below is the whole thing: how to bucket pending supplements by age, the day-by-day touch schedule that keeps a file moving, what "packet completeness" actually means and why it is the single biggest lever you have, the metrics that tell you whether your cadence works, and where the legal line sits so your follow-up stays on the documentation-and-estimate side of public-adjusting law.

One framing note before anything else, because it governs every word that follows. As a roofing contractor you may inspect the roof, document the damage, write an accurate repair estimate aligned to standard estimating units, and state facts about YOUR scope and YOUR pricing to the carrier. You may not, for a fee, negotiate or adjust the claim on the homeowner's behalf, interpret the policy or what it covers, promise a specific approval or payout, promise the deductible is waived or absorbed, advertise a "free roof," or represent the homeowner against their insurer. That last cluster is unlicensed public adjusting in most states, and it is exactly the behavior a sloppy "follow-up" slides into when somebody gets impatient. The cadence here is built to keep you firmly on the side of the line where you belong: document thoroughly, price accurately, follow up on the STATUS of your documentation, and let the homeowner file and the insurer decide coverage.

Why pending supplements rot — and why cadence is the cure

Supplements do not usually get denied. They get forgotten. If you pull your own aging report and read the actual reason each old file is still open, you will find the same handful of causes over and over, and almost none of them are "the carrier disagrees with the roofing on the merits."

The common stall patterns:

• The file went to a queue, not a person. You emailed the supplement to a claims intake address, it got a confirmation auto-reply, and then nothing. No human was ever assigned to read it. This is the single most common cause of a 90-day-old supplement that has no decision either way.
• The desk adjuster changed. Reassignments happen constantly. The new adjuster opens a file with a supplement attached and no context, sees a number larger than the original estimate, and parks it pending review they will get to "later."
• The packet was incomplete and nobody told you. A reviewer needs the line-item estimate, the photos that prove each item, and the documentation that supports the price or the code requirement. If one of those is missing, many reviewers simply set the file aside rather than reaching out. Silence reads as denial when it is actually "waiting on docs."
• The estimate format created friction. A PDF or a phone photo of an estimate forces a reviewer to re-key numbers. An estimate delivered in the carrier's expected exchange format (an ESX file from Xactimate, or whatever the carrier accepts) moves faster because the reviewer can open it natively.
• Recoverable depreciation is sitting there because completion was never proven. This is a different animal — the money was already approved, it is being held back until the work is finished and the final invoice plus completion evidence is submitted. A lot of "pending" AR is actually recoverable depreciation that nobody released because the closeout packet never went in.

The through-line is that every one of these stalls is detectable and curable with a timely, specific touch. A cadence is just a guarantee that the touch happens. Without one, your fastest, most organized supplement coordinator carries the whole load in their head and the files they forget about are the files that age out. With one, the system reminds you which file is due for which touch today, and your follow-up becomes a routine instead of a heroic act.

The cost of a day of delay

It helps to put a number on it so the cadence gets the urgency it deserves. Suppose your insurance-side business runs an average supplement of $2,800 and you do 40 supplemented jobs a month. That is $112,000 a month of supplement revenue in motion. If your average pending supplement ages 75 days instead of 35, you are carrying roughly 40 extra days of that float — call it $112,000 × (40/30) ≈ $149,000 tied up at any given moment that a tighter cadence would free. You are financing the carrier's slowness with your own working capital. And the longer a file ages, the lower the odds it ever closes at full value: people leave, memories fade, the homeowner gets nervous, and a file that could have been a clean 30-day collection becomes a negotiation you should not legally be having.

None of those numbers are claims about a specific carrier or a guaranteed result. They are your own arithmetic on your own book. Run it with your real average supplement and your real volume — the point is that days-to-resolve is a dollar figure, and cadence is how you compress it.

The foundation: an honest supplement aging report

You cannot run a cadence on memory. The first build is an aging report that every pending-supplement file lands in, sorted by how many days it has been waiting since its last meaningful event. If you have ever run a standard accounts-receivable aging, this is the same idea, with one critical adjustment: the clock that matters is not days since invoice, it is days since the last carrier-side event. A file you touched yesterday is not "90 days old" for cadence purposes even if the job closed three months ago — it is fresh. A file that has had zero movement in 21 days is the emergency, regardless of total age.

Track these fields for every open supplement:

The two columns people skip — date of last carrier event and packet completeness — are the two that make the report useful. The first tells you which files are genuinely stuck versus merely in transit. The second tells you which stuck files are stuck for a reason you can fix today.

Aging buckets that match how supplements actually behave

Standard AR uses 30/60/90/120 buckets. Supplements move on a faster internal clock because the early days are where the resolution happens. Bucket them by days-since-last-event:

• 0–7 days (In flight): Recently submitted or recently touched. Confirm receipt and that a human is assigned. Do not pester; do verify it landed.
• 8–21 days (First follow-up window): The file should have movement by now. If it is silent, this is where a well-placed status touch prevents a stall.
• 22–45 days (Stalled — diagnose): Something is wrong. The file went to a queue, the adjuster changed, or the packet is incomplete. Your touch here is a diagnostic, not a nudge.
• 46–75 days (At risk): Escalation territory. You need a named human and a specific reason the file is open. This is the last bucket where a clean documentation fix reliably revives a file.
• 76+ days (Write-off risk): These files need a decision: escalate one more time with a complete packet, or recognize the realistic collectible value and stop carrying the full amount on your books. Carrying dead AR at face value lies to your own financials.

The goal of the cadence is to keep files from ever reaching the 76+ bucket. Every touch is designed to move a file LEFT (resolved) or to surface the exact reason it is stuck so you can fix it. A file should never sit in a bucket silently; the moment it has no next action with a due date, your system has failed.

The day-by-day follow-up cadence

Here is the actual schedule. It assumes a properly documented, accurately priced supplement was submitted on day 0 with the estimate, the photo evidence, and the supporting documentation already attached — because the cadence cannot rescue a packet that was never complete. Each touch has a purpose, a channel, and a script frame. Notice that every script stays on YOUR documentation and YOUR scope; none of them negotiate coverage or predict an outcome.

Day 0 — Submission with a complete packet

Submit the supplement with everything attached: the line-item estimate in the carrier's preferred format, labeled photos tied to each supplemented line, and the supporting documentation (manufacturer install instructions, the relevant code section, or the field condition) for any item that is not obvious. Log the submission, the channel, and a confirmation reference. The clock starts now.

What you are doing: Making the reviewer's job trivial. A complete packet on day 0 is worth more than ten follow-ups on an incomplete one.

Day 2 — Receipt confirmation

A short, factual touch to confirm the supplement was received and to get a human's name. Not "is it approved" — that is weeks early and not your call to push. Just: did it arrive, and who is reviewing it.

"Hi — confirming you received the supplemental estimate I sent on [date] for claim [number]. Can you tell me which adjuster the file is assigned to so I direct future documentation to the right person? Happy to resend anything that didn't come through cleanly."

This single touch eliminates the most common stall — the file that landed in a queue and was never assigned. If you cannot get a name, that is your first red flag, and the file goes on a tighter watch.

Day 7 — Status check

A week in, confirm the file is in active review and ask if anything is missing. The phrasing matters: you are offering to complete YOUR documentation, not asking them to commit to a number.

"Following up on the supplemental estimate for claim [number]. Is the file in review, and is there any additional documentation or photos you need from me to evaluate the roofing scope? I want to make sure you have everything on my end."

The "is there anything you need from me" frame is the workhorse of the whole cadence. It is polite, it is squarely on your side of the line, and it repeatedly surfaces the real blocker — "actually we never got the photos for the ice-and-water line" — that you would otherwise never hear.

Day 14 — First substantive follow-up

Two weeks of silence means the file may be stalled. Reference the specific scope and reattach the estimate. Pick up the phone if email has gone unanswered — a call gets a status that three emails will not.

"Checking on the supplement for claim [number]. The items are the drip edge, the second layer of tear-off, and the code-required ice-and-water shield — all documented in the estimate and photos I sent on [date], reattached here. Can you let me know where the review stands or what you still need to make a determination?"

If you reach a person and they cannot find the estimate, resend it immediately and confirm the format they prefer. If they say it is in review, ask for a realistic timeframe and log it as the next event date.

Day 21 — Escalation if still silent

Three weeks with no movement is a stall, not a delay. Now you confirm you are talking to the right person and, if not, find who owns the file. You are still only ever asking about status and your documentation.

"I haven't been able to get a status on the supplemental estimate for claim [number] (submitted [date]). Is this file still assigned to you, or has it moved to another adjuster? I want to make sure my documentation is in front of whoever is reviewing the roofing scope."

Reassignment is so common that simply asking "is this still your file" resolves a meaningful share of 21-day stalls on its own. Keep a running note on each file of every name you have spoken to and the date — when an adjuster leaves mid-claim, the next call goes faster if you can say "the file was with [prior adjuster] as of [date], who has it now?" instead of starting cold. A file that has cycled through three adjusters without a single party owning it is the classic 90-day ghost, and the only way out is to plant a named human on it and keep referencing that name in every subsequent touch.

There is also a discipline question hiding in the day-21 touch: if you genuinely cannot reach anyone and the carrier offers no named reviewer after three weeks of documented attempts, that absence is itself information. Note it, escalate to a supervisor sooner than the day-30 framework suggests, and make sure the homeowner is aware — factually, without editorializing about coverage — that their claim's supplemental estimate is in review and you are working the status. The homeowner is the party who can call their own carrier as the policyholder, which is a lever you do not have and should never try to use on their behalf.

Day 30 — Formal status request and supervisor visibility

At a month, the touch becomes more formal and creates a paper trail. Restate the submission date, the items, and the documentation already provided, and ask for a written status. If you have had no substantive response from the assigned adjuster across multiple attempts, it is reasonable and routine to copy or ask for their supervisor — not as a threat, as a way to get the file looked at.

"This is a formal status request on the supplemental estimate for claim [number], submitted [date], with no determination to date. The supplement covers [items], fully documented in the attached estimate and photos. Please provide a written status of the review. If this file has been reassigned, please direct me to the current adjuster or reviewing supervisor."

Keep the tone factual. You are documenting your own diligence, which protects you and the homeowner and keeps the file legitimate.

Day 45, 60, 75 — Structured escalation

From here, the touches are spaced wider but heavier. Each one: restates the facts, reattaches the complete packet, references prior contact dates, and asks for a written determination. By day 45 you should know the specific reason the file is open — if you still do not, that is the problem to solve before anything else. By day 60–75 you are deciding whether this is a collectible file that needs one more clean escalation or a file to mark down to its realistic value.

Throughout all of it, the discipline is the same: every touch references YOUR documented scope and YOUR pricing, asks about STATUS, and offers to complete YOUR documentation. No touch ever argues coverage, predicts an approval, or speaks for the homeowner against the insurer.

Cadence at a glance

The specific days are a starting framework, not gospel. Some carriers and regions move faster or slower, and your own data should tune the intervals. The non-negotiable part is that a file never sits without a scheduled next touch.

Packet completeness: the lever that beats every follow-up

Here is the uncomfortable truth that separates shops that collect from shops that chase: the best follow-up cadence in the world cannot rescue an incomplete packet, and a complete packet needs far less follow-up to get paid. If you only fix one thing, fix what you submit on day 0.

A supplement reviewer is asking three questions about every line you add: Is the item really there? Is the price right? Is it required? A complete packet answers all three before they ask. Score every supplement against this checklist before it goes out, and do not submit anything below a high bar.

The packet completeness checklist

1. The line-item estimate, in the right format.

• Every supplemented item as a discrete line with quantity, unit, and unit price.
• Pricing aligned to a standard estimating database for the region and time, so the reviewer can reconcile it against their own.
• Delivered in the carrier's preferred exchange format (an ESX file where they accept it) rather than a flattened PDF or a phone photo, so the reviewer is not re-keying numbers.

2. Photo evidence tied to each line.

• A labeled photo (or set) for every supplemented item, named or captioned so the reviewer can match photo to line without guessing.
• Wide context shots plus tight detail shots — the elevation, then the specific condition.
• Date-stamped, ideally with the claim or address visible in metadata or a slate.

3. Support for anything not self-evident.

• For a code-required item (ice-and-water shield, drip edge, fastener pattern, decking), cite the specific adopted code section and edition for that jurisdiction. "Code requires it" with no citation is an invitation to ignore the line.
• For a manufacturer-required item, attach the relevant page of the install instructions.
• For a field condition (a second layer found at tear-off, deteriorated decking), the photo IS the support, but caption it plainly.

4. The administrative anchors.

• Correct claim number and carrier on every page.
• Property address and homeowner name matching the policy.
• Your contractor info and a clear statement that this is a supplemental estimate to the existing claim.

5. For recoverable-depreciation releases specifically:

• Proof of completion (final photos showing the finished roof).
• The final invoice reflecting actual work performed.
• Any certificate of completion or signed homeowner acknowledgment the carrier requires.
• A clear reference that this is a depreciation release, not a new-scope supplement — these are different requests and conflating them stalls both.

Score each packet 0–100 across those categories and treat anything under, say, 90 as not ready to submit. The discipline feels slow the first month and then pays for itself, because a 95-completeness packet routinely closes in one cadence cycle while a 60-completeness packet generates five follow-ups and still ages out.

A worked example

A hail job comes back with the original carrier estimate paying for a basic tear-off and re-roof but missing several items the crew actually performed and the code actually requires. Your supplement, built to a high completeness score, looks like this:

Every line answers is it there, is the price right, is it required on its own. A reviewer can approve this without a phone call. That is the goal: a packet so complete that the cadence barely has to work. The follow-up cadence then exists to catch the administrative stalls — the queue, the reassignment, the lost attachment — not to argue the merits, because the merits are already documented.

Note what is NOT in any of those rows: no promise about what the carrier will pay, no statement about the homeowner's coverage, no claim that the deductible disappears. Just your scope, your evidence, your pricing. That is the line, and a complete packet keeps you on the right side of it by default.

Recoverable depreciation is a different cadence — run it separately

A large share of "pending supplement" AR is not a contested supplement at all. It is recoverable depreciation that was already approved and is simply being withheld until the job is proven complete. Mixing these into the same bucket as contested new-scope supplements is how shops lose track of money they have effectively already earned.

When a claim pays on an actual-cash-value basis, the carrier holds back the depreciation and releases it once the work is done and documented. That release is yours to trigger by submitting the closeout packet — it requires almost no negotiation, only proof. The failure mode is purely operational: the roof finished, the crew moved on, and nobody sent the completion evidence and final invoice. The money sits there for months not because anyone disputes it but because no one asked.

Run depreciation releases on their own short cadence:

• At job completion (day 0): Capture final photos, generate the final invoice, and collect any completion certificate the carrier requires. Submit the release packet immediately — the same week the crew rolls off, not "when we get to it."
• Day 7: Confirm the carrier received the completion documentation and the file is queued for the release.
• Day 21: If not released, confirm what specific completion evidence is outstanding — often a single missing document.
• Day 35: Escalate with the full closeout packet reattached.

Because depreciation releases are documentation-gated rather than judgment-gated, they should close faster and more reliably than contested supplements. If yours are aging, the fix is almost always upstream: build completion-evidence capture into your job-closeout process so the packet is ready the day the job ends. Tracking recoverable depreciation separately, with its own aging view, is one of the highest-return changes a roofing AR process can make.

Deductibles, and the line you do not cross

Any conversation about supplement AR eventually runs into the deductible, so be precise. The homeowner is responsible for their deductible. You may, and should, track it as a receivable — it is part of what you are owed. You may invoice it and collect it like any other amount due.

What you may not do: tell a homeowner the deductible will be waived, absorbed, eaten, or made to disappear; build a supplement designed to recover the deductible amount so the homeowner pays nothing; or advertise a "free roof." In most states that is insurance fraud or a violation of statutes that specifically prohibit a contractor from rebating or absorbing the deductible on an insurance job. It is one of the fastest ways to turn a legitimate business into a legal problem.

So in your AR system, the deductible is a clean line item the homeowner owes, tracked and collected on its own terms. Your supplement to the carrier covers legitimately performed and required work, priced accurately, and stands or falls on its documentation. The two never blur. When a homeowner asks whether you can "take care of" their deductible, the honest answer is that the deductible is theirs to pay and you will provide them an accurate invoice for the work — and that you cannot and will not absorb it. Putting that in writing protects everyone.

Email triage: stop reading the claim inbox by hand

Most of the cadence breaks down at the inbox. Carrier responses, requests for additional documentation, partial-approval notices, payment notifications, and reassignment notices all land as email, often to a shared address that three people watch and nobody owns. A request for one more photo sits unread for nine days, and a file you thought was "pending review" was actually "waiting on you" the whole time.

Triage discipline fixes this:

• Route claim email to a single owned queue, not a shared inbox where responsibility evaporates. Every inbound carrier message should map to a specific open file and a specific person responsible for that file.
• Classify on arrival: is this an info request (act today), a partial approval (review and respond), a payment notice (close or partially close the file), or a reassignment (update the adjuster field and re-anchor the cadence)? The classification determines the next action.
• An info request resets your obligation, not the carrier's clock. When a carrier asks for one more photo, the file is now stalled on YOU. Those should be the fastest touches in your whole operation — same-day if at all possible — because every day you sit on a documentation request is a day you added to your own aging.

A pending-supplement file that is actually "waiting on the contractor" is the most embarrassing line on an aging report, because it is entirely self-inflicted. Triage exists to make sure that line is always zero.

How RoofPredict runs this cadence for you

Everything above is doable on a whiteboard and a shared spreadsheet — for about a dozen open files. Past that, the cadence lives or dies on whether somebody remembers to make the day-14 call on the right file at the right time, and humans do not remember reliably at scale. This is the specific problem RoofClaim, the claim revenue-cycle side of RoofPredict, is built to carry.

What it actually does for a pending-supplement AR process:

• Supplement aging with the right clock. Every claim is linked to the home and the original job, and the supplement-aging view sorts by days-since-last-carrier-event — the clock that drives the cadence, rather than days since invoice. You open the dashboard and see exactly which files crossed into the 8–21 or 22–45 window today and what their next action is. Nothing sits silent.

• Packet-completeness scoring before you submit. Upload the claim documents — carrier and contractor estimates, photos, denial letters, invoices — and they are auto-classified and OCR'd. The completeness score tells you whether a packet answers is it there, is the price right, is it required before it goes to the carrier, so you stop submitting 60-completeness packets that generate five follow-ups. This is the lever that beats follow-up, made into a number you can act on.

• Opportunity detection that maps estimate line items to a roofing knowledge base. It compares the carrier's estimate against what the roof and the code actually require and flags missing scope, code-required items, and missed supplements — each with an evidence anchor and a price reference. That is how you build the high-completeness packet in the first place: the scope gaps surface with the support attached, on UPPA-gated, contractor-documentation-only templates that keep the output on your side of the line.

• Supplement aging plus a follow-up cadence, together. The cadence above is the system's default rhythm: it schedules the day-2, day-7, day-14, day-21, day-30 touches against each file, surfaces the ones due today, and keeps the next-action-with-a-due-date field from ever going blank.

• Recoverable-depreciation autopilot. Depreciation releases run on their own track, with a completion-evidence and final-invoice checklist so the closeout packet is ready the day the crew rolls off — turning the slowest self-inflicted AR delay into a same-week submission.

• Deductible tracking, kept separate. The deductible is tracked as what the homeowner owes, on its own line, invoiced cleanly — never blurred into the carrier supplement, which keeps the whole operation on the right side of deductible law.

• Claim-inbox email triage. Inbound carrier email is classified — info request, partial approval, payment, reassignment — and tied back to the file, so a "we need one more photo" message becomes a same-day action instead of a nine-day stall.

The honest limit: none of this negotiates your claims, predicts an approval, or speaks to the homeowner's coverage, and it should not — that is the public-adjusting line. What it does is make the documentation airtight, the cadence automatic, and the aging visible, so the files that should get paid get paid faster and the files that are stuck surface the reason today instead of in ninety days.

Metrics: how to know your cadence is working

A cadence without measurement is just a habit. Track these and review them monthly:

• Days-to-resolve (median, not average). From submission to determination. The median tells you the typical experience; the average hides behind a few catastrophic outliers. Driving the median down is the whole game.
• Percent of files with a named adjuster within 7 days. A leading indicator. Files that get a human early resolve faster; if this number is low, your day-2 touch is failing.
• Average packet-completeness score at submission. The single best predictor of days-to-resolve. If completeness climbs, resolve time falls — that relationship is the most reliable one in supplement AR.
• Percent of touches that were on-schedule. Did the day-14 touch actually happen on day 14? Cadence adherence is the difference between having a system and having a document describing a system.
• Aging distribution over time. Watch the share of dollars in each bucket month over month. A healthy operation pushes dollars LEFT — out of 46–75 and 76+ and into resolved.
• Self-inflicted stall rate. Of currently-open files, how many are waiting on YOU (an unanswered info request) versus the carrier? Anything above near-zero is a triage failure you control.
• Recoverable-depreciation lag. Days from job completion to depreciation-release submission. This should be near-zero with a closeout-built process; if it is weeks, your money is sitting in the easiest-to-collect bucket there is.

Review these as a team, monthly, and tie the cadence intervals to what the data shows. If your carriers in a given region reliably move at a certain pace, tune the touch days to that reality rather than the generic framework.

What pros get wrong

A few patterns separate shops that collect from shops that chase:

• Treating follow-up as a rescue instead of a system. The shops that collect submit complete packets and run a scheduled cadence. The shops that chase submit thin packets and rely on a hero coordinator to fight each file individually. The first scales; the second burns out the coordinator and ages out files the moment that person is on vacation.
• Confusing busy with effective. Five emails to an intake address that no human reads is not follow-up. One call that gets you the adjuster's name is. Touches that surface a named human and a specific blocker are worth more than a high volume of touches into the void.
• Letting the deductible blur into the supplement. The temptation to make the homeowner's out-of-pocket disappear by padding a supplement is a legal trap. Keep them separate, always, in writing.
• Submitting estimates as photos or flat PDFs. If the reviewer has to re-key your numbers, you added friction and days. Match the carrier's expected format.
• Ignoring recoverable depreciation. It is the easiest money to collect and the most commonly forgotten. Build completion evidence into closeout and submit the day the job ends.
• Carrying dead AR at face value. A 120-day file with no named adjuster and no movement is not worth its face on your books. Make the markdown decision honestly so your financials tell the truth and your team stops burning hours on files that will not close.
• No clock on the carrier's silence. Silence is not a status. Every open file needs a next action with a due date, full stop. The moment a file goes quiet with no scheduled touch, it has started aging toward a write-off.

Putting it together

Pending-supplement AR is not won by being aggressive with carriers. It is won by being relentless about your own documentation and your own cadence. Submit a packet so complete the reviewer can approve it without a phone call. Track every file by days-since-last-carrier-event, not days-since-invoice. Run the day-2, day-7, day-14, day-21, day-30 touches like clockwork, each one referencing your scope and your evidence and asking only about status and what you can provide. Run recoverable depreciation on its own fast track. Keep the deductible clean and separate. Triage the claim inbox so a request for one more photo never becomes a nine-day stall. And measure days-to-resolve and packet completeness so you know the system is working instead of hoping it is.

Do that, and "pending" stops being a place files go to die. It becomes a short, well-lit hallway with a scheduled exit. The money that is rightfully yours — for work you performed and documented and priced honestly — comes in faster, your working capital stops financing the carrier's queue, and your team spends its energy on documentation discipline instead of frantic chasing.

If you want the aging view, the completeness scoring, the depreciation autopilot, and the cadence running automatically against every linked claim — on templates built to keep you on the documentation-and-estimate side of the line — that is exactly what RoofClaim inside RoofPredict is for. Start by pulling your own honest aging report this week, score your last ten submitted packets for completeness, and put a scheduled next action on every silent file. The cadence does the rest.

FAQ

How often should I follow up on a pending roofing supplement?

Run scheduled touches at day 2 (confirm receipt and get the adjuster's name), day 7 (status and ask if anything is missing), day 14 (substantive follow-up with the estimate reattached), day 21 (confirm the file hasn't been reassigned), and day 30 (a formal written status request). After that, escalate at roughly day 45, 60, and 75. The exact days are a framework to tune to your carriers' real pace; the rule that does not change is that every open file always has a next action with a due date.

What is the single biggest reason supplements sit pending for months?

An incomplete packet, followed closely by the file landing in a queue that no human was ever assigned to read. Most pending supplements are not denied on the merits — they are stalled because a photo, a code citation, or the estimate in the right format is missing, or because the desk adjuster changed and the new one parked the file. A complete day-0 packet and a day-2 touch to get a named adjuster prevent the large majority of long stalls.

How should I bucket a supplement aging report?

Bucket by days since the last carrier-side event, not days since invoice: 0-7 (in flight), 8-21 (first follow-up window), 22-45 (stalled, diagnose), 46-75 (at risk, escalate), and 76+ (write-off risk). The last-event clock matters because a file you touched yesterday is fresh even if the job closed months ago, and a file silent for 21 days is the emergency regardless of total age.

What goes into a complete supplement packet?

Four things: a line-item estimate with quantities, units, and region-aligned pricing delivered in the carrier's preferred format; a labeled photo tied to every supplemented line; support for anything not self-evident (a specific code section and edition for code-required items, the manufacturer install page for manufacturer-required items, the field photo for found conditions); and clean administrative anchors (correct claim number, carrier, address, and a statement that it is a supplemental estimate). Score each packet and don't submit below a high bar.

Why is recoverable depreciation different from a regular supplement?

Recoverable depreciation is usually already approved and simply withheld until the work is proven complete, so it is documentation-gated, not judgment-gated. It needs proof of completion, a final invoice, and any required completion certificate, not a negotiation. Run it on its own faster cadence and submit the release packet the week the crew rolls off the job. It is the easiest insurance money to collect and the most commonly forgotten.

Can I tell a homeowner I'll take care of their deductible through a supplement?

No. The deductible is the homeowner's responsibility, and telling them it will be waived, absorbed, or made to disappear — or building a supplement designed to cover it so they pay nothing — is prohibited in most states and can constitute insurance fraud. Track and invoice the deductible as a clean, separate receivable the homeowner owes, and keep it completely distinct from the carrier supplement, which covers legitimately performed and required work priced accurately.

What can I legally do as a contractor when following up on a supplement?

You may inspect the roof, document damage, write an accurate repair estimate, state facts about your own scope and pricing to the carrier, and follow up on the status of your documentation. You may not, for a fee, negotiate or adjust the claim on the homeowner's behalf, interpret the policy or what it covers, promise a specific approval or payout, promise the deductible is waived, or represent the homeowner against the insurer — that is unlicensed public adjusting in most states. Keep every follow-up on status and on your own documentation.

What should I do when a carrier asks for one more photo or document?

Treat it as the most urgent touch in your operation and respond same-day if possible. An information request means the file is now stalled on you, not the carrier, and every day you sit on it is a day you personally added to your aging report. A pending file that is actually waiting on the contractor is the most embarrassing and most self-inflicted line on an aging report; triage your claim inbox so those requests never go unread.

Which metrics tell me whether my follow-up cadence is working?

Track median days-to-resolve (not average), the percent of files with a named adjuster within 7 days, average packet-completeness score at submission, on-schedule touch rate, the aging distribution over time, your self-inflicted stall rate (files waiting on you versus the carrier), and recoverable-depreciation lag from job completion to submission. Packet completeness is the single best predictor of how fast a file resolves.

When should I write down a pending supplement instead of chasing it?

When a file passes roughly 75 days with no named adjuster, no movement, and a complete packet already submitted and escalated, it is worth far less than its face value. Make one final clean escalation with the full packet, and if that produces nothing, recognize the realistic collectible value on your books rather than carrying the full amount. Carrying dead AR at face value lies to your own financials and keeps your team burning hours on files that will not close.