Ohio traffic control documentation requirements
What Ohio DOT asks a contractor to record about temporary traffic control, where that requirement comes from, and how strong the evidence behind it is.
What Ohio requires
Verified via direct PDF read.
ODOT Manual of Procedures Section 614 explicit: "Contractor personnel – if a Worksite Traffic Control Supervisor is specified in the contract documents, the review is to be performed and documented on a daily basis." And: "Ensure that the form is signed and dated by the contractor's worksite traffic supervisor as specified in the contract documents."
ODOT District 4 General Notes M401 (incorporated into project plans): "The designated individual shall also inspect all traffic devices at the beginning and at the end of each work day. The designated individual or a qualified representative shall also be available on an around-the-clock basis to repair and/or replace damaged or missing devices."
CA-D-8 form (Long Term Inspection Form) documents the inspection — must be signed and dated by the contractor's Worksite Traffic Supervisor when WTS is specified in contract documents.
Source: ODOT 2023 Construction & Material SpecificationsHow DTCD satisfies it
Daily Entries + Smart Photo Capture produce the daily review record required by ODOT MOP Section 614 when WTS is specified. PDF Diary Generation produces ODOT CA-D-8 form-compatible documentation. Personnel Tracking documents WTS presence, certification, and the beginning/end-of-day inspection points required by D4 General Notes M401.
What DTCD adds beyond the requirement
- AI safety analysis identifies compliance issues during the daily review automatically
- CWZ 1.0 feed publishes to ODOT OHGO traveler information system
- Auto-Capture Signs documents devices with photo evidence — exceeds the CA-D-8 form's checkbox approach
- Public Dashboard provides ODOT District construction office real-time visibility
- Daily Reminders auto-schedules the beginning-of-day and end-of-day inspections required by D4 General Notes M401
Who this helps
Contractor: ODOT Section 614 daily review obligation is automated with photo evidence; D4 General Notes M401 begin/end-of-day inspections fully supported. DOT: ODOT District construction office receives real-time visibility via Public Dashboard.
One caveat
The daily contractor documentation requirement is conditional on a Worksite Traffic Control Supervisor being specified in the contract documents. ODOT specifies WTS on most projects of meaningful size. For projects without a specified WTS, Section 614 still requires contractor TC maintenance but daily-documentation specifically applies when WTS is required.
On federal-aid work, 23 CFR 630 Subparts J and K apply whatever Ohio 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 Ohio requirement on the generated PDF. Open a sample before deciding anything.
Try it on one Ohio project See pricing
Draw the closure on a map and the builder reads the route, mileposts and county from Ohio’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 Ohio builder → · open the offline build · all 50 statesWhat changes at the Ohio 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 Ohio compare:
| State | Citation | Evidence we have |
|---|---|---|
| Indiana | Section 801 (Traffic Controls for Construction and Maintenance) — referenced via INDOT GIFE Section 2.8 | Binding language identified |
| Kentucky | Section 112 (Maintenance and Control of Traffic) + standard Project Note "II. TRAFFIC COORDINATOR" | Contract-binding spec language |
| Michigan | Section 812.03 (Temporary Traffic Control for Construction Zone Operations) | Contract-binding spec language |
| Pennsylvania | Not yet verified | Agency source, high confidence |
| West Virginia | Not yet verified | Agency source, high confidence |
All 50 states → · The full 50-state analysis, with every citation →