The Traffic-Control Log May Be the Most Important Document You Create on a Highway Project

A traffic-control diary is treated as routine paperwork right up until the moment it becomes evidence. Then every entry, omission, timestamp, inspection, and photograph can be read aloud in a deposition. There is no public master list of every lawsuit that turned on a work-zone log — many settle quietly or live only in county court files — but the published decisions that do exist tell a consistent story. When a motorist, a contractor, and a transportation agency disagree about how a work zone actually appeared on the day of a crash, the record of that work becomes the thing the case is fought over.

A fatality, years of litigation, and one unprovable fact

Start with a case that reached a state supreme court. In Third Coast Services and SpawGlass Civil Construction v. Castaneda, a Texas matter decided in 2025, Pedro Castaneda was killed in a collision at a highway intersection that was under construction. Traffic signals had been installed but were not yet in service, and the parties disputed a single physical fact: whether the signal heads had been properly covered to show they were not yet operational. Notice what the fight was about. Not what the traffic-control plan required — that was known — but what a driver could actually see at that intersection on that day.

The case turned on a statutory contractor-immunity question, and the Texas Supreme Court sent it back for further proceedings rather than declaring a winner — but that immunity is what makes the documentation point sharper, not weaker. Under the Texas statute, a highway contractor is shielded from liability only if it can show it was in compliance with the contract documents governing the condition that caused the harm. The protection exists, but a contractor has to prove it earned it — and contemporaneous records of what was installed, covered, and inspected are exactly how that proof is made. So a field record is not only how a contractor defends what it did; in a state like Texas, it can be how a contractor unlocks the immunity in the first place. Underneath all of it sat one visual fact — whether the signal heads were covered — that no one could establish with certainty years after the crash, precisely what a geotagged, time-stamped photograph is built to capture.

When there is no record of a plan at all

If a disputed record is a problem, a missing one is worse. In Arreguin-Leon v. Hadco Construction, a Utah case, a highway worker was standing on a ladder installing signs along Interstate 15 when a driver veered into the work area and struck the ladder, seriously injuring him. The core of the plaintiff’s case was documentary absence: the evidence showed that no traffic-control plan had been designed by an engineer or approved, and that no protective devices were in place at the site. A jury set the plaintiff’s total damages at roughly $2.9 million and placed 40% of the fault on the contractor — an exposure of about $1.18 million — before an appellate court ordered a new trial over an unrelated evidentiary ruling. The narrow point survives the retrial: when the question is whether a protective plan ever existed, the absence of any documented plan is not a neutral fact.

The sign that was there — until it wasn’t

The point that a setup which existed in the morning can be gone by afternoon is not hypothetical. In White v. Cox Bros. Construction Co., a California road-reconstruction case, a ‘SLOW’ sign mounted on a barricade with an orange flasher normally sat in the center of the highway about fifty feet from the pavement’s edge. At the time of the crash it was lying in the grass at the side of the road — and the contractor’s crews had been off the job on strike for two days. The court affirmed a verdict against the contractor, holding that the duty to maintain the warning signs and the roadway did not pause simply because active work had stopped. A warning device is only as good as its last verified position, and ‘we put it out’ is a very different statement from ‘it was still standing where it belonged when the crash happened.’

A related question is who was responsible in the first place. In Robinson v. Dustrol, Inc., a Nebraska case, a motorcyclist struck an abrupt vertical edge — a ‘mill cut’ — left in a resurfacing zone, and the dispositive problem was that the paperwork never clearly said which contractor was supposed to ramp it: the contract called for ramping but did not state who would do it, and in the ambiguity the contractor prevailed. A field record does not rewrite a contract or resolve a scope dispute — but in a zone with a prime and several subcontractors, it does establish who actually performed each task and when, which is the factual groundwork a responsibility fight is built on. That groundwork is frequently the part nobody can produce.

‘We just followed the plan’ is not the end of it

Contractors sometimes argue they simply built what the agency’s plan specified. Courts have repeatedly held that this is not a complete answer. In Harlan v. APAC-Missouri, a motorcyclist was injured by an uneven lane-height difference in a resurfacing zone. The contractor argued it had no authority to add warning signs beyond the state’s plan. The court disagreed: highway contractors carry a continuing, non-delegable duty to the traveling public, and the contract itself let the contractor add any signs or devices it ‘considers necessary’ to protect the public. A jury put the contractor’s share of the fault at 25% — a $250,000 judgment against it, part of a $1 million award. The lesson for record-keeping is direct — a contractor can be judged on what its crew observed and chose to do, not only on what the plan drew, and being unable to show what it observed is what turns a defensible position into a payment.

The mirror image is Brettman v. Virgil Cook & Son, an Illinois case in which temporary signal heads were mounted higher than the MUTCD’s maximum height. There was no documentation showing that the extra height was a deliberate engineering judgment rather than an installation oversight, and the absence of that record helped push the case past summary judgment and toward a jury. Whether a deviation was a considered decision or a mistake is precisely the kind of thing a contemporaneous field note exists to settle.

