DTCD 50-State Traffic Control Documentation Analysis

Version 25 (Markdown) Last updated: April 2026 Author: PurposeBuilt Systems, LLC

Purpose

This document serves two purposes:

1. Identify specific existing state and federal requirements that support using DTCD for traffic control documentation
2. Show how DTCD meets and exceeds each of those requirements with specific feature-to-clause mappings

It is built for use in M Street pitch materials, RFP responses, procurement conversations, and direct customer/agency outreach. Every claim is anchored to either a verified state spec citation, a verified federal CFR section, or a documented DTCD capability from the app's About screen.

Quick Summary

Tier A states: Arkansas, Delaware, Florida, Iowa, Kentucky, Louisiana, Maryland, Mississippi, Ohio, Oregon, Texas, Washington, Wyoming

Tier B states: Colorado, Georgia, Illinois, Indiana, Minnesota, Oklahoma, Vermont, Virginia

DTCD Capabilities (Reference)

DTCD offers 25 documented capabilities organized into 7 functional areas:

Documentation & Reporting

• PDF Diary Generation — Professional reports with maps, photos, daily entries
• Daily Entries — Track daily work zone updates and changes
• Multi-Format Export — CWZ 1.0, WZDx, KML, invoice generation
• Invoice & Billing — Configurable rates, bid items, invoice generation

Capture & AI Recognition

• Smart Photo Capture — GPS-tagged, MUTCD sign recognition, landscape support
• Auto-Capture Signs — Drive-through detection with night mode and low-light adaptation
• AI Safety Analysis — Flags compliance issues in captured photos
• Auto-detect closure types — Lane, full road, sidewalk, detour configurations

Mapping & Tracking

• Road-Snapped Mapping — Accurate route display with road alignment
• Detour Route Mapping — Draw and publish detour routes for full road closures
• Mobile Work Tracking — Live GPS for striping, sweeping, mowing operations
• Personnel Tracking — Flagger and pilot car hours with auto-calculation

Devices & Integration

• Connected Devices — Auto-discover arrow boards, message signs, smart devices
• V2X Integration — Work zone alerts to Waze, Google Maps, HERE, TomTom
• Digital ROW Integration — Seamless data exchange with DRU for utility coordination

Real-Time Operations

• Public Dashboard — Real-time monitoring for oversight agencies
• Agency Messaging — Two-way communication with DOT inspectors
• Live Activities — Lock screen and Dynamic Island countdown
• Home Screen Widget — At-a-glance closure countdown
• Daily Reminders — Scheduled notifications for diary updates
• Safety Alerts — AI-powered safety analysis and crash/incident reporting

Operational/Workforce

• Certification Management — Track ATSSA, IMSA, NSC, and state-specific certifications
• Training Mode — Practice without publishing to public feeds

Compliance Standards

• CWZ 1.0 — ITE Common Work Zone Standard (FHWA successor to WZDx)
• WZDx v4.2 — Backwards-compatible export via Multi-Format Export
• MUTCD — Manual on Uniform Traffic Control Devices sign recognition
• KML / GeoJSON / Shapefile — Geographic visualization for GIS integration
• PDF/A — Archival-quality document generation with metadata
• ISO 8601 — International date/time format for data exchange
• ASCE 75-22 — Subsurface utility engineering standard (via DRU integration)

Federal Mandate Foundation

The federal regulations below apply to every federal-aid highway project — which is essentially every state DOT highway construction project. This is the universal floor that DTCD's compliance stack maps to.

23 CFR 630 Subpart J — Work Zone Safety and Mobility

Effective Dec 2, 2024; compliance Dec 31, 2026

23 CFR 630 Subpart K — Temporary Traffic Control Devices

23 CFR Part 635 — Construction and Maintenance

23 CFR Part 655 Subpart F — MUTCD

The Manual on Uniform Traffic Control Devices establishes the federal sign and traffic control device standard binding on all state and local highway agencies.

DTCD Compliance Stack → Federal Mandates Mapping

Defensible federal-floor claim:

DTCD's compliance stack — CWZ 1.0, MUTCD, PDF/A, ISO 8601, KML — directly maps to the federal regulations that apply to every state DOT highway construction contract. Under 23 CFR 630.1108(f), every federal-aid project is federally required to include Temporary Traffic Control pay item provisions. Under 23 CFR 630.1008(c) and (d), every state DOT is required to use field observations and operational data to monitor work zones, and to ensure all TC personnel are trained. DTCD makes those existing obligations efficient, auditable, and digitally documented.

Tier A States — Verified Spec-Binding Daily TC Documentation

These 12 states have contract-binding language requiring the contractor to perform daily traffic control documentation. Each has a sales-ready summary below.

Iowa

Strict Tier: A | Broader Tier: A | Spec Year: 2023

Citation: Section 2528.01.C (Traffic Quality Control)

Source: Iowa DOT ERL Section 2528

Requirement (verbatim from spec)

Contractor's Traffic Control Technician shall "maintain a project traffic control daily diary in a format provided by the Contracting Authority." The Technician supervising installation/removal of TC devices shall be on site and document in the daily traffic control diary what was installed or removed. Submitted to the Engineer; becomes part of permanent project records.

