TxDOT Work Zone Requirements: What Traffic Control Contractors Should Know

Texas is the largest highway construction market in the country, and TxDOT is a well-documented owner — nearly everything it expects is published, and most of it is findable. That is good news and a trap at the same time. The material is public, so nobody is going to walk a new subcontractor through it, and the parts that bite hardest are the administrative ones nobody reads until they cost money.

This is a practical orientation for traffic control contractors and subcontractors working on or around TxDOT projects: how the traffic control plan functions as a contract document, how device inspections actually run, who the named responsible people are, what prequalification involves, and what the crew has to be able to prove afterward.

One caveat that is not boilerplate: requirements vary by jurisdiction and change over time. A TxDOT contract, a City of Houston permit, and a county road are three different rule sets, and a project can sit under more than one. Nothing here substitutes for the requirements of the agency having jurisdiction over your specific work, or for the specifications incorporated into your specific contract. Verify with them, every time.

Start with why the stakes are what they are

Before the administrative material, the reason any of it exists.

Using Fatality Analysis Reporting System data compiled by the Work Zone Safety Information Clearinghouse, there were 850 work zone fatalities in 763 fatal crashes nationally in 2024, following 905 fatalities in 824 fatal crashes in 2023 and 903 in 833 in 2022. FHWA's work zone facts and statistics breaks the mechanism down: of 821 fatal work zone crashes tallied for 2022, 174 were rear-end collisions, 246 involved a commercial motor vehicle, and speeding was a factor in 281. The same source, drawing on the Bureau of Labor Statistics Census of Fatal Occupational Injuries, records 94 highway construction worker occupational fatalities in 2022 and 108 in 2021.

Texas contributes a large share of national work zone exposure simply by volume of lane-miles under construction. The regulatory intensity follows from that. It is not an agency being difficult.

The traffic control plan as a contract document

On a TxDOT construction contract, the traffic control plan is not a courtesy drawing. It is part of the contract, and the department's construction contract administration guidance on traffic control plans treats it that way — as a document with named accountability attached, not a reference sheet.

Two structural facts about how TxDOT plans get built are worth internalizing early:

Standard sheets do a lot of the work. TxDOT publishes standard traffic control plan sheets — the familiar TCP-series and work zone standards — and a great deal of a project's traffic control is assembled from them rather than drawn from scratch. The department's traffic control plan and work zone reference guide is the orientation document for how these fit together. If you are a subcontractor pricing work, the standard sheet referenced on the plan tells you more about what you are actually expected to furnish than the line item description does.

Design-phase guidance is public too. TxDOT's project development process manual documents how the traffic control plan is developed during final design. This is unusually useful for a sub: reading the design-side expectations tells you what the plan you were handed was trying to accomplish, which is exactly the knowledge you need when field conditions force a deviation.

The national floor under all of it is Part 6 of the MUTCD 11th Edition, published December 2023 and now carrying Revision 1 dated December 2025, with Part 6 published in full by FHWA. Note the edition question carefully: states adopt the national manual, adopt a state manual in substantial conformance, or adopt the national manual with a supplement, and department standard sheets and specifications sit on top of whichever applies. Work to what the inspector enforces. Being right about the newest national edition is not a defense.

And the OSHA hook, which applies regardless of who owns the road: 29 CFR 1926.201(a) requires that signaling by flaggers and the use of flaggers, including warning garments, conform to Part 6 of the MUTCD. OSHA's highway work zones page points employers to the MUTCD for setup guidance and flags struck-by and caught-between among the recurring hazard categories.

Named responsible persons, and why that matters to you

TxDOT's construction administration guidance establishes that each work zone should have designated individuals from the contractor and from the department charged with responsibility for managing work zone safety. In the manual's shorthand these are the contractor's responsible person and the district's responsible person.

