When 30 Truckloads Becomes 90
- Jean-Sebastien Rolland
- 3 days ago
- 3 min read
A municipal procurement story about why paper hauling records hide the worst kind of cost overrun, and how the city found out too late.
A medium-sized municipal project — call it a road reconstruction with a base-and-asphalt scope — gets scoped for somewhere around 30 truckloads of haul over a few weeks. The estimate comes from the engineer, the contractor signs off, the work starts.
By the time the project closes out, the manifest count is closer to 90.
I've seen this happen more than once on Canadian municipal work. The numbers vary. The mechanic doesn't.
How the multiplication stays invisible on paper
When the manifests are paper or emailed PDFs, three things make the discrepancy disappear:
The contractor produces both the load count and the invoice. They generate the manifests at their end, hand a stack to the city at month-end, and bill against what's in the stack. The reconciliation is a single-source check against itself.
The estimate lives in a different system. The engineer's projection sits in a design document or a spreadsheet, off the procurement desk. Nobody puts the estimate and the actuals on the same page in real time. The compare-and-flag moment doesn't exist.
By the time anyone notices a count drift, the project is half over. The first time somebody adds up the stack and says "wait, didn't we say 30?", you're already at 50. The contractor's answer is always available — "base layer was deeper than expected," "we had to import additional cover material," "the engineer's quantities were optimistic." None of those answers can be tested against what actually happened.
So the city pays. Council never hears the story. The next project starts.
What a structured live record changes
When every haul is logged at the gate, in the field, structured into the same record by the generator and the receiver, the multiplication can't hide. A few things happen automatically:
Live count visible to the project owner. Not at month-end. Not at close-out. While the project is running. The city's PM can see the load count climb on day eight and ask the contractor what's happening, when the answer is still recoverable.
The contractor's count and the generator's count are the same record. No reconciliation gap. A phantom load needs a corresponding gate log on the generator side — different party, different timestamp, often different signature. Multi-party records are harder to invent than single-party ones.
Cycle times stop matching the count if the count is wrong. A truck that does eight runs in a day has a specific cycle-time fingerprint: load time, transit, dump time, return. If the invoiced count implies twenty runs but the cycle times only support eight, the data tells you. It doesn't need an investigator.
That last point is the one procurement teams underestimate. The platform isn't trying to catch fraud, it's producing a record at the right resolution. The math falls out.
The audit moment changes shape too
When a city has to defend a project's cost — to a councillor, an external auditor, an insurance carrier, the local paper — the document they want is "how many loads, by whom, when, where to." On paper, that's a quarter of administrative work to assemble. In a connected workspace, it's a query.
For a city that finished a project at the scope the engineer drew up, that's a routine confirmation. For a city that ended up at three times the scope, it's a chance to recover what's recoverable and structure the next contract differently.
For private owners, the same shape
Developers, institutional builders, landlords doing major renovations — anyone who hires a hauler and pays per load sees the same pattern. The mechanics aren't municipal-specific. The difference for a city is that the political accountability layer compounds the financial one.
Bottom line
Paper hauling records can't tell you in real time when a 30-load project is on its way to a 90-load invoice. By the close-out reconciliation, the contract is over and your leverage is gone. Live, structured, multi-party records change the math by changing the record.
Want to see what a live load count looks like across an active project? Book a demo.
Jean-Sébastien Rolland
General Manager
1-833-922-0999