Iowa Regulatory Exclusion (Form 105023)

Pursuant to PurposeBuilt Systems LLC's filing under Iowa Code § 68B.4 and 351 IAC 6.11(68B), use of DTCD by Iowa DOT, by contractors and consultants subject to Iowa DOT regulatory authority, and by engineering and consulting firms holding active Iowa DOT contracts is unauthorized. Whether your organization falls within the excluded class is determined under Iowa Code Chapter 68B by the Iowa Ethics & Campaign Disclosure Board or Iowa DOT, not by PurposeBuilt. The Iowa entry is included in this 50-state survey for informational completeness only and is not a solicitation of Iowa DOT or Iowa-regulated entities.

Wyoming

Strict Tier: A | Broader Tier: A | Spec Year: 2021

Citation: Section 703.4.2 (Documentation)

Source: WYDOT 2021 Standard Specifications

Requirement

Section 703.4.2 requires a daily traffic control device record. Form E-101 "Daily Traffic Control Device Record" is referenced from the binding spec section.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the equivalent of Form E-101 with location, timestamps, and device descriptions automatically captured. PDF Diary Generation exports in WYDOT-compatible format. Multi-Format Export supports KML for WYDOT GIS integration.

DTCD Adds Beyond the Requirement

• Auto-Capture Signs uses drive-through MUTCD sign recognition to populate the device record automatically — Form E-101 captures what was deployed; DTCD captures it the moment it's deployed
• CWZ 1.0 feed publishes work zone data for WYDOT 511 traveler information system
• Connected Devices auto-discovers arrow boards and message signs typically required to be logged manually on Form E-101

Audience

Contractor: Replaces Form E-101 paper workflow with automated digital capture. DOT: WYDOT can adopt for inspector use to verify Section 703.4.2 compliance.

Washington

Strict Tier: A | Broader Tier: A | Spec Year: 2026 (M 41-10)

Citation: Section 2-04.3(1)B (Traffic Control Supervisor)

Source: WSDOT Standard Specifications M 41-10

Requirement

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."

DTCD Satisfies

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.

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

Audience

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.

Oregon

Strict Tier: A | Broader Tier: A | Spec Year: 2024

Citation: Section 00220 (Accommodations for Public Traffic) — TCS duties

Source: ODOT 2024 Standard Specifications

Requirement

ODOT 2024 Section 00220 spec-binds the Contractor's TCS to: "Perform routine inspections of the TCD. Prepare and sign the daily 'Traffic Control Inspection Report.'" Form 734-2474 is the standard form. Confirmed via Eugene amendment which adopts ODOT spec verbatim.

DTCD Satisfies

Daily Entries + PDF Diary Generation produce the equivalent of ODOT Form 734-2474 with the daily inspection requirement defined in Section 00220. Personnel Tracking documents TCS presence; Certification Management tracks Oregon TCS card validity (ATSSA or ESC, 4-year recert).

DTCD Adds Beyond the Requirement

• Smart Photo Capture provides timestamped GPS-tagged photo evidence of every TCD inspected — exceeds the form's text-only checkbox approach
• CWZ 1.0 feed publishes to ODOT TripCheck and partner systems automatically
• AI safety analysis flags non-compliance during inspection
• Detour Route Mapping handles full road closure documentation that Form 734-2474 only describes verbally

Audience

Contractor: Section 00220 daily TCIR signing obligation is automated. DOT: ODOT inspectors and project engineers can review TCIRs in real-time rather than waiting for paper submission.

Florida

Strict Tier: A | Broader Tier: A | Spec Year: 2025

Citation: Section 102-3.2 (Worksite Traffic Supervisor)

Source: FDOT 2025-26 Standard Specifications eBook

Requirement

FDOT Spec 102-3.2: WTS "conducts daily daytime and weekly nighttime inspections within the limits of the project for projects with predominant daytime work activities and daily nighttime and weekly daytime inspections for projects with predominant nighttime work. The WTS notes any deficiencies in the MOT Review Report Form and provides a weekly report to the Project Administrator using form number 700-010-08."

DTCD Satisfies

Daily Entries + PDF Diary Generation produce daily inspection records consistent with the WTS daily inspection requirement under Section 102-3.2. The MOT Review Report Form 700-010-08 weekly compilation is supported via Multi-Format Export. Smart Photo Capture documents deficiencies as required for the report. Certification Management tracks WTS certification (FDOT TTC training, ATSSA, IMSA, NSC).

DTCD Adds Beyond the Requirement

• Daily daytime + weekly nighttime inspection schedule auto-managed via Daily Reminders
• AI safety analysis identifies deficiencies in captured photos automatically — going beyond the WTS's manual notation requirement
• CWZ 1.0 feed publishes to FDOT FL511 traveler information system
• Public Dashboard provides FDOT Project Administrator real-time visibility instead of waiting for the weekly Form 700-010-08 submission

Audience

Contractor: Section 102-3.2 WTS daily inspection obligation produces stronger evidentiary record than Form 700-010-08 alone. DOT: FDOT Project Administrator can review WTS daily inspections in real-time and direct corrective action via Agency Messaging.

Texas

Strict Tier: A | Broader Tier: B | Spec Year: 2024

