Bidding Traffic Control Jobs: What Estimates Usually Miss

Traffic control estimating looks simple from outside. Count the devices, count the flaggers, add a rate. Most companies that estimate that way are profitable on some jobs and unprofitable on others, and cannot reliably tell which is which until the year closes.

The gap is rarely in the device count. It is in everything around it.

The costs that hide outside the device list

Mobilization and demobilization. Loading, driving, setting up, tearing down, and returning. On a short job this is a large fraction of total labor and it produces nothing a client sees on the invoice, which makes it the first thing shaved when a number feels high. It does not become cheaper because you priced it low.

Standby. Crews waiting because the prime is not ready, weather stopped work, or an inspection is pending. Whether standby is billable depends on the contract — that is exactly why the contract language deserves reading before the bid rather than after the dispute.

Maintenance visits during the deployment. Devices get struck, blown over, and moved by the public. A multi-week setup requires inspection and repair trips. An estimate covering setup and teardown but not the middle has priced two visits for a job that needs eight.

Equipment as an earning asset. Devices on a site for three weeks are unavailable for other work. Pricing them as a one-time consumable understates long deployments and hides the opportunity cost. Rental-style pricing reflects the reality.

Losses and damage. Cones disappear. Barricades get destroyed. Some rate of attrition is normal and belongs in overhead rather than being absorbed silently.

Permitting labor. Preparing submittals, responding to review comments, and tracking approvals is real office time. Companies working across multiple jurisdictions carry a meaningful permitting burden and rarely price it. The permitting process is more involved than a single application, and resubmittal cycles are often the largest controllable component of lead time.

Night and weekend differentials, and the productivity difference. Night work is slower as well as more expensive per hour.

Credential and training overhead. A certified workforce has a cost — training time, cards, and the administrative work of keeping them current across a rotating crew.

Scope questions to settle before pricing

Most estimating disasters are scope misunderstandings rather than arithmetic errors. Settle these in writing:

Who supplies the traffic control plan, and who pays for revisions if the agency requires them? Who pulls and pays for permits? What are the actual hours, including whether the schedule assumes night or weekend work? How many phases, and does each require a separate setup? What happens if the job extends — is there an agreed extension rate? Is standby billable, and at what rate? Who is responsible for devices damaged by the public or by other trades? What documentation does the client require for payment, and in what format?

That last one is worth more attention than it gets. If payment depends on a signed daily ticket in a specific format, that is a process requirement with a cost, and discovering it after the first invoice is rejected is expensive.

Pricing labor honestly

Labor dominates most traffic control jobs, and the common error is estimating from base wage rather than from loaded cost.

Loaded cost includes payroll taxes, workers' compensation — which is not a trivial line in this industry — general liability, vehicle cost, PPE, training, and the non-productive time that is genuinely part of employing someone. A bid built on base hourly rate plus a thin markup is usually pricing below actual cost without anyone realizing.

On prevailing wage work, use the official determination for the specific contract and locality. Determinations are published through SAM.gov, and the Department of Labor maintains tools and guidance for construction contractors. Never estimate from a rate quoted secondhand, remembered from a previous job, or copied from another locality — determinations vary by classification and geography, and using the wrong one is both a bidding error and a compliance problem.

Job costing is what makes bidding improvable

Everything above is guesswork until you compare estimates against actuals.

Job costing means capturing, per job: actual labor hours by person and classification, actual equipment days, actual mobilization trips, actual maintenance visits, and actual expenses — then comparing them to what the bid assumed.

This is where most companies are blind, and the reason is mechanical rather than philosophical. If time is not attributed to a job at capture, it cannot be job-costed later. If equipment deployment is not tracked with dates, equipment days are a guess. If maintenance trips are not recorded, they are invisible. The data has to be captured as work happens, because it cannot be reconstructed afterward with any accuracy.

Once you have a season of it, the questions that were unanswerable become routine. Which job types are actually profitable. Whether your mobilization assumption is right. Which clients generate standby. Whether night work is priced correctly for its lower productivity.

Most companies discover the same two things: short jobs are less profitable than assumed because mobilization dominates, and long deployments are more profitable than assumed because equipment keeps earning while labor drops off. Both change how you bid — and neither is visible without the data.

This is the practical reason field capture matters beyond compliance. A GPS-stamped ticket recording crew, hours, and equipment is simultaneously the billing document, the compliance record, and the job-costing input. That triple duty is why it tends to actually get completed: documentation that exists only for costing gets skipped, while documentation that also gets you paid does not.

A workable estimating discipline

Build from a checklist, not from memory. Every category above, every time, even when the answer is zero. Omissions come from items nobody thought about.

Estimate mobilization separately from the work. Rolling it into a day rate hides it and guarantees it gets shaved.

Price equipment by deployment duration.

Use loaded labor cost.

Record your assumptions with the bid. Crew size, days, equipment days, mobilization trips. Without them the eventual comparison against actuals tells you the job lost money but not why.

Review actuals against bids monthly. Not annually. A bad assumption caught in month two is corrected for the season; caught in December it has already run.

If you want to see how quoting, tickets, and job costing connect in one flow, the features overview covers it, or book a walkthrough to see it on real screens.