50-State Coverage › Washington

Washington traffic control documentation requirements

What Washington 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 2-04.3(1)B (Traffic Control Supervisor)

Spec year

2026 (M 41-10)

Evidence tier

A — contract-binding specification language

Primary source

WSDOT Standard Specifications M 41-10

What Washington requires

From the specification

TCS shall maintain a daily project traffic control diary. WSDOT Forms 421-040A (Summary) and 421-040B (Traffic Control Log) are the WSDOT-provided forms; alternates accepted. WSDOT Construction Manual Ch. 2 explicitly states this requirement is "in accordance with the Standard Specifications."

Source: WSDOT Standard Specifications M 41-10

How solid is this? We have verified contract-binding specification language for Washington and cite the section above. You can open the source and read it yourself — we would rather you did.

How DTCD satisfies it

Daily Entries + PDF Diary Generation produce the daily project traffic control diary as required by Section 2-04.3(1)B. WSDOT's Forms 421-040A and 421-040B format is supported via Multi-Format Export. Personnel Tracking captures TCS presence and certification status; Certification Management tracks ATSSA TCS expiration.

What DTCD adds beyond the requirement

Auto-Capture Signs and Smart Photo Capture provide photographic evidence with each entry — exceeding the textual log requirement
CWZ 1.0 feed publishes to WSDOT's data exchange in real-time
Connected Devices auto-discovers TC equipment for the log
Public Dashboard gives WSDOT region engineers real-time visibility into TCS daily diary activity

Who this helps

Contractor: TCS daily diary obligation under Section 2-04 is satisfied with a stronger evidentiary record than 421-040B alone. DOT: WSDOT inspectors can verify TCS compliance via Public Dashboard without site visits.

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

Try it on one Washington project See pricing

Filing a work-zone request in Washington?

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

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

State	Citation	Evidence we have
Idaho	Not yet verified	Agency source, high confidence
Oregon	Section 00220 (Accommodations for Public Traffic) — TCS duties	Contract-binding spec language

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