240-861-5050

State DOT Traffic Control Plan Requirements by Jurisdiction


The federal Manual on Uniform Traffic Control Devices (MUTCD) establishes the national baseline for work zone traffic control. Each state adopts the MUTCD or implements state-specific standards that align with it, often through supplements, standard plans, and DOT manuals. Requirements can vary by state, district, and project complexity. Projects spanning multiple jurisdictions often require separate approvals, and PE licensure considerations may apply by state depending on the reviewing agency's rules.

Last reviewed: February 2026. This page is maintained as states update their supplements and standard plans.

How State DOT Requirements Differ from the Federal MUTCD

The MUTCD, published by the Federal Highway Administration (FHWA), provides national minimum standards for traffic control devices, including temporary traffic control in work zones. States are required to adopt the MUTCD or develop state-specific editions that meet or exceed federal standards. In practice, this means every state transportation agency applies its own layer of requirements on top of the federal baseline.

Some states publish standalone supplements that address state-specific roadway configurations, regional traffic patterns, and local regulatory preferences. Others adopt the federal MUTCD with targeted amendments or additional detail in specific chapters. Some states publish manuals and standard plans that add state-specific requirements and typical applications beyond MUTCD Part 6 for work on state-maintained facilities.

District-level engineering offices within each state DOT often retain discretionary authority over plan review and approval. This means that requirements for the same type of project can vary not only between states but between districts within a single state. Plan reviewers may require additional detail, alternative device spacing, or specific detour routing based on local conditions.

Federal minimum vs. state standard: The MUTCD establishes the floor, not the ceiling. State supplements may impose stricter device spacing, additional signage, or different taper formulas.

Typical Applications vs. engineered plans: Many states provide standard Typical Application drawings for common scenarios. Projects that fall outside these standard configurations typically require custom-engineered traffic control plans.

PE seal requirements: Whether a traffic control plan requires a licensed Professional Engineer's seal often depends on project complexity, roadway classification, and the specific DOT district. Complex projects on high-volume or interstate roadways are more likely to require PE-stamped plans.

Submission and review timelines: Plan review periods vary widely by state, district workload, and project scope. Submitting plans with adequate lead time is essential to avoid project delays.

State-by-State Traffic Control Plan Requirements

The following summaries provide general guidance for traffic control plan development in each state. Requirements vary by district, project type, and roadway classification. Always consult the applicable DOT district office for current submittal procedures and format requirements.

Virginia

Virginia Department of Transportation (VDOT)

Governing Standards

VDOT publishes the Virginia Work Area Protection Manual (WAPM), which serves as the state's primary reference for temporary traffic control on state-maintained roadways. The WAPM supplements the federal MUTCD with Virginia-specific requirements, typical application drawings, and additional guidance for common work zone configurations.

PE Seal Requirements

PE-stamped traffic control plans are often required for complex projects, particularly those involving interstate highways, high-volume arterials, multi-phase lane closures, or extended-duration work zones. For routine maintenance activities and simple operations that align with standard WAPM typical applications, a PE seal may not be required. Requirements vary by VDOT district and residency office.

Submission and Review

Traffic control plans for permitted work on VDOT roadways are generally submitted through the applicable residency or district office. Review timelines vary by district workload and plan complexity. Plans that deviate from standard typical applications or involve complex phasing typically require longer review periods. Submitting complete and accurate plans reduces the likelihood of revision cycles.

Common Plan Deficiencies

Examples below reflect common revision themes across DOT reviews and are not specific to every district. Frequent issues that result in plan revisions include incomplete taper calculations, missing or incorrect sign spacing, failure to address pedestrian or bicycle accommodations where required, inconsistent phasing between plan sheets, and insufficient detour routing detail for full road closures. Plans that do not reference current WAPM typical applications or that omit required device specifications are also commonly returned for correction.

Maryland

Maryland Department of Transportation State Highway Administration (MDOT SHA)

Governing Standards

Maryland adopts the federal MUTCD with state-specific modifications and supplemental guidelines published by MDOT SHA. The agency provides additional guidance through its Standard Specifications for Construction and Materials, which includes temporary traffic control provisions. Maryland also publishes typical traffic control plan drawings for common work zone configurations on state highways.

PE Seal Requirements

Complex traffic control plans on state-maintained roadways in Maryland often require a PE seal, particularly for projects involving controlled-access highways, significant traffic management during peak periods, or multi-phase construction sequencing. Simpler operations that conform to established typical application drawings may not require PE-stamped plans. District traffic engineers retain authority to determine when engineering certification is necessary.

Submission and Review

Plan submittals are generally directed to the applicable MDOT SHA district or regional office. Review timelines vary by project complexity and district workload. Projects involving federal-aid highways or work within specific corridor management zones may involve additional review requirements. Coordination with local jurisdictions may be necessary for projects near municipal boundaries.

Common Plan Deficiencies

