Virginia traffic control documentation requirements
What Virginia DOT asks a contractor to record about temporary traffic control, where that requirement comes from, and how strong the evidence behind it is.
What Virginia requires
VDOT LAP Manual Chapter 13 (verified): "A daily diary of project activities must be kept for all projects and made available for VDOT review on all federal aid projects or projects to be maintained by VDOT."
This is a Locally Administered Projects Manual provision binding on LAP contracts and federal-aid projects. Section 105.14 requires accredited Basic/Intermediate WZTC personnel. Project SP requires TCS to maintain a project work zone TC diary in a bound book with payment consequences when incorporated.
Source: VDOT 2020 Road and Bridge SpecificationsHow DTCD satisfies it
Daily Entries + PDF Diary Generation produce the "daily diary of project activities" required by VDOT LAP Manual Chapter 13 for federal-aid and VDOT-maintained projects, and the "project work zone traffic control diary in a bound book" required by VDOT Section 512 SP (when incorporated). PDF/A archival-quality export with metadata replaces the bound paper book with a stronger record. Personnel Tracking documents accredited WZTC personnel.
What DTCD adds beyond the requirement
- Digital diary with photo evidence, GPS, and timestamps exceeds the "bound book" format
- CWZ 1.0 feed publishes to VDOT's 511 system
- Auto-Capture Signs automates device documentation
- AI safety analysis identifies deficiencies
Note: LAP Manual Ch. 13 daily diary applies to federal-aid projects and VDOT-maintained projects (broad scope). Section 512 SP language is project-specific. Daily-doc clause exists at LAP/Federal-aid level even if not in Section 512 itself.
On federal-aid work, 23 CFR 630 Subparts J and K apply whatever Virginia 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 Virginia requirement on the generated PDF. Open a sample before deciding anything.
Try it on one Virginia project See pricing
Draw the closure on a map and the builder reads the route, mileposts and county from Virginia’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 Virginia builder → · open the offline build · all 50 statesWhat changes at the Virginia 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 Virginia compare:
| State | Citation | Evidence we have |
|---|---|---|
| District of Columbia Traffic-Control Documentation | Not yet verified | Agency source, medium confidence |
| Kentucky | Section 112 (Maintenance and Control of Traffic) + standard Project Note "II. TRAFFIC COORDINATOR" | Contract-binding spec language |
| Maryland | Section 104 (Maintenance of Traffic) — PTS daily log + Traffic Barrier daily visual inspection clauses | Contract-binding spec language |
| North Carolina | Section 1105-4 (Maintenance and Inspection); Section 1105-5 (Failure to Maintain Traffic Control) | Binding language identified |
| Tennessee | 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 →