A Delaware case, Pavik v. George & Lynch, sharpens the point from a different direction. A resurfacing project’s approved plan called for warning signs during active work hours, but the road surface deteriorated into loose gravel between shifts, and a fatal crash happened off-hours. The court held that following the approved plan did not, by itself, discharge the contractor’s duty to address a foreseeable hazard the plan never contemplated. The record that decides a case like that is not the plan on file — it is the field documentation of what the road actually looked like when no crew was present.

The record cuts both ways — and sometimes it wins

This is not a one-sided argument, and the honest version has to include the cases where documentation protected the people who kept it. In Peterson v. Progressive Contractors, a Missouri case, a vehicle dropped into an uncovered expansion-joint opening on a bridge that was under repair, and a passenger later died of her injuries. The contractors had obtained formal approval to modify the original traffic-control plan, and their job diaries and the resident engineer’s testimony established that they had followed the modified plan. That contemporaneous record was central to the defense, and the verdict in the contractors’ favor was affirmed on appeal. A complete field record is not only a source of liability exposure — it is frequently the strongest evidence a diligent contractor has that it did the job right.

Who knew, and when: the record fixes the timeline

Many highway cases turn less on a single instant than on a sequence — when a hazard appeared, when it was inspected, when a warning went up, and when it was finally corrected. The daily record is what reconstructs that sequence. In Everhardt v. Louisiana DOTD, arising from a crash on an active resurfacing project on Louisiana Highway 46, the project diaries laid out the timeline with uncomfortable precision: the asphalt overlay had been completed, but the permanent edge striping was not applied until eleven days after the accident, the shoulder was not brought to grade until four days after, and no warning signs were present in the interim. Those diary entries were the evidence that established what the road looked like during the window that mattered, and the agency was assigned a share of the fault. A record that timestamps each inspection, condition, and correction is exactly what answers the ‘who knew, and when’ question that so often decides these cases.

The questions a case actually asks

Strip these cases down and the questions that decide them are almost always simple:

• Was the device present?
• Where exactly was it?
• When was it installed, inspected, moved, damaged, or removed?
• What did the crew observe?
• Who was responsible at that time?
• Was a deficiency found, and when was it corrected?
• What would a motorist actually have seen?

A handwritten paper log can assert answers to these. What it usually cannot do is independently prove location, time, visibility, configuration, or that the entry was written when the work happened rather than reconstructed weeks later. That is the difference between an assertion and evidence.

Agencies already treat this as a risk

None of this is DTCD’s theory. The states that own these roads already write the requirement into their specifications. Louisiana requires the traffic-control supervisor to keep the traffic-control diary current on a daily basis, sign each daily entry, and make it available for inspection — with a weekly review alongside the project engineer. Washington folds temporary-traffic-control documentation into the official project record through inspectors’ daily reports and traffic-control reports that are retained for years after the work is done. And Iowa’s construction manual authorizes a price adjustment for failing to keep the traffic-control diary current — an additional 10% of the traffic-control bid item or $500, whichever is greater — assessable repeatedly, even daily, when the diary is not kept up to date.

Read together, those requirements make a single point: the daily traffic-control record is already an obligation, not an optional extra. DTCD does not invent a new administrative burden — it modernizes one that agencies have been enforcing for years, and one the federal floor is making more explicit. Under 23 CFR Part 630, systematic work-zone documentation is a program requirement on federal-aid projects, with the compliance expectation tightening at the end of 2026 (we break that down in the December 2026 documentation deadline). What your state actually names as the deliverable varies — we mapped all fifty back to the federal rule, so you can find your state’s exact requirement here.

What a modern record changes

The value of a digital field record is not that it wins cases. No document does that, and no honest vendor should promise it. The value is narrower and more useful: it turns the questions above from a matter of recollection into a matter of record. The table below maps the litigation problem to the specific thing DTCD captures in the field.

Each of those is a field action a crew already performs, captured once, on site — the closure photographed, located, timestamped, attributed to the person who did the work, and protected by a tamper-evident audit trail. (For the traits that separate a defensible record from a typed recollection, see the companion piece, How to Keep a Work-Zone Record That Holds Up in a Dispute.)

The real cost of the diary

The cost of a traffic-control diary was never the time it takes to fill out. The real cost shows up years later, when a contractor, an inspector, or an agency cannot prove what was present at 2:17 p.m. on the day of a crash. DTCD’s purpose is to close that gap — to turn a recollection into a record of who inspected the work zone, where the devices were, what conditions were observed, what changed, and when corrective action happened. Whether that record ever ends up in a conference room is not the point. The point is that if it does, it is the strongest thing on the table instead of the weakest.

Then weigh that against what the record costs to produce. The exposure in the cases above ran from a $250,000 judgment to seven figures; the record that answers those questions is a field action a crew already performs, captured on a phone for less than $10 a user. If you want to see the shape of a defensible record before changing anything, start with our free daily traffic-control diary template — and the day filling it in by hand starts to feel like the expensive option is the day DTCD earns its keep.

This article is transportation-risk analysis and general information, not legal advice. Cases are summarized from published decisions to illustrate how work-zone records function as evidence; outcomes turn on the specific facts and jurisdiction, and nothing here predicts any result. No documentation tool prevents litigation or guarantees compliance. Consult qualified counsel about your own contracts, agency requirements, and record-keeping.