You bid the job at a healthy margin. The revenue is on schedule, the billings look fine, and the project still shows green on the dashboard. Then you rebuild the WIP at year-end and the projected gross profit has quietly collapsed, too late to do anything but explain it. That is profit fade, and in construction the problem is almost never the fade itself. It's that a year-end-only WIP turns a slow, recoverable margin slide into a closeout surprise.
Profit fade in construction is your projected job margin shrinking as estimated costs climb over the life of the job. This post covers what causes it, why it stays hidden until year-end, and (the part the typical "5 tips to avoid profit fade" article skips) exactly how a Controller catches it off a monthly WIP, before close, while there's still margin left to protect.
What Is Profit Fade in Construction?
Profit fade in construction is the shrinkage of a project's projected gross margin over its life, as the Estimated Cost at Completion (EAC) rises above the cost you assumed at bid. You win a job at 22% gross profit; by month three the estimated total costs climb, the projected margin compresses, and the job you priced as a winner is now a thin one. As one surety underwriter puts it, "Profit fades occur when the actual costs of a project exceed initial estimates, eroding profitability." Mahki Abner, Old Republic Surety, NASBP Pipeline, 2025
The mechanics are pure WIP math. Under ASC 606 and the percentage-of-completion (cost-to-cost) method, Estimated Gross Profit = Contract Value − EAC, and margin % = Estimated Gross Profit ÷ Contract Value. Foundation Software EAC is costs incurred to date + ETC (Estimate to Complete): the PM's estimate of what's left to spend. When the ETC creeps up cycle over cycle, EAC rises, and the projected margin falls. That gap between your bid margin and your current EAC-based margin is the fade.
The framing comes straight from practitioners: "Profit fade is when your estimated job margin shrinks over the life of a job. You bid a job at 22% GP. By month three the estimated total costs" rise and the margin falls. Civil CFO
Here is what it looks like on one job. Take Lincoln HS Renovation, run by Meridian Construction Group. On revenue, the job reads fine. At 78% complete it has billed $8.4M against an $11.2M contract, right on schedule. But the EAC has climbed from roughly $10.2M at bid to $11.09M today, and that single move compresses the projected margin from about 9% to 1.0%.
| Metric | At bid | Today (78% complete) |
|---|---|---|
| Contract value | $11,200,000 | $11,200,000 |
| Estimated total cost (EAC) | ~$10,192,000 | $11,090,000 |
| Estimated gross profit | ~$1,008,000 | $110,000 |
| Gross margin | ~9% | 1.0% |
Lincoln HS Renovation, Meridian Construction Group — synthetic example, ASC 606 cost-to-cost. % complete = $8.65M costs to date ÷ $11.09M EAC = 78.0%. Margin = ($11.2M − $11.09M) ÷ $11.2M = 1.0%.
The most dangerous job on the schedule isn't the one already flashing red. It's this one: on schedule, fully billed, and quietly down to a 1.0% margin. Without a monthly WIP, that slide is invisible until year-end close.
What Causes Profit Fade on a Job?
Profit fade has a short list of causes, and every one of them shows up in a column on the WIP before it shows up in your year-end number. The job costs more to finish than you bid, the ETC rises, EAC rises, and the projected margin erodes. The value of naming the causes is that each one maps to a WIP input you can watch.
- Underestimated ETC. The single most common driver. The PM's Estimate to Complete was too low at bid or hasn't kept up with the field. It surfaces as the ETC column climbing cycle over cycle. Sureties watch exactly this: "If your 'estimated costs to complete' keeps climbing on the same project, your original estimate was wrong and you are chasing the number." Projul
- Scope creep and unapproved change orders. Work is being performed and costs are accruing, but the change order hasn't been approved and added to contract value. Costs go up, revenue doesn't — margin fades. It shows up as costs-to-date outrunning the contract.
- Productivity loss. Labor and equipment burning more hours per unit of work than estimated. The crew is busy; the job is bleeding. It surfaces as cost-to-date rising faster than percent complete.
- Estimating error at bid. The job was underpriced from day one; every WIP just confirms it. The fade is baked in, and the only question is when you see it.
- Late-stage underbillings on a losing job. Underbillings (earned revenue you haven't billed yet) can be a warning, not just a timing quirk. Per Old Republic Surety, "Underbillings can signal deeper financial challenges, particularly when they contribute to profit fades" (NASBP Pipeline, 2025).
The throughline: profit fade is computed entirely from inputs that already live on your WIP: bid margin versus current EAC-based margin. That is also why it can be caught early, and eventually flagged automatically, instead of discovered at year-end.
Why Does Profit Fade Hide Until Year-End?
Profit fade hides until year-end for one operational reason: it only becomes visible when you rebuild the WIP, and most teams rebuild it too infrequently to catch the slide while it's still small. A faded margin doesn't announce itself. The revenue is still flowing, the billings still go out, the job still looks busy. The number that moved, projected gross profit, lives only inside a current WIP. Build the WIP once a year, and you learn about a year's worth of fade in a single sitting.
This is the operational wedge the typical profit-fade article misses. Fade isn't a reporting failure; it's a cadence failure. Run the WIP monthly and a 2-point slip is a question you ask the PM in week one. Run it at year-end and the same slip has compounded across twelve months and several jobs into a closeout you have to explain to the CFO and the bonding agent.
The cadence guidance is explicit. A profit fade analysis "should be done monthly, at a minimum." CMAA, "How to Analyze WIP Schedules" The reason monthly beats annual isn't diligence for its own sake. It's that a year-end-only WIP "means the surety is making decisions for 12 months based on a single snapshot. Projects come and go, margins shift, and capacity changes throughout the year." Grit Insurance The same snapshot problem is why fade stays hidden from you.
How Do You Catch Profit Fade Before Close (Not at Year-End)?
You catch profit fade before close by treating it as a monthly metric, not a year-end discovery: produce or refresh the WIP every month, compute each job's current EAC-based margin, compare it to the bid margin, and review any job whose margin has slipped past a threshold you set. The catch is mechanical, it runs off data you already collect, and it takes minutes once the WIP exists. Here is the workflow a Controller can run every close.
- Produce or update the WIP monthly. Pull current contract value, costs-to-date, and billings for every active project, and collect a fresh ETC from each PM. Most of this already sits in your project and accounting systems; the ETC is the one input you have to gather each cycle. (See whether Procore can generate the WIP report itself.)
- Compute the current EAC-based margin per job. For each project: EAC = costs-to-date + ETC; Estimated Gross Profit = Contract Value − EAC; current margin % = that profit ÷ contract value (Foundation Software).
- Compare current margin to bid margin. The delta between the margin you priced and the margin you're projecting today is the fade, in points. A job bid at 9% now projecting 1.0% has faded 8 points.
- Flag any job whose fade exceeds your threshold. Pick a slippage threshold and apply it consistently — a few percentage points is a reasonable starting point (more on the number below). Any job past it goes on the review list, before the WIP is finalized.
- Investigate before close, not after. For each flagged job, find the cause (rising ETC, an unapproved change order, a productivity problem) and decide what to do while there's still a job left to manage. The whole point of monthly cadence is that "before close" is a position you can act from. Year-end isn't.
Run this every month and profit fade stops being a closeout shock. It becomes a short list of two or three jobs you've already discussed with their PMs, which is exactly the position you want to be in when the bonding agent calls.
How Much Margin Slippage Should Trigger a Review?
There is no universal number, but a practical starting point is to review any job whose projected margin has dropped a few percentage points (on the order of 5 points) from its bid margin, then tune that threshold to your portfolio's risk. A high-volume, thin-margin GC and a selective heavy-civil contractor will draw the line in different places. The 5-point figure is a starting threshold, not a rule: set it where a slip is big enough to matter on your jobs but small enough to catch while it's still recoverable.
What matters more than the exact number is applying it consistently across every job, every month, so fade can't slip through because nobody was watching a particular project. A single faded job is ordinary variance. Estimates move, conditions change. The signal worth escalating is the pattern: several jobs fading at once, or the same job's ETC climbing cycle after cycle. That pattern is what your surety reads too.
Why Does Your Surety Care About a Pattern of Profit Fade?
Your surety cares about profit fade because one faded job is noise but a pattern across jobs is a signal. It tells the underwriter your estimating or project management is unreliable, and that costs you bonding capacity. The WIP is the document the underwriter reads to answer four questions: are your jobs profitable, are you billing accurately, are you overextended, and are your cost estimates reliable (Projul). Repeated fade answers the last two in the worst possible way. Sureties discount projections from contractors with a history of low ETC estimates, because PM optimism "can mask cost overruns until it is too late" (Projul; Grit Insurance). The WIP schedule is the artifact where all of this is visible. It's worth understanding what a WIP schedule is and who requires it.
The most concrete illustration of how this plays out comes from the surety side itself. In an Old Republic Surety analysis, one contractor's job that was 97% complete at year-end carried $296,000 in underbillings; six months later, with the job 99% complete, that figure had grown to $419,000, despite ongoing losses. The underwriter read the trend as a low likelihood of collection and disallowed those amounts from the contractor's working-capital calculation. Across the file, underbillings had inflated that contractor's working capital by nearly $3 million, overstating its financial position and its qualifying surety program (Mahki Abner, Old Republic Surety — NASBP Pipeline, 2025).
Read that example as a warning about timing as much as accounting. The picture only resolved when the surety compared one WIP to the next and saw the number going the wrong way. (Underbillings and profit fade are related but distinct signals.) A contractor running monthly WIPs sees that trend forming in real time; a contractor running a year-end WIP hands over a clean-looking snapshot the surety later marks down — losing working capital and bonding room as a result.
Frequently Asked Questions
What is profit fade in construction? Profit fade is the shrinkage of a project's projected gross margin over its life, as the Estimated Cost at Completion rises above the cost assumed at bid. A contractor bids a job at, say, 22% gross profit; rising costs push the EAC up and the projected margin compresses, sometimes to near zero. The danger isn't the fade itself. It's detecting it in time to act (Old Republic Surety — NASBP Pipeline, 2025).
What causes profit fade on a construction job? The main causes are an underestimated ETC, scope creep and unapproved change orders, productivity loss in the field, an estimating error at bid, and late-stage underbillings on a losing job. Each one shows up as a movement on the WIP (usually a rising ETC or costs-to-date outrunning the contract) before it shows up in the year-end result (Civil CFO).
How do you catch profit fade before year-end? Run the WIP monthly, compute each job's current EAC-based margin, compare it to the bid margin, and review any job whose margin has slipped past your threshold, before you finalize the close. Profit fade is computed entirely from WIP inputs, so the catch is mechanical once the monthly WIP exists (Foundation Software).
How much margin slippage should trigger a review? There's no universal figure. A common starting point is a few percentage points of slip from bid margin (around 5 points), then tune it to your portfolio. Apply the threshold consistently across every job, and escalate a pattern of fade faster than a single faded job.
What is the difference between profit fade and underbilling? Profit fade is your projected margin shrinking as EAC rises. Underbilling is earned revenue you haven't billed yet: a balance-sheet timing position, not a margin movement. They're distinct but related: per Old Republic Surety, underbillings "can signal deeper financial challenges, particularly when they contribute to profit fades," especially late in a losing job (NASBP Pipeline, 2025).
Why does a surety care about profit fade? A single fade is ordinary variance, but a pattern across jobs tells the underwriter your estimating or project management is unreliable. That erodes the confidence that sets your bonding limits. Underwriters track WIP-to-WIP trends, and a job whose ETC keeps climbing "destroys credibility" (Projul).
How often should a contractor run a profit fade analysis? Monthly, at a minimum (CMAA, "How to Analyze WIP Schedules"). Year-end-only analysis means a year of fade compounds before anyone sees it; monthly cadence turns the same fade into an early warning you can still act on.
How WIP Ready Flags Profit Fade Before Close
Old Republic Surety's own advice to contractors is to "leverage technology — use integrated accounting and project management software to maintain accurate and real-time job cost data" (NASBP Pipeline, 2025). That is the gap WIP Ready fills between closes. Between monthly WIPs, WIP Ready monitors your Procore cost data and fires a profit-fade alert when a job's projected margin drops more than your configured threshold from its bid margin, so finance gets advance warning before the close, not a surprise during it. WIP Ready product brief
The alert is computed from the same WIP inputs you already own: contract value and costs-to-date from Procore, and the ETC your PM enters. WIP Ready never invents the ETC — the PM who knows the job owns that number, which is exactly why the resulting WIP holds up with your auditor and your bonding agent. It's a reporting layer that reads from Procore; it doesn't write back, and it doesn't replace your accounting system.
If profit fade has ever ambushed you at year-end, the fix is cadence, not heroics. See how WIP Ready turns the monthly WIP into an early-warning system at wipready.com.
