Traffic Control Plans in Maryland
MUTCD Part 6 compliant TCP design and field deployment for county and state routes across Maryland. Engineered to MDOT SHA standards. From plan submission through crew deployment.
Statewide Coverage Across All SHA Districts
Maryland's highway network is administered across seven MDOT SHA districts, each with distinct permitting pathways, standard plan requirements, and coordination contacts. Effective traffic control planning for state-maintained routes requires working knowledge of the district your project falls within — not a generic plan template dropped into a permit package.
LADMA operates across all seven SHA districts, designing and deploying traffic control for state highway corridors, county arterials, and multi-jurisdictional projects that cross district boundaries mid-route. For projects spanning multiple districts or transitioning between SHA jurisdiction and county right-of-way, coordination must account for each authority's plan review process separately.
State route jurisdiction and county ROW jurisdiction carry different TCP requirements, permit approval chains, and plan submission standards. SHA-maintained routes require TCP designs that meet SHA Standard Traffic Control Plans and the Maryland Supplement to the MUTCD. County ROW projects are reviewed by individual county departments of public works or highway, each operating on their own standard. For projects that cross both — a utility running along an SHA corridor through a county road intersection, for example — both sets of requirements apply simultaneously.
For Maryland-wide project scopes, multi-district operations, or permit coordination across SHA and county jurisdictions, view LADMA's full Maryland traffic control services.
Note on Baltimore City: Baltimore City operates as an independent jurisdiction separate from Baltimore County and is not administered through the standard SHA district structure for local permits. Projects within Baltimore City limits require coordination through Baltimore City DOT rather than SHA District 4 for local street work, even when adjacent to SHA-maintained routes.
-
D1
District 1 — Eastern Shore
Queen Anne's, Kent, Caroline, Talbot, Dorchester, Wicomico, Worcester, Somerset, Cecil
-
D2
District 2 — Southern Maryland
St. Mary's, Calvert, Charles
-
D3
District 3 — Washington Suburban
Montgomery, Prince George's
-
D4
District 4 — Baltimore
Baltimore City, Baltimore County, Anne Arundel, Howard
-
D5
District 5 — Annapolis
Anne Arundel (shared with D4), administrative and permit coordination hub
-
D6
District 6 — Western Maryland
Allegany, Garrett, Washington, Frederick (partial)
-
D7
District 7 — Northeast
Harford, Cecil (partial with D1), Carroll, Frederick (partial)
Traffic Control Plans We Engineer and Deploy
From initial site assessment through crew deployment, LADMA manages the full traffic control scope under one engagement. The following plan types represent the range of TCP work we design and execute across Maryland state and county routes.
Lane Closures & Shoulder Work
Lane closure TCPs for state highway and county arterial routes, including taper design, buffer calculations, and device spacing to MUTCD Part 6 standards. Applicable to single-lane, alternating, and multi-lane closure configurations on both SHA and county-maintained roads.
View TCP Services →Intersection & Signal Control
Traffic control plans for work zones at signalized and unsignalized intersections, including flagging operations, temporary signal modifications, and turn prohibition management. Designed for utility work, ADA ramp reconstruction, and pavement repair at controlled intersections.
Multi-Phase Construction Staging
Sequenced TCP design for construction projects requiring multiple lane configuration phases over extended durations. Each phase is documented separately with clear transition procedures and permits submitted on the project timeline rather than as a single static plan.
Pedestrian Detour & ADA Accommodation
Work zone pedestrian management plans meeting ADA accessibility requirements, including accessible detour routing, temporary curb ramp installation requirements, and pedestrian signal accommodation. Required for any work zone affecting existing sidewalk or curb ramp access on public right-of-way.
Night Work Operations
Traffic control plans specifically engineered for after-hours operations, including enhanced device visibility requirements, reduced speed zone design, and flagging operations configured for low-visibility conditions. Common for utility restoration work, emergency repairs, and projects on high-volume daytime corridors.
Flagging Operations →Rolling & Progressive Closures
Mobile operation TCPs for crews advancing along a route — common in pavement marking, sweeping, and linear utility installation. Rolling closure plans require specific advance warning configurations and operational speed parameters that differ from stationary work zone plans.
Utility Corridor TCP
Traffic control plans for gas, water, sewer, electric, and telecom installations along public ROW corridors. Utility corridor projects frequently cross SHA and county jurisdictional boundaries within a single project scope, requiring coordinated permit submissions to multiple reviewing authorities.
Emergency & Short-Notice Plans
TCP design and deployment for unplanned utility breaks, emergency road closures, and time-critical work zone situations. When a permit window is short or the job site is already active, response time between plan submission and crew deployment matters.
Permitting Across Maryland Jurisdictions
Maryland traffic control permitting operates across three distinct authority structures — state highway, county right-of-way, and independent city jurisdictions. Understanding which authority reviews your TCP submission, and to what standard, determines the plan design requirements and submission process before a single permit package is assembled.
SHA State Highways — MDOT SHA Permit Process
Work affecting state-maintained highways — any route designated as a Maryland state route, US route, or interstate within Maryland — requires a Lane Closure Permit through MDOT SHA. The TCP submitted with this permit must meet SHA's Standard Traffic Control Plans and the Maryland Supplement to the MUTCD, which specifies device placement, taper lengths, and buffer requirements for Maryland conditions.
SHA distinguishes between standard and complex TCP classifications based on road classification, speed limit, number of lanes closed, and duration of the closure. Complex plans typically require engineering review and may involve coordination with the appropriate SHA district office. Plan complexity directly affects review timelines and submission requirements, though LADMA does not guarantee specific permit approval timeframes, which are determined by SHA based on plan completeness and current review queue.
For projects on the state highway network, LADMA manages TCP design to SHA standards, assembles permit documentation, and coordinates with the applicable SHA district office throughout the review process. Field deployment is coordinated to align with the approved permit window.
County ROW Permits — Local Jurisdiction Process
County-maintained roads operate under each county's Department of Public Works, Department of Transportation, or Highway Division — the structure varies across Maryland's 23 counties. Each county applies its own TCP review standards, permit application requirements, and work authorization processes, though all must comply with MUTCD Part 6 as a baseline.
Some Maryland counties reference SHA's Standard Traffic Control Plans as a baseline for their own reviews; others maintain separate county-specific standards. The submission process also varies — some counties accept digital submissions through permit portals, while others require physical plan sets. Permit fees, notice requirements, and inspection processes differ by county.
County TCP projects may also require coordination with county utility authorities (such as WSSC in Montgomery and Prince George's counties for water and sewer work) separately from the ROW permit itself. LADMA coordinates TCP design to match the applicable county standard and manages permit submissions based on the requirements of the specific county authority.
City-specific TCP permit processes for Baltimore, Frederick, Annapolis, and Rockville are covered on their respective service pages.
Multi-Jurisdiction Projects — Coordinated Submissions
Projects that cross between SHA-maintained routes and county ROW within a single scope require separate permit submissions to each authority — SHA for the state highway segments and the applicable county for the county road segments. The TCP design must satisfy both sets of requirements simultaneously, which may produce different device configurations for different segments of the same project corridor.
Utility corridor projects are particularly prone to multi-jurisdiction scope because infrastructure installations frequently run along state routes before transitioning to county roads through intersections or at jurisdiction boundaries. A gas main running along a state route into a county-maintained road requires coordinated TCP design for the full corridor and permit submissions to both SHA and the county, on parallel timelines.
When Baltimore City is involved — particularly for projects near the city-county boundary — a third permit authority (Baltimore City DOT) may be required. Projects near SHA-maintained roads in Baltimore City that also affect local streets require coordination between SHA and BCDOT as independent reviewing authorities, not as a single SHA district submission.
LADMA manages multi-jurisdiction TCP scopes as a single coordinated engagement, designing to the requirements of each applicable authority and managing permit submissions across authorities on a coordinated timeline.
From Site Assessment to Field Deployment
Most TCP design firms deliver a plan and stop. LADMA manages the full scope — from initial site review through permit coordination and field crew deployment. The process below reflects how a Maryland TCP project moves through LADMA's engagement, start to finish.
Site Assessment & Scope Review
Field conditions, road classification, traffic volumes, and existing infrastructure are assessed before plan design begins. SHA vs. county jurisdiction is confirmed at this stage to determine which permit authority and plan standard applies.
TCP Design & MUTCD Compliance Check
Traffic control plans are engineered to MUTCD Part 6 and the Maryland Supplement, including device placement, taper calculations, buffer distances, and pedestrian accommodation. SHA Standard Traffic Control Plans are referenced where applicable for state highway work.
Jurisdiction Determination
SHA-maintained routes, county ROW segments, and independent city jurisdictions are identified within the project scope. Multi-jurisdiction projects require separate permit submissions assembled to each authority's specific requirements — both are prepared in parallel.
Permit Application Coordination
Permit packages are assembled and submitted to the applicable SHA district office, county highway authority, or municipal DOT. Submission format, plan requirements, and supporting documentation are prepared to the reviewing authority's current standards.
Plan Review Support
Review comments from SHA or county reviewers are addressed and revised plans are resubmitted as needed. LADMA coordinates directly with the reviewing authority during the plan review cycle to resolve comments efficiently and keep the project timeline on track.
Field Crew Deployment & On-Site Implementation
With permit in hand, LADMA deploys the field crew. Flaggers, devices, and signing are set to the approved plan. Field operations are managed by LADMA from the same engagement that produced the plan — no handoff to a separate deployment contractor required.
Representative Project Scope
The following profiles illustrate the type and complexity of TCP projects LADMA designs and deploys across Maryland. These are representative of typical project scopes — not documented case studies with named clients.
Urban Arterial Lane Closure — Water Main Replacement
Multi-Phase Highway Construction Staging
Frequently Asked Questions
Maryland-specific questions on TCP requirements, SHA permitting, jurisdiction differences, and how LADMA handles design through deployment.
Get a TCP QuoteWhat is a traffic control plan and when is one required in Maryland?
A traffic control plan — also referred to as a Maintenance of Traffic (MOT) plan — is an engineered drawing that specifies how vehicle, pedestrian, and bicycle traffic will be managed safely through a work zone. It defines device placement, lane configuration, taper design, signage, and flagging operations for a specific site and scope of work.
In Maryland, a TCP is typically required any time work impacts public right-of-way, including lane closures, shoulder work, sidewalk disruption, or utility installations that affect traffic flow. Both MDOT SHA and individual county permitting authorities require an approved TCP before issuing a work permit for most ROW encroachment activities. The specific trigger thresholds vary by jurisdiction and road classification.
What are MDOT SHA's TCP requirements for state highway work?
Work affecting MDOT SHA-maintained routes requires a Lane Closure Permit, with an approved TCP included in the permit package. SHA evaluates TCPs against its Standard Traffic Control Plans and the Maryland Supplement to the MUTCD, which defines device types, placement distances, taper lengths, and buffer zones for different road classifications and speed environments.
SHA classifies TCPs as standard or complex based on factors including road classification, posted speed, number of lanes affected, and closure duration. Complex plans require more detailed engineering documentation and are subject to SHA district office review. All SHA TCP submissions must demonstrate compliance with MUTCD Part 6 as the baseline federal standard, with Maryland-specific requirements applied on top.
What is the difference between an SHA permit and a county ROW permit?
An SHA permit covers work on state-maintained routes — Maryland state routes, US routes, and interstates within Maryland. It is issued by MDOT SHA and reviewed by the applicable SHA district office. The TCP submitted with this permit must meet SHA's standard plan requirements.
A county ROW permit covers work on county-maintained roads and is issued by the applicable county department — Department of Public Works, Department of Transportation, or Highway Division depending on the county. Each of Maryland's 23 counties operates its own permit process with its own TCP review standards, though all must comply with MUTCD Part 6 as a federal baseline. Projects that span both SHA and county road segments require separate permit submissions to both authorities on coordinated timelines.
How long does TCP plan review typically take in Maryland?
Review timelines vary significantly by authority, plan complexity, and current review queue volume. LADMA does not guarantee specific review or approval timelines, as these are determined entirely by the reviewing authority — SHA district office or county department — not by the plan designer or permit applicant.
Plan completeness and compliance quality directly affect review speed. Incomplete or non-compliant submissions generate review comments that require revised plans and restart the review cycle. Submitting a fully compliant, complete permit package on the first submission is the most effective way to minimize review time. LADMA designs to the applicable standard specifically to reduce the likelihood of review comments on first submission.
What MUTCD standards apply to Maryland work zones?
Maryland work zones must comply with Part 6 of the Manual on Uniform Traffic Control Devices (MUTCD), which covers temporary traffic control device standards, work zone design requirements, and flagger operations. Part 6 establishes the federal baseline that all state and local jurisdictions in Maryland must meet at minimum.
Maryland has adopted a state supplement to the MUTCD that applies additional or modified requirements for certain conditions on Maryland roads. For work on SHA-maintained routes, SHA's Standard Traffic Control Plans provide pre-approved configuration templates that satisfy SHA's application of the MUTCD Supplement. County jurisdictions may apply additional local requirements on top of the MUTCD baseline. All LADMA TCP designs are engineered to the applicable MUTCD standard and the requirements of the specific reviewing authority.
Can LADMA design and deploy traffic control for the same project?
Yes. This is a core operational capability that distinguishes LADMA from firms that provide TCP design only. LADMA manages both the engineering side — site assessment, plan design, MUTCD compliance, permit coordination — and the field side — flaggers, devices, signing, and lane closure execution — under one scope of work.
For contractors and project managers, this eliminates the coordination gap between plan approval and field deployment. There is no handoff to a separate flagging contractor, no risk of a deployment crew working from a different version of the plan, and no split accountability between who designed the work zone and who is implementing it. LADMA holds both responsibilities from site assessment through field operations across Maryland and our full 5-state footprint.
What types of projects in Maryland typically require a TCP?
In Maryland, a traffic control plan is typically required for any work that encroaches on public right-of-way and affects vehicle or pedestrian movement. Common project types that require TCPs include utility main replacements and installations (water, sewer, gas, electric, fiber), lane closures for pavement resurfacing or patching, sidewalk and curb ramp reconstruction, bridge maintenance and inspection, and new construction that requires sustained lane shifts or detours.
Emergency work — utility breaks, emergency road repairs, and similar unplanned closures — also requires TCP compliance, though emergency permit pathways vary by jurisdiction and may accommodate expedited review under certain conditions. Both SHA-permitted and county-permitted projects within LADMA's Maryland service area may require TCPs depending on the specific scope and road classification affected.
How do I request a TCP quote for a Maryland project?
Submit a quote request through LADMA's contact page or call (240) 861-5050 directly. For TCP quotes, it helps to have the project location (county and road name or route number), the type of work being performed, the anticipated duration, and whether the work is on an SHA-maintained route or county road. If you know which SHA district the project falls in, include that as well.
LADMA handles TCP projects across all 24 Maryland counties and Baltimore City, including projects with multi-jurisdiction permit requirements. If your project scope spans SHA and county ROW, or involves multiple counties, note that in your request so the quote reflects the full coordination scope from the start. Quote response targets same business day during normal business hours. For time-critical or emergency TCP needs, call directly for the fastest response.
Traffic Control Plan Services by Region
LADMA provides TCP design and field deployment across Maryland, Virginia, Washington DC, Delaware, and Pennsylvania — under one regional provider for contractors operating across state lines.
Request a TCP Quote for Your Maryland Project
TCP design and field deployment across all Maryland SHA districts and county jurisdictions. 24/7 dispatch available for emergency work zones. Same-day quote response during business hours.
Same-day quote response during business hours • 24/7 dispatch available