Margin Fade: Catching Profit Erosion Before the WIP Does
A construction job rarely loses its profit all at once. It loses it the way a tire loses air — slowly, quietly, a little at a time, until someone finally checks the gauge and discovers the margin is mostly gone. The industry has a name for this: margin fade, or profit fade. It is the erosion between the gross margin a contractor estimated when it bought out the job and the margin the job actually delivers at completion. And it is one of the most damaging patterns in construction finance precisely because it is undramatic.
Fade is dangerous for two reasons. The first is that a faded job does not just earn less profit — it can swing a project from a contributor to a drag, and a few faded jobs in the same period can erase a contractor's annual earnings. The second is timing. By the time fade is unmistakable on the financial statements, the work that caused it has usually already been performed. The money is spent. The contractor is reacting to a loss instead of preventing one.
The contractors who manage fade well are not the ones who never experience it — every contractor experiences some fade. They are the ones who detect it early, while a job is at 40% or 50% complete and there is still enough remaining work to take corrective action. That is a discipline question, not a luck question, and it starts with understanding where fade actually comes from.
$0
Average annual pretax profit per employee at top-performing contractors versus far thinner results at the median — a gap that uncontrolled margin fade routinely closes (Construction Financial Management Association industry benchmarking)
Fade is not a single problem; it is a category of problems that all show up the same way on the income statement. Diagnosing fade means knowing its common sources, because the fix for one is useless against another.
The common sources of margin fade
- Unpriced and under-priced change orders — extra work is performed before it is priced and approved, or it is priced too thin to recover its true cost; the cost lands in job cost while the revenue lags or never fully arrives
- Productivity loss — crews install at a slower rate than the estimate assumed, so labor hours overrun without any corresponding increase in contract value
- Buyout shortfalls — the subcontracts and material purchases come in above the values carried in the estimate, so the job starts behind before a shovel hits the ground
- Scope gaps — work that nobody priced into the estimate or the subcontracts becomes the contractor's cost to absorb
- Escalation — material and labor costs rise between the bid and the buy, and on a fixed-price job the contractor eats the difference
- Rework and quality cost — defective or rejected work has to be redone, doubling the cost of that scope while the contract value stays flat
- Schedule slippage and extended general conditions — a job that runs long keeps incurring supervision, equipment, and overhead costs the original duration never budgeted
Notice what these sources share: in almost every case, cost rises while contract value does not. That asymmetry is the mechanical signature of fade. A contractor that wants to control fade is really trying to keep contract value moving in step with cost — recovering for extra work, holding productivity to the estimate, and buying out at or below the numbers the bid was built on.
The work-in-progress schedule is the contractor's primary tool for measuring job profitability, and it is built around percentage-of-completion accounting. On most commercial work, percent complete is measured cost-to-cost — costs incurred to date divided by total estimated cost — and that percentage is applied to the contract value to recognize revenue. The mechanism is sound. The problem is the cadence.
Most contractors close their WIP monthly. That means a job can be quietly fading for an entire month — productivity slipping, change order work piling up unpriced, costs running over the estimate — and none of it is visible until the next WIP close. When the WIP finally updates, the contractor sees the result: a job whose estimated final margin has dropped, and a corresponding earnings adjustment. By then the faded work is already in the rearview mirror.
Worse, the cost-to-cost mechanism can mask fade if the estimate of total cost is not kept honest. If a job is overrunning but the estimated total cost has not been revised upward, the percent-complete calculation will understate how far along the job really is and overstate the margin still remaining. The WIP will look acceptable right up until the estimated cost is finally corrected — at which point the fade appears all at once. The WIP schedule does not cause fade, but a stale or infrequent WIP lets fade hide.
The single most common reason fade surfaces late is a cost-to-complete estimate that nobody has revised since buyout. Percentage-of-completion is only as honest as the total-cost estimate underneath it — if estimated cost is stale, reported margin is fiction.
The antidote to fade hiding inside a monthly WIP close is the job-margin trend review — sometimes called a fade report. Instead of looking at each job's margin as a single current number, the trend review tracks the estimated final gross margin for every active job across successive periods, and watches the direction it moves.
The power of the trend view is that it makes drift visible. A job that was estimated at 18% margin at buyout, then reported 17% last quarter, then 15% this quarter, is fading — and the trend line says so even though 15% on its own might not look alarming. Three or four percentage points of slide over consecutive updates is a clear signal that something on that job is not going to plan, and it is a signal the contractor gets while the job is still in progress.
What an effective job-margin trend review includes
- Estimated final gross margin for every active job, period over period, not just the current snapshot
- The direction and size of the move — which jobs are sliding, by how much, and how fast
- The cost-to-complete estimate behind each margin, reviewed for whether it has actually been updated
- An explanation attached to every material slide — what caused it and what is being done
- Project-manager accountability — the PM owns the job's margin and presents its trend, not just the accountant
- Aggregation to the company level — total estimated job profit this period versus last, so leadership sees portfolio-wide fade
Run monthly, with discipline, the trend review converts fade from a year-end surprise into a managed, monitored number. It does not eliminate fade — but it changes when the contractor learns about it, and in construction, when you learn is most of the battle.
Margin fade is preceded by operational signals that show up before the WIP catches the dollars. A contractor who watches for these is reading the leading indicators rather than the lagging ones.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Signals that a job is starting to fade
- Labor hours burning faster than physical progress — the crew is consuming the labor budget faster than the work is getting installed
- A growing log of change order work performed but not yet priced or approved — cost is accruing with no matching revenue
- Buyout savings turning into buyout overruns — subcontracts and purchase orders coming in above the estimate's carried values
- RFIs and design changes accumulating — a sign of scope churn that tends to drag cost
- Schedule slippage — a job falling behind will keep incurring general conditions the budget did not allow for
- Rework or punch list growing during the job rather than only at the end — a quality cost signal
- A cost-to-complete estimate the project manager has not meaningfully revised in weeks — the estimate has gone stale and is hiding the real picture
None of these require a financial close to detect. A project manager walking the job and an accountant reading the cost reports can both see them in real time. The contractors who arrest fade are the ones who treat these signals as triggers for action, not as items to revisit at the next WIP meeting.
Detecting fade early is only valuable if the contractor acts on what it finds. Arresting fade comes down to a handful of operational disciplines, each aimed at one of fade's common sources.
Unpriced and under-priced change orders are the single largest source of fade, and they are largely controllable. The rule is straightforward in principle and hard in practice: extra work gets priced and approved before it is performed, not after. A contractor that lets crews build change order scope on a handshake is accumulating cost with no guarantee of recovery. A formal log of every change order — proposed, priced, submitted, approved — and a policy against self-performing un-priced changes keeps this source of fade from compounding.
The estimate of cost to complete is the heart of an honest WIP, and it has to be genuinely re-forecast each period — not rolled forward unchanged. That means the project manager actually re-estimating the remaining work based on current productivity, current buyout, and current scope, rather than assuming the original budget still holds. A rigorous cost-to-complete makes fade visible early; a lazy one defers fade until it can no longer be hidden.
Fade is an operational problem, and it has to be owned operationally. When the project manager — not just the accountant — owns the job's margin, presents its trend in the monthly review, and explains every slide, fade gets managed at the place it actually occurs. Making PMs accountable for the margin number, and reviewing it with them regularly, turns fade into a performance metric rather than an accounting footnote.
Buyout shortfalls put a job behind before it starts, so the buyout has to be tracked against the estimate, line by line. As each subcontract and major purchase is bought out, the contractor should compare the committed value to the value carried in the bid, and surface overruns immediately. Catching a buyout overrun at award gives the contractor the whole job to make it up; discovering it at closeout gives it nothing.
Margin fade is the slow, quiet erosion between the gross margin a contractor estimated at buyout and the margin a job actually delivers — and its danger lies in its timing. By the time fade is obvious on the WIP schedule, the faded work has usually already been performed and the profit is already gone. Fade comes from a recognizable set of sources — unpriced change orders, productivity loss, buyout shortfalls, scope gaps, escalation, rework, schedule slippage — and they all share one signature: cost rising while contract value does not. The contractors who control fade do not avoid it; they catch it early, through a monthly job-margin trend review that watches estimated final margin move period over period, through honest cost-to-complete forecasting, and through a habit of reading operational early-warning signals instead of waiting for the financial close. Then they arrest it with change-order discipline, cost-to-complete rigor, project-manager accountability, and real buyout tracking. The profit in a construction job is not lost in a single moment — and that is exactly why it can be saved, if someone checks the gauge before the tire is flat.
Written by
Marcus Reyes
Construction Industry Lead
Spent twelve years running AP at a $120M general contractor before joining Covinly. Lives in the world of AIA G702/G703, retainage schedules, and lien waiver deadlines. Writes about the construction-specific workflows that generic AP tools get wrong.
View all posts