North Dakota traffic control documentation requirements
What North Dakota 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 Dakota requires
NDDOT Construction Records Manual says daily diaries should clearly show regular traffic-control inspections are being performed and documented, including follow-up corrections.
Source: North Dakota DOT — primary sourceOn federal-aid work, 23 CFR 630 Subparts J and K apply whatever North Dakota 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 Dakota requirement on the generated PDF. Open a sample before deciding anything.
Try it on one North Dakota project See pricing
Draw the closure on a map and the builder reads the route, mileposts and county from North Dakota’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 Dakota builder → · open the offline build · all 50 statesWhat changes at the North Dakota 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 Dakota compare:
| State | Citation | Evidence we have |
|---|---|---|
| Minnesota | Traffic Control Special Provision 2563 + Technical Memorandum 22-08-T-02 | Binding language identified |
| Montana | Not yet verified | Agency source, high confidence |
| South Dakota | Not yet verified | Agency source, medium confidence |
All 50 states → · The full 50-state analysis, with every citation →