Citation: Item 502 (Barricades, Signs, and Traffic Handling) — General Notes

Source: TxDOT Item 502 Standard Specifications

Requirement

TxDOT Item 502 General Notes: "Inspect and correct deficiencies each day throughout the duration of the Contract. In accordance with Article 502.4., 'Payment,' no payment will be made for the month if the Contractor fails to provide or properly maintain signs and devices in compliance with Contract requirements."

This is the strongest enforcement teeth in any state — payment consequence for noncompliance.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the daily inspection-and-correction record required by Item 502 General Notes. Multi-Format Export produces TxDOT-compatible documentation for Article 502.4 payment compliance. Personnel Tracking captures contractor crew presence and corrective actions taken.

DTCD Adds Beyond the Requirement

• AI-powered MUTCD sign recognition automatically identifies device deficiencies — exceeds the manual "inspect and correct" obligation by flagging issues before they become payment-affecting noncompliance
• CWZ 1.0 feed publishes to TxDOT DriveTexas and partner systems
• Photo evidence with timestamps and GPS provides defensible documentation in case of payment dispute under Article 502.4
• Public Dashboard gives TxDOT Area Engineer real-time visibility

Audience

Contractor: Item 502 daily inspection and Article 502.4 payment risk is mitigated by photo-evidenced auditable record. DOT: TxDOT Area Engineer can verify Item 502 compliance via Public Dashboard, reducing inspection labor.

Louisiana

Strict Tier: A | Broader Tier: B | Spec Year: 2025 (Std Plan TTC-00(B) + Section 713)

Citation: DOTD Standard Plan TTC-00(B) Temporary Traffic Control General Notes

Source: DOTD Standard Plan TTC-00(B)

Requirement

DOTD Standard Plan TTC-00(B) (rev. Feb 7, 2025): "Daily updates to the DTOE, Project Engineer and TMC operator (if applicable) will be required for all projects where active closures are in place. Weekly updates… for all ongoing lane closures." And: "Contractors are responsible for complying with all TTC standards."

Standard Plan is contract-binding via Section 713.

DTCD Satisfies

Daily Entries + Agency Messaging produce the "daily updates to the DTOE, Project Engineer and TMC operator" required by Standard Plan TTC-00(B) for projects with active closures. Multi-Format Export supports the weekly update reporting cadence. CWZ 1.0 feed integrates with LADOTD TMC systems for real-time closure status.

DTCD Adds Beyond the Requirement

• Auto-Capture Signs and Connected Devices automate the device-by-device log that DOTD inspectors verify
• AI safety analysis identifies compliance issues
• Real-time CWZ 1.0 feed feeds LADOTD's regional and statewide TMC operators automatically — replacing the explicit "updates to TMC operator" obligation with automated data flow
• Public Dashboard provides DTOE real-time visibility

Audience

Contractor: Standard Plan TTC-00(B) daily update obligation under Section 713 is satisfied automatically through real-time data flow. DOT: DTOE, Project Engineer, and TMC operators receive updates without manual reporting.

Delaware

Strict Tier: A | Broader Tier: A | Spec Year: 2025

Citation: Section 812 (Certified Traffic Control Supervisor)

Source: DelDOT 2025 Standard Specifications

Requirement

DelDOT Section 812: "Preparing a Daily Log to record traffic control maintenance including the number and location of TC devices, placement times, changes, and repairs." And: "Ensure that the traffic control supervisor checks in and checks out daily with the engineer."

This is decisive Daily Log language directly in the spec.

DTCD Satisfies

Daily Entries + PDF Diary Generation produce the "Daily Log" required by Section 812 (CTCS duties) — recording the number and location of TC devices, placement times, changes, and repairs as the spec specifies. Personnel Tracking documents the "check in and check out daily with the engineer" requirement. Certification Management tracks ATSSA TCS certification.

DTCD Adds Beyond the Requirement

• Smart Photo Capture provides photographic evidence of every device's number and location — exceeds the textual log requirement of Section 812
• AI sign recognition automates device identification
• CWZ 1.0 feed publishes to DelDOT's data exchange
• Agency Messaging enables the daily check-in/check-out with the Engineer to happen in real-time rather than face-to-face only

Audience

Contractor: Section 812 Daily Log requirement is fully satisfied with auditable photo evidence. DOT: DelDOT engineers receive real-time CTCS check-in/check-out via Agency Messaging.

Maryland

Strict Tier: A | Broader Tier: B | Spec Year: 2025

Citation: Section 104 (Maintenance of Traffic) — PTS daily log + Traffic Barrier daily visual inspection clauses

Source: MDOT SHA Section 104 wiki

Requirement

MDOT SHA Section 104 contains TWO explicit contract-binding daily contractor obligations:

1. "The contractor shall keep a daily log at the signal site which shall include, but not be limited to, hours of operation, type and time of any equipment malfunctions, and type and time of any crashes or incidents..." (Portable Traffic Signal sites)
2. "Perform a daily visual inspection of the devices to ensure that no damage has occurred, and that the end treatment is capable of functioning as intended." (Temporary Traffic Barrier End Treatments)

