North Carolina traffic control documentation requirements
What North 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 North Carolina requires
North Carolina requires the inspection regime to be designed and approved before a single device goes out: “Submit a proposed traffic control device maintenance schedule and checklist for approval before construction. Perform continuous maintenance and daily scheduled inspections of temporary traffic control devices.”
Two things follow from that wording. The inspections are daily and scheduled, not as-needed. And the instrument you inspect against is a checklist NCDOT has already approved — so the question after an incident is not only whether you inspected, but whether you inspected against the checklist you committed to.
Section 1105-5 then puts a clock on the response: remedial action immediately for an imminent-danger situation as directed by the Engineer, and within 48 hours after notification of a safety issue that is not an imminent danger. Proving you met a 48-hour clock requires knowing when you were notified and when the correction was verified — both of which are timestamps, and neither of which survives being written up at the end of the week.
Devices deemed unacceptable are replaced according to the ATSSA Quality Guidelines for Work Zone Traffic Control Devices, which makes device condition an assessable, recordable fact rather than a judgment call.
Source: NCDOT 2024 Standard Specifications for Roads and Structures, Division 11How we know: Full-text search of the NCDOT 2024 Standard Specifications for Roads and Structures (fetched from connect.ncdot.gov), Division 11, Section 1105-4 and 1105-5. Note: the 2018 Section 1101 PDF on the NCDOT construction-manual site is a scanned image with no extractable text; the 2024 book was used instead. Verified 2026-09-05.
On federal-aid work, 23 CFR 630 Subparts J and K apply whatever North 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 North Carolina requirement on the generated PDF. Open a sample before deciding anything.
Try it on one North Carolina project See pricing
Draw the closure on a map and the builder reads the route, mileposts and county from North 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 North Carolina builder → · open the offline build · all 50 statesWhat changes at the North 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 North Carolina compare:
| State | Citation | Evidence we have |
|---|---|---|
| Georgia | Section 150 Special Provision (Traffic Control) — WTCS duties | Binding language identified |
| South Carolina | Not yet verified | Agency source, high confidence |
| 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 |
All 50 states → · The full 50-state analysis, with every citation →