50-State Coverage › Utah

Utah traffic control documentation requirements

What Utah DOT asks a contractor to record about temporary traffic control, where that requirement comes from, and how strong the evidence behind it is.

Citation
Section 01554 (Traffic Control) — 1.5 Submittals and 1.9 Traffic Control Supervisor
Spec year
2026
Evidence tier
A — contract-binding specification language

What Utah requires

From the specification

Utah is among the most prescriptive states in the country on inspection frequency. Section 01554 requires the Traffic Control Supervisor to “document inspections on a form acceptable to the Engineer,” including at minimum an assessment of device quality and items in compliance with the authorized traffic control plan. Those forms are a contract submittal: “Traffic Control Inspection forms weekly for information,” submitted on a day and time acceptable to the Engineer.

The inspection cadence is spelled out rather than left to judgment. When construction work is occurring, inspect at least four times each day, with at least one inspection during nighttime hours: before the beginning of shift, at mid-shift, half an hour after shift ends, and at the midpoint of the off-shift period. When construction is not occurring but traffic control is still present, inspect twice each day — once in daylight, once at night, at least eight hours apart.

The Traffic Control Supervisor must also remain available 24 hours a day, seven days a week, be on site within 30 minutes of notification, and correct deficiencies immediately upon notification from the Engineer.

Source: UDOT 2026 Standard Specifications, Section 01554
How solid is this? We have verified contract-binding specification language for Utah and cite the section above. You can open the source and read it yourself — we would rather you did.

How we know: Read directly from the UDOT 2026 Standard Specifications, Section 01554, pp. 3 and 6-7. Verified 2026-09-05.

The agency's form. UDOT C-111 Project Daily Reports and Daily Traffic Control Inspection Reports appear on the agency's final packet checklist.

On federal-aid work, 23 CFR 630 Subparts J and K apply whatever Utah 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 Utah requirement on the generated PDF. Open a sample before deciding anything.

Try it on one Utah project See pricing

Filing a work-zone request in Utah?

Draw the closure on a map and the builder reads the route, mileposts and county from Utah’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 Utah builder → · open the offline build · all 50 states

What changes at the Utah 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 Utah compare:

StateCitationEvidence we have
ArizonaNot yet verifiedAgency source, high confidence
ColoradoSection 630.10/630.11 (TCS requirements)Binding language identified
IdahoNot yet verifiedAgency source, high confidence
NevadaSection 624.03.06 (Traffic Control Supervisor)Contract-binding spec language
WyomingSection 703.4.2 (Documentation)Contract-binding spec language

All 50 states → · The full 50-state analysis, with every citation →