How to Track Pending Roofing Supplements Like Accounts Receivable

Walk into the accounting office of almost any roofing company and you will find an accounts receivable aging report that nobody questions. Invoices over 90 days get flagged. Someone gets a phone call. The owner reviews the report on Monday and asks pointed questions about the oldest balances. The discipline is automatic because everyone agrees that an unpaid invoice is real money that belongs to the company.

Now ask the same company to show you their pending supplements. You will usually get a blank stare, a shared spreadsheet that three people edit and nobody trusts, or a production manager who taps their temple and says "it's all up here." The supplements that have been submitted to carriers but not yet approved, the recoverable depreciation that hasn't been released, the scope items a desk adjuster pushed back on three weeks ago and nobody has answered — that is money the company has already earned by doing the work and documenting it, and it is being tracked with less rigor than a $40 office-supply invoice.

That gap is where restoration revenue quietly leaks out. A pending supplement is functionally identical to a receivable: work has been performed or documented, a request has gone out, and the company is waiting to be paid. The difference is that nobody built an aging ledger for it, so supplements fall through the cracks. They age past the point where anyone remembers the context. They get "closed" in the field crew's mind when the production wraps, even though $4,000 of recoverable depreciation never got released. They die because a desk adjuster asked one question that sat unanswered until the file went cold.

The fix is not a new piece of software you have to buy before lunch. The fix is a mindset and a system: treat every pending supplement as a line on a receivables ledger, give it an owner and an aging bucket, and run a follow-up cadence with the same boring discipline you already apply to unpaid invoices. Below is how to build that, from the conceptual model down to the exact columns in the spreadsheet, the aging buckets, the cadence, and the documentation pipeline that feeds it.

One boundary before we start, because everything here lives near insurance work. This is about how a contractor documents and tracks its own scope, its own field evidence, and its own submitted paperwork — the operational discipline of not losing track of work you've already earned. It is not about representing a homeowner, negotiating a settlement, or interpreting what a policy covers. The homeowner files the claim and the insurer decides it. The contractor documents its own work and follows up on its own submitted documentation. Keep that line clean and the system below is squarely in operations, not advocacy. We will come back to where that line sits in practice.

Why a supplement is a receivable, not a maybe

Most roofing companies file supplements in the "maybe" column. The estimate came back light, somebody put together additional line items with photos, it got emailed to the carrier, and now everyone waits and hopes. "Maybe it comes back, maybe it doesn't." That framing is the root of the leakage, because nobody builds a follow-up system around a maybe.

Think about what a supplement actually represents. Your crew tore off the roof and found a second layer that the initial scope didn't account for. Your estimator documented a code-required item — drip edge, ice-and-water shield to code, a ventilation component — that the carrier's first estimate omitted. Your field notes and photos show steep-pitch or two-story access that changes the labor. Each of those is a factual condition you observed and documented. You're not inventing it; you're requesting that the documented reality be reflected. That is work and evidence you already produced. The request to have it reflected in the approved scope is, in cash terms, an invoice waiting to be paid.

The receivable framing changes three things immediately:

1. It assigns ownership. A maybe belongs to nobody. A receivable belongs to whoever is responsible for collecting it. The moment you call it a receivable, the question "who owns this number" has to be answered.
2. It creates an aging clock. Receivables age. The day you submit a supplement, a clock starts. Thirty days is normal. Sixty days means something is stuck. Ninety days means the file is at real risk of dying. You can't manage what you don't date-stamp.
3. It makes the number visible to the owner. When pending supplements live in a head or a private spreadsheet, the owner sees a fuzzy "we have some stuff out there." When they live on a ledger with a total at the bottom, the owner sees "$83,400 in submitted supplements, $31,000 of it over 60 days." That number gets attention. Attention is what closes files.

There is also a documentation-completeness angle that the receivable framing forces. In accounting, an invoice that goes out incomplete — wrong PO, missing line item, no backup — gets disputed and delayed. Same with supplements. A supplement submitted without the page-cited photos, the measurements, the code reference, and a clean factual narrative is the equivalent of an invoice with no backup attached. It will sit. The receivables discipline of "never send it incomplete" maps directly onto "never submit a supplement without the evidence index attached."