Examples below reflect common revision themes across DOT reviews and are not specific to every district. Plans are commonly returned when they lack adequate transition areas, omit required channelizing device specifications, do not account for adjacent intersection operations, or fail to address construction phasing in sufficient detail. Missing coordination notes for utility work, inadequate provisions for emergency vehicle access, and failure to meet minimum lane width standards during traffic shifts are also frequently cited issues.

Pennsylvania

Pennsylvania Department of Transportation (PennDOT)

Governing Standards

PennDOT publishes Publication 213 (Temporary Traffic Control Guidelines), which provides the state's framework for work zone traffic control design. Publication 213 supplements the federal MUTCD with Pennsylvania-specific typical applications, device specifications, and plan preparation guidance. PennDOT also references Publication 408 (Specifications) for material and installation standards related to temporary traffic control devices.

PE Seal Requirements

PE-stamped plans are often required for projects involving complex work zone configurations, state highway or interstate operations, and situations that deviate from standard Publication 213 typical applications. PennDOT district offices determine PE requirements based on roadway classification, project duration, and the level of traffic management complexity involved.

Submission and Review

Traffic control plans are typically submitted to the relevant PennDOT district office or engineering district. Review timelines vary by district and project scope. Plans associated with Highway Occupancy Permits (HOPs) follow the applicable permit review process. PennDOT encourages pre-submission coordination with district traffic units for complex or atypical projects.

Common Plan Deficiencies

Examples below reflect common revision themes across DOT reviews and are not specific to every district. Common reasons for plan returns include non-compliance with Publication 213 typical applications, missing or incorrect advance warning sign distances, inadequate provisions for nighttime operations, lack of accommodation for local access during detours, and insufficient detail on temporary pavement markings. Plans that do not clearly identify construction phasing or fail to address flagging operations at critical points are frequently flagged for revision.

California

California Department of Transportation (Caltrans)

Governing Standards

Caltrans publishes the California MUTCD (CA MUTCD), which is the state's adopted edition of the federal MUTCD with California-specific modifications and additional standards. The CA MUTCD governs all traffic control device applications on public roadways in California. Caltrans also provides Standard Plans and Standard Specifications that include specific temporary traffic control details for work on the state highway system.

PE Seal Requirements

For work on the state highway system, traffic control plans are commonly prepared or reviewed under the supervision of qualified engineering personnel, and a PE seal may be required depending on project scope, contract requirements, and district procedures. For complex projects involving freeway operations, extended closures, or significant traffic management, PE-stamped plans are typically expected. Requirements for local agency roadways vary by jurisdiction. Caltrans district offices and local agencies may have differing thresholds for when engineering certification is required.

Submission and Review

Plan submission processes vary between Caltrans districts and local agencies. Encroachment permits for work on the state highway system require traffic control plans as part of the permit application. Review timelines vary by district workload and project complexity. For large capital projects, traffic management plans may undergo multiple review cycles and require coordination with Caltrans traffic operations staff.

Common Plan Deficiencies

Examples below reflect common revision themes across DOT reviews and are not specific to every district. Frequently cited issues include non-conformance with CA MUTCD standards, failure to address multi-modal accommodations (bicycle and pedestrian facilities), missing construction area signs as specified in Standard Plans, incomplete traffic handling during phased construction, and lack of coordination notes for ramp metering or changeable message sign operations. Plans that do not reflect current Caltrans standard drawings or that omit required environmental considerations are also commonly returned.

Florida

Florida Department of Transportation (FDOT)

Governing Standards

FDOT publishes Design Standards and the FDOT Standard Plans, which include temporary traffic control typical applications and device specifications. Florida adopts the federal MUTCD with state-specific modifications documented through the state's traffic engineering guidelines and design manuals. FDOT's Traffic Engineering Manual provides additional guidance on work zone traffic control design and implementation.

PE Seal Requirements

PE-stamped Maintenance of Traffic (MOT) plans are often required for projects on the State Highway System, particularly those involving limited-access facilities, complex intersection work, or extended-duration construction. FDOT district offices determine the level of engineering review required based on project scope and roadway classification. FDOT and many owners require qualified MOT/TTC personnel for plan development and field implementation. Specific credential requirements vary by project type, contract, and district.

Submission and Review

MOT plans are submitted through the applicable FDOT district office as part of the overall project development or permit application process. Review timelines depend on project phase, complexity, and district workload. FDOT may require MOT plans at multiple stages of project delivery, including design, permitting, and construction phases.

Common Plan Deficiencies

Examples below reflect common revision themes across DOT reviews and are not specific to every district. Common deficiencies include failure to comply with FDOT Design Standards typical indices, incomplete coordination with adjacent signal systems, missing provisions for law enforcement support during complex operations, insufficient detail on temporary barrier installation, and lack of accommodation for emergency vehicle preemption. Plans that do not address drainage impacts from temporary traffic shifts or that omit required lighting specifications for nighttime operations are also frequently returned for revision.

Texas

Texas Department of Transportation (TxDOT)

Governing Standards

