Unit price bid forms: matching your takeoff to the pay items
How to map takeoff quantities onto agency unit price bid forms, handle owner-supplied quantities, and protect yourself on measurement-and-payment language.
6 min read
Key takeaways
- Read the measurement and payment clause before measuring anything.
- Owner quantities govern payment; your quantities govern cost.
- Measure both, and price the difference deliberately.
- Incidental items get no pay line — they must be inside another unit price.
On public and agency work you rarely bid a lump sum. You bid unit prices against quantities the owner supplies, and you get paid for what is measured in the field. That changes what your takeoff is for: it is no longer the basis of payment, it is the basis of your cost.
Read measurement and payment first
Every specification section has a measurement and payment clause, and it defines the item more precisely than the drawings do. It tells you whether pipe is paid along the centerline through structures or between them, whether excavation is paid separately or is incidental, and what the unit price is deemed to include.
| Clause says | Consequence |
|---|---|
| Pipe measured through structures | Slightly more paid footage than your net trace |
| Trench excavation incidental to pipe | No pay line — bury it in the pipe unit price |
| Structures paid by depth band | Your banding must match the form's bands |
| Aggregate paid by ton, certified tickets | Waste and yield risk is yours |
| Aggregate paid by plan CY | No payment for over-excavation |
| Seeding paid by acre of finished area | Deductions matter to revenue |
Measure it twice, on purpose
- Measure the item the way the pay clause defines it — this is your revenue quantity.
- Measure the item the way you will actually build it — this is your cost quantity.
- Compare. Where they diverge, decide consciously how to price the gap.
- Compare both against the owner's stated quantity on the form.
A large gap between the owner's quantity and yours is a bidding decision, not an error to hide. Unbalanced bidding has real consequences; the important thing is knowing the gap exists before you price it.
Where estimators get hurt
- Incidental scope with no pay item — dewatering, shoring, testing, traffic control.
- Depth bands on the form that do not match how you measured structures.
- Plan-quantity payment on items where field conditions will exceed the plan.
- Restoration paid by area while the real driver is the number of separate patches.
- Mobilization capped as a percentage, with real costs front-loaded.
Practical mapping
Build your condition library so it maps onto the agency's standard pay items for the agencies you bid regularly. When your conditions are named after the pay items — including the depth bands and the section designations — filling in the bid form becomes a read-across rather than a reconciliation exercise, and the risk of pricing a band you did not measure disappears.
That mapping is reusable. Agencies change their standard items slowly, so a condition set built once for a state DOT or a county standard pays back on every bid you submit to them afterwards.
Doing this work in TakeoffAI? Quantity reports.
Related guides
Units and conversions every civil estimator should know cold
A working reference for civil takeoff units: LF, SF, SY, CY, tons, acres and EA, with the conversions and density factors used daily on sitework bids.
6 min readPricing & reportingQuantity reports that survive bid-day scrutiny
How to structure a takeoff quantity report so it is fast to price, easy to audit, and organized to match the bid form scope by scope.
5 min readMeasurement methodTakeoff vs estimating: where measurement ends and pricing begins
Takeoff produces quantities; estimating applies production, crews, costs and markup. Understanding the boundary keeps both defensible.
5 min read