The cost of not tracking: where the money actually goes

Before building the ledger, it helps to name the specific failure modes, because the ledger is designed to catch each one. In restoration roofing, leaked revenue usually escapes through five doors.

Missed scope at the kitchen table. The first estimate is light and nobody ever builds the supplement. This isn't a tracking failure exactly — it's an upstream documentation failure — but it feeds the ledger, because a scope item you never documented can never become a tracked receivable. The ledger's intake step is where you catch it.

Unclaimed recoverable depreciation. This is the quietest and often the largest leak. On a replacement-cost-value claim, the carrier typically pays the actual-cash-value amount up front and holds back the depreciation, releasing it once the work is complete and documented. If nobody tracks which jobs have completed work with depreciation still held back, that money never gets requested. The homeowner doesn't know to ask, the file is closed in the crew's mind, and a $3,000-to-$8,000 holdback evaporates. The National Association of Insurance Commissioners' consumer materials describe how RCV claims hold back depreciation pending completion; the operational point for a contractor is simply: completed job + held-back depreciation = a documentation task that must be tracked to completion.

Dead supplements. Submitted, then nothing. A desk adjuster asked a clarifying question, or requested an additional photo, and the request landed in a shared inbox nobody owns. Two weeks pass, then a month. The file goes cold. The supplement isn't denied — it's abandoned, which from a cash standpoint is the same thing.

Stalled paperwork. Certificate of completion not sent. Final invoice not uploaded. Lien waiver or other closeout document missing. The approved money is sitting there waiting for one piece of paper that nobody is assigned to produce.

Documentation gaps that weaken the request. A supplement with thin backup gets pushback, and pushback that nobody answers becomes a dead supplement. Weak documentation doesn't just lower approval odds on one item; it slows the whole file and consumes the follow-up bandwidth you need for everything else.

Notice that four of those five are tracking-and-follow-up failures, not estimating failures. The roofs were correctly scoped and the work was real. The money leaked because no system held the file from "submitted" to "paid." That is precisely the gap an A/R-style ledger closes.

The core model: a supplement aging ledger

The heart of the system is a single ledger where every pending supplement and every held-back depreciation amount lives as a row, ages in days, and has an owner. Build it in whatever you already have — a spreadsheet is completely sufficient to start, and we will spec the spreadsheet version in detail. The model matters more than the tool.

The line item: what one row represents

A receivables ledger has one row per invoice. A supplement ledger should have one row per distinct pending money event on a job. That usually means a single job can have more than one row:

• The supplement request itself (additional scope submitted).
• The recoverable depreciation holdback (a separate clock with separate triggers).
• Occasionally a second supplement on the same job (a follow-up after tear-off revealed more).

Keeping these as separate rows matters because they age differently and clear differently. A supplement clears when the carrier approves the revised scope. Depreciation clears when completion documents are submitted and the holdback is released. Lumping them into one "job status" hides the fact that the work is done and only the depreciation paperwork is missing — which is the single most recoverable category of leak.

The columns

Here is the full column set for a working ledger. Treat the first block as required and the second as high-value-if-you-can-maintain-it.

The high-value-if-you-can block:

That last block is what turns the ledger from a to-do list into an analytics engine. Once you have a few hundred rows of reason category and outcome, you can see which documentation gaps cause the most pushback and fix them upstream.

Aging buckets and what each one means

The aging buckets are not decoration. Each one carries a different operational meaning and a different default action.

0-30 days (Current). Normal cycle. The carrier is reviewing; you are not late and neither are they, usually. Default action: one confirmation touch around day 7-10 to verify the submission was received and is in queue. No pressure, just a received-confirmation.

31-60 days (Watch). Past the comfortable window. If you haven't had a substantive response, something is slowing it. Default action: a specific, documented follow-up referencing the submission date and asking for status. Confirm nothing is missing on the carrier's side and that no additional factual information has been requested of you.

61-90 days (At risk). This is where files start dying. Default action: escalate ownership. The coordinator's routine email isn't moving it; it needs a manager touch, a phone call, and a re-verification that the file is complete on your end. Many of these are stuck on a question you never saw.

