Maryland traffic control documentation requirements
What Maryland DOT asks a contractor to record about temporary traffic control, where that requirement comes from, and how strong the evidence behind it is.
What Maryland requires
MDOT SHA Section 104 contains TWO explicit contract-binding daily contractor obligations:
- "The contractor shall keep a daily log at the signal site which shall include, but not be limited to, hours of operation, type and time of any equipment malfunctions, and type and time of any crashes or incidents..." (Portable Traffic Signal sites)
- "Perform a daily visual inspection of the devices to ensure that no damage has occurred, and that the end treatment is capable of functioning as intended." (Temporary Traffic Barrier End Treatments)
Plus certified Traffic Control Manager (TCM) on-site requirement.
Source: MDOT SHA Section 104 wikiHow DTCD satisfies it
Daily Entries + Smart Photo Capture produce the "daily log at the signal site" required by Section 104 for Portable Traffic Signal sites — capturing hours of operation, equipment malfunctions, crashes, and incidents. Auto-Capture Signs and AI safety analysis support the "daily visual inspection of the devices" for Temporary Traffic Barrier End Treatments. Personnel Tracking documents TCM presence.
What DTCD adds beyond the requirement
- Connected Devices auto-discovers PTS equipment to populate the daily log automatically
- AI safety analysis identifies barrier end treatment damage automatically, going beyond the manual "visual inspection" requirement
- Public Dashboard gives MDOT SHA real-time visibility
- Multi-Format Export supports the MDOT SHA TTC Inspection/Rating Report Form workflow
Who this helps
Contractor: Section 104 daily PTS log AND daily barrier end treatment inspection obligations are both automated. DOT: MDOT SHA can adopt for inspector use to verify TCM compliance with Section 104.
On federal-aid work, 23 CFR 630 Subparts J and K apply whatever Maryland specifies, with a compliance date of December 31, 2026 — the federal floor, explained. And after an incident the questions come from the incident, not the specification: 105 published judicial matters on that.
DTCD produces this record from the drive-through itself, and names the controlling Maryland requirement on the generated PDF. Open a sample before deciding anything.
Try it on one Maryland project See pricing
Draw the closure on a map and the builder reads the route, mileposts and county from Maryland’s own public GIS, checks bridge clearance on the route and the detour, and exports a WZDx feature, a PDF or an email. It runs in the browser — nothing is submitted or stored.
Open the Maryland builder → · open the offline build · all 50 statesWhat changes at the Maryland state line
Crews rarely work one state, and the record a neighbouring DOT expects is often named differently and cited somewhere else entirely. Here is how the states bordering Maryland compare:
| State | Citation | Evidence we have |
|---|---|---|
| District of Columbia Traffic-Control Documentation | Not yet verified | Agency source, medium confidence |
| Delaware | Section 812 (Certified Traffic Control Supervisor) | Contract-binding spec language |
| Pennsylvania | Not yet verified | Agency source, high confidence |
| Virginia | Section 105.14 (WZTC Accreditation) + Section 512 (Maintaining Traffic) + project Special Provisions + VDOT LAP Manual Chapter 13 | Binding language identified |
| West Virginia | Not yet verified | Agency source, high confidence |
All 50 states → · The full 50-state analysis, with every citation →