Where Your Margin Goes: Productivity Erosion and What Your Numbers See First

A job rarely loses money all at once. It bleeds, an hour here, a redo there, a crew waiting on materials, and by the time it’s obvious in the field, the margin is already gone. The frustrating part is that the financials usually saw it coming. Productivity erosion shows up in your numbers before anyone files a report about it, if your books are set up to show it. This article walks through the five common causes and, more importantly, where each one surfaces financially so you can catch it while you can still act.

The premise is simple: your job-cost data and your WIP schedule are an early-warning system. Most contractors treat them as a rear-view mirror, a record of what already happened. Set up right and read regularly, they’re closer to a dashboard, flashing a warning while the job is still running.

How erosion hides in the numbers

Before the specific causes, it helps to understand the general mechanism. On a fixed-price job, your profit is the gap between the contract value and what it costs you to build. Productivity erosion attacks the cost side: the same scope takes more labor hours, more redo materials, more equipment time than you estimated. Because you recognize revenue based on costs incurred (the percentage-of-completion method most contractors use), rising costs against a fixed contract show up as a shrinking expected margin, which is exactly what profit fade on a WIP schedule measures.

So the financial signature of productivity erosion is consistent across all five causes: actual costs running ahead of the estimate for the work completed, and estimated profit at completion drifting downward period over period. The causes differ, but the warning light is the same. Here’s how each one trips it.

Overtime fatigue

Pushing a crew into sustained overtime feels like buying progress, and in the short term it does. But productivity per hour falls as fatigue accumulates, so you’re paying premium wages for declining output. The first week of overtime might be worth it. By the fourth, you can be paying time-and-a-half for hours that produce less than straight-time hours did.

Where it shows up financially: your labor cost as a percentage of the work completed climbs, and your labor cost per unit of production rises even faster because of the overtime premium. If you track labor cost against the estimate by phase, you’ll see the burn rate accelerate without matching progress. The job’s estimated cost at completion creeps up, and profit fade appears on the WIP. The numbers reveal that you’re spending more labor dollars to complete the same percentage of work, which is the financial fingerprint of fatigue, long before a superintendent calls it.

Trade stacking

When the schedule compresses, trades get stacked, too many crews working the same space at once, tripping over each other, waiting for access, redoing work disturbed by the trade behind them. Each crew is “working,” so it doesn’t look like a problem, but the productivity of all of them drops.

Where it shows up financially: labor hours accumulate across multiple cost codes without proportional progress on any of them. If your job costing is detailed enough to track labor by phase or area, you see hours piling into a zone of the job faster than that zone is completing. Committed and incurred costs rise while the percent-complete barely moves. On the WIP, this reads as costs outrunning earned revenue, the gap between what you’ve spent and what you’ve genuinely completed widening. A contractor tracking labor only at the whole-job level can’t see trade stacking until it’s done its damage; one tracking by phase can spot the zone that’s absorbing hours without producing completion.

Rework

Rework is the most direct margin killer because you pay twice: once to do it wrong, once to do it right, plus the materials you consumed the first time. It also frequently triggers the other problems, rework crammed into a tightening schedule causes trade stacking and overtime in turn.

Where it shows up financially: material costs run ahead of the estimate for the completed scope, because you bought materials twice for the same finished product. Labor hours similarly exceed plan for work that, on paper, should already be done. The tell is a cost code that’s well over budget while its deliverable is only nominally complete, you’ve spent 130% of the labor and material budget for a phase that’s 90% finished. That divergence between cost consumed and work completed is rework’s signature, and it’s visible in job costing immediately if costs are coded to the right phase.

Weather

Weather is partly outside your control, but its financial effect is very much trackable, and how you account for it matters. Lost days, standby time, protecting or re-doing weather-damaged work, and the schedule compression that follows all add cost without adding completion.

Where it shows up financially: idle or standby labor hits your labor costs with no corresponding progress, a direct hit to the cost-versus-completion ratio. Weather-driven schedule compression then often produces the overtime and trade-stacking effects above, compounding the cost. On the WIP, a weather-hit job shows costs incurred without matching earned revenue during the affected period. Tracking weather impact deliberately also matters for any claim or change-order conversation: if you can show the cost of documented weather days in your job-cost data, you’re in a far stronger position than if it’s blended invisibly into general labor.

Poor material staging

When materials aren’t staged where and when crews need them, people stop working to go find, move, or wait on materials. It’s some of the most expensive idle time there is, because it’s skilled labor standing around, and it’s almost invisible day to day because everyone looks busy solving the problem.

Where it shows up financially: labor hours accumulate faster than production, similar to trade stacking, but the cause is logistics rather than crowding. You also often see equipment and handling costs rise from moving materials multiple times. In job costing, the signature is labor burn outpacing completion in phases where the work itself is straightforward, when a simple phase is over on labor, staging and logistics are a prime suspect. Material delivery and handling costs that exceed plan reinforce the picture.

The common thread: your books as an early-warning system

Notice that all five causes produce the same core financial symptom: costs running ahead of completion, and estimated profit drifting down. That’s not a coincidence, it’s why financial data is such a powerful early-warning system for field productivity. You don’t need to diagnose the exact cause from the numbers alone; you need the numbers to tell you which job and which phase is bleeding, early enough to send someone to find out why.

But this only works under two conditions. First, your job costing has to be detailed enough, costs coded to the right job and the right phase or cost code, not dumped into company-wide buckets. A job-cost system that only shows whole-job totals can’t isolate the bleeding phase. Second, someone has to actually look, regularly, while jobs are running, not just at the end. A WIP schedule reviewed monthly catches profit fade with time to react; one produced once a year is an autopsy.

This is the real connection between field productivity and accounting. The erosion happens in the field, but the early warning lives in the financials, and whether you get that warning depends entirely on how your books are set up and how often you read them.

The bottom line

Overtime fatigue, trade stacking, rework, weather, and poor material staging are the usual suspects behind a job that quietly loses its margin. They happen in the field, but they all leave the same financial fingerprint: costs outrunning completion, and profit fade on the WIP. The contractors who catch erosion early aren’t necessarily running tighter job sites, they’re reading job-cost data detailed enough to show which phase is bleeding, while the job is still running and there’s still time to act.

That early-warning capability is a setup question as much as a discipline question. If your job costing is structured for it, the numbers will flag trouble before the field does. If it isn’t, you find out at closeout, when it’s too late. If you want your job costing and WIP set up so your financials actually warn you in time, book a discovery call and we’ll talk through how to build that visibility into your books.

For the mechanics behind the WIP signals described here, the companion pieces on reading a WIP schedule and on the percentage-of-completion method show exactly where profit fade and cost-versus-completion live on the page.