For a traffic control subcontractor this has a consequence that catches people out: you are frequently not the contractor's responsible person. The prime's CRP is, and the deficiency notice, the correction instruction, and the schedule pressure all route through them. If your crew leader is fixing a device deficiency they learned about third-hand, forty minutes after the inspector found it, that is an information-flow problem you can fix on your side regardless of contract structure — by making sure your field record and your prime's field record are the same record, timestamped, rather than two accounts reconciled later.

Device inspections run on a cadence

This is the operational fact most worth planning around, and it is published plainly. TxDOT's construction contract administration manual states that "The DRP will perform formal inspections of all traffic control devices twice a month at approximately 2-week intervals," and directs that at least one of these be conducted at night, as soon as possible after the initial setup, on projects with overnight traffic control. The contractor's responsible person is to be given the opportunity to accompany department staff, and deficiencies are corrected per the instructions on the department's form.

Three implications for how a traffic control operation should run:

1. A night inspection is coming. Sheeting that reads fine at 2 p.m. and poorly at 2 a.m. is a night-inspection finding, not a daytime one. Retroreflectivity degrades, and it degrades invisibly in daylight. Devices that have been rotated through enough jobs to be scuffed are the ones that fail this.
2. Roughly every two weeks, someone walks your zone with authority. Any documentation practice that depends on a person remembering to write things down at the end of the week is going to be tested about twice a month, in an adversarial context.
3. Accompanying the inspection is an opportunity, not an imposition. Being present when a deficiency is identified is the difference between fixing it that hour and receiving a description of it later.

Devices and field practices TxDOT documents explicitly

A few items from the department's published work zone guidance that traffic control subs should treat as baseline rather than nice-to-have:

High-visibility apparel for everyone in the zone. TxDOT's guidance requires that all contractor employees in the work zone have proper high-visibility safety apparel. This is not only the flagger. For what the garment classes actually mean and how to choose between them, see our explainer on high-visibility apparel classes.

AFADs require a qualified flagger and must not be left unattended. TxDOT's guidance states that each automated flagger assistance device be operated by a qualified or certified flagger, and that flaggers operating AFADs not leave them unattended while in use. An AFAD reduces exposure; it does not remove the person.

Arrow panels denote lane closures, placed on the shoulder at the beginning of the merging taper where space permits — the convention documented in the department's work zone reference guide.

Attenuators where barrier is absent. TxDOT's guidance describes truck-mounted attenuators and trailer-mounted attenuators being used in advance of the work area to protect both workers and the traveling public when barriers are not used. Note that this is positive protection, which is a different thing from buffer space; the two are complementary. We cover the distinction in the four areas of a temporary traffic control zone.

Flagger qualification. Chapter 6E of MUTCD Part 6 covers flagger control, including qualification and high-visibility apparel. Treat the qualification record as a per-person, per-shift artifact rather than a binder in the office: the question an inspector asks is not whether your company trains flaggers, but whether the specific person directing traffic on this specific shift was qualified to do it, and that is a question a roster answers poorly and a dated record answers immediately. What "qualified" means in practice — who certifies, how long it lasts, what a state accepts — is jurisdiction-dependent; see flagger certification requirements explained and confirm against the agency that will be inspecting you.

Prequalification: the administrative gate

If you want to bid TxDOT work directly rather than only subcontract, prequalification is the door.

TxDOT qualifies bidders before they are eligible to bid or receive a bid proposal on a construction or maintenance project. Per the department's contractor prequalification guidance, there are three levels of qualification, all of which require annual requalification, and a bidder may prequalify by submitting one of three questionnaires:

• The Confidential Questionnaire (CQ) reflects detailed financial and experience data and requires an audited financial statement prepared by an independent CPA firm. This is the normal level for construction projects.
• The Bidder's Questionnaire (BQ) reflects detailed equipment and experience data but waives the audited financial requirement. It is used for projects where the full requirements are waived — normally smaller construction, routine maintenance, emergency, and specialty projects.
• The Materials Supplier's Questionnaire (MQ) covers supply rather than construction.

TxDOT directs that the appropriate questionnaire be submitted at least 10 calendar days before the last day of the bid opening, and recommends emailed submission for faster processing.

Three things a small traffic control company should take from that:

