Traffic Control Services
in Baltimore, MD

The jurisdiction depends on which road classification the work falls on. Work within Baltimore City limits on city-maintained streets typically requires a Baltimore City DOT right-of-way permit. Work on state-maintained routes, including those that run through Baltimore City, falls under MDOT SHA authority and typically requires a Lane Closure Permit (LCP) submitted to SHA District 4.

A quick check of the road's maintenance jurisdiction, which is usually indicated on your TCP or available from the permit office, will confirm which agency governs the closure. Some roads within city limits are state-maintained, so the city/state distinction does not always align with geographic boundaries.

Projects that span both city-maintained and state-maintained road segments require coordination with both agencies. This typically means a Baltimore City DOT ROW permit for the city portion and an MDOT SHA LCP for the state portion, with separate documentation and potentially different lead time requirements for each.

Pre-mobilization planning for dual-jurisdiction projects includes identifying the permit boundary, confirming which TCP governs each segment, and establishing communication with both permit contacts. LADMA handles this coordination as part of standard project setup on cross-jurisdiction deployments.

Yes. If you have an approved TCP, LADMA deploys directly to that plan. We review the current version prior to mobilization to confirm device list, taper geometry, and sign sequence align with site conditions. If field conditions differ from what the plan shows, we coordinate with your project team before setup begins rather than deviating from the approved document.

If a plan needs to be developed or revised, LADMA can coordinate TCP design through our traffic engineering resources. Bring the plan version that has agency approval to intake, along with any field-modified markups.

For MDOT SHA work, lane closure permits typically require a minimum of five business days advance notice to District 4 before activation. Baltimore City DOT permit timelines vary depending on corridor classification and current workload at the permit office. Complex or high-volume corridors may require additional review time.

Common delays include incomplete permit applications, TCP revisions requested during agency review, conflicts with pre-scheduled corridor closures, and work hour restrictions on specific roads. Submitting complete documentation early and confirming the corridor is not already under a conflicting closure reservation reduces lead time risk.

Yes. LADMA deploys for night operations and weekend work across Baltimore City and the surrounding county network. Night work on high-volume corridors is often required by permit conditions to minimize peak-hour traffic impact, and LADMA schedules field operations accordingly.

Night and weekend deployments follow the same pre-mobilization review and documentation process as daytime operations. Work hour restrictions specific to certain corridors, such as restrictions on I-695 or key Baltimore City arterials during peak commute windows, are confirmed during permit coordination before the schedule is finalized.

MUTCD Part 6 and MdMUTCD require that pedestrian access through or around a work zone be maintained and that detour routing be clearly signed and compliant with ADA accessibility standards. This includes maintaining minimum pathway widths, providing detectable warning surfaces where required, and ensuring that pedestrian detours do not route users into active traffic lanes.

For Baltimore City projects, pedestrian accommodation requirements are often more specific given higher foot traffic volumes and transit stops along many corridors. The approved TCP should address pedestrian routing. If it does not, LADMA flags this during plan review before mobilization.

LADMA maintains the current approved TCP version, permit documentation with applicable lane closure authorization details, pre-shift setup verification notes, a shift log with start and end times, and a record of any field adjustments made during the operation. Supervisor contact information and the escalation path for site issues are also on hand throughout the deployment.

If an agency inspector visits the site, the field supervisor can produce documentation covering the plan version in use, the permit basis for the closure, and the setup verification from the start of shift. Incident or hazard notes, if applicable, are recorded and available as part of the shift record.

Yes. LADMA provides 24/7 emergency dispatch for unplanned lane closures, utility breaks, road hazards, and other situations requiring immediate work zone traffic control. Emergency response covers Baltimore City and all four surrounding counties.

For emergency deployments, call (240) 861-5050 directly. The dispatch line is staffed around the clock. Provide the location, road classification, and nature of the hazard and LADMA will mobilize resources to the site. Emergency configurations are set up to immediately address the hazard and can be formalized into a permitted closure once the situation is stabilized.

ATSSA flagger certification covers the basic training and qualification requirements for individual flaggers operating in a work zone. The Traffic Control Manager (TCM) designation is a separate, higher-level certification administered through the Maryland Transportation Builders and Materials Association (MTBMA) and required on MDOT SHA projects of certain scope and complexity.

The TCM is responsible for overall work zone setup, compliance verification, and coordination with the permit authority on SHA projects where the designation is required. ATSSA certification and TCM certification serve different roles in the field hierarchy and are not interchangeable. Project requirements for TCM presence are typically specified in the permit or contract documents.

MDOT SHA requires that traffic control devices used on state highway projects meet the standards outlined in the MUTCD and the MdMUTCD, and that specific device types, particularly channelizing devices and crash attenuators, be sourced from the SHA Qualified Products List (QPL). The QPL confirms that a device model has been reviewed and accepted for use on Maryland state roads.

LADMA sources devices for SHA corridor work consistent with QPL requirements. Device compliance is confirmed during pre-mobilization plan review against the approved TCP's device list. Using non-QPL devices on SHA work can result in rejection during agency inspection, so this verification step is part of standard pre-deployment protocol.