Plus certified Traffic Control Manager (TCM) on-site requirement.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the "daily log at the signal site" required by Section 104 for Portable Traffic Signal sites — capturing hours of operation, equipment malfunctions, crashes, and incidents. Auto-Capture Signs and AI safety analysis support the "daily visual inspection of the devices" for Temporary Traffic Barrier End Treatments. Personnel Tracking documents TCM presence.

DTCD Adds Beyond the Requirement

• Connected Devices auto-discovers PTS equipment to populate the daily log automatically
• AI safety analysis identifies barrier end treatment damage automatically, going beyond the manual "visual inspection" requirement
• Public Dashboard gives MDOT SHA real-time visibility
• Multi-Format Export supports the MDOT SHA TTC Inspection/Rating Report Form workflow

Audience

Contractor: Section 104 daily PTS log AND daily barrier end treatment inspection obligations are both automated. DOT: MDOT SHA can adopt for inspector use to verify TCM compliance with Section 104.

Mississippi

Strict Tier: A | Broader Tier: A | Spec Year: 2017 + SP 907-618-12

Citation: Special Provision No. 907-618-12 (Section 618 Maintenance of Traffic)

Source: MDOT LPA PDM checklist

Requirement

MDOT Special Provision 907-618-12: "Once work begins, daily daytime inspections and weekly nighttime inspections are required on projects with predominantly daytime work, and daily nighttime inspections and weekly daytime inspections are required on projects with predominantly nighttime work. Weekly inspections will be allowed for periods outside of active construction."

SP is on MDOT LPA Project Development Manual checklist confirming recurrence across MDOT contracts.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the daily daytime and weekly nighttime inspection records required by SP 907-618-12 (or daily nighttime + weekly daytime depending on project schedule). Daily Reminders auto-schedules inspection cadence per project work-time profile.

DTCD Adds Beyond the Requirement

• AI-powered safety analysis automates deficiency identification — exceeds the manual SP 907-618-12 inspection requirement
• CWZ 1.0 feed publishes to MDOT MS511 system
• Auto-Capture Signs documents device installation and removal with timestamps and GPS
• Public Dashboard provides MDOT real-time visibility
• Multi-Format Export supports MDOT documentation requirements

Audience

Contractor: SP 907-618-12 daily inspection obligation is automated with stronger evidentiary record. DOT: MDOT can verify SP compliance via Public Dashboard without inspector site visits.

Arkansas

Strict Tier: A | Broader Tier: A | Spec Year: 2014 + SS-604 + Doc Express

Citation: Special Provision SS-604 (Inspection of Traffic Control Devices in Construction Zones) + ARDOT Doc Express Contract Submittal System

Source: ARDOT Doc Express Contractor Guide

Requirement

ARDOT Doc Express Contractor Guide: "All Traffic Control Device Inspection reports shall be uploaded by the Contractor directly to the Traffic Control Device Inspection Report – Contractor Submittal drawer." And: "The Contractor may submit each day as a separate file or a full week as a single file."

Doc Express is the ARDOT paperless contracting system; submittals are mandatory contract obligations. Combined with SS-604 and the ARDOT Traffic Control Device Inspection Form, this establishes contract-binding daily contractor inspection report submission.

DTCD Satisfies

Daily Entries + PDF Diary Generation produce the Traffic Control Device Inspection Report submitted via ARDOT Doc Express Contractor Submittal drawer per SS-604. Multi-Format Export produces the daily file (or weekly compilation) format Doc Express requires. Smart Photo Capture documents deficiencies as required.

DTCD Adds Beyond the Requirement

• Doc Express Contractor Submittal drawer can be populated automatically — DTCD generates the daily submittal file ready for upload
• AI sign recognition automates device identification
• CWZ 1.0 feed publishes to ARDOT IDriveArkansas system
• Photo evidence with GPS and timestamps provides defensible record
• Agency Messaging enables real-time communication with ARDOT Engineer

Audience

Contractor: SS-604 daily TC Device Inspection Report submission via Doc Express is automated. DOT: ARDOT Engineer receives stronger documentation than current Doc Express submission alone.

Kentucky

Strict Tier: A | Broader Tier: A | Spec Year: 2012 + Section 112 + standard Project Note

Citation: Section 112 (Maintenance and Control of Traffic) + standard Project Note "II. TRAFFIC COORDINATOR"

Source: KYTC Standard Specifications

Requirement

Verified via direct PDF read of an actual KYTC contract proposal (Call No. 103, McLean County, Contract ID 25-5400). Project Note II: "Furnish a traffic coordinator as per section 112. The traffic coordinator shall inspect the project maintenance of traffic, at least three times daily, or as directed by the engineer, during the Contractor's operations and at any time a lane closure is in place. The traffic coordinator shall report all incidents throughout the work zone to the Engineer."

KYTC Form TC 63-67 cites Spec 112.03.15 for non-correction penalties.

This is the most aggressive contractor inspection frequency in any state spec/SP system reviewed.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the "three times daily" inspection record required by Section 112 Project Note (Traffic Coordinator). Daily Reminders auto-schedules the three inspection windows. Agency Messaging supports the "report all incidents to the Engineer" requirement. Personnel Tracking documents Traffic Coordinator presence.

DTCD Adds Beyond the Requirement

