Subcontracting Traffic Control Work: What to Nail Down First

Subcontracting in this trade tends to start informally. A contractor calls with a job three hours outside your radius, you know somebody who works up there, you make an arrangement over the phone, and it works out.

Then it works out four more times, and on the sixth one a vehicle takes out a taper, the setup did not match the approved plan, and the questions arrive: whose devices were those, who was supervising, and who is answering the agency.

This is about the terms worth settling before the sixth job, whichever side of the relationship you are on.

Get clear on which relationship this is

Three arrangements get called "subcontracting" and they have different economics.

Capacity overflow. You have the contract, you cannot staff it this week, someone else's crew runs your job. Your plan, your customer relationship, usually your devices.

Geographic reach. The job is outside your practical radius. Their crew, their yard, their devices, your contract.

Specialty scope. Barrier placement, engineered plan preparation, or equipment you do not own. Their expertise, and often their professional liability.

The distinction matters because it determines who controls the work, and control is the axis most of the downstream questions turn on. A capacity-overflow crew executing your plan under your supervision is a very different arrangement — commercially and legally — from a firm in another region running their own operation under your contract.

Write down which one you are in. A surprising number of these relationships are ambiguous on exactly this point, which means every later question has to be renegotiated.

Scope: what "traffic control" includes on this job

The most common source of subcontract disputes in this trade is not price. It is scope boundary.

Settle these explicitly:

Who prepares the traffic control plan, and who bears the cost and the delay of revisions. Plan preparation is a distinct scope — see how traffic control plans get drawn — and it is frequently assumed to be included by one party and excluded by the other.

Who pulls and holds the permit, and who is responsible for renewals on a long job. Our post on lane closure permits covers the process; the ownership question is a contract question.

Whose devices are on the road, in what quantity, and who bears attrition. See charging for damaged and lost devices — the terms exist to be agreed in advance, not litigated after a truck destroys forty drums.

Who handles callbacks. Overnight resets, knocked-down devices, weather events. On a recurring closure this is a material cost, covered in managing recurring lane-closure contracts.

Who interfaces with the agency inspector. Two parties both talking to the inspector, saying slightly different things, is how a routine observation becomes a formal issue.

Flow-down: the clauses that have to travel

If you are a prime on a public contract, obligations from your contract generally have to flow down to subs, and a generic subcontract form frequently does not carry them.

The recurring ones in this trade: prevailing wage and certified payroll reporting where applicable — see certified payroll for traffic control contractors — DBE participation documentation, safety program and reporting requirements, insurance limits and endorsements, retainage terms, and change order procedures.

The failure mode is specific and expensive: a prime accepts a certified payroll obligation and does not flow it down, discovers in month two that the sub has been paying below determination, and now owns a back-wage exposure plus a delayed progress payment for the whole contract.

Where the compliance obligation is genuinely technical — as prevailing wage classification for flaggers can be — telling the sub the obligation exists is not sufficient. Confirm they know how to meet it before the first shift, not after the first payroll submission bounces.

Standing caveat: flow-down requirements, subcontracting approval rules, and licensing obligations vary by state, county, city, and by the terms of your prime contract. Nothing here is legal advice. Have counsel review your actual subcontract form against your actual prime contract.

Standards: they are working to the same manual, probably

A sub in a different state may be working to a differently-numbered manual than you are, and both of you may be correct.

States adopt the national MUTCD, a supplement, or their own manual on their own schedules. Under 23 CFR 655.603, states "shall adopt changes issued by the FHWA to the National MUTCD within two years from the effective date of the final rule," and a state manual must conform as a minimum to the national Standard statements without contravening or negating them.

Practically: the sub works to the manual adopted where the job is, plus whatever the permit conditions say. If you send them a setup card built from your home state's supplement, you may be sending them something that does not apply. We cover the edition-change problem in the 11th Edition post.

The occupational floor does not vary by state in the same way. 29 CFR 1926.201(a) requires that "Signaling by flaggers and the use of flaggers, including warning garments worn by flaggers, shall conform to Part 6 of the MUTCD," and that obligation attaches to the employer of the workers — which is the sub, not you, though that division rarely feels reassuring after an incident.

Documentation: the part that actually protects you

Whatever the contract says, the practical question after an incident is what the setup looked like and who built it. If your sub's field documentation is a paper ticket in a truck, you have no answer.

Three requirements worth making non-negotiable in any subcontract for field work:

Daily tickets with times, headcount, device counts, and a customer signature. These are your billing basis and your evidence. Our post on preventing daily ticket disputes covers the mechanics.

Setup documentation at installation. Photographs of the advance warning, taper, and activity area, timestamped and located. This is what answers the conformance question later.

Incident and intrusion reporting to you, not just internally. A vehicle entering the work space on a job carrying your name is something you need to know about the same day. Most property-damage-only intrusions appear in no external dataset — see work zone intrusion prevention and response — so if the sub does not tell you, nothing else will.

The exposure is not hypothetical. The Associated General Contractors of America, reporting its annual survey with HCSS, states that "Sixty percent of highway construction firms report having at least one car crash into their work zones during the past year". And FHWA reports speeding as a factor in 281 of 821 work zone fatal crashes in 2022, roughly 34 percent. Over enough subcontracted shifts, something happens.

Specifying the format of documentation, not just its existence, is what makes it usable. "Provide daily tickets" produces a scan of a handwritten page three weeks later. "Provide tickets in a shared system, same shift" produces something you can reconcile against an invoice.

Payment terms, and pay-when-paid

Two structural points.

Pay-when-paid and pay-if-paid clauses. These shift owner-payment risk down the chain, and their enforceability varies substantially by jurisdiction. Whichever side you are on, know what your contract says and what your state does with that language. This is a question for counsel, not for an article.

Retainage. If your prime contract holds retainage, and your subcontract does not, you are financing the difference for the length of the job. Our note on getting paid faster covers the cash-flow side generally.

A short checklist before the first shift

Certificate of insurance with the limits and endorsements your prime contract requires, verified rather than promised.

Licensing and registration for the jurisdiction the work is in.

Flagger certifications for the people actually assigned, not for the company generally.

Written scope covering plan, permit, devices, callbacks, and agency interface.

Documentation standard stated in the subcontract, with format and timing.

Rate schedule including callback rates and device damage terms.

None of that is exotic and all of it takes an afternoon once. The reason it usually does not happen is that the first subcontract arrangement started as a favor between people who trusted each other — which is a fine way to start and a poor way to operate at volume.

Keeping subcontracted jobs in the same system as your own work, with the same ticket and setup documentation, is the difference between a sub relationship you can audit and one you have to take on faith. That is how Traffic OS handles multi-crew and multi-party jobs; the pricing page shows what is at each tier, and you can book a walkthrough to see the field documentation flow.

The relationship that survives is the one where both parties knew, before the first cone went out, exactly what each was responsible for.