Progress Billing on Unit-Price Contracts: Quantities Are Money

On lump-sum jobs, billing disputes are about percent complete. On unit price contracts, they’re about something more fundamental: how many units you actually installed. Every cubic yard, linear foot, and ton is a line on your invoice, which makes measured quantities the single most contested number in heavy-civil progress billing. Get measurement discipline right and monthly pay applications go out clean; get it wrong and you’re renegotiating last month’s invoice while this month’s work piles up unbilled.

The Billing Equation

Unit price billing reduces to one formula:

Payment = measured quantity installed × contract unit price

The contract fixes the price per unit. Your job each period is to defend the quantity:

Item	Unit	Contract qty	Unit price	Measured to date	Billed to date
Common excavation	CY	48,000	$6.50	31,200	$202,800
24” RCP storm pipe	LF	2,400	$185	1,450	$268,250
Aggregate base course	TN	6,800	$28	4,975	$139,300

Multiply across dozens of pay items and the whole month’s revenue lives in those “measured to date” cells — which is exactly why owners’ engineers re-measure them.

Where Defensible Quantity Evidence Comes From

Different items demand different proof, and strong contractors layer multiple sources:

• Load tickets for materials paid by weight or volume — concrete, asphalt, aggregate — reconciled daily against placement locations
• Survey data for earthwork: cross-sections before and after, drone topography, GPS machine control logs
• Crew production logs recording pipe laid, structures set, or square yards placed, tied to stationing or locations
• Daily reports with photos establishing what was installed where, when

Two independent sources that agree are hard to dispute. One foreman’s memory is not evidence.

Overruns, Underruns, and the Final Reconciliation

Here’s the trap unique to unit price work: estimated quantities in the bid schedule are not guaranteed. Most contracts state the owner may adjust payment proportionally if final quantities deviate beyond a threshold — commonly somewhere in the 15–25% range, though terms vary by contract.

That creates two failure modes:

1. Overrun items: You bid 10,000 CY at $8 because the work looked easy; it turns out to be 14,000 CY. If the deviation exceeds the contract threshold, you may recover a rate adjustment. If not, you eat it — so track burn against estimated quantities continuously.
2. Underrun items: The owner can claim proportional price relief when quantities shrink dramatically, since fixed costs spread over fewer units.

At final measurement, every item gets reconciled. Contractors who tracked quantity drift all along know which items deserve re-measurement scrutiny and which clauses to invoke. Contractors who didn’t discover the damage at closeout, when it’s too late to document anything.

Audit-Proof Measurement Records

Public agencies audit unit price bills routinely, and private owners increasingly do the same. Records that survive review share traits:

• Same-period capture: measurements recorded daily or weekly as work happens, not reconstructed before billing
• Location references: stations, grids, or structure numbers tying each quantity to physical places an auditor can spot-check
• Named accountability: who measured, who witnessed, signatures where required
• Consistency: the same method used all project long — switching from survey to tickets mid-job invites challenge
• Retention: survey files, ticket images, and production logs kept together per pay item

Field time and production data belong in the same system as billing for exactly this reason; crew hours feed both labor productivity tracking and quantity verification, and extra-work days flow straight into T&M tickets.

BidSync AI captures field production daily inside the same platform that generates progress billing, so measured quantities carry their evidence with them. See the financials capabilities or book a demo to watch a unit-price bill assemble from live field data.