• Three-times-daily inspection cadence auto-scheduled and tracked — exceeds the manual notation approach of paper diaries
• AI safety analysis identifies incidents automatically, supporting the "report all incidents" obligation
• CWZ 1.0 feed publishes to KYTC's data system
• Form TC 63-67 deficiency penalties under Spec 112.03.15 are mitigated by photo-evidenced corrective action documentation

Audience

Contractor: Section 112 three-times-daily inspection AND incident reporting obligations are automated. KYTC's most aggressive inspection frequency in the country is fully supported. DOT: KYTC Engineer receives real-time incident reports via Agency Messaging.

Ohio

Strict Tier: A | Broader Tier: B | Spec Year: 2023

Citation: Section 614 (Maintaining Traffic) + ODOT Manual of Procedures Section 614 + ODOT D4 General Notes M401

Source: ODOT 2023 Construction & Material Specifications

Supporting source: ODOT MOP Section 614 (online docs)

Requirement

Verified via direct PDF read.

ODOT Manual of Procedures Section 614 explicit: "Contractor personnel – if a Worksite Traffic Control Supervisor is specified in the contract documents, the review is to be performed and documented on a daily basis." And: "Ensure that the form is signed and dated by the contractor's worksite traffic supervisor as specified in the contract documents."

ODOT District 4 General Notes M401 (incorporated into project plans): "The designated individual shall also inspect all traffic devices at the beginning and at the end of each work day. The designated individual or a qualified representative shall also be available on an around-the-clock basis to repair and/or replace damaged or missing devices."

CA-D-8 form (Long Term Inspection Form) documents the inspection — must be signed and dated by the contractor's Worksite Traffic Supervisor when WTS is specified in contract documents.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the daily review record required by ODOT MOP Section 614 when WTS is specified. PDF Diary Generation produces ODOT CA-D-8 form-compatible documentation. Personnel Tracking documents WTS presence, certification, and the beginning/end-of-day inspection points required by D4 General Notes M401.

DTCD Adds Beyond the Requirement

• AI safety analysis identifies compliance issues during the daily review automatically
• CWZ 1.0 feed publishes to ODOT OHGO traveler information system
• Auto-Capture Signs documents devices with photo evidence — exceeds the CA-D-8 form's checkbox approach
• Public Dashboard provides ODOT District construction office real-time visibility
• Daily Reminders auto-schedules the beginning-of-day and end-of-day inspections required by D4 General Notes M401

Audience

Contractor: ODOT Section 614 daily review obligation is automated with photo evidence; D4 General Notes M401 begin/end-of-day inspections fully supported. DOT: ODOT District construction office receives real-time visibility via Public Dashboard.

Conditional Caveat

The daily contractor documentation requirement is conditional on a Worksite Traffic Control Supervisor being specified in the contract documents. ODOT specifies WTS on most projects of meaningful size. For projects without a specified WTS, Section 614 still requires contractor TC maintenance but daily-documentation specifically applies when WTS is required.

Tier B States — Likely Spec-Binding (Pending Verification)

These 9 states have spec sections identified with strong evidence of contract-binding daily TC documentation, but the exact clause text needs direct PDF page read to fully lock the citation as Tier A.

Vermont

Strict Tier: B | Broader Tier: C | Spec Year: 2024

Citation: Section 641 (Traffic Control)

Source: VTrans 2024 Standard Specifications

Requirement

Section 641 governs TC at p. 6-164. Earlier (2001) GSP language required Contractor to conduct daily inspections of daytime/nighttime TC operations/devices. Specific 2024 clause text needs direct PDF review.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the daily inspection records called for by Section 641. PDF Diary Generation supports VTrans documentation requirements.

DTCD Adds Beyond the Requirement

• Auto-Capture Signs and AI safety analysis automate deficiency identification
• CWZ 1.0 feed publishes to VTrans 511 traveler information
• Public Dashboard provides VTrans real-time visibility
• Multi-Format Export supports VTrans inspection report formats

Note: PDF read of Section 641 in 2024 spec book recommended to lock the exact clause language DTCD addresses.

Colorado

Strict Tier: B | Broader Tier: A | Spec Year: 2025

Citation: Section 630.10/630.11 (TCS requirements)

Source: CDOT 2025 Construction Specifications

Requirement

Section 630.11 binds Contractor to designate certified Traffic Control Supervisor. CDOT TCS Endorsement + ATSSA TCS Certification required (CDOT or approved vendors, 2-day training + exam + in-field hours).

DTCD Satisfies

Daily Entries + PDF Diary Generation produce the daily diary CDOT Construction Manual implements. Section 630.11 TCS designation and certification tracked via Certification Management. Personnel Tracking documents TCS presence on-site.

DTCD Adds Beyond the Requirement

• AI safety analysis identifies compliance issues automatically
• CWZ 1.0 feed publishes to CDOT COtrip system
• Auto-Capture Signs automates device documentation
• Public Dashboard provides CDOT region engineers real-time visibility
• Detour Route Mapping handles MHT/TMP detour documentation

Note: "Daily diary submitted within 24 hours" language from older CDOT documentation has not been verified in current Section 630 — DTCD can satisfy whichever interpretation CDOT specifies.

