South Carolina traffic control documentation requirements
What South Carolina DOT asks a contractor to record about temporary traffic control, where that requirement comes from, and how strong the evidence behind it is.
What South Carolina requires
SCDOT ED-3 requires frequent day/night WZTC inspections and documenting device conditions in the project diary; frequency may be daily for complex projects.
Source: South Carolina DOT — primary sourceOn federal-aid work, 23 CFR 630 Subparts J and K apply whatever South Carolina 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 South Carolina requirement on the generated PDF. Open a sample before deciding anything.
Try it on one South Carolina project See pricing
Draw the closure on a map and the builder reads the route, mileposts and county from South Carolina’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 South Carolina builder → · open the offline build · all 50 statesWhat changes at the South Carolina 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 South Carolina compare:
| State | Citation | Evidence we have |
|---|---|---|
| Georgia | Section 150 Special Provision (Traffic Control) — WTCS duties | Binding language identified |
| North Carolina | Section 1105-4 (Maintenance and Inspection); Section 1105-5 (Failure to Maintain Traffic Control) | Binding language identified |
All 50 states → · The full 50-state analysis, with every citation →