The audited financial statement is a real cost and a real lead time. An independent CPA audit is not a same-week deliverable. If the CQ level is where you need to be, the accounting work has to start months before the letting you are aiming at, not after you see it posted.

Annual requalification means this is a recurring calendar item, not a one-time onboarding task. Companies lose bid eligibility by letting it lapse far more often than by being denied.

The BQ path exists for exactly the profile most traffic control companies have — specialty work, equipment-heavy, without the appetite for an annual audit. Read the waived-project criteria carefully before assuming you need the CQ.

The federal layer sitting above the state contract

TxDOT requirements do not exist in isolation. On federally funded projects, a federal rule shapes how work zone impacts are planned before your crew is ever engaged, and knowing it explains a lot of what shows up in your scope.

In September 2004 FHWA updated the work zone regulations at 23 CFR 630 Subpart J — the Work Zone Safety and Mobility Rule — which applies to all state and local governments receiving Federal-aid highway funding, with compliance required no later than October 12, 2007. FHWA's implementation guide describes three primary components: a state-level work zone safety and mobility policy, standard processes and procedures supporting it, and procedures to assess and manage work zone impacts on individual projects, including identifying significant projects and developing transportation management plans.

The consequential change for contractors is in the last item. Per FHWA's TMP fact sheet, the rule expanded the existing requirement for a traffic control plan into a requirement for a transportation management plan on every Federal-aid highway project. A TMP contains the TCP but goes wider — transportation operations and public information components sit alongside it.

Why a subcontractor should care about a rule addressed to agencies: the TMP is where commitments about lane closure windows, allowable durations, public notification, and mobility performance originate. When your contract says a closure may only be in place between 9 p.m. and 5 a.m., that restriction usually descends from a TMP decision, not from an inspector's preference. Arguing it in the field is arguing with a document nobody on site can amend. The distinction between these documents is covered in TCP vs TMP vs MOT.

Permits are a separate track from the construction contract

One structural point that trips up companies moving from subcontract work into direct work.

If you are a sub on a TxDOT construction contract, the traffic control authorization generally flows through that contract and its plans. If you are doing work in the right of way that is not under a construction contract — a utility tie-in, a private development's driveway connection, a special event, a survey — you are usually in permit territory instead, and permits are administered at the district level with district-specific submission processes and contact points. TxDOT's district pages, such as the Houston district's contractor information, are where those local processes are published.

Three practical consequences:

The approving party is different, and so is the timeline. A permit review is not a contract submittal. Build the lead time into your schedule rather than discovering it.

The traffic control requirement may be attached as a permit condition rather than appearing as a plan sheet. Read the conditions; they are enforceable in exactly the way plan notes are.

A project can sit under more than one authority at once — a state highway crossing a city street means both agencies have a legitimate say. Ask early which conditions govern where they differ, and get the answer in writing. General guidance on the permit path is in lane closure permits: how the process works.

What this means for how you run the back office

Nothing above is exotic. What makes it expensive is that the requirements arrive on three different clocks — the daily clock of setup and teardown, the roughly-biweekly clock of formal inspections, and the annual clock of requalification — and most traffic control companies track all three in the same place: someone's head, a truck folder, and a spreadsheet that is out of date by Wednesday.

The failure mode is predictable. The inspection finds something the crew already fixed but did not record. The prime disputes a ticket because their account of the day and yours were written at different times by different people. Requalification comes due during the one month everyone is buried.

What a system fixes here is narrow but real: the record exists by default instead of by discipline. A GPS-stamped daily ticket signed at the zone is contemporaneous evidence, not a Friday reconstruction. Device counts that live in an inventory instead of a memory make the twice-monthly walk boring. Traffic OS was built for this shape of company — see what it covers, how it is priced at a flat monthly tier rather than per user, or bring a real disputed ticket to a walkthrough and we will run it end to end.

For the broader documentation problem this all rests on, preventing daily ticket disputes is the companion piece; for how the plan itself is built and approved, start with what a traffic control plan is.