Virginia

Strict Tier: B | Broader Tier: A | Spec Year: 2020

Citation: Section 105.14 (WZTC Accreditation) + Section 512 (Maintaining Traffic) + project Special Provisions + VDOT LAP Manual Chapter 13

Source: VDOT 2020 Road and Bridge Specifications

Supporting source (verified): VDOT LAP Manual Chapter 13 — Project Delivery (Construction Administration)

Requirement

VDOT LAP Manual Chapter 13 (verified): "A daily diary of project activities must be kept for all projects and made available for VDOT review on all federal aid projects or projects to be maintained by VDOT."

This is a Locally Administered Projects Manual provision binding on LAP contracts and federal-aid projects. Section 105.14 requires accredited Basic/Intermediate WZTC personnel. Project SP requires TCS to maintain a project work zone TC diary in a bound book with payment consequences when incorporated.

DTCD Satisfies

Daily Entries + PDF Diary Generation produce the "daily diary of project activities" required by VDOT LAP Manual Chapter 13 for federal-aid and VDOT-maintained projects, and the "project work zone traffic control diary in a bound book" required by VDOT Section 512 SP (when incorporated). PDF/A archival-quality export with metadata replaces the bound paper book with a stronger record. Personnel Tracking documents accredited WZTC personnel.

DTCD Adds Beyond the Requirement

• Digital diary with photo evidence, GPS, and timestamps exceeds the "bound book" format
• CWZ 1.0 feed publishes to VDOT's 511 system
• Auto-Capture Signs automates device documentation
• AI safety analysis identifies deficiencies

Note: LAP Manual Ch. 13 daily diary applies to federal-aid projects and VDOT-maintained projects (broad scope). Section 512 SP language is project-specific. Daily-doc clause exists at LAP/Federal-aid level even if not in Section 512 itself.

Illinois

Strict Tier: B | Broader Tier: A | Spec Year: 2022

Citation: Project Special Provision (BDE / Recurring Special Provision)

Source: IDOT eplan example BDE SP

Requirement

Illinois project SPs require maintaining a project traffic control diary as part of Department records.

DTCD Satisfies

Daily Entries + PDF Diary Generation produce the "project traffic control diary" required by IDOT BDE/Recurring SP. Multi-Format Export produces IDOT-compatible documentation as part of Department records. Personnel Tracking documents TCS presence.

DTCD Adds Beyond the Requirement

• Photo evidence with GPS and timestamps produces a stronger record than IDOT inspector's CMMS Diary
• CWZ 1.0 feed publishes to IDOT's data exchange
• Auto-Capture Signs and AI safety analysis automate documentation
• Public Dashboard gives IDOT region engineers real-time visibility

Note: Verify whether BDE SP is recurring/statewide vs. project-specific.

Indiana

Strict Tier: B | Broader Tier: A | Spec Year: 2026

Citation: Section 801 (Traffic Controls for Construction and Maintenance) — referenced via INDOT GIFE Section 2.8

Source: INDOT 2026 Section 800

Requirement

INDOT GIFE Section 2.8: CWTS "is required to keep a daily record of the total number and location of signs displayed, using the roadway reference system, the area where each worksite speed limit is established, and the times they are established." GIFE references Section 801 as the underlying spec basis.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the daily record CWTS is required to keep per INDOT GIFE Section 2.8 (referencing Section 801 of Standard Specifications). Certification Management tracks INDOT-approved CWTS certification. Personnel Tracking documents CWTS presence.

DTCD Adds Beyond the Requirement

• AI-powered MUTCD sign recognition automates the "total number and location of signs displayed" requirement — daily record generated automatically rather than manually
• CWZ 1.0 feed publishes to INDOT TrafficWise system
• Auto-Capture Signs and AI safety analysis automate documentation
• Public Dashboard provides INDOT real-time visibility

Minnesota

Strict Tier: B | Broader Tier: A | Spec Year: 2020 + SP 2563 + TM 22-08-T-02

Citation: Traffic Control Special Provision 2563 + Technical Memorandum 22-08-T-02

Source: MnDOT Pre-letting Specs

Requirement

MnDOT TM 22-08-T-02: "As stated in CFR Title 23 Part 630, Subpart J, the road authority and the contractor shall each designate a trained person, at the project level, who has the responsibility and sufficient authority for implementing the TMP."

MnDOT TCS 2-day course is "designed to fulfill the language contained in MnDOT's Traffic Control Supervisor Special Provision 2563." Local agency adoptions of MnDOT specs (Bloomington, St. Paul) explicitly require: "The Contractor shall inspect, on a daily basis, all traffic control devices..."

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the daily inspection and daily log required by MnDOT TC SP 2563. Certification Management tracks MnDOT TCS Certification (5-year recert).

DTCD Adds Beyond the Requirement

• AI safety analysis automates deficiency identification — exceeds the manual SP 2563 inspection requirement
• CWZ 1.0 feed publishes to MnDOT 511 system
• Detour Route Mapping handles TMP changes that SP 2563 requires marked up

Oklahoma

Strict Tier: B | Broader Tier: B | Spec Year: 2019

Citation: Section 880 family (Construction Zone Traffic Control)