90+ days (Critical). Real risk of total loss. Default action: owner-level review. Decide deliberately: re-document and resubmit, escalate within the carrier's process, or — if this has become a coverage or causation dispute rather than a documentation question — recognize that it has left the operational lane and route it to the homeowner and a qualified licensed professional. (More on that boundary below.) A 90+ row should never just sit; it gets a decision.

The single behavior that recovers the most money is simply looking at the 61-90 and 90+ buckets every single week. That is the supplement equivalent of an A/R manager calling on the oldest invoices first. Most of what dies in those buckets dies from neglect, not from a real denial.

Building the ledger in a spreadsheet (step by step)

You can run this in a spreadsheet for a long time before you need anything fancier. Here is a concrete build that a coordinator can stand up in an afternoon.

Step 1 — One sheet, one row per money event

Create a single tab called LEDGER with the columns above as the header row. Resist the urge to make a tab per month or per rep; a single, filterable ledger is the whole point. You want one place where the total at the bottom is the true sum of all pending money.

Step 2 — Make aging automatic

The "Days aging" column should never be typed by hand. Use a formula so it recalculates every day the sheet is opened:

Days aging  = TODAY() - [Date submitted]
Aging bucket = IF(Days>90,"90+", IF(Days>60,"61-90", IF(Days>30,"31-60","0-30")))

Then conditionally format the bucket column: green for 0-30, yellow for 31-60, orange for 61-90, red for 90+. The instant somebody opens the sheet, the red rows draw the eye. That visual is doing the same job as a highlighted overdue invoice.

Step 3 — Build the worklist view

Add a second tab called TODAY. It filters the ledger to rows where Next action date is on or before today, sorted oldest-aging first. This is the coordinator's morning screen. They don't scan the whole ledger; they work the TODAY list top to bottom. A receivables clerk doesn't read the entire A/R report every morning — they work the call list. Same idea.

Step 4 — Build the Monday rollup

Add a third tab called ROLLUP with a small summary table the owner looks at weekly:

Use COUNTIF/SUMIF against the bucket column. Now the owner has, in one glance, the same instrument as the A/R aging summary: how much is current, how much is stuck, and whether the stuck pile is growing or shrinking week over week. The 90+ dollar figure is the one to watch obsessively. If it climbs, files are dying faster than you're closing them.

Step 5 — Lock the discipline of "no row without an owner and a next action"

The two columns that kill the system if left blank are Owner and Next action date. Add conditional formatting that turns a row red if either is empty. A pending supplement with no owner is the exact thing that leaks. Make a blank owner physically impossible to ignore.

A worked example

Make it concrete. Suppose your ledger on a given Monday holds these rows (simplified):

Five rows, $19,050 pending. Read what the ledger is telling you:

• Job 4452 is the highest-value, lowest-effort recovery on the board. The work is done, $4,600 of depreciation is sitting there, and it simply hasn't been submitted. That row alone justifies the entire system. Without the ledger, this is exactly the kind of money that evaporates because the crew considered the job "finished."
• Job 4419 is stuck on a missing photo — an info request that landed somewhere and didn't get answered. The ledger surfaces it as a specific, closeable action, not a vague "check on 4419."
• Job 4388 has crossed into the at-risk bucket while still in plain "Submitted" status, meaning 71 days passed with no substantive response. That is a manager-touch signal.
• Job 4361 is the one to decide on, not drift on. Approved but unpaid for 96 days usually means a closeout document is missing. If instead it has turned into a dispute over what's covered, that is the moment it leaves the operational lane.

That is the whole value proposition of the ledger in one screen: it converts a fog of "stuff we have out there" into a ranked, owned, dollar-weighted worklist.

The follow-up cadence

A ledger without a cadence is just a nicer way to watch money die slowly. The cadence is the engine. Model it on how a disciplined A/R function works: regular, scheduled, escalating, and documented.

Daily (the coordinator, 20-30 minutes)

Work the TODAY tab top to bottom. For each row due:

1. Take the specific next action (send the document, make the call, answer the question).
2. Log the contact: update Last contact with date and channel.
3. Set the next action and next action date. A row should essentially never leave a daily session without a future date on it. If there is genuinely nothing to do until the carrier responds, set a tickler date (e.g., +7 days) rather than leaving it blank.

