A carrier can follow every federal recordkeeping rule, purge a driver’s logs exactly on schedule, and still lose a case because those logs are gone. That is not a paradox. It is arithmetic.

Federal ELD data retention rules require motor carriers to keep records of duty status and supporting documents for six months from the date of receipt, under 49 CFR 395.8(k)(1). Texas gives an injured party two years from the crash to file suit. Do the subtraction. The electronic record of what a driver was doing in the eleven hours before impact can be lawfully deleted eighteen months before anyone files a petition asking about it.

Plaintiff firms read that calendar more carefully than most carriers do. One published account of how Texas truck accident cases actually get built describes a response team deploying to the crash scene within days and moving on driver logs, engine control module data, and dispatch records immediately, on the theory that the six-month clock starts when the carrier receives the record and not when someone finally thinks to ask. By the time a claim is formally filed, the evidence question has usually already been settled one way or the other.

Takeaways

• Federal rules set a six-month floor on ELD record retention, not a target and not a ceiling.
• Texas allows two years to file a personal injury or wrongful death claim, leaving roughly an eighteen-month gap where relevant records may no longer exist.
• Routine deletion stops being routine the moment a carrier is on notice that litigation is coming.
• Most preservation failures are operational, not legal. The notice arrives at a terminal and the purge job runs on schedule anyway.
• Shippers and 3PLs can write retention terms into carrier agreements the same way they write insurance minimums.

What the six-month rule actually covers

The obligation is broader than the log file. Section 395.8(k)(1) reaches records of duty status and the supporting documents behind them, which in practice means bills of lading, dispatch records, fuel purchase receipts, toll records, and payroll documents that show where a driver was and when. FMCSA restates the same period in its own guidance on how long carriers must retain RODS and supporting documents, and adds that a backup copy of ELD data belongs on a device separate from the original for that same six months.

The driver carries a much shorter window. Seven consecutive days of duty status records must be in the cab and available at roadside. Everything past that lives with the carrier or the ELD vendor, and it lives there on whatever schedule the carrier chose when it configured the account.

That last part gets overlooked. Six months is a regulatory minimum. Nothing stops a fleet from keeping three years of telematics history. Plenty of fleets keep less than they think they do, because the retention setting came out of the box and nobody revisited it.

Why ELD data retention runs out before the lawsuit starts

Serious truck crash claims move slowly at the front end. A catastrophically injured claimant spends months in acute care and rehab before anyone talks to a lawyer. Families in wrongful death cases often spend the first year on grief and probate. Insurers negotiate. Counsel gets retained at month fourteen, sends a records request at month sixteen, and files at month twenty-three.

Every one of those months burns against a six-month record. The ELD data that would have shown a driver on hour twelve of an eleven-hour limit was purged before the claimant’s first surgery finished healing.

Carriers sometimes read that as good news. It is not. An empty file does not read as innocence. It reads as an absence a jury gets to interpret, and the interpretation tends to run against the party that controlled the system.

When a preservation letter lands, the rule changes

A litigation hold letter rewrites the retention question in a single afternoon. Once a carrier is on notice that a claim is reasonably anticipated, continuing to delete relevant records stops being compliance and becomes spoliation. Federal courts address it under Rule 37(e), and Texas applies its own spoliation standard in state court. The sanctions range from an adverse inference instruction to something considerably worse.

The failure is almost never a decision. It is a workflow. The preservation letter arrives by certified mail at a terminal office, gets scanned into a shared drive, and waits for someone to route it. Meanwhile the ELD platform runs its scheduled purge on day one hundred eighty-one, exactly as configured, and nobody connects the two events until a deposition.

Fleet software rarely helps here. Most ELD platforms have a retention setting and an export function. Very few have a hold flag that freezes a specific vehicle, driver, or date range and blocks deletion until someone with authority clears it. That is a product gap worth raising with a vendor at renewal.

What this means for supply chain and procurement teams

This lands outside legal more often than people expect. Shippers, brokers, and 3PLs get pulled into truck crash litigation regularly, and their exposure depends partly on records they do not own.

• Ask carrier partners what their ELD retention setting is, in months, and get the number rather than an assurance that they are compliant. Compliant means six.
• Ask who at the carrier receives a preservation letter and how fast that person can freeze a record. If the answer involves a terminal manager and a scanner, the answer is too slow.
• Write retention terms into carrier agreements. A twenty-four-month floor on ELD data, dispatch records, and maintenance history costs the carrier storage and costs you nothing.
• Confirm where the backup copy actually lives. If the ELD vendor holds it and the carrier switches vendors, the history may not travel.
• Treat your own dispatch and appointment records the same way. Detention times and scheduling pressure show up in these cases, and those records are yours.

The bottom line

Six months is the number a compliance auditor cares about. Two years is the number a plaintiff’s lawyer cares about. Fleets and the supply chains that hire them keep planning around the first number and get surprised by the second.

Retention length is not a storage decision. It is a decision about what evidence exists on the day someone finally asks for it, and that day is almost always later than the file survives. Setting the number higher is the cheapest risk control available to a fleet, and one of the few that costs nothing but a configuration change.