The compounding problem
Construction cost overruns rarely arrive as a single event. They build — day by day, activity by activity — through small deviations that each look acceptable in isolation.
A crew that runs 8% over budget on labour hours for five consecutive days does not trigger alarms the way a $200,000 change order does. But over a three-month activity, that 8% compounds into a significant overrun — one that nobody noticed because no single day looked abnormal.
This is the core mechanism of cost drift: small deviations, repeated daily, across multiple resource types, over time.
How compounding works on a real activity
To understand why drift is dangerous, you need to see the arithmetic.
Setup
Activity: storm sewer installation (450 mm pipe).
Budget: 14 m per crew-hour. Crew cost: $72/crew-hour.
Total scope: 1,800 linear metres.
Planned duration: 16 working days.
Planned cost
| Metric | Planned |
|---|---|
| Productivity | 14 m/crew-hour |
| Total crew-hours | 1,800 ÷ 14 = 128.6 hours |
| Labour cost | 128.6 × $72 = $9,257 |
| Unit cost | $9,257 ÷ 1,800 = $5.14/m |
Actual performance: 12% below plan
The crew installs 12.3 m/crew-hour instead of 14. Not a dramatic failure. Just slightly slower every day.
| Metric | Actual | Variance |
|---|---|---|
| Productivity | 12.3 m/crew-hour | −12% |
| Total crew-hours | 1,800 ÷ 12.3 = 146.3 hours | +17.7 hours |
| Labour cost | 146.3 × $72 = $10,534 | +$1,277 |
| Unit cost | $10,534 ÷ 1,800 = $5.85/m | +$0.71/m |
A 12% productivity shortfall created a 14% cost overrun on labour alone.
Why small percentages matter more than they look
Project teams often dismiss single-digit productivity shortfalls. The numbers below show why that instinct is wrong.
| Productivity shortfall | Additional hours required | Labour cost increase |
|---|---|---|
| 5% | +5.3% | +5.3% |
| 10% | +11.1% | +11.1% |
| 15% | +17.6% | +17.6% |
| 20% | +25.0% | +25.0% |
| 25% | +33.3% | +33.3% |
| 30% | +42.9% | +42.9% |
A 20% productivity shortfall does not cost 20% more. It costs 25% more. A 30% shortfall costs 43% more. The gap widens as the deviation grows.
And this is labour alone. When equipment, material, and extended duration costs are included, the multiplier is larger.
The multi-resource multiplier
Drift rarely affects one cost category in isolation. When productivity drops, multiple resources are consumed simultaneously.
Labour drift
More crew-hours for the same output. Direct cost increase.
Equipment drift
Equipment stays on site longer. Rental or ownership cost continues even when the machine is idle or underutilised. If productivity drops 15%, the equipment is needed for 18% more days.
Material drift
Extended duration can increase material waste, storage cost, and handling damage. Rework from productivity issues generates additional material consumption.
Duration drift
The activity takes longer, which affects downstream sequencing. General conditions cost (site supervision, temporary facilities, insurance) continues for every additional day.
How drift compounds across multiple activities
A single drifting activity is manageable. The real danger is when drift appears across several activities simultaneously — which is common because the same crew, equipment, or site conditions affect multiple scope items.
Example: 3 activities drifting at once
| Activity | Budget | Drift | Overrun |
|---|---|---|---|
| Excavation | $85,000 | 8% | +$7,400 |
| Pipe installation | $62,000 | 12% | +$8,500 |
| Backfill & compaction | $41,000 | 10% | +$4,600 |
| Combined | $188,000 | +$20,500 |
No single activity looks catastrophic. But $20,500 across three activities on a project with a 5% margin ($188,000 × 5% = $9,400 profit) means the project has lost more than double its planned margin.
This is how contractors “suddenly” discover they lost money on a project. The drift was always there. It just was not measured.
Where drift starts
Drift usually originates in one or more of these operational areas:
Labour inefficiency
Slower production pace, excess crew size, skill mismatch, or unplanned overtime that increases cost per unit installed.
Equipment underutilisation
Machines on-site but idle — waiting for materials, instructions, or access. The rental cost accrues while output stalls.
Material overuse
Waste, rework, or inaccurate quantities that push consumption above the budgeted allowance.
Production shortfalls
Fewer units installed per day than the plan assumed. More days and more resources are needed to complete the activity.
Site and access constraints
Congestion, weather, permit delays, utility conflicts. These reduce effective working time without reducing cost.
What to watch — daily drift indicators
- Output per hour trending downward over 3+ days
- Cost per unit ($/m³, $/tonne, $/m) trending upward
- Idle equipment time increasing as a percentage of total hours
- Recurring constraint notes in daily logs
- Overtime hours increasing without matching production increase
- Crew-hours per unit rising while output per day is flat
- Material consumption per installed unit above budget
Why drift is hard to detect with monthly reporting
Monthly cost reports aggregate everything. A 5% labour overrun on one activity gets averaged with underruns on others, making the project-level number look acceptable.
By the time the overrunning activity is large enough to move the project total, weeks of corrective opportunity have already been lost.
Daily activity-level tracking makes drift visible at the point where it starts — not after it has been locked into committed costs.
How to respond to drift signals
Effective drift response follows a short cycle:
- Identify the activity and resource type where variance is concentrated.
- Investigate root cause within 24 hours — method, crew composition, equipment match, site conditions.
- Adjust the operation — reassign resources, change sequencing, or address the constraint.
- Monitor the same metric for the next 3 days to confirm the correction is holding.
Delay in response is usually more expensive than the initial variance. The cost of waiting one more week to act is another week of above-plan spending on that activity.
The cost of waiting
Using the storm sewer example above (12% productivity shortfall, $72/crew-hour):
| Detection timing | Days of drift absorbed | Extra cost before correction |
|---|---|---|
| Day 3 | 3 | ~$240 |
| Day 7 | 7 | ~$560 |
| Day 16 (activity complete) | 16 | $1,277 (full overrun) |
| Month-end report | 16+ | $1,277+ (no correction possible) |
On this single activity, catching drift on Day 3 saves over $1,000 compared to month-end discovery. Scale that across 10–20 active activities on a civil project, and the savings are substantial.
How TCC makes drift visible
TCC connects daily field data to activity-level cost logic so drift becomes visible as it forms.
Each daily report captures:
- labour hours by activity
- equipment hours by activity
- installed production quantities
- material consumption
- weather and field notes
TCC then compares actual performance against:
- planned productivity rates
- budgeted unit costs
- expected production volumes
Deviations surface within 24–72 hours. That gives the project manager time to investigate and correct before small daily deviations compound into project-level overruns.
Try it — estimate your cost drift exposure
Enter your planned unit cost and productivity drop to see the estimated cost impact.
Enter your email and we'll send you a personalized analysis of your numbers in under 2 minutes. No account needed.
Get an AI-powered equipment production estimate.
Frequently asked questions
What is construction cost drift?
The gradual, often invisible deviation between planned and actual unit cost during execution, caused by small daily operational inefficiencies that compound over time.
How does cost drift compound?
A productivity shortfall means more hours per unit. The cost increase is proportionally larger than the productivity decrease. A 10% productivity drop creates an 11% cost increase on labour alone — more when equipment and duration are included.
Why is cost drift hard to detect?
Because no single day looks alarming. Monthly reports aggregate the deviation with other activities, hiding it until the cumulative impact is too large to ignore.
How quickly can drift be detected?
With daily production and resource tracking, within 2–3 days of the deviation starting.
What is the difference between cost drift and cost overrun?
Cost drift is the daily process. Cost overrun is the accumulated financial result. Drift causes overruns. Detecting drift early prevents overruns from growing.
Related guides
- Construction cost drift explained
- Early warning signs in construction projects
- Construction performance monitoring
- Detect cost overruns early
- Construction cost control
- Construction cost control software
- Construction Execution Intelligence
- Construction cost overrun causes
Drift is always present. The question is whether you see it.
Every construction project experiences cost drift. The difference between a profitable project and a losing one is often just visibility — how quickly the team sees the deviation and whether they act before it compounds.