The daily session has one rule: every row you touch leaves with a future date. That single rule is what prevents the silent gaps where a file ages 40 days untouched.

Weekly (the production or supplement manager, 30-45 minutes)

Review the 61-90 and 90+ buckets specifically. For each:

• Confirm nothing is pending on your side. The most common reason a file is stuck at 70 days is an unanswered carrier request, and that's on you, not them.
• Escalate ownership where the routine cadence isn't moving it. A manager phone call moves files that emails don't.
• Make explicit keep-or-route decisions on the 90+ rows. Nothing in 90+ should drift another week without a decision.

Weekly (the owner, 10 minutes)

Look at the ROLLUP tab. Ask three questions: Is total pending growing or shrinking? Is the 90+ dollar figure growing or shrinking? Are there rows with no owner? That's it. Ten minutes of owner attention on the rollup creates more accountability than any amount of software, because the team knows the number gets looked at.

Cadence cheat sheet

What a follow-up actually says

The content of a follow-up matters as much as the timing, and this is where the UPPA boundary lives in day-to-day language. A good contractor follow-up is a documentation and status inquiry, not an argument about entitlement. Keep it factual:

• "We submitted the additional documented scope on [date]. Could you confirm it was received and let us know if any additional factual information or photos would help your review?"
• "The work on this property was completed on [date]; completion documentation and photos are attached. Please let us know what else you need to process the file."
• "You requested an additional photo of the valley flashing; it's attached, with the corresponding measurement. Happy to provide anything else that supports the review."

What you are doing is confirming receipt, supplying factual support, and asking what else the reviewer needs. What you are not doing — because it isn't your role and crosses into licensed-professional territory — is telling the carrier what they owe, asserting what the policy covers, or pressing for a particular settlement. Status and documentation are squarely operational. Coverage and entitlement are not. We'll draw that line sharply in the next section.

The documentation pipeline that feeds the ledger

A receivables ledger is only as good as the invoices feeding it, and a supplement ledger is only as good as the documentation behind each row. A clean, well-documented supplement ages faster and closes more reliably because there's nothing for a reviewer to bounce. So the system has a front end: a documentation pipeline that turns field reality into a submittable, evidence-backed packet before the row ever hits the aging clock.

Think of it as four gates a supplement passes through before it counts as a tracked receivable.

Gate 1 — Capture (in the field)

Every condition that could become a supplement line gets documented at the moment it's visible, not reconstructed from memory three weeks later. That means:

• Photos with context: a wide shot establishing location, then the close-up showing the condition. A flashing photo nobody can place on the roof is nearly useless in a review.
• Measurements tied to the photo where dimension drives the line item (steep pitch, story height, linear feet of a code-required component).
• A short factual field note: what was found, where, on what date, by whom.

A practical field rule: photograph the condition as if the person reviewing it has never seen the roof and never will. Because they haven't and they won't.

Gate 2 — Structure (turn documents into data)

Everything that comes in — the carrier's estimate, your estimate, photo sets, measurement reports, invoices — should be turned into structured, referenceable data rather than living as a pile of PDFs in a folder. The practical version of this is page-cited extraction: when a line item is in question, you can point to the exact page and field in a document that supports it. "The drip edge is on page 3, line 14 of our estimate and absent from the carrier's estimate; here are the two photos and the code reference." That precision is what makes a supplement reviewable instead of disputable.

This is also where you build the internal comparison between your documented scope and the carrier's estimate — a side-by-side that flags every line you documented that their estimate omitted. That comparison is internal and factual: it identifies documentation gaps for your own review. It is not a coverage determination.

Gate 3 — Completeness check (the gate that protects the ledger)

Before a supplement is submitted — before it becomes a row with an aging clock — it passes a completeness check. The Doc completeness column on the ledger exists so that nothing submitted incomplete starts aging. The check is a short, fixed list:

• Every requested line item has supporting photo evidence
• Every dimension-driven item has a measurement
• Code-required items cite the applicable code provision
• The factual narrative is plain and references the evidence
• Nothing in the packet asserts coverage, entitlement, or what is owed
• A human has reviewed and approved everything insurer-facing

That last two checkboxes are the compliance gate. Nothing goes to a carrier without a person reviewing it, and nothing in the packet crosses into coverage or entitlement language. This is non-negotiable, and it's where automation must stop and a human must sign off.

