Doug Marcello
Plaintiff attorneys have a seminar title for your safety data. They call it a treasure trove.
At their conferences and webinars, they teach each other exactly what data trucking companies generate, how to obtain it through discovery, and how to make it admissible at trial. They study your telematics systems, your electronic control modules, your collision avoidance alerts, your driver performance platforms. They know what you have, often better than you do.
The goal of all of this education is straightforward: leverage your own data against you. Take the information you collected to operate more safely and use it to construct the narrative that your company represents a systemic threat to community safety — the Reptile Theory strategy we covered in Part 5 of this series.
The trucking industry’s most common response to this reality has been what I call the Discovery Fallacy.
The Discovery Fallacy
The Discovery Fallacy is the belief that if you don’t look at your data, you won’t have to turn it over. That avoiding analysis is the same as avoiding exposure. That ignorance of your own safety record is a litigation strategy.
It is not. It is the opposite.
The data exists whether you look at it or not. Your telematics system is recording. Your ECM is logging. Your collision avoidance system is generating alerts. Your communication platform is archiving. None of that stops because your safety department decided not to build a formal analysis program.
What the Discovery Fallacy actually produces is the worst possible outcome: plaintiff attorneys discover data you never reviewed, surface patterns you never identified, and present to a jury evidence that your company had warning signals it never acted on. The narrative that creates — the picture of an organization that generates safety data it deliberately ignores — is precisely the systemic indifference argument that Reptile Theory is designed to exploit.
You do not choose whether your data exists. You choose whether you get there first.
The Alternative: The Identify-Analyze-Manage-Enforce Framework
The carriers that have transformed their data from a liability into a defense asset did not do it by generating less data or avoiding analysis. They did it by implementing a systematic approach to their own safety information — one that creates a documented record of organizational competence that defeats the systemic failure narrative before it can be constructed.
The framework has four steps. They are sequential and interdependent. Skipping any one of them produces a partial record that is worse than no record at all.
Step 1: Identify — Know What You Have
The starting point sounds obvious: know what data your operation generates. In practice, many carriers do not have a clear answer to this question until after an accident, when they are working with counsel and accident reconstructionists to determine what records exist and what they contain.
Your data landscape likely includes: telematics systems capturing location, speed, and route data; electronic control module records including hard brakes, rapid deceleration, and engine performance; collision avoidance and lane departure system alerts; dashcam footage, both forward and driver-facing; communication and dispatch records; driver performance and safety scoring data from any platform you use; hours of service and ELD records; drug and alcohol testing records; and training documentation.
Each system generates a different type of record. Each type of record has different preservation implications, different discovery exposure, and different evidentiary potential — for both sides. You cannot manage what you have not identified. The first step is a complete data inventory: what systems are running, what they capture, how long records are retained, and who has access to them.
Conduct this inventory before the accident. After the accident, everything you learn about your data landscape is potentially discoverable and potentially harmful.
Step 2: Analyze — Which Data Relates to Maximum Risks
Once you know what data you have, the second step is understanding what it tells you about your specific operation’s risk profile. This is where many carriers stop — they have the data but they have not translated it into operational intelligence.
Different operations generate different primary risk signals. A carrier running long-haul routes on I-80 through Nebraska is going to see a different leading indicator of crash potential than a carrier making urban deliveries on the George Washington Bridge corridor into New York. Speeding on open highway is a different risk profile than hard braking in dense urban traffic. Know which indicators are most predictive of accident potential for your specific routes, loads, and driver population.
This analysis serves two purposes simultaneously. Operationally, it tells you where to focus your safety management attention. For litigation defense, it establishes that your company conducted a genuine, data-driven assessment of its safety risk — not a generic compliance exercise, but a specific analysis of the conditions most likely to produce harm in your operation. That documented analytical process is evidence of organizational competence that directly defeats the Reptile Theory systemic failure argument.
The analysis should be documented. The methodology should be defensible. The conclusions should be specific to your operation and updated as your routes, fleet, and driver population change.
Step 3: Manage — Monitor and Respond
Identifying and analyzing your data creates knowledge. Managing it creates defense.
Management means establishing ongoing monitoring of the key indicators you have identified as most predictive of accident potential in your operation — and taking documented action when those indicators exceed the thresholds you have set. This is the step that transforms your data from a static record into an active safety management system.
The critical word is documented. Monitoring that does not generate records of what was observed and what action was taken is monitoring is difficult to defend. When plaintiff counsel asks — and they will ask — whether your company reviewed its safety data and responded to warning signs, the answer needs to be supported by a paper trail that shows exactly what was reviewed, when, by whom, and what happened as a result.
This is also where the DataQs reform we covered in the series becomes relevant internally. Just as you need to manage and challenge your external FMCSA safety record, you need to manage and respond to the internal signals your own systems generate. The carrier whose records show a pattern of identifying risk indicators and addressing them before accidents occur is the carrier with a fundamentally different litigation posture than one whose records show warning signs that were never acted on.
The documented management record is the most powerful single defense asset you can build. It answers the Reptile Theory’s central argument — that your company ignored warning signs — with objective evidence that you did not.
Step 4: Enforce — The Hardest Step
The fourth step is where safety data management becomes genuine organizational accountability — and where many carriers struggle.
Enforcement means acting on what your data tells you about individual drivers. It means coaching, retraining, and when necessary, disciplinary action or termination based on documented performance data. In a tight driver market, these are difficult decisions. The temptation to look past warning signs from a driver you need on the road is understandable.
But consider the calculus. Your best drivers — the ones with clean records, who follow your safety protocols, who drive defensively and professionally — are generating revenue and building your reputation. How many safe miles do they have to run to pay for one bad actor’s nuclear verdict? And the more serious question: will that one bad actor, left unchecked because the driver market is tight, be an existential threat to your business?
Documented enforcement is not just a safety practice. It is the final piece of the litigation defense. It shows that when your data identified a problem, your organization acted. That documented accountability — the coaching sessions, the performance improvement plans, the terminations when warranted — is the evidentiary record that defeats the argument that your company knew about dangerous driver behavior and did nothing.
The absence of documented enforcement, by contrast, is one of the most damaging things plaintiff counsel can surface. A driver with a history of speeding alerts, hard brake events, and collision avoidance triggers who is still on the road at the time of an accident — without any documented response to those indicators — is a Reptile Theory case waiting to happen.
The Choice
The Data Dilemma comes down to a single decision that every trucking company makes, either explicitly or by default.
You can get ahead of your data — identify what you have, analyze what it means, manage the key indicators, and enforce accountability when the data demands it. You create the narrative: a safety-focused organization that uses data proactively, responds to warning signs systematically, and holds itself accountable to the standards it sets.
Or you can abdicate the narrative to plaintiff attorneys. They will find your data. They will analyze it. They will identify your warning signs. And they will present it to a jury in the worst possible light — as evidence that your company had every opportunity to prevent what happened and chose not to.
The data is there. The question is who tells the story.
The DENUCLEARIZATION Connection
The Data Dilemma is Part 6 of the DENUCLEARIZATION series because it sits at the center of everything we have covered. The Reptile Theory (Part 5) requires a systemic failure narrative — your unmanaged safety data is the raw material. The DataQs reform (news reactive, two weeks ago) addressed your external FMCSA safety record. This week addresses your internal safety data. The Motus piece addressed your regulatory compliance record. All three records — external safety data, internal operational data, and regulatory profile — contribute to the organizational narrative that plaintiff attorneys construct and that a proactive carrier can defeat.
The defense that wins is built before the accident. The data management framework is how you build it.