Source: ODOT 2019 Specifications

Requirement

ODOT specs require certified observer for traffic-control surveillance and require maintaining the log of devices until completion/acceptance.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the device log required by ODOT Section 880 family "maintained until completion/acceptance." Auto-Capture Signs automates device-by-device logging. Personnel Tracking documents certified observer presence.

DTCD Adds Beyond the Requirement

• AI-powered MUTCD sign recognition automates the device log automatically
• CWZ 1.0 feed publishes to ODOT's data exchange
• AI safety analysis identifies compliance issues
• Public Dashboard provides ODOT real-time visibility

Georgia

Strict Tier: B | Broader Tier: A | Spec Year: 2021

Citation: Section 150 Special Provision (Traffic Control) — WTCS duties

Source: GDOT Section 150 SP

Requirement

GDOT Section 150 SP: "The WTCS shall perform inspections, at a minimum once a month, to ensure that traffic control is maintained. For all interstate and limited access highways, the WTCS shall perform, as a minimum, weekly traffic control inspections. The inspections shall be reported to the Engineer on a TC-1 report."

AND: "The WTCS shall inspect the activity area daily to ensure that effective pedestrian TTC is being maintained. The inspection of TTC for pedestrian traffic shall be included as part of the TC-1 report."

Daily clause is narrowly scoped to pedestrian TTC; full daily TC inspection is weekly/monthly.

DTCD Satisfies

Daily Entries + Smart Photo Capture produce the daily pedestrian TTC inspection required by GDOT Section 150 SP, with weekly/monthly inspection of all TC for interstates and limited access highways. Multi-Format Export produces TC-1 report format. Personnel Tracking documents WTCS presence; Certification Management tracks ATSSA or NSC certification.

DTCD Adds Beyond the Requirement

• AI safety analysis automates pedestrian TTC compliance identification
• Daily Reminders auto-schedules the daily pedestrian + weekly/monthly all-TC inspection cadence
• CWZ 1.0 feed publishes to GDOT 511 system
• Public Dashboard provides GDOT region engineers real-time visibility into Section 150 compliance

Tier C States — Dual-Market Positioning

These 28 states have inspector-side daily TC documentation in non-contractual sources (Construction Manuals, EPGs, inspector forms, QA checklists). DTCD positions for dual-market use:

1. Contractor positioning: Volunteer documentation that supports the inspector's workflow
2. State DOT positioning: Adopt DTCD for inspector use directly — replaces paper DWRs and project diaries

Generic DTCD Mapping for Tier C States

DTCD Satisfies: Daily Entries, Smart Photo Capture, and PDF Diary Generation produce contractor-side documentation. Certification Management tracks state-required TC personnel certifications. Multi-Format Export supports state inspection report formats.

DTCD Adds Beyond the Requirement: Photo evidence with GPS and timestamps exceeds inspector-side paper documentation. CWZ 1.0 feed publishes to state 511/data exchange systems. Auto-Capture Signs and AI safety analysis automate documentation. Public Dashboard enables potential state DOT adoption for inspector use.

Audience: DOT-primary positioning. The state inspector currently bears daily TC documentation burden via DWR/checklist. DTCD enables contractor to volunteer documentation that supports inspector work, OR state DOT can adopt DTCD for inspector use directly.

Tier D — Hawaii

Spec Year: 2005 | Citation: Section 645 (Work Zone Traffic Control)

After multiple deep searches, no daily Contractor TC documentation clause located in HDOT Standard Specs. Section 645 requires furnishing, installing, maintaining barricades/signs/cones. TTCP submittals required but not a daily diary or daily inspection report.

This is the cleanest "no clause located" case across all 50 states.

DTCD positioning: federal mandate floor (23 CFR 630.1108(f) pay items, 23 CFR 630.1008(c) field observations) still applies; HDOT can adopt DTCD for inspector use to satisfy federal monitoring obligations even without state-level spec language.

DTCD Capability × Requirement Matrix

Defensible External Claims

High-Stakes Written Claims (sales contracts, M Street pitch, RFP responses)

"DTCD addresses spec-binding daily traffic control documentation requirements in 13 verified states (Iowa, Wyoming, Washington, Oregon, Florida, Texas, Louisiana, Delaware, Maryland, Mississippi, Arkansas, Kentucky, Ohio), with 8 additional states having likely spec-binding requirements pending verification (Colorado, Georgia, Illinois, Indiana, Minnesota, Oklahoma, Vermont, Virginia)."

Federal-Anchor Claims (universal, all 50 states)

"Under 23 CFR 630.1108(f), every federal-aid project — which is essentially every state DOT highway construction project — is federally required to include Temporary Traffic Control pay item provisions in the contract."

"Under 23 CFR 630.1008(c), every state DOT is federally obligated to use field observations and operational data to monitor work zones."

"Under 23 CFR 630.1008(d), every state DOT is federally required to ensure all personnel involved in work zone traffic control are trained — which is why all 50 states have certified TC personnel requirements (TCT, TCS, WTCS, or equivalent role)."

DTCD Compliance Stack Claim

"DTCD's compliance stack — CWZ 1.0, MUTCD, PDF/A, ISO 8601, KML — directly maps to the federal regulations that apply to every state DOT highway construction contract."

