DTCD captures structured, GPS-tagged, photo-supported work zone documentation in the field — and turns it into the live data your dashboards, 511 system, traffic management center, and connected-vehicle partners already expect. Used by contractors. Useful to you.
Nearly every state DOT requires some form of daily traffic-control record from its contractors. Most receive that record as paper, scanned PDFs, or fragmented spreadsheets — too late, too late-formatted, and too disconnected to be useful for real-time visibility, corridor coordination, or audit.
DTCD changes the input format without requiring you to change anything. Contractors keep documenting the same things they already document. The output becomes:
WZDx v4.2 and CWZ v1.0 feeds publish automatically as soon as a contractor publishes a closure. Ingest into your 511 system or work zone dashboard with no integration burden on the contractor.
Every diary entry is tied to GPS coordinates and timestamped photos. Inspectors and engineers can verify field conditions, MUTCD compliance, and deficiency corrections without driving to the site.
DTCD's PDF output cites the controlling state spec (Caltrans CEM-2210, PennDOT CS-901, etc.) by name. Inspectors receive the format they expect.
Public agency dashboard shows live closures across all DTCD users in your jurisdiction. Compare planned vs actual setup, monitor active work zones, see deficiency trends.
Every closure carries a GPS-tagged, photo-backed, time-stamped record of what was placed, changed, and removed — an auditable history for compliance reporting, contested-case proceedings, or post-incident review.
Field-level data is the missing ingredient for connected corridor projects. DTCD provides the contractor-side feed that integrates with your existing TMC and CV/V2X infrastructure.
DTCD directly supports several FHWA Every Day Counts Round 8 priorities (2026–2027):
EDC-8’s Subsurface Utility Engineering (SUE) track is covered by DTCD’s sister app, Digital ROW Utilities (DRU) — field-grade locator-mark, potholing, GPR, and as-built capture for utility-impact surveys. EDC-8’s UAS 2.0 track is on the roadmap: DTCD aerial-orthomosaic overlay and DRU drone-DXF import for planned-vs-as-built compare.
Free for agencies: the public WZDx feed and a simple single-county closure view. Everything above that — multi-county / statewide visibility, work-zone photos & AI compliance review, and contractor oversight — is licensed per seat plus a county-coverage tier.
The public WZDx feed plus a read-only single-county closure map — view active work zones for one county. For cities, counties, and small agencies getting started.
Up to 5 counties, real-time updates, advanced map features, API access. Includes work-zone photos, AI compliance review, and contractor oversight.
All counties in one state. Full feature set, API access, priority support, and jurisdiction-wide contractor oversight.
All 50 states, all counties, full API, multi-state reporting. For federal agencies and national operators.
State-DOT enterprise licenses, integration scoping, custom WZDx ingest pipelines, on-premise data residency, federal procurement vehicles.
DTCD is licensed per user on the same published plans available to every organization — see standard pricing. Agency dashboards add a county-coverage tier on top of the per-seat licenses. There’s no separate “agency price” to get started; enterprise and statewide deployments are scoped individually.
The same published per-seat plans everyone uses, plus a county-coverage tier for agency dashboards. Start today — no custom contract required.
Statewide rollouts, API / WZDx integration, on-premise data residency, named SLAs, or SDVOSB set-asides: reach out with your user count, county / coverage scope, and integration needs, and we’ll quote through your procurement vehicle.
Enterprise and statewide pricing is established by negotiation through standard procurement vehicles. Iowa DOT and Iowa-regulated entities are subject to the Iowa Regulatory Exclusion (Form 105023). Whether an 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; uncertain organizations should contact those agencies directly before procurement engagement.
Independence notice: PurposeBuilt Systems LLC is independent of and not affiliated with the Iowa Department of Transportation or any other governmental agency. References to state DOT specifications are for informational coverage purposes only and do not imply endorsement.
PurposeBuilt Systems LLC is a Service-Disabled Veteran-Owned Small Business (SDVOSB), eligible for federal SDVOSB set-asides and many state veteran-business preferences.
DTCD runs on Supabase (managed PostgreSQL, authentication, and storage on AWS, US region) and Cloudflare (web hosting and edge compute), with TLS 1.2+ in transit and AES-256 encryption at rest. Our underlying infrastructure providers — AWS, Cloudflare, and Supabase — maintain their own SOC 2 Type II attestations. An append-only, tamper-evident audit log (SHA-256 hash-chained) records closure and certification changes, with independently verifiable integrity. Custom data residency available under enterprise agreement.
DTCD does not currently sell or share personal information for monetary or other valuable consideration as those terms are defined under CCPA/CPRA. Full privacy policy →
30-minute walkthrough showing DTCD's WZDx feed, contractor-side workflow, and agency dashboard. We'll provide sample feeds and a 50-state coverage brief tailored to your jurisdiction.
Request Demo View 50-State CoverageDTCD’s 50-state compliance analysis classifies every state DOT into four tiers based on the strength of their daily traffic-control documentation requirements. 13 states have verified contract-binding spec language requiring the contractor to perform daily TC documentation; 8 more are likely-binding pending PDF page verification. Every claim is anchored to a specific spec citation, federal CFR section, or documented DTCD capability.
PurposeBuilt’s field-grade apps turn site documentation into structured, usable infrastructure data — directly supporting several FHWA EDC-8 priorities (2026–2027 cycle). DTCD covers the work-zone tracks; DRU (Digital ROW Utilities) covers the subsurface-utility track:
Digital photos, timestamps, inspections, deficiency tracking, and corrective-action records document nighttime setups when visibility, risk, and documentation challenges are highest. DTCD.
Field-level closure and traffic-control data supports WZDx, 511, dashboards, traffic management centers, and multi-state corridor visibility. DTCD + DRU — utility contractors doing ROW work generate their own maintenance of traffic that is rarely federated upstream; the paired apps close that agency blind spot.
Traffic-control diaries, inspections, photos, device records, and payment support become part of the digital project record. DTCD + DRU contribute paired work-zone and ROW-utility evidence into the same delivery file.
Alternative delivery (DB, CMGC, P3) requires defensible field-condition records. DTCD + DRU provide the digital evidence on both the work-zone and ROW-utility sides of the same project.
Digital ROW Utilities (DRU) captures field-grade SUE Quality Level data — locator marks, potholing, GPR readings, locator confidence, and as-built positions — the digital evidence EDC-8’s SUE track is asking owners and contractors to put in the project record.
Drone-captured deliverables become first-class inputs across the portfolio: DTCD aerial-orthomosaic overlay (drop a georeferenced drone image over a closure map for as-deployed work-zone visualization) and DRU drone-DXF import (planned-vs-as-built ROW + utility geometry from aerial photogrammetry). Targets EDC-8’s UAS 2.0 track for innovative infrastructure management.
Coverage and compliance claims on this page are backed by primary state-DOT, federal, and industry sources.