Gate 4 — Submit and clock

Only now does the supplement become a tracked row: date-stamped, owned, aging. Because it passed the completeness gate, it ages cleanly — there's nothing for the carrier to bounce it on, which is exactly why disciplined documentation up front produces faster cycle times on the back end.

The pipeline as a flow

Field capture  ->  Structure (page-cited data)  ->  Internal scope comparison
      ->  Completeness check (+ human approval)  ->  Submit  ->  LEDGER row (aging starts)
      ->  Cadence (follow-up)  ->  Approved / Released  ->  Closeout docs  ->  Closed

Each completed job also generates a parallel depreciation row at the completion step, with its own clock and its own closeout-document trigger. That parallel track is where the largest, quietest recoveries live.

The UPPA boundary, drawn sharply for tracking and follow-up

Because this entire system lives next to insurance claims, the line between operational documentation and unlicensed public adjusting has to be explicit. Public-adjuster licensing exists in every state and is administered by state departments of insurance; the National Association of Insurance Commissioners maintains model standards, and states like Texas (through the Texas Department of Insurance) publish specific guidance on what unlicensed parties may not do. The safe, simple rule for a contractor: you document your own work and follow up on your own paperwork; the homeowner files the claim and the insurer decides it.

Here is how that maps onto the ledger and cadence specifically:

The phrases to keep out of every follow-up, note, and packet are the entitlement-and-coverage phrases: "the policy says," "they owe you," "you're entitled to," "demand," "bad faith," "proof of loss," "settlement offer," "waive the deductible." The safe rewrites are the documentation phrases: instead of "they owe this," write "the documented scope shows this"; instead of "the policy covers it," write "please route for coverage review"; instead of telling a homeowner what they should get, write a factual document request.

And there's a clean operational trigger for the boundary built right into the aging buckets. When a 90+ row stops being a documentation-or-status question and becomes a dispute over what is covered or what caused the damage, it has left the operational lane. That is the moment to route it: hand it back to the homeowner, who can engage a licensed public adjuster or attorney for coverage and causation questions. Coverage disputes, denials, appraisal, and proof of loss are not contractor follow-up tasks. Building that hand-off into the 90+ decision keeps the whole system on the right side of the line — you pursue documentation and status relentlessly, and you route entitlement and coverage out.

Metrics: running the ledger like a real receivables function

Once the ledger has been running for a quarter, it produces numbers worth managing. A few that earn their keep:

Days Sales Outstanding, supplement edition. Average days a supplement spends from submitted to approved. Trend it. If it's creeping up, your follow-up cadence is slipping or your documentation is getting bounced more. A clean number here is the single best indicator that the system is healthy.

Depreciation recovery rate. Of jobs that completed with held-back depreciation in a period, what percentage had the depreciation actually released? This should be very high — close to all of it — because completed work plus completion documents is the most recoverable category. If this number is mediocre, you have found a large, fixable leak.

90+ aging dollars, week over week. The owner's headline metric. Growing means files are dying faster than you close them. Shrinking means the cadence is working.

Bounce-back rate by reason category. Using the Reason category and Outcome columns, see which documentation types get pushback most. If "access" supplements bounce constantly, your field capture of story height and pitch needs work. This is the analytics loop that improves the front-end pipeline.

Touch compliance. Percentage of rows that received their scheduled touch on time. This is the early-warning metric. When touch compliance slips, the dollar metrics follow a few weeks later. Watch it like a leading indicator.

None of these require special software. They're COUNTIF and AVERAGEIF formulas against the ledger you already built. The point isn't sophistication; it's that you're now managing pending supplements with the same instruments accounting uses for cash, which is exactly the level of seriousness the money deserves.

A short note on how to read these numbers together, because looking at any one in isolation can mislead. Touch compliance is the leading indicator; if it dips below where you want it, expect supplement DSO to drift upward roughly two to three weeks later and the 90+ dollar figure to swell a few weeks after that. So the order you should watch them in is the reverse of the order they matter: touch compliance first as the early warning, then DSO as the mid-cycle confirmation, then the 90+ bucket as the lagging proof. If you only react when the 90+ dollars climb, you're reacting to damage that was set in motion a month earlier. The whole reason a real A/R function watches call volume and contact rates alongside the aging total is that the activity metrics move first. Borrow that habit. Pair it with a simple monthly review of bounce-back reasons, and you close the loop between what dies on the back end and what you fix on the front end — the access photos, the code citations, the measurements — so next quarter's submissions age cleaner than this quarter's did.

