Why do traffic control proposals need exclusions?

Because a price implies a scope, and if the scope is not written down the customer's version of it will be broader than yours. Exclusions and assumptions state the basis of the price so that when conditions differ, the conversation is about a change rather than about whether you are entitled to one.

What are the most valuable ones to state?

Hours and days assumed, duration, number of setups and moves, devices included, who provides the traffic control plan and permits, standby and show-up treatment, police or flagging assumptions, access and staging assumptions, and what happens if the agency changes the requirements.

Do exclusions protect you legally?

They help, but the contract governs. On public work and on prime subcontracts the flow-down terms usually control, and a proposal exclusion inconsistent with the contract you later sign may be overridden. Have the important agreements reviewed by counsel.

Will exclusions cost us work?

A page of defensive legalese might. A short, specific list that reads as professional competence usually does the opposite — it tells a buyer you have done this before and priced the actual job.

Where do exclusions fit with change orders?

Exclusions define the starting line; change orders record movement from it. Without the first, the second is an argument. With it, it is arithmetic.

How specific should they be?

Specific enough to be tested against reality. 'Normal working hours' means nothing. '7:00 a.m. to 3:30 p.m., Monday to Friday, excluding holidays' can be checked by anyone.

Exclusions and Assumptions in Traffic Control Proposals

Most disputed traffic control invoices trace back to a proposal that did not say what was excluded. The assumptions worth stating on every quote, how to write them so they read as professional rather than defensive, and where they stop working.

Nearly every disputed traffic control invoice has the same shape. The customer believed the price covered something; the company believed it did not; and the proposal said nothing either way.

Exclusions and assumptions are the cheapest risk control available to a traffic control company. They cost a paragraph on a quote and they convert the most common commercial argument in this trade — was that included? — from a contest of memories into a reading of a document.

Assumptions, not just exclusions

There is a useful distinction. An exclusion says what you are not providing. An assumption states the basis of the price. Assumptions do more work, because they describe reality and can therefore be tested against it.

"Excludes overtime" invites an argument about what counts as overtime. "Price is based on an 8-hour shift between 7:00 a.m. and 3:30 p.m., Monday to Friday; hours outside this window are charged at the rate sheet's premium rates" describes the world, and the moment the job runs at night, both parties can see what changed.

The list worth stating on most quotes

Not all of these apply to every job. Each of them has been the subject of a dispute somewhere.

Hours and days. The shift window assumed, the days of the week, whether holidays are included, and what happens outside the window.

Duration and number of days. How many days of work the price covers, and how a longer job is priced.

Setups and moves. How many setups the price includes, and what a relocation costs. Multiple moves in a day is one of the most common unpriced scope creeps in this trade.

Devices included. Counts and types, and what happens if the approved plan requires more. If the plan is not final at quoting time, say so and tie the price to a stated device schedule.

Who provides the traffic control plan. Plan preparation is real work. If the customer is providing the plan, say so; if you are, say what that includes and what a redesign after agency comments costs. Who pays for the traffic control plan covers the question directly.

Permits and fees. Who applies, who pays, and who carries the delay if a permit is late. Lane closure permits: how the process works covers the process.

Standby and show-up time. State that standby is chargeable and at what rate, and what happens if the crew arrives and the job is not ready. Pricing standby and show-up time covers the pricing.

Law enforcement. Whether officers are included, excluded, or passed through at cost, and who books them. Law enforcement in work zones: when to use it covers when they are required.

Flagger count. How many flaggers the price includes, and that additional flaggers required by site conditions or the agency are chargeable. A single-flagger operation that the site turns into a two-flagger operation is a real and frequent cost.

Access and staging. Whether you have somewhere to park, stage devices and turn around, and whether maintaining access to specific properties is included. Maintaining driveway and business access in work zones covers how much work that can be.

Agency-directed changes. State plainly that changes required by the agency after award — additional devices, revised plans, different hours — are a change in scope. This is the single most valuable line for public work.

Weather and cancellation. Notice required to cancel without charge, and how a weather-shortened day is billed. Adverse weather traffic control operations covers the operational side.

Device losses. That devices damaged, stolen or removed by others are chargeable. Charging for damaged and lost traffic control devices covers making that stick.

Validity period. How long the price holds. With input costs moving, an open-ended quote is an open-ended risk — see fuel costs and surcharges.

Write them so they read as competence

The tone matters commercially. A proposal that reads as though it was drafted in anticipation of litigation makes a buyer wonder what happened last time. The same content, written plainly, reads as someone who knows the work.

Three habits:

Lead with the basis, not the refusal. "Priced for two setups per day" beats "excludes additional setups."

Keep it short and specific. Eight to fifteen lines covering the items above is plenty for most jobs. A two-page schedule of exclusions gets skimmed, and a term nobody read is a weak term.

Use the same list every time. A standard block, adjusted per job, means nothing gets forgotten on the busy Friday quote — which is exactly the quote that turns into the dispute.

Where exclusions stop working

Be realistic about the limits.

The contract governs. If you sign a subcontract or a public contract whose terms conflict with your proposal, the contract normally wins. Proposal exclusions carried into an agreement by reference are stronger than ones that sit in an email. On public work in particular, the contract documents control, and payment terms for federal construction contracts are set by regulations such as FAR 52.232-27, not by your quote.

Flow-down clauses. Prime subcontracts routinely flow down obligations from the owner contract. An exclusion that contradicts a flow-down term is likely to lose. Subcontracting traffic control work: what to nail down covers what to read.

Agency requirements are not negotiable. Excluding something the agency requires does not remove the requirement — it only establishes that it was not in the price. The work still has to be done, under the applicable state manual and Part 6 of the MUTCD. That is the point: the exclusion turns it into a change order rather than free work.

Nothing replaces the daily record. An exclusion establishes the baseline; the ticket establishes what actually happened. Without a signed, dated record of the extra setup or the two hours of standby, the exclusion has nothing to attach to. Preventing daily ticket disputes and change orders on traffic control jobs cover the field half.

Make them travel with the job

The common operational failure is that the assumptions live in the quote document and nowhere else. The crew never sees them, so nobody in the field notices when the job stops matching them.

Better: the assumptions that describe field conditions — shift window, setups per day, flagger count, devices — should be visible on the job record the crew lead can see, so that the second setup or the third flagger is flagged the day it happens, not discovered at month end.

Traffic OS keeps the quote, the job and the daily ticket on one record, so the basis of the price and what actually happened sit together and a variance is visible while it can still be billed. Flat monthly tiers — $499, $949 and $1,499 as of September 2026, no per-user charge — are on the pricing page, with detail on the features page and a walkthrough available.

Nothing in this post is legal advice. Contract terms, flow-down provisions and the enforceability of proposal conditions vary by jurisdiction and by agreement — have your standard terms reviewed by counsel.