Traffic Control Plans in Virginia
MOT & TCP Design for VDOT Projects

In Virginia practice, the terms are often used interchangeably, but there is a distinction in scope. A Traffic Control Plan (TCP) is the broader document — the engineered plan set that details signing, channelization, taper geometry, staging, and device placement for a specific work zone. A Maintenance of Traffic (MOT) plan refers to the same concept but is more commonly used in contractor and utility contexts, particularly when describing how traffic will be maintained through or around a work area over the life of a project.

VDOT and most Virginia jurisdictions accept both terms. The permit application will typically reference a TCP or MOT plan as a required submittal, and the content requirements are functionally the same.

A TCP is generally required any time work is performed within the roadway right-of-way that involves lane closures, shoulder closures, or any activity affecting travel lanes, sidewalks, or bicycle facilities. On VDOT-maintained roads, a Lane Use Permit (LUP) application typically requires a TCP as a submittal. County and city roadways have their own permit requirements, and most jurisdictions require a plan for closures affecting any travel lane, regardless of duration.

Short-duration operations on low-volume roadways may qualify for a simplified plan using applicable MUTCD Part 6 typical application layouts, but a documented plan is still generally required. When in doubt, the permit intake office for the applicable jurisdiction will indicate whether a plan is required and at what level of detail.

Virginia traffic control plans must comply with MUTCD Part 6 — Temporary Traffic Control, which sets federal baseline requirements for signing, channelization, taper calculations, and advance warning configurations. On state-maintained roads, plans are additionally aligned with the VDOT Work Area Protection Manual (WAPM), which establishes Virginia-specific requirements and references typical application layouts where applicable for common work zone configurations.

County and city jurisdictions generally defer to MUTCD Part 6 and may reference VDOT standards as a baseline, though individual jurisdictions can have additional requirements. Reviewing the applicable permit intake documentation before plan preparation is advisable.

At a minimum, the following are needed to begin: project location (address, route number, or GIS pin), work limits (stationing or cross-street references), roadway classification and posted speed, proposed work dates and hours, and a description of the lane closure or restriction requested. If the project involves multiple phases or phases across different shifts, a brief description of the staging sequence is helpful.

Existing MOT conditions, permit contacts, and any previous plan sets or permit applications for the same location are also useful if available. Site photos help when the work zone has unusual geometry or constraints not captured in aerial mapping.

Preparation time depends on project complexity. A single-phase plan for a straightforward lane closure on a standard arterial or secondary road typically requires two to four business days after complete project information is received. Multi-phase plans, phased staging across shifts, or projects with atypical geometry, detour requirements, or multiple permit jurisdictions typically take longer and should be factored into project scheduling accordingly.

Jurisdiction review timelines are separate from plan preparation and vary significantly — VDOT residencies and local jurisdictions operate on their own schedules. Building adequate time into project planning for both plan preparation and permit review is advisable.

Agency review comments are addressed and an updated plan set is resubmitted. The revision process typically involves correcting specific items noted by the reviewer — geometry adjustments, signing changes, additional notes, or formatting requirements — and turning around a revised PDF for resubmission. The number of revision cycles varies by jurisdiction, plan complexity, and the nature of the reviewer's comments.

Revision coordination is handled directly with the project contact to avoid delays from miscommunication about what was changed and why.

Yes, when the work zone affects existing sidewalks, crosswalks, curb ramps, or other pedestrian facilities. MUTCD Part 6 requires that pedestrian access be maintained or a temporary accessible route be established when existing pathways are disrupted. Plans should show the alternate pedestrian path, any channelization needed to direct pedestrians to that route, and applicable signing.

Projects that do not affect any pedestrian facilities may not require a full pedestrian routing note, but the plan should document that no sidewalks or crosswalks are within the work zone limits. When accessible route requirements apply, the specific design standards are determined by the applicable jurisdiction and project conditions.

Yes. Night work plans include additional notes specific to reduced-visibility conditions — enhanced device specifications, lighting requirements where applicable, and any speed limit modifications required by VDOT or local jurisdiction for the work period. Phased staging is documented with separate plan sheets or clearly labeled phases on a single sheet showing the MOT configuration for each distinct work phase or shift.

When a project has multiple phases with meaningfully different lane restrictions or device layouts, each phase is treated as a separate plan sheet to reduce ambiguity in the field and during reviewer evaluation.

A standard submission package includes a PDF plan set with all necessary plan sheets, a signing schedule listing signs by number, legend, and placement, and device notes identifying channelizing devices by type and quantity consistent with the layout. Where phased staging is required, separate phase sheets are included. For projects with detours, supplemental sheets showing the alternate route and signage are part of the package.

The package is formatted to meet the submittal requirements of the applicable jurisdiction — VDOT residency, county permit office, or city engineering department — so that it can be submitted as part of the LUP or ROW permit application without modification.

The TCP is submitted by the party applying for the Lane Use Permit or Right-of-Way permit — typically the general contractor, utility contractor, or subcontractor responsible for the work. The TCP is a required attachment to the permit application, not a standalone submission. The permit applicant is responsible for submitting the permit application, managing correspondence with the jurisdiction, and ensuring all required attachments and project information are included.

LADMA prepares the plan set and formats it for the applicable permit submittal. The permit application itself — including any required forms, fees, insurance documentation, or project contacts — remains the responsibility of the permit applicant.