Everyone Wants Work-Zone Data. Almost Nobody Captures It Where It's Created.

Walk the industry today and there's no shortage of work-zone technology. WZDx feed tools. Agency dashboards. Crowdsourced traffic apps guessing where the cones are. Connected arrow boards phoning home. Inspector systems generating Daily Work Reports back at the office. Every one of them solves a real slice of the problem.

But look closely and they share one blind spot: they consume or infer work-zone data — they don't capture it where the work happens.

• The crowdsourced map guesses a lane is closed because traffic slowed. It doesn't know where the taper starts, which lane, or whether the crew is still there.
• The 511 feed is only as current as whatever a person remembered to update.
• The connected device knows its own status — not the closure it belongs to.
• The inspector's DWR and the contractor's diary are two different records that rarely line up in time or evidence.
• And the paper diary — the one contemporaneous, legally significant record of what actually happened — never makes it into any of them.

So we've built an entire ecosystem downstream, hungry for accurate work-zone data, on top of a source that mostly doesn't exist in usable form. You can't dashboard, publish, or feed a connected vehicle what was never captured cleanly in the first place. That isn't a feature gap — it's a foundation gap.

DTCD starts at the source: the crew

When the person setting up the work zone captures it once — GPS-tagged, photo-backed, time-stamped, with the devices and personnel — that single record becomes everything downstream needs:

• a DOT-ready daily diary or inspection report — the paperwork they already owe;
• a live WZDx / CWZ feed the moment the closure goes active — the same data 511s, maps, and connected-vehicle platforms are trying to source;
• defensible backup for pay items and disputes;
• and real-time visibility for the agency, without a windshield trip.

Same field action. One capture. Every output.

I'm not knocking the rest of the stack — a lot of it is genuinely good, and the feeds we publish are meant to feed it. Maps, TMCs, fleets, and connected-vehicle systems are the display and decision layer. But they're only as trustworthy as their source. DTCD is that source — captured by the people who actually deploy the devices, in the standards the ecosystem already runs on.

The work zone nobody else can see

DTCD also captures the one thing nothing else does: moving operations. Striping, sweeping, mowing, crack-sealing — work zones that travel down the road at walking speed, invisible to every planning system and crowdsource feed, and among the most dangerous hazards out there. A crew-carried app is the only thing that can publish them live — current position, projected route, workers present.

For the contractor, this isn't new work — it's the diary they already keep, done in one tap and turned into a stronger record. For the DOT, it's oversight and DWR modernization without ripping out a statewide system. For everyone downstream, it's finally a clean source of truth.

The work zone has been generating the data all along. We just stopped letting it die on the clipboard.

— Matthew Miller, Founder, PurposeBuilt Systems · U.S. Navy veteran