What happens when traffic-control documentation becomes evidence?
We reviewed 105 published judicial matters involving temporary traffic control, work-zone conditions, inspection records, contractor responsibility, and related liability — then verified every citation against the opinion it came from.
43 jurisdiction labels represented. Decisions span 1950–2026. All 105 source links resolved to a genuine court opinion or order; three case captions were corrected during the audit; no rows were removed as irrelevant. Audit completed 2026-07-28.
It is a researched inventory of published, publicly accessible U.S. judicial decisions and orders — not every lawsuit filed, every trial-level matter, every confidential settlement, or every claim. It does not say that 105 crashes were caused by missing traffic-control logs, and it is not a legal opinion on liability in any matter. What it does show is how often, and how directly, the question “what was actually in place, and who can prove it?” becomes the disputed issue.
How the matters are classified
Every row carries one of four evidentiary-relevance classes. The classification is what keeps the top-line number honest: a coverage appeal arising from a crash already counted is a D, not a second crash.
A — Direct documentation evidence
The published opinion expressly discusses a diary, daily report, traffic-control inspection report, project diary, or equivalent contemporaneous field record.
11 of 105 matters
B — Strong DTCD relevance
Traffic-control configuration, device placement, inspection, plan or MUTCD compliance, photographs, or a time-specific field condition was materially disputed.
79 of 105 matters
C — General work-zone liability
The matter shows work-zone exposure, contractor duty, or warning obligations, but a field record would have played a more indirect role.
7 of 105 matters
D — Related proceeding
A coverage, indemnity, or later appellate proceeding arising from an incident already counted elsewhere. Never counted as a separate crash.
8 of 105 matters
Collapsing 6 known related-proceeding groups — an underlying tort case and its later coverage, indemnity, or appellate proceeding — brings 105 published matters down to approximately 99 unique underlying incidents or disputes.
The questions that appear after an incident
Across these matters, the same short list of factual questions decides who carries the exposure. They are almost never answered from the plan set. They are answered — or not answered — from whatever the crew wrote down that day.
- Was the sign, barricade, signal cover, or channelizing device present at the relevant time?
- What were its location, orientation, sequence, spacing, and visibility?
- Who inspected the location, and when?
- What deficiency was observed, how severe was it, and who was assigned to correct it?
- When was corrective action completed, and what evidence verifies the closure?
- Which contractor or agency controlled the location at that moment?
- Can the record be produced quickly, in a readable and auditable format?
DTCD is built to answer those questions from contemporaneous field records: GPS-anchored device placement, timestamped photographs, inspection findings tied to a specific location, corrective actions with a verified closure, and an export that can be produced on demand.
The 11 direct documentation matters
In these matters the opinion expressly discusses a diary, daily report, project diary, or traffic-control inspection record. They cut both ways — good records have defeated claims, and vague ones have kept claims alive.
Brown v. Whitaker Contracting Corp.
Records at issue. County daily traffic-control inspection reports and project diary
How the record mattered. Inspection reports noted a general construction sign but did not record a low-shoulder sign. The county representative could not confirm the sign existed on the crash date.
Reported posture. Summary judgment for contractor reversed; claim continued.
What it means for a field record. Missing or nonspecific entries weakened proof that the required warning was actually present.
Read the opinion →Mississippi Transportation Commission v. Montgomery
Records at issue. MDOT project diary and contractor repair records
How the record mattered. Diary documented notice of a pothole, later vaguely stated repairs were made, and then recorded 'NO WORK' on a day the agency claimed emergency repairs occurred. Contractor had no matching work record.
Reported posture. Immunity and notice issues litigated; conflicting records were central to the factual dispute.
What it means for a field record. A vague or contradictory log can undermine claims that a known hazard was repaired.
Read the opinion →Schmidt v. Washington Contractors Group
Records at issue. Construction diary, foreman's daily diaries, and traffic-control notes
How the record mattered. Records were used to estimate the distance from a BUMP sign to the roadway transition. Conflicting interpretations created a factual issue regarding sign placement.
Reported posture. Summary judgment reversed and case remanded.
What it means for a field record. Mapped, time-stamped device placement could have resolved the exact-distance dispute.
Read the opinion →Paul Craig Jordan v. Jerry D. Sweetser, Inc.
Records at issue. Daily diary of inspections and traffic-control inspection reports
How the record mattered. Resident engineer testified that daily inspections showed no warning-device deficiencies and compliance with the project plans. Plaintiff also alleged falsification of inspection reports.
Reported posture. Directed verdict for contractor affirmed.
What it means for a field record. Contemporaneous inspection records helped the contractor establish compliance and defeat causation allegations.
Read the opinion →Price Construction, Inc. v. Castillo
Records at issue. TxDOT traffic-control inspection reports
How the record mattered. Numerous inspection reports cited deficiencies elsewhere, but the records did not establish actual knowledge of the specific conditions alleged to have caused the collision. A post-crash inspection found required devices present.
Reported posture. Appellate court found insufficient evidence of actual knowledge; later reviewed by Texas Supreme Court.
What it means for a field record. Structured location-specific deficiencies are more useful than broad inspection findings.
Read the opinion →Minerva Castillo v. Price Construction, Inc.
Records at issue. TxDOT inspection reports documenting traffic-control deficiencies
How the record mattered. The Texas Supreme Court evaluated whether prior inspection citations gave the contractor actual knowledge of the precise dangerous condition alleged by the plaintiffs.
Reported posture. Texas Supreme Court held the cited reports did not show actual knowledge of the specific alleged condition.
What it means for a field record. Logs must tie each deficiency to exact location, device, condition, notice, and correction.
Read the opinion →Rondell Fagan et al. v. Jennifer Sees et al.
Records at issue. TxDOT inspector diary, correspondence, change orders and accident history
How the record mattered. At least nine crashes occurred in the work area. Diary and project records were used to track discussions, proposed shoulder modifications, notice, and decisions.
Reported posture. Denial of official-immunity summary judgment was appealed; factual and discretionary-duty issues continued.
What it means for a field record. An auditable sequence of observed hazards, recurring incidents, escalation, and corrective decisions is essential.
Read the opinion →Smith v. Wilson
Records at issue. Resident engineer diary / work report
How the record mattered. Diary established when the contractor completed work, was released, removed equipment, and ceased control of the area before the crash.
Reported posture. Judgment against contractor reversed; directed judgment ordered for contractor.
What it means for a field record. Reliable control-transfer and completion records can prevent liability from attaching to the wrong party.
Read the opinion →Canfield v. State of New York
Records at issue. Engineer daily project diary, construction records and inspection evidence
How the record mattered. Diary documented discussions about retaining, extending, and selecting the guide rail. The court separately examined installation deficiencies such as missing bolts and incorrect height.
Reported posture. Liability allocated; damages trial followed.
What it means for a field record. DTCD-style records should document both the approved decision and the field-installed condition.
Read the opinion →Wadsworth v. State of New York
Records at issue. Daily inspection reports, inspector drawing and photographs
How the record mattered. Daily reports and field documentation were used to establish lane widths, barrier placement, taper geometry, and sign compliance.
Reported posture. Court evaluated design and placement evidence in determining negligence.
What it means for a field record. Geospatial geometry and photographs can preserve exact temporary-barrier configuration.
Read the opinion →Jeffrey B. Hodges v. Attala County
Records at issue. Weekly traffic-control device inspection reports
How the record mattered. Multiple weekly reports stated that barricades were damaged and needed replacement.
Reported posture. Notice and governmental-immunity issues litigated.
What it means for a field record. Repeated unresolved deficiencies create a clear notice trail; closure tracking is critical.
Read the opinion →Recurring themes
| Theme | Core point | What a field record has to do about it |
|---|---|---|
| The sign was supposed to be there—but was it? | Plans do not prove field conditions on the crash date. | Timestamped, geotagged photographs and mapped device placement. |
| The repair supposedly happened—but the diary disagreed | Contradictory or vague entries can undermine notice and repair defenses. | Corrective-action workflow with before/after proof and immutable audit history. |
| Good logs can win cases | Documentation can support compliance, control-transfer, and lack-of-causation defenses. | Searchable inspection history and specification-linked checklists. |
| Repeated deficiencies create notice | Unresolved inspection findings can establish knowledge and escalation failures. | Automatic escalation, aging, assignment, and closure verification. |
| Location specificity matters | General deficiencies may not prove knowledge of the precise crash-causing condition. | Every observation tied to a GPS point, device ID, lane, station, and photograph. |
| Design decision versus field execution | An agency may document a reasonable design but still face installation claims. | Separate approval records from as-installed verification. |
How often the exposure occurs
Published appellate decisions are the visible tip. Most claims settle, resolve at the trial level, or never leave an insurer's file. The underlying crash volume is not in dispute:
| Measure | What it counts | Source |
|---|---|---|
| 42,094 | people injured in work-zone crashes | United States, 2024 (National Safety Council) |
| 850 | people killed in work-zone crashes | United States, 2024 (National Safety Council) |
| 891 | work-zone fatalities | United States, 2022 (FHWA) |
| 246 | fatal work-zone crashes involving a commercial motor vehicle | United States, 2022 (FHWA) |
We do not publish a percentage of work-zone crashes that become lawsuits. No national litigation denominator or standardized claim database exists to support one, so we do not estimate it.
What digital documentation changes
| The evidentiary problem | On paper | In DTCD |
|---|---|---|
| Was the device there? | A checkbox, if it was checked | GPS-anchored device entry with a timestamped photograph |
| Where exactly? | “Approximately 500 feet” | A coordinate, on a road-snapped map |
| When did it go up, and come down? | Reconstructed from memory | Recorded as it happened, per device |
| Who inspected it? | An initial, sometimes | Named user, timestamped, with the finding attached |
| Was the deficiency corrected? | Often unresolved in the file | Corrective action with assignment and verified closure |
| Who controlled the location? | Contested years later | Closure ownership and completion recorded contemporaneously |
| Can you produce it? | Boxes, or a former employee's truck | Searchable export, plus a tamper-evident audit trail |
Methodology and limitations
- Scope: published and web-accessible U.S. decisions located through targeted legal research. Not an exhaustive census of filed cases, and settlements are systematically invisible.
- Every row records a primary source URL, a verification status, and a confidence rating. All 105 links resolved; three captions were corrected against the cited opinion.
- Classification is an evidentiary-relevance framework, not a legal conclusion. A Class A designation does not mean the record caused or prevented the incident.
- The 99-incident figure is an estimate based on 6 identified related-proceeding groups. Additional overlaps may exist.
- Nothing here is legal advice. If you are in a dispute, talk to your counsel — not to a vendor's web page.
Get the full report
The complete write-up — methodology, the 11 direct-documentation matters, the recurring themes, five case studies, and the limitations in full — is a free PDF. No email required.