Texas adopts the federal MUTCD with state-specific modifications published through the Texas MUTCD (TMUTCD). TxDOT provides additional guidance through district standards, standard sheets, and traffic control resources used for plan development. The specific references used can vary by district and project delivery method. The TMUTCD applies to all public roadways in Texas and serves as the primary reference for temporary traffic control design.

PE Seal Requirements

PE-stamped traffic control plans are often required for projects on the TxDOT highway system involving complex phasing, limited-access highways, or configurations that deviate from standard TCP sheets. TxDOT district offices and area engineers determine PE requirements based on project-specific factors. Routine maintenance operations that conform to standard TCP sheets may not require PE certification.

Submission and Review

Traffic control plans are submitted to the applicable TxDOT district or area office. Review timelines vary by district and project scope. For projects involving the state highway system, TCP review is typically integrated into the overall plan review process. TxDOT encourages early coordination with district traffic operations staff for complex or non-standard work zone configurations.

Common Plan Deficiencies

Examples below reflect common revision themes across DOT reviews and are not specific to every district. Common issues include non-compliance with TMUTCD spacing and device requirements, failure to address high-speed approaches adequately, missing or incomplete detour plans for full closures, insufficient provisions for oversized vehicle accommodation, and lack of coordination details for work in TxDOT-maintained medians or interchange areas. Plans that do not clearly delineate responsibility between the contractor and TxDOT for traffic control device maintenance are also frequently cited.

Multi-State and Multi-Jurisdiction Projects

Projects that cross state lines or span multiple jurisdictions within a single state introduce additional complexity to traffic control plan development and approval. Each jurisdiction typically requires its own compliant set of plans, and requirements may differ significantly even between neighboring states or adjacent municipal and state-maintained roadways.

Key Considerations for Multi-Jurisdiction Work

Separate approvals per state. Each state DOT generally requires traffic control plans that comply with its own standards and manuals. A plan developed to meet one state's requirements may not satisfy an adjacent state's standards without modification.

PE licensure requirements. Professional Engineer licensure is state-specific. A PE licensed in one state typically cannot stamp plans for work in another state without holding licensure there. Multi-state projects often require coordination between PE-licensed professionals in each applicable jurisdiction.

State highway vs. municipal roadways. Projects that transition between state-maintained highways and locally maintained roadways may require separate plan sets or additional coordination with municipal traffic engineering departments. Standards and review processes often differ between these jurisdictions.

Federal-aid project overlays. Projects receiving federal funding are subject to additional requirements, including compliance with the federal MUTCD and FHWA guidelines. These requirements apply in addition to, not in replacement of, state-specific standards.

Railroad and utility coordination. Work zones that affect railroad crossings or utility corridors may require additional approvals from railroad companies, utility owners, or federal agencies. These coordination requirements exist independently of DOT plan approval and may carry separate timelines.

Note: Multi-jurisdiction projects benefit from early coordination with all applicable agencies. Identifying conflicting requirements between jurisdictions early in the planning process helps avoid costly plan revisions and project delays.

State DOT TCP Requirements Comparison

The following table provides a general comparison of traffic control plan requirements across the jurisdictions covered in this guide. All information is subject to change and should be verified with the applicable state DOT. Where a requirement varies by district or contract, this table uses conservative phrasing.

State Primary Governing Manual MUTCD Relationship PE Seal Review Timeline
Virginia VA Work Area Protection Manual (WAPM) State supplement to MUTCD Project-dependent; often required for complex work Varies by VDOT district
Maryland MUTCD with MDOT SHA modifications Adopts MUTCD with state modifications Project-dependent; typically required for complex operations Varies by MDOT SHA district
Pennsylvania PennDOT Publication 213 State supplement to MUTCD Project-dependent; often required for state highway work Varies by PennDOT district
California California MUTCD (CA MUTCD) State edition of MUTCD Often expected or project-dependent Varies by Caltrans district
Florida FDOT Design Standards and Traffic Engineering Manual Adopts MUTCD with state modifications Project-dependent; commonly required on complex projects Varies by FDOT district
Texas Texas MUTCD (TMUTCD) State MUTCD with Texas-specific modifications Project-dependent; often required for complex TxDOT work Varies by TxDOT district
Disclaimer: This table is provided for general reference only. Requirements change as states update their standards and procedures. Consult the applicable DOT district office for current requirements before developing or submitting traffic control plans.

Related Resources

For additional information on traffic control plan development, engineering standards, and LADMA's approach to work zone safety, the following resources provide further detail.

Traffic Control Plans: Standards, Requirements, and Compliance covers the regulatory framework, governing standards, and compliance expectations for work zone traffic control planning.

Traffic Control Plan Services provides an overview of LADMA's TCP development capabilities, including plan engineering, state DOT coordination, and multi-jurisdiction project support.

Traffic Control Plan Development and Coordination

LADMA develops MUTCD-aligned traffic control plans and jurisdiction-ready TTC layouts for projects nationwide. For field deployment and on-site operations, we currently support active coverage across Maryland, Virginia, Washington D.C., Delaware, and Pennsylvania, and we coordinate plan review requirements with the controlling agencies for multi-jurisdiction work.