When the spreadsheet starts to creak — and where a documentation platform fits

A spreadsheet ledger will carry a small or mid-size restoration operation a long way. The discipline matters far more than the tooling, and most companies should start exactly where the model above points: a single tab, automatic aging, a daily worklist, a weekly rollup. If you take nothing else from here, build that.

The spreadsheet starts to creak at predictable points. When you're running enough volume that the documentation behind each row — the photo sets, the measurements, the carrier estimate versus your estimate, the page-cited support — becomes too much to keep linked by hand. When the completeness gate is only as reliable as whoever remembered to check it. When you want the internal scope comparison built automatically instead of eyeballed. When you want the audit trail of who touched what, when, and what the human approver signed off on. Those are document-and-evidence problems more than ledger problems, and they're where a purpose-built documentation system earns its place on top of the tracking discipline you've already established.

This is the part of the workflow RoofClaimRCM, the claim revenue-cycle side of RoofPredict, is built for. It treats every document on a job — the carrier estimate, your estimate, field photos, measurement reports, invoices — as verified, page-cited structured data rather than a folder of PDFs, builds the internal carrier-estimate-versus-contractor-estimate comparison that surfaces documented gaps, and tracks each gap as an evidence-linked documentation opportunity from the kitchen table through to the depreciation check and material order. The completeness and approval gates are enforced rather than remembered: nothing insurer-facing moves without a human review step, and the language stays on the factual-documentation side of the UPPA line by design — document requests and factual support, never coverage conclusions or entitlement claims. The aging-ledger thinking in this piece is exactly the operating model it runs on, with the documentation pipeline wired in underneath so the rows feeding your aging report are complete before they ever start aging.

Honest limits, because the receivable framing can be taken too far. A tracking system does not change what a carrier ultimately approves; it makes sure nothing dies from neglect and that every request is as well-documented and as well-followed-up as it can be. It does not, and must not, push into coverage or entitlement — those remain the homeowner's and the insurer's domain, with licensed professionals for disputes. And no platform removes the human approval step on anything insurer-facing; that gate is a feature, not friction. What disciplined tracking reliably does is stop the quiet leaks: the unsent depreciation, the dead supplement, the unanswered info request, the missing closeout document. That category of loss is entirely within your control, and it's usually the difference between a restoration operation that wonders where its margin went and one that collects what it documented.

A 30-day rollout you can actually run

If this is new, don't try to build the analytics engine on day one. Sequence it.

Week 1 — Stand up the ledger. Build the single tab with the required columns and automatic aging. Back-fill every pending supplement and every completed-but-undepreciated job you can find. This back-fill alone usually surfaces money — the depreciation rows nobody was tracking. Assign an owner to every row. Make blank-owner rows turn red.

Week 2 — Start the cadence. The coordinator works the TODAY tab daily. Every touched row leaves with a future date. Don't worry about elegance; worry about the rule that no row goes silent.

Week 3 — Add the gates. Put the completeness checklist in front of every new submission so new rows enter the ledger clean. Start logging Reason category and Outcome so you'll have analytics later.

Week 4 — Turn on the rollup and the owner review. Build the ROLLUP tab. The owner spends ten minutes on it weekly and starts asking about the 90+ bucket. The moment the team knows that number is being watched, behavior changes.

After a quarter, you'll have your first real DSO and depreciation-recovery numbers, and you'll know exactly which documentation categories cause pushback. That's when the question of a purpose-built platform stops being theoretical and starts being a clear decision based on your own data.

The core idea is the simplest part: money you've documented and earned but not yet collected is a receivable, whether it's an invoice or a pending supplement. Track it like one. Give it an owner, an aging clock, and a cadence. Watch the oldest buckets every week. Keep the documentation complete and the language factual. Do that, and the revenue that used to leak quietly out the back — the unsent depreciation, the dead supplement, the forgotten closeout — stays on your ledger, where you can collect it.

