Lump Sum vs Unit Price: How Traffic Control Bid Items Shift Risk

On many public projects, the most consequential decision about traffic control money is made before anyone prices a device. It is the structure of the bid item: one lump sum for all traffic control, a set of unit-priced items, or some mix of the two.

The structure decides who carries the risk when a project runs long, when phasing changes, or when the agency asks for three more arrow boards than the plans showed. A traffic control company that prices a lump sum like a unit-price item, or the other way around, can lose money on a job it priced correctly on paper.

This post explains how the two structures work, what the federal rule says about paying for traffic control on federal-aid projects, and how to price each one. It is general information about how these contracts typically work. The specifications and bid form of each contract govern, and you should read them in full.

What the federal rule says

For federal-aid highway projects, FHWA's work zone rule on temporary traffic control devices — 23 CFR 630 Subpart K — includes a section on payment. Section 630.1108(f), paraphrased:

• Project plans and specifications should provide for compensation for implementing the traffic control plan, through method-based or performance-based specifications.
• Traffic control should not be incidental to other items of work.
• At a minimum, the rule provides that "separate pay items shall be provided for major categories of traffic control devices."
• Lump sum payment should be used only when the quantities are provided in the project documents or when the quantities depend on the contractor's own scheduling choices.
• Unit price payment is appropriate when the contractor has little control over the quantities.
• Lump sum items should include provisions for adjusting payment when changes are made that are outside the contractor's control.
• The specifications should make clear how placement, movement and maintenance of traffic control devices will be paid.

That is a statement of good contracting practice for federal-aid projects, and states implement it through their own specifications. It is useful to a subcontractor for a simple reason: it tells you what questions the contract should already answer, and what to ask when it does not. Our post on positive protection in work zones covers the other parts of Subpart K, and our explainer on the work zone safety and mobility rule covers Subpart J.

Lump sum: you own the quantity risk

A lump sum item pays one price for a defined scope — often "traffic control" for the whole project or a phase — regardless of how many devices or days it actually takes.

What you gain: simplicity, no daily quantity arguments, and upside if you execute efficiently.

What you carry: the risk that the job takes longer, needs more devices or needs more crew than you estimated. If the prime's schedule slips by six weeks and the contract has no mechanism to adjust your lump sum, those six weeks of devices, maintenance trips and inspections are yours.

How to price it:

1. Build it bottom-up as if it were unit priced. Device-days for every device, every phase, maintenance visits, installation and removal crews, moves between phases. Our guide to traffic control plan quantity takeoffs covers the method.
2. Price the schedule you actually believe, not the one in the bid documents. If the project duration looks optimistic, price the realistic one or state your assumption.
3. Read the change provisions. The rule says lump sum items should include provisions for changes outside the contractor's control. Find them. If they are not there, your exclusions and assumptions need to say what the lump sum covers — our post on exclusions and assumptions in traffic control proposals covers how to write them.
4. Carry a contingency that is honest about the uncertainty, and know what it is for.

Unit price: you own the rate, the owner owns the quantity

Unit-priced items pay per unit actually furnished — per device-day, per hour of flagging, per each, per day of an attenuator truck.

What you gain: protection against quantity growth. If the job runs long or the agency adds devices, you are paid for them.

What you carry: the risk that the rate does not recover your cost at the quantity actually used. If the estimate showed 200 device-days and the job used 60, fixed costs you spread across 200 are now spread across 60.

How to price it:

1. Put mobilization, delivery and removal costs where they belong. If the contract has a separate mobilization item, use it; if not, those costs have to live in the unit rates.
2. Price each unit to stand alone. Do not rely on volume to cover fixed costs.
3. Watch for unbalanced quantities. If the estimate for one item looks much too high or too low, think about which way it is likely to move and what that does to your recovery.
4. Know the measurement rules. How is a device-day counted? Is a partial day a day? Is standby paid? Our guide to pricing standby and show-up time covers the time questions, and traffic control device rental rates covers device pricing.

Mixed structures

Many projects combine the two: a lump sum for general traffic control and advance signing, plus unit-priced items for the pieces whose quantity is hardest to predict — arrow boards, portable message signs, attenuators, flaggers, law enforcement, temporary barrier.

Mixed structures create one specific trap: overlap. If your lump sum price already includes some flagging and the flagging is also a unit-priced item, you have either priced it twice (and lost the bid) or priced it once in the wrong place (and will argue about payment). Map every cost to exactly one item before you submit.

When the prime restructures the items

Subcontractors often do not bid the owner's items directly. The prime may ask for a single lump sum for "all traffic control" while the prime is paid on unit prices by the owner. That mismatch means the prime keeps the quantity upside and hands you the quantity risk.

You can accept that, but price it knowingly — or ask for your subcontract to mirror the owner's items, so your payment moves with the owner's measurement. Our post on subcontracting traffic control work covers what to settle in the subcontract, and change orders on traffic control jobs covers what to do when the job changes.

The records decide what you actually get paid

Both structures depend on daily records, for different reasons. Under unit pricing, the daily record is the measurement: no record, no payment. Under a lump sum, the daily record is your evidence when you claim that the work changed beyond what the lump sum covered.

The daily ticket should capture, in the contract's units, what was furnished that day — lanes closed, devices deployed, flaggers and hours, protection vehicles — and it should be signed or verified by the owner's or prime's representative.

In Traffic OS, the daily ticket records lanes closed, route, direction and mile markers, and carries quantities and rates for lane-closure units, flaggers, TMA units and queue units, with the crew by role. It is signed on site with the time and GPS position recorded, and it becomes the basis of the invoice. Quotes keep a version history after acceptance, so the priced scope can be compared against what was actually furnished. See the features page or book a demo.

A short checklist

• Identify every traffic control item on the bid form and its unit of measure.
• Map each cost to exactly one item.
• For lump sums: price the realistic schedule and find the change provisions.
• For unit prices: price each unit to stand alone at a lower quantity.
• Check whether the subcontract mirrors the owner's items.
• Write assumptions and exclusions into the proposal.
• Make the daily ticket measure what the contract pays for.