Kentucky traffic control documentation requirements
What Kentucky DOT asks a contractor to record about temporary traffic control, where that requirement comes from, and how strong the evidence behind it is.
What Kentucky requires
Verified via direct PDF read of an actual KYTC contract proposal (Call No. 103, McLean County, Contract ID 25-5400). Project Note II: "Furnish a traffic coordinator as per section 112. The traffic coordinator shall inspect the project maintenance of traffic, at least three times daily, or as directed by the engineer, during the Contractor's operations and at any time a lane closure is in place. The traffic coordinator shall report all incidents throughout the work zone to the Engineer."
KYTC Form TC 63-67 cites Spec 112.03.15 for non-correction penalties.
This is the most aggressive contractor inspection frequency in any state spec/SP system reviewed.
Source: KYTC Standard SpecificationsHow DTCD satisfies it
Daily Entries + Smart Photo Capture produce the "three times daily" inspection record required by Section 112 Project Note (Traffic Coordinator). Daily Reminders auto-schedules the three inspection windows. Agency Messaging supports the "report all incidents to the Engineer" requirement. Personnel Tracking documents Traffic Coordinator presence.
What DTCD adds beyond the requirement
- Three-times-daily inspection cadence auto-scheduled and tracked — exceeds the manual notation approach of paper diaries
- AI safety analysis identifies incidents automatically, supporting the "report all incidents" obligation
- CWZ 1.0 feed publishes to KYTC's data system
- Form TC 63-67 deficiency penalties under Spec 112.03.15 are mitigated by photo-evidenced corrective action documentation
Who this helps
Contractor: Section 112 three-times-daily inspection AND incident reporting obligations are automated. KYTC's most aggressive inspection frequency in the country is fully supported. DOT: KYTC Engineer receives real-time incident reports via Agency Messaging.
On federal-aid work, 23 CFR 630 Subparts J and K apply whatever Kentucky 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 Kentucky requirement on the generated PDF. Open a sample before deciding anything.
Try it on one Kentucky project See pricing
Draw the closure on a map and the builder reads the route, mileposts and county from Kentucky’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 Kentucky builder → · open the offline build · all 50 statesWhat changes at the Kentucky 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 Kentucky compare:
| State | Citation | Evidence we have |
|---|---|---|
| Illinois | Project Special Provision (BDE / Recurring Special Provision) | Binding language identified |
| Indiana | Section 801 (Traffic Controls for Construction and Maintenance) — referenced via INDOT GIFE Section 2.8 | Binding language identified |
| Missouri | Not yet verified | Agency source, medium confidence |
| Ohio | Section 614 (Maintaining Traffic) + ODOT Manual of Procedures Section 614 + ODOT D4 General Notes M401 | Contract-binding spec language |
| Tennessee | 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 →