TxDOT Traffic Control Plans: What the TCP Sheets Contain and What Your Crew Still Has to Decide

"TxDOT TCP" is one of the queries people reach this site with, and it hides two different questions. One is documentary: what is actually in a Texas traffic control plan? The other is practical: when the plan on the truck does not cover what the crew is looking at, what happens?

This post answers the first from TxDOT's own published manuals and gives you a list of questions for the second. It is a description of how the process generally works, not legal or engineering advice. Requirements vary by project, district, county and city, and the authority having jurisdiction decides. Verify with the TxDOT district or the local agency that owns the road before you rely on anything here.

What TxDOT says a TCP contains

TxDOT's Project Development Process Manual section on the Traffic Control Plan describes a TCP as the set of plan sheets that move traffic, including bicyclists, pedestrians and transit vehicles, through or around the work zone in a safe, expeditious and clear manner. In paraphrase:

• Traffic control is planned during preliminary engineering, but the detailed TCP sheets are developed in final design.
• A TCP typically consists of a narrative, typical sections, layouts, miscellaneous details and the traffic control standards.
• Low-rigor projects typically include the narrative sheet and the applicable standards as a minimum.
• The plan has to show provisions to move users with minimal delay and to minimize hazards for both the public and workers at the work zone interface with traffic.
• The manual refers designers to the Texas MUTCD and TxDOT's traffic standards for TCP design guidance.

The companion PS&E Preparation Manual section on TCP sheets adds detail relevant to contractors. It says minor projects can usually be described by a single traffic control narrative sheet rather than a full phased plan, with the traffic control standards and the barricade construction standard sheets for advance signage. It also says TCP sheets developed by the divisions or districts should be used when practical, and that when an existing standard sheet is not used, the TCP sheet must be signed, sealed and dated.

How to read that as a contractor

You do not write the TxDOT TCP on most TxDOT-let work. The designer does, and you build it. Still, knowing the structure tells you where to look when something does not add up.

The narrative describes the sequence of work and, on phased jobs, the phases and steps. If your crew's sequence differs from the narrative, the narrative is the document the agency will measure against.

Typical sections and layouts show the cross-section and plan view of the setup for each phase. These are what a crew lead should have in the cab, and our guide to reading a traffic control plan in the field covers how.

Miscellaneous details carry project-specific items that standard sheets do not.

The standards are the generic sheets, including the barricade construction sheets, that the plan refers to. Our post on TxDOT traffic control standard sheets explains how those sheets are organized.

When the field does not match the sheet

Every work zone is a little different from the drawing. TxDOT's own manual acknowledges that existing standard sheets may not cover every situation and can serve as a starting point that is tailored to the project. What your crew does when the sheet and the road disagree is not a field call. Questions to put to the district or the project's inspector before you need the answer at 6 a.m.:

1. Who has authority to approve a field change? The contract and the project's traffic control specifications answer this. Get the name and phone number.
2. What has to be written down, and when? Some agencies want a change documented before the setup changes, some after. Ask which.
3. Does a change need an engineer's seal? TxDOT's own manual ties sealing to departures from standard sheets on the design side. Whether a contractor-proposed change falls under that is for the agency and a licensed engineer to say.
4. Who is the after-hours contact? An emergency callout does not wait for office hours.
5. What does the agency want recorded on the daily record? Our posts on field changes to an approved TCP and submitting a TCP for approval cover the general pattern.

None of these have a universal answer. That is the point of asking.

Keep the plan and the day in one place

Disputes about traffic control mostly come from a mismatch between what the plan said and what the field did, with no record connecting the two. Two habits help. First, store the plan revision with the job, so the crew is working from the current sheets. Second, make the daily ticket carry the setup as built, with times and a location stamp, so a later question has an answer. Traffic OS's features include GPS-stamped, signed daily tickets for exactly that record. Pricing is flat tiers, and a demo is the quickest way to see how a ticket attaches to a job. If you are comparing it with general field-service software, see our ServiceTitan comparison.

The short version

A TxDOT TCP is a narrative, typical sections, layouts, details and standards, scaled to the project. The designer owns it, the contractor builds it, and when the field disagrees with the paper, the answer comes from the contract and the district, not from a blog. Ask early who decides, and write it down.