NEW Traffic Control Plan Portal

Use this portal to submit:

  • Traffic Control Plans
  • TCP Conflict Review Request
  • Shared TCPs

Tutorial Resources:

Standard Details to ASMP Street Levels Comparison Guide (.pdf)

Traffic Control Plan Portal Walkthrough Video

TCP Submittal Instructions (.pdf)

I have a question about ...

Barricading Summary Table Example Bike Lane Standard Details  Contractor's Self-Inspection Checklist  TCP Standard Notes
Standard Details TCP Design Checklist TCP Conflict & Shared TCP Request Permits

What is a traffic control plan (TCP)?  What types of TCPs exist?

A TCP describes traffic controls to be used for helping all modes of traffic through a work zone.  All TCPs must be in accordance with the most current version of the Texas Manual on Uniform Traffic Control Devices and the City of Austin, Transportation Criteria Manual.

The following types of TCPs exist:

  • Engineered TCPs: TCPs designed by an engineer which must then be approved/stamped by a ROW TCP Reviewer
  • Special Details: Preapproved TCPs that must be sealed by an Engineer 
  • Standard Details: Preapproved TCPs already sealed by an Engineer and provided by the City of Austin

Is a TCP always required?  Is a TCP the same as a permit?

A TCP is required for all right of way work zones.  TCPs are not the same as permits.  To occupy/close a portion of the right of way, you must have an approved permit AND approved TCP.

How do I submit my TCP for approval? How do I provide my approved TCP?

Typcially, only Engineered TCPs need to be submitted for approval.  For detailed instructions on when and how to submit a TCP for review and approval, read our "TCP Submittal Instructions".  All TCP files must be submitted in PDF format.  

Your approved TCP should be provided at the time of permit application.  Engineered TCPs and Special Details should be attached to the application.  Standard Details only need to be referenced in the application; provide the specific Standard Detail sheet number.

How do I resolve conflicts with my TCP?

View our ROW Conflict Resolution webpage for a detailed breakdown of how to clear conflicting TCPs.

Does my TCP expire?

Yes.  TCPs expire if they are not currently set.  If the TCP falls within the DAPCZ, it expires after 6 months.  If the TCP falls outside of the DAPCZ, it expires after 12 months. To request a rereview, submit a .pdf copy of the TCP to  Type "REREVIEW" at the beginning of the Subject line.  Permits will not be issued or extended if the corresponding TCP is expired.

What if I need a TCP for work associated with a Site Plan (SP), General Permit (GP), or Small Cell Permit (SCP)?

TCP can either be reviewed:

  • During your Development Services Department (DSD) plan review (i.e. SP, GP, SCP).  This is known as an in-process review.  Review fees are $425 per plan set, plus a 4% ATD Technology Surcharge Fee.


  • Separate from your plan review.  This is known as an out-of-process or deferred review.  Initial reviews are allotted 9 work days.  Subsequent review timeframes will vary.  Review fees are $425 per plan set, plus a 4% ATD Technology Surcharge Fee.  These TCPs must be submitted to the TCP Portal a minimum of 6 weeks prior to the start of the closure. 

Who can set, maintain, and remove temporary traffic control (TTC) devices?

TTC may only be set by a competent and/or certified person.  A “competent person” is experienced and knowledgeable in the placement of TTC.  A “certified person” is credentialed through ATSSA, TEEX, or another relevant agency.  The person who places TTC accepts tort liability for the setup.  Contractors who have been excluded from working in the City of Austin are not authorized to set, maintain, or remove TTC devices.