You already close a WIP every month. The schedule gets built, finance ties it to the GL, and a copy goes to the bonding agent and the bank. That part is muscle memory. The part nobody hands you is the monitoring framework that sits on top of it: in a monthly WIP review, which numbers do you pull off the schedule each cycle, and what does each one tell you about where those jobs are heading?
This is for the construction controller who already runs that close and wants a named, repeatable read — not a refresher on what a WIP is. If you do need the basics first, start with what a WIP schedule is. Here are the five signals to track every month:
- Gain/fade velocity trend
- Overbilling-to-backlog ratio (per job)
- ETC staleness (days since the PM last updated)
- Underbilling aging
- Cost-to-cost POC accuracy band
Two of the five, you can't get cleanly from a static Excel WIP. We'll get to which.
What a monitoring framework adds to the monthly close
A monthly WIP close produces a document. A monitoring framework produces decisions. The difference is knowing, before you open the schedule, which metrics you'll extract, what reading triggers a conversation, and what action follows when it does.
None of these five signals is a WIP Ready invention. They're what your surety and your CPA already read. Marcum LLP is explicit that gain/fade "should be done monthly, at a minimum," and that "sureties and other recipients of contractor financial statements will do a gain/fade analysis" (Marcum LLP, Construction Business Owner). The construction-CPA association CICPAC teaches the "Profit Gain/Fade Report" for CPE credit (CICPAC). This is standard practice, not vendor language.
One framing note, because three different jobs are easy to conflate. This post is the month-in, month-out dashboard. It is not the WIP pre-renewal self-audit you run once before a surety meeting, and it is not the standalone gain/fade trend deep-dive — here that's just Signal 1. Same controller, different moments.
The 5-signal WIP monitoring framework at a glance
| Signal | What it is | What it predicts (the forward read) | Excel-computable? |
|---|---|---|---|
| 1 — Gain/Fade Velocity Trend | Period-over-period change in projected gross profit per job | Which jobs are heading toward a margin surprise before year-end | Yes — with manual trailing-period tracking |
| 2 — Overbilling-to-Backlog Ratio (per job) | A single job's overbilling (BIE) as a percentage of that job's remaining work to bill — read per project, not netted across the portfolio | Whether that job has enough remaining work to burn off the overbilling liability before it closes | Partially — each job's remaining backlog must be pulled from job-cost data each cycle |
| 3 — ETC Staleness (Days Since PM Update) | Number of days since each project's Estimate to Complete was last updated by the PM | Which POC percentages — and therefore revenue figures — are based on stale assumptions | No automatic timestamp — visible only if you hand-maintain a separate "ETC last reviewed" date column |
| 4 — Underbilling Aging | How long each underbilled project has carried an underbilling balance | Which underbillings are approaching the age where sureties will disallow them from working capital | No — aging requires historical-period tracking; a static WIP shows the balance, not its age |
| 5 — Cost-to-Cost POC Accuracy Band | Variance between the PM's subjective % complete and the cost-to-cost formula result | Which projects have systematic ETC bias — and whether the WIP is overstating or understating earned revenue | Partially — requires maintaining both POC methods per project per period |
Signal 1: what does your gain/fade trend tell you about the next quarter?
Gain/fade measures the period-over-period change in each job's projected gross profit. A gain means the EAC-based margin improved since last close; a fade means it shrank. The velocity (the direction and rate of that change across three or more cycles) is what predicts whether a job closes at a profit or a loss, well before the surprise reaches the income statement.
Marcum LLP puts the definition plainly: "If the gross profit calculation comes in higher than originally estimated, this is known as a gain. Alternatively, gross profit projected to be lower than anticipated is known as a fade" (Marcum LLP, Construction Business Owner).
What it predicts: One fade can be a timing artifact. Two consecutive fades on the same job — especially in the back half of the contract — is a strong predictor of a closeout loss. A contractor "that fades on a consistent basis will most likely render unfavorable determinations from sureties" (Marcum LLP), and underwriters treat margin fade as a red flag "particularly if it's more than a one-off and the surety begins to see margin fades as a trend" (American Global, IRMI). Catch the trend at month 6 and you have leverage to intervene. Catch it at month 11 and you have a write-off.
On a Meridian Construction Group schedule, Lincoln HS Renovation faded from a roughly 9% bid margin to 1.0% as its EAC climbed — the kind of move you want flagged at the third cycle, not at closeout. (Illustrative.)
Excel vs. Procore: Velocity needs a trailing table — three or more WIP periods compared side by side, per job. Excel can do it if the controller keeps a historical tab by hand; most don't. Procore's job-cost data already holds every period's ingredients, so WIP Ready surfaces the velocity automatically each close. For the full treatment, see reading the gain/fade trend column across periods.
Signal 2: is your overbilling position sustainable through job completion?
An overbilling (billings in excess of earned revenue) is a liability on the balance sheet, not income. The signal isn't the dollar amount; it's whether your remaining work is large enough to absorb it before the job closes. A modest overbilling on a job with millions left to bill is routine. The same overbilling on a job that's 95% complete has nowhere to go.
Compute it per job: that project's billings in excess of earned revenue (BIE, the overbilling) divided by its remaining backlog — the work it still has left to bill. Read it project by project, never netted across the portfolio, because netting all overbillings against all backlog hides the one near-complete, overbilled job you most need to see. The portfolio does have its own netted figure — what Marcum LLP calls "Total Job Borrow," total underbillings (CIE) against total overbillings (BIE), which "indicates the net percentage-of-completion adjustment" for the whole book (Marcum LLP, Construction Executive). That roll-up is useful context, but it is a different number from the per-job ratio, and it is the per-job ratio that flags the dangerous job.
What it predicts: A per-job ratio that climbs in the back half of a project predicts a cash squeeze at closeout: the contractor either returns overbilled funds or absorbs a loss the overbilling had been masking. Sureties watch this as "job borrow": "cash that is represented as overbilling for a project but is, instead, being used to fund a shortfall on another project" (IRMI).
On a Meridian Construction Group schedule, the contrast is concrete: Riverside Medical Center is overbilled by $336,000 but still carries about $5.1M of backlog left to bill — room to burn it off. Metro Transit Garage, at roughly 90% complete, has only about $0.8M of backlog; an overbilling that size there has nowhere left to go but a cash return or a closeout loss. Net the two jobs together and the portfolio looks balanced — which is exactly why you read the ratio per job. (Illustrative.)
Excel vs. Procore: Each job's remaining backlog has to be pulled from job-cost commitments — a separate export every cycle in an Excel workflow — while the BIE side sits on your WIP. In Procore, both live in the same job-cost data, so WIP Ready computes the ratio for every job each close.
Signal 3: how old are your ETC entries, and why that date matters?
Every percentage-of-completion figure on your WIP is only as current as the ETC behind it. The ETC (Estimate to Complete, the PM's estimate of the cost to finish the remaining work) feeds the EAC (Estimated Cost at Completion: costs to date plus ETC), which sets percent complete, earned revenue, and the over/under-billing position. A POC computed from an ETC that's 45 days old isn't a current number; it's a historical guess wearing a current date. ETC staleness tells you which rows of the schedule you can rely on.
This matters mechanically. The cost-to-cost method "only produces accurate calculations… if estimates are kept current" (Foundation Software). A stale ETC flows straight into a stale POC, stale earned revenue, and a stale over/under-billing balance, three lines that move both statements.
What it predicts: An ETC untouched for 30-plus days on a job past 50% complete is a leading indicator of a surprise fade. Bonding guidance already warns that project managers "tend to be optimistic, and that optimism can mask cost overruns until it is too late" (Projul). A PM who has quietly stopped updating the ETC is often avoiding exactly that conversation.
The Procore nuance: Procore does have a Forecast to Complete column — but it defaults to a net-zero automatic calculation, carries no PM attestation, and puts no timestamp on the override. Switch a line from manual entry back to automatic and "all previously added Manual Entry… items will be deleted" (Procore support). It's a budget cell, not a dated, attributed estimate.
Excel vs. Procore: You can build this signal yourself without any tool. Add an "ETC last reviewed" date column beside each job, stamp it every time a PM confirms or revises the number, then sort by that date each close so the stale rows rise to the top. It works — it just lives or dies on the discipline to hand-update a date for every job, every cycle, which is the first thing to slip in a busy close. WIP Ready records the PM's name and submission date on every ETC automatically, so staleness becomes a column you never maintain by hand — part of what makes a 45-minute WIP close repeatable.
Signal 4: which underbillings are too old to count?
Underbillings (costs and earned revenue in excess of billings) are a current asset, but only while they're collectible. An underbilling that lingers on a job at 97% complete and still losing money isn't an asset; it's a probable write-off. Surety underwriters age underbillings for exactly this reason: to separate the current and collectible from the ones that should come out of the working-capital calculation.
The anchor case is well documented. In a 2025 analysis, Old Republic Surety found underbillings had inflated one contractor's working capital "by nearly $3 million." A single project, 97% complete at year-end, carried $296,000 in underbillings; "six months later, with the project 99% complete, underbillings had grown to $419,000, despite ongoing losses." Old Republic disallowed those amounts from the contractor's working-capital calculation (Mahki Abner, Old Republic Surety, NASBP Pipeline).
What it predicts: An underbilling that keeps growing on a near-complete job is the highest-probability candidate for surety disallowance. A controller who tracks the age each month can force a billing conversation with the PM, or flag the exposure to the CFO, before the surety does it for them. It's the same shape as a Meridian job whose underbilling climbs while the margin fades: the balance looks like an asset on this month's WIP, but its trend says otherwise.
Excel vs. Procore: Aging requires knowing when each underbilling first appeared — comparing this WIP against at least two prior periods. A static Excel WIP shows the balance, not its age. You can approximate it by hand if you keep a prior-period column or a separate aging tab, but that's the second signal that depends on multi-period tracking most teams don't sustain.
Signal 5: are your PMs' POC estimates consistent with the cost-to-cost math?
Every WIP carries two implicit percent-complete figures: the PM's subjective read ("we're about 60% done") and the cost-to-cost calculation (costs incurred ÷ EAC). When they diverge by more than the tolerance you set — say, 10 percentage points — one of them is wrong. The POC accuracy band tracks that gap across every active job, every close.
The cost-to-cost figure is the disciplined one. "If you have incurred 40% of a project's expected costs, you recognize 40% of the contract value as revenue" (Saltmarsh Advisors). Cost-to-cost is an input method; the subjective estimate is "less precise and can be more prone to error" (Foundation Software). A PM who claims 60% while cost-to-cost says 40% has either understated the ETC — the job will cost more to finish than the WIP shows — or front-loaded cost-heavy early work that doesn't represent proportional progress. Either way, this period's earned revenue is overstated.
What it predicts: A systematic gap between subjective and cost-to-cost POC across several jobs from the same PM points to an estimating problem, not a one-off. Spot the pattern at month 3 and you can investigate; spot it at month 11 and you're absorbing the fade. On a Meridian schedule, Cedar Crest Apartments might show the PM reporting 70% complete while cost-to-cost computes 58% — a 12-point gap that clears a 10-point band and earns a question. (Illustrative.)
Excel vs. Procore: The band needs both POC figures — cost-to-cost from job-cost data and the PM's ETC-implied estimate — side by side, per job, per period. In Excel, the cost-to-cost numbers are a manual export and the divergence tracking is hand-built. In Procore, WIP Ready computes both from the same source each cycle.
Which signals does Excel give you, and which need connected data?
A controller working from a static Excel WIP can get part of the way. Gain/fade velocity (Signal 1) is reachable with a manually maintained trailing tab. The overbilling-to-backlog ratio (Signal 2) and the POC accuracy band (Signal 5) are partly reachable with extra job-cost pulls each cycle. ETC staleness (Signal 3) and underbilling aging (Signal 4) are the hardest two: neither lives in the WIP's own numbers, so each needs tracking you bolt on yourself — a "last reviewed" date column for staleness, a prior-period comparison to age an underbilling. You can keep both by hand, but that upkeep is the first thing to slip in a busy close. A snapshot shows the number, never its history.
That's the honest version of the Excel gap: not that Excel is wrong (it feeds your bonding company's template cleanly) but that two of the five signals need timestamps and period-over-period memory a rebuilt-from-scratch spreadsheet doesn't keep on its own. So most teams sustain two of the five at best.
What makes these five a monitoring framework rather than a close procedure is the read: each signal is backward-looking in execution but forward-looking in interpretation. Monthly data, a forward read on where each job lands.
How WIP Ready surfaces all five signals automatically from Procore data
WIP Ready reads the same Procore job-cost data that drives your budget and the Forecast to Complete column, assembles it into an ASC 606 cost-to-cost WIP schedule, and surfaces each of the five signals as a metric you read each close — not a report you rebuild. Gain/fade velocity comes from the trailing periods it already holds. The overbilling-to-backlog ratio and the POC accuracy band come from pairing the WIP with job-cost backlog in the same data layer. And the two Excel can't sustain — ETC staleness and underbilling aging — come from the part WIP Ready adds: every ETC arrives through a no-login mobile form, stamped with the PM's name, a date, and a note, and every balance is compared against prior cycles automatically.
WIP Ready never calculates the ETC; the PM owns that number, which is what keeps the WIP defensible with your surety and your CPA. There's no migration and no second system of record — it reads from Procore and never writes back.
If you run a monthly WIP review and want these five signals computed for you instead of assembled by hand, see how it works at wipready.com.
Frequently asked questions
What is a monthly WIP review for a construction controller? A monthly WIP review is the read a construction controller runs at financial close to pull the current financial status of every active job off the WIP schedule. A review framework goes one step further: the same five diagnostic signals get applied every cycle — gain/fade velocity, the overbilling-to-backlog ratio, ETC staleness, underbilling aging, and cost-to-cost POC accuracy — so the controller knows which jobs need a conversation before the next period, not at year-end. Gain/fade analysis "should be done monthly, at a minimum," and sureties run it too (Marcum LLP).
What are the five WIP signals a construction controller should track every month? (1) Gain/fade velocity trend — the period-over-period change in each job's projected gross profit; (2) overbilling-to-backlog ratio — whether each job's overbilling is covered by its own remaining work; (3) ETC staleness — days since each PM last updated the Estimate to Complete; (4) underbilling aging — how long a job has carried an underbilling balance; and (5) cost-to-cost POC accuracy band — the gap between the PM's subjective percent complete and the cost-to-cost result. All five come off the WIP schedule, but two of them need timestamps and prior-period history a static Excel sheet doesn't keep (Foundation Software).
How do you calculate the overbilling-to-backlog ratio on a WIP schedule? For a single job, divide its billings in excess of earned revenue (BIE, the overbilling balance) by that job's remaining backlog — the uninvoiced work it has left to bill. Read it per project, not netted across the portfolio: netting every overbilling against every job's backlog hides the one near-complete, overbilled job that has nowhere left to burn it off. A ratio rising in the back half of a job is the warning. Sureties read the same math as "job borrow" — overbilling on one job quietly funding a shortfall on another (IRMI).
What does ETC staleness mean on a WIP schedule, and why does it matter? ETC staleness is the number of days since a project manager last updated the Estimate to Complete for their job. A stale ETC flows straight into a stale percentage-of-completion figure, stale earned revenue, and a stale over/under-billing balance — three numbers that hit both the income statement and the balance sheet. The cost-to-cost method "only produces accurate calculations if estimates are kept current," so the date on the ETC is part of the number's reliability (Foundation Software).
How does underbilling aging affect surety bonding capacity? Surety underwriters analyze how long each underbilling has sat on the books and whether it's still collectible. In a 2025 Old Republic Surety analysis, underbillings inflated one contractor's working capital by nearly $3 million — and the surety disallowed late-stage underbillings that kept growing despite ongoing losses, removing them from working capital entirely. The longer an underbilling persists on a near-complete, money-losing job, the less likely the surety is to count it as a real asset (NASBP / Old Republic Surety).
What is a cost-to-cost POC accuracy band on a WIP schedule? The accuracy band is the gap between a PM's subjective percent complete and the cost-to-cost result — costs incurred divided by EAC. Cost-to-cost is an input method; the subjective "estimated percent complete" is "less precise and can be more prone to error." When the two diverge by more than the tolerance a controller sets, one of them is wrong — and a systematic gap across several jobs from the same PM points to an estimating or ETC problem, not a rounding error (Foundation Software).
Which of the five WIP signals can a controller compute from Excel? Gain/fade velocity can be approximated in Excel with a manually maintained trailing-period tab. The overbilling-to-backlog ratio and the POC accuracy band are partially doable if the controller pulls the underlying job-cost data each cycle. ETC staleness and underbilling aging are the two that lean hardest on extra upkeep a static Excel WIP doesn't keep on its own — a hand-maintained "last reviewed" date column for staleness, and a prior-period comparison to age an underbilling — the kind of manual tracking that's first to slip in a busy close.