FAQ

Why should I treat a pending supplement like a receivable instead of just tracking job status?

Because the two age and clear differently, and lumping them hides money. A job can be marked 'complete' in production while a $4,000 depreciation holdback or a submitted supplement is still outstanding. Tracking it as a separate receivable row — with its own owner, aging clock, and dollar amount — forces a follow-up system around money you've already earned, which job-status tracking alone never does.

What columns does a supplement aging ledger actually need?

At minimum: job/claim ID, carrier, row type (supplement vs depreciation vs closeout), amount pending, date submitted, days aging (a formula, never typed), aging bucket, status, owner, next action, next action date, last contact, and documentation completeness. High-value additions are reason category and outcome, which turn the ledger into an analytics tool that shows which documentation gaps cause the most pushback.

What aging buckets should I use for pending supplements?

The same shape as accounts receivable: 0-30 (current, one confirmation touch), 31-60 (watch, documented status follow-up), 61-90 (at risk, escalate to a manager phone call), and 90+ (critical, owner-level decision to resubmit, escalate, or route out). Reviewing the 61-90 and 90+ buckets every single week is the single behavior that recovers the most money, because most files in those buckets die from neglect rather than denial.

Where does most restoration supplement revenue actually leak?

Five places: missed scope at the kitchen table, unclaimed recoverable depreciation on completed jobs, dead supplements that stalled on an unanswered carrier request, stalled closeout paperwork on already-approved money, and weak documentation that invites pushback. Four of those five are tracking-and-follow-up failures, not estimating failures — the work was real and correctly scoped, but no system carried the file from submitted to paid.

How do I track recoverable depreciation so it doesn't get forgotten?

Give it its own ledger row, separate from any supplement, created at the moment the job completes. On a replacement-cost claim the carrier typically pays actual cash value up front and holds depreciation back until completion is documented. So the depreciation row's trigger is 'work complete + completion documents submitted.' Tracking it separately is what keeps the crew's sense of 'job finished' from quietly closing a file that still has thousands in held-back money.

What does a compliant supplement follow-up message look like?

It confirms receipt, supplies factual support, and asks what else the reviewer needs — for example, 'We submitted the documented additional scope on [date]; could you confirm receipt and let us know if any additional photos would help your review?' It never tells the carrier what they owe, asserts what the policy covers, or pushes a settlement. Status and documentation are operational and fine; coverage and entitlement language are not, because they cross into licensed-professional territory.

When does following up on a supplement cross into unlicensed public adjusting?

The line is clean: documenting your own work and following up on your own submitted paperwork is operational and allowed; representing the homeowner, negotiating a settlement, or interpreting coverage is not. The practical trigger is when a file stops being a documentation-or-status question and becomes a dispute over what's covered or what caused the damage. At that point it leaves the contractor's lane and should be routed back to the homeowner, who can engage a licensed public adjuster or attorney.

Can I run this in a spreadsheet, or do I need software?

A spreadsheet is completely sufficient to start and will carry a small or mid-size operation a long way. You need one tab with automatic aging formulas, a daily worklist view filtered to rows due today, and a weekly rollup with COUNTIF/SUMIF by bucket. The discipline matters far more than the tooling. Software earns its place later, when the documentation behind each row — photos, measurements, page-cited estimate comparisons, audit trail — becomes too much to keep linked by hand.

What metrics tell me the supplement ledger is working?

Supplement DSO (average days from submitted to approved, trended over time), depreciation recovery rate (percentage of completed jobs whose depreciation was actually released — this should be near-total), 90+ aging dollars week over week (the owner's headline number), bounce-back rate by reason category (where your front-end documentation needs work), and touch compliance (the leading indicator — when scheduled follow-ups slip, the dollar metrics follow a few weeks later).

What's the fastest money this system usually surfaces?

Unsent recoverable depreciation on completed jobs. When you back-fill the ledger in week one, you typically find jobs where the work is done, completion documents were never submitted, and several thousand dollars of held-back depreciation has simply been sitting there. It's the highest-value, lowest-effort category because the work and the documentation already exist — the only thing missing is the closeout submission and the follow-up to release it.