By Pascal Patrice, PMP, ECCQ
The excavator sat waiting on trucks that never came back. The haul cycle was running longer than anyone had planned due to a longer route than estimated, a slow turnaround at the dump, a fleet one truck short, and every rotation left the machine parked a little longer with its bucket in the air.
The operator saw it by midmorning. The foreman knew it by lunch: At these cycle times, the trucks can’t feed the machine.
Nobody wrote that down anywhere a project manager would read it. The daily report that evening said what daily reports say: Normal operations.
Five weeks later, a cost report landed on the project manager’s desk showing the excavation activity 22 per cent over budget — hours burned by a machine that spent a third of every shift waiting.
The crew had long since moved on. Every decision that could have changed the outcome — adding a truck, shortening the haul, resequencing the work — had already been made without the one piece of information that mattered.
Anyone who has run field work knows this story. The interesting part is why it keeps happening. It isn’t carelessness, and it isn’t bad software. It’s the structure of how cost information travels.
The lag is built into the chain
Follow the path a field event takes to become a number a project manager can act on. Something changes on site — productivity drops, conditions shift, the crew adapts.
The foreman registers it, maybe mentions it to the superintendent. Hours get logged, often to the nearest activity code rather than the precise one.
Timesheets go to payroll, which processes weekly or biweekly. Payroll posts to job costing. Accounting closes the month. Subcontractor invoices arrive 15 to 30 days after the work. Then — finally — a variance appears in a report.
Count the steps and the calendar: three to five weeks between the moment the ground told the operator something and the moment the number told the office the same thing.
On a 12-month project, that lag is uncomfortable. On a four-month paving or utilities job, it means a third of the work is in place before the first honest cost signal arrives.
By then the overrun isn’t a warning. It’s a record. You can explain it in detail. You can’t do anything about it.
It’s structural, not cultural
The reflex is to blame reporting discipline — push the foremen to write more. But the foreman on that job did his job. He observed, he adapted, he managed his crew.
The system above him simply had no container for what he knew. Cost systems are built to receive validated, structured, reconciled data — and validation is precisely what takes weeks.
The information didn’t fail to travel because someone withheld it. It failed to travel because nothing asked for it in a form that moves fast.
There’s a second, quieter problem: on many jobs the daily report has become a liability document rather than an operational one. When reports are mainly used for claims and disputes, crews learn to write for lawyers — cautious, vague, “normal operations” 14 days in a row before a cost spike.
That’s not dishonesty. That’s people responding rationally to what the document is actually used for.
The signal that beats the paperwork
Closing the gap doesn’t take a bigger system. It takes a simple daily calculation: quantity installed divided by hours consumed.
The foreman who says “we moved 400 cubic metres today against a plan of 550” has already done the cost analysis — he’s just never been asked for it in that form.
Installed quantity and crew hours, recorded the same day, against the same activity code, give you a productivity rate you can compare to the budget’s assumption by tomorrow morning.
One low day proves nothing — weather, access, a bad delivery. But two or three consecutive days below plan is not noise. It’s a drift starting.
Caught at that moment, it’s cheap to fix: change the method, resize the crew, fix the material flow. Caught at month-end, the same drift is a number in a report and a paragraph in a claim.
The question worth asking on any project is simple: how many hours pass between a field event and the moment someone who can act on it has the information?
If the answer is measured in weeks, the problem isn’t your people. It’s the route the information has to travel.
The industry has spent a decade buying software that organizes information after the fact. The harder problem — turning what a foreman knows at 3:30 on Tuesday into something a project manager can act on Wednesday morning — is solved at the daily report, by deciding what that document is actually for.
Pascal Patrice, PMP, ECCQ, is a construction project director with three decades of field experience in civil and heavy construction, still leading projects of $200 million and more. He is the founder of Projestim TCC, a construction cost control platform that connects daily field data to activity budgets and surfaces cost drift in 24 to 72 hours — before it reaches the monthly report. To learn more, visit projesttcc.com/construction-cost-control-software. Tel: 514-892-6501 · p.*******@*******im.com.
