Load tickets don't match the survey? How to true up the pay app
The earthmoving sub hands you a stack of load tickets totaling 14,200 loose cubic yards moved off the east pad. The engineer's cross-section takeoff from last month's topo says 9,800 bank cubic yards of cut. Your pay app is due Friday and the owner's rep is going to ask which number you're billing against.
This happens on almost every mass-grading job big enough to need more than a handshake. Two different measurement methods were never going to agree on their own.
Why the two numbers never matched to begin with
A load ticket counts trucks. It assumes every truck left the cut full, that the bed capacity on the ticket is accurate, and that nobody rode half-empty because the haul road was soft or the loader operator was running behind. None of those assumptions hold for every load on a real site.
The survey measures ground. A cross-section takeoff compares elevations at stations spaced down the alignment, usually every 50 or 100 feet, and interpolates the volume between them. If the cut has an irregular toe, a stockpile nobody flagged, or a section that got re-cut after a slope failure, the stations between survey points can hide real volume in either direction.
Then there's the conversion problem. Tickets run in loose cubic yards off the truck. The engineer's number is bank cubic yards, measured in place before anything got dug. Somewhere a swell factor is supposed to bridge those two, and on half the jobs nobody can point to which swell factor got used or whether it came from the geotech report or got guessed.
Reconciling ticket count to survey volume
Start with the swell factor. Pull the geotech report and find the stated swell or shrinkage percentage for the material being moved. Clay and shale behave very differently once they're loose, and a 25% swell assumption on rock that actually swells 40% will throw your whole reconciliation off before you've looked at a single ticket.
Convert the ticket total to bank measure using that factor, not the other way around. Loose yards divided by (1 + swell factor) gets you back to bank. Now compare that converted number to the survey's bank cubic yards. If they land within a few percent, the gap is rounding and partial loads, not a real dispute.
If they're still far apart, check the truck capacity assumption on the tickets themselves. A lot of haul contracts bill by the load regardless of how full the bed was that trip. If the super was running trucks at 80% capacity to beat a soft spot on the haul road, the ticket count overstates volume no matter how clean the swell factor math is.
Last, check the survey's station spacing against where the actual grade changes happened. A toe that moved 15 feet between stations can hide or add several hundred cubic yards that a cross-section takeoff spaced too wide will never catch.
When neither side wants to trust the other's number
Once you've run the reconciliation and the gap is still real money, you're in a position where the ticket count is a vendor's self-reported log and the cross-section takeoff is a snapshot that may or may not have caught the grade change when it happened. Neither one is independently verifiable after the fact, because the dirt that moved last week is gone.
This is the gap Earthwork Volumes was built to close. Instead of relying on a truck count or a monthly cross-section pull, it compares a weekly drone survey of the site against the prior week's surface and reports the cut and fill volume directly from the ground that changed. That volume goes into the pay app as the backing documentation, not the sub's own tally of trucks leaving the pit.
If your next pay app is going to come down to a ticket count argument again, it's worth seeing what a surface-to-surface volume looks like on your site before the dispute starts.