50-State Coverage › California

California traffic control documentation requirements

What California 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 12-4.02C(11)(a)(iii) (Traffic Control Technician — Submittals)
Spec year
2025
Evidence tier
A — contract-binding specification language

What California requires

From the specification

Caltrans requires a traffic control daily report for every closure, submitted weekly: “Every Monday by noon, submit traffic control daily reports for the previous week as an informational submittal.” A traffic control technician must be assigned to each closure.

The specification then enumerates what the report must contain — date; name of the traffic control technician; location by description, county, route, postmile or station and direction; a reference to the traffic control standard plan or project plan sheet; lane requirement chart number with start and end times; facility type; which lanes or shoulder were closed; names of flaggers; and use of a work-zone speed reduction, buffer lanes or COZEEP support.

It also requires documentation of LCS status confirmation, verification that the closure complies with the contract, modifications to the traffic control including a description of the change, the reason for it and the time it was implemented, traffic control system monitoring including time of inspection and observations, and incidents that occur while the traffic control system is in place.

Source: Caltrans 2025 Standard Specifications, Section 12
How solid is this? We have verified contract-binding specification language for California 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 Caltrans 2025 Standard Specifications, Section 12 (Temporary Traffic Control), pp. 200-201. Verified 2026-09-05.

The agency's form. Caltrans Form CEM-2210 Traffic Control Daily Report is the agency's form for this.

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

Try it on one California project See pricing

Filing a work-zone request in California?

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

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

StateCitationEvidence we have
ArizonaNot yet verifiedAgency source, high confidence
NevadaSection 624.03.06 (Traffic Control Supervisor)Contract-binding spec language
OregonSection 00220 (Accommodations for Public Traffic) — TCS dutiesContract-binding spec language

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