What NOT to Claim

• Do not claim "all 50 states require a daily traffic control diary" — overstates the case; only 12 are verified, 9 likely
• Do not claim "all 50 states require certified ATSSA TCT" — only a few states (Iowa, Utah, Colorado) explicitly require TCT specifically; most states certify the supervisor role (TCS/WTCS)
• Do not claim the CFR requires DTCD or any specific software product — accurate framing is "DTCD is one way to satisfy the federal-state-contract chain efficiently"
• Do not claim active CWZ 1.0 publication to specific state systems beyond Iowa Real-Time Network without confirming integration is operational

TC Personnel Certification — All 50 States

Bottom line: ALL 50 STATES require certified Traffic Control personnel.

Federal driver: 23 CFR 630.1008(d) mandates that "States SHALL require that personnel involved in development, design, implementation, operation, inspection, and enforcement of WZ TM and TC be trained."

States vary in: (1) what role they certify (TCT, TCS, WTCS, WTS, etc.), (2) which certifying body they accept, and (3) whether the requirement is in the spec, special provision, or both.

Role Terminology

• TCT (Traffic Control Technician) — Hands-on placement and maintenance role. Used by Iowa (Section 2528), Utah (Section 01554 §1.9), Colorado (PD 1512.1 endorsement). ATSSA-certified.
• TCS (Traffic Control Supervisor) — Most common term; oversees TCT operations and project-level TC. Used by WA, OR, CO, IL, MN, MS, OK, AR, ME, KY (Coordinator), MD (TCM), and ~20 others.
• WTCS / WTS (Worksite Traffic Control Supervisor / Worksite Traffic Supervisor) — Equivalent to TCS, different states use different naming. Used by GA (WTCS), IN (CWTS), OH (WTCS), AK (WTS), TN (WTS), FL (WTS).
• Traffic Control Coordinator — Used by NJ (TCC), KY (Traffic Coordinator).
• Qualified Work Zone Supervisor + Work Zone Installer — Used by NC (Article 1101-13).
• PTCI (Project Traffic Control Inspector) — Department role, not contractor. Used by Alabama.

Primary Certifying Bodies

• ATSSA (American Traffic Safety Services Association) — Accepted in all 50 states for TCT, TCS, and Flagger certifications. Most widely recognized.
• IMSA (International Municipal Signal Association) — Work Zone Traffic Safety Specialist accepted in many states.
• NSC (National Safety Council) — Accepted in some states (GA, RI, others).
• State-specific certifications: Caltrans-certified TCT, MnDOT 2-day TCS course, SD AGC-DOT TCS Training, MDOT SHA TTCMC, VDOT WZTC accreditation, University of Tennessee NHI TTC training, WSDOT card.

DTCD Certification Management

DTCD's Certification Management capability tracks ATSSA, IMSA, NSC, and state-specific certifications per personnel. This satisfies the 23 CFR 630.1008(d) trained-personnel requirement across all 50 states with a single workflow.

Methodology — How Tiering Was Determined

Strict Tier Bar (DTCD daily-doc bar)

Counts only contract-binding language requiring the contractor (not the inspector) to perform daily traffic control documentation. Construction Manuals, EPGs, inspector forms, QA checklists used by Department/inspectors, and form-only references do NOT count.

Counts:

• Standard Specifications
• Supplemental Specifications
• Special Provisions formally incorporated into a contract
• Special Provision Copied Notes (SPCNs)
• Standard Plans / Standard Drawings (when incorporated by spec section)
• Project General Notes (when incorporated via spec items)
• State contracting systems (e.g., ARDOT Doc Express Contractor Submittal drawer)

Does NOT count:

• Construction Manuals (often explicitly disclaimed as non-contractual)
• Engineering Policy Guides / wikis
• Inspector job guides / inspection guidelists
• Documentation Manuals
• Training materials
• LPA flowcharts and processes
• Form references where only the form is named (the spec that requires the form is what counts)
• QA Review Checklists used by Department/inspectors (e.g., PennDOT CS-901)
• FHWA best-practice docs and external sources
• TMP templates (binding only when called out for a specific TMP level)

Tier Definitions

• Tier A: Spec-binding (verified). Spec section identified and exact daily-TC-documentation clause confirmed.
• Tier B: Spec-binding (likely). Spec section identified with strong evidence; exact clause text needs PDF page read to lock.
• Tier C: Incorporated reference / non-contractual. Daily TC documentation appears only in non-contractual sources.
• Tier D: No clause located after extensive search.

Broader Tier Bar (Alternative Reference)

A separate "broader bar" classification (from the deep-dive document referenced in the Bar Comparison) counts any spec/pay/cert/inspection contract obligation that DTCD can map to. Under that bar, all 50 states have some path to DTCD use. This is the basis for the universal federal-mandate claim under 23 CFR 630.1108(f).

Contact

Matt Miller, CPM Founder, PurposeBuilt Systems, LLC SBA-certified Service-Disabled Veteran-Owned Small Business (SDVOSB) Clive, Iowa UEI: RXHKC1RKZH65 | EIN: 39-4688990 | DUNS: 141073953 | CAGE: 16VC8