Jul 23, 2026
.webp)
Under 49 CFR 395.8(k)(1), a motor carrier must retain records of duty status and supporting documents for six months. Most fleets build their data retention policy directly around that number, and most ELD platforms are configured to match it. Records age out on a rolling schedule, storage stays manageable, and the carrier remains compliant with the rule as written.
That arrangement works until the day a serious crash happens. At that point, the six-month schedule stops being a compliance asset and starts being a liability, because the obligation to preserve evidence in anticipated litigation does not run on the same clock as the obligation to retain records for FMCSA. A carrier whose system quietly purges records on day 181, exactly as designed, exactly as compliant, can be found to have destroyed evidence. The fact that the deletion was automatic and policy-driven is not the defense most safety directors assume it is.
The most consequential misunderstanding in this area is about timing. Many carriers operate on the assumption that their preservation obligation begins when a preservation letter, sometimes called a spoliation letter, arrives from a plaintiff attorney. Until that envelope shows up, the thinking goes, normal retention policy applies.
That is not how the obligation works. The duty to preserve attaches when litigation becomes reasonably foreseeable. A serious injury crash or a fatality generally satisfies that standard on its own, without any letter, notice, or filed claim. Plaintiff-side firms understand this well, which is why their published guidance instructs attorneys to send preservation letters within the first day or two after a crash, before client engagement is even complete. The letter is not what creates the duty. The letter is what makes it impossible for the carrier to later claim the duty was not apparent.
The practical consequence is that the window in which a carrier can act without exposure is narrow and starts immediately. Records that cycle off during the gap between a crash and the arrival of formal notice are still records that were destroyed after the duty attached. The carrier's own retention automation becomes the mechanism of the destruction, and automation does not read as innocent when the underlying event was a fatality.
ELD records are the most cited category in crash litigation, but they are one item on a much longer list. Published discovery guidance from firms handling commercial truck cases consistently identifies the same broad set: hours of service records, the electronic control module or event data recorder download, dashcam footage from forward-facing and in-cab units, GPS and telematics history, dispatch records and communications, driver qualification file contents, drug and alcohol testing records, maintenance and repair history, fuel card transactions, and internal messages between dispatch, safety, and the driver.
Several of these live outside the ELD platform entirely, on separate systems with separate retention schedules and separate administrators. A litigation hold that covers only the ELD account leaves gaps in every other system, and those gaps are not treated as partial compliance. They are treated as the categories where evidence went missing.
There is also a physical dimension that catches carriers off guard. Event data recorder captures can be overwritten by subsequent events, meaning the crash data can be lost simply by continuing to operate the vehicle. A truck that is repaired, sold, or returned to service before its ECM is imaged may take the most precise record of the seconds before impact with it.
When ELD records are produced in litigation, the expected format is the provider's native export, the file that carries embedded metadata, timestamps, and the underlying audit trail. Plaintiff attorneys are explicitly coached to refuse summary reports, PDF printouts, and screen captures, and to treat a carrier's resistance to native production as a credibility problem in front of the court.
This turns into a straightforward operational question that most fleets have never asked their provider: can your platform produce a native-format export of the complete record for a specified driver and date range, including the edit history and the original unedited entries, without a support ticket and without a multi-week turnaround? Many platforms can. Some cannot, or can only produce a formatted report that looks complete but has stripped the metadata that makes it defensible.
Knowing the answer before a crash is meaningfully better than discovering it during one. The same ELD compliance reports a safety coordinator uses for routine review are generated from the same underlying record that would be produced in discovery, which means the export capability is not a specialized legal feature. It is the ordinary reporting function, tested against an unusual requirement.
Under 49 CFR 395.30(f), when a record of duty status is edited, the original unedited entry must be preserved alongside the edit and the annotation explaining it. An edit does not overwrite. It layers.
Carriers sometimes misread this as a limitation. In litigation it is closer to a protection, provided the annotations are done properly. A log that shows an original entry, a corrective edit, and a contemporaneous annotation explaining why the correction was made reads as a functioning compliance program. A log with edits and no annotations, or annotations added long after the fact, reads as something else entirely. The ELD fleet reports guide covers the edit report and what patterns investigators look for in it, and the same report is among the first things examined when the audience shifts from an FMCSA investigator to opposing counsel.
The related point is that ELD events are recorded in real time and cannot legitimately be cached and rewritten later. That design feature is what gives the record its evidentiary weight, and it is also why attempting to clean up a record after a crash is both detectable and far more damaging than whatever the original record showed.
Two additional deadlines run concurrently with the preservation question, and both are short enough to be missed in the disorder of the first day.
Post-accident testing under 49 CFR 382.303 requires alcohol testing within eight hours and controlled substances testing within thirty-two hours where the regulatory criteria for testing are met. Plaintiff-side commentary specifically watches for carriers who let those windows lapse, because a missed test is straightforward to characterize as avoidance regardless of the actual reason. The Clearinghouse and testing obligations that intersect here are covered in the Clearinghouse compliance review guide.
Separately, 49 CFR 390.15(b) requires carriers to maintain an accident register with specified information for each recordable accident, retained for three years. This is a routine recordkeeping obligation that becomes a discovery item, and an incomplete register invites questions about what else was not maintained.
Issuing a hold is a legal decision made with counsel. Executing one is an operational task that lands on whoever administers your data systems, and it involves work most fleets have never rehearsed.
The hold has to reach every system that contains relevant data, which means identifying those systems in advance rather than during a crisis. Automatic deletion routines have to be suspended, not just noted, and in some platforms that is not a setting an administrator can toggle without provider involvement. Custodians across dispatch, safety, maintenance, and IT need to be notified and their acknowledgment recorded. Equipment involved in the incident needs to be sequestered rather than swapped or returned to service.
The documentation of all of this is the part carriers most often skip and most need. A contemporaneous record showing when the hold was issued, which systems it covered, who was notified, and what was preserved is the carrier's answer if a gap is later alleged. Without it, the carrier is arguing from memory against a documented timeline, which is a poor position regardless of the underlying facts.
There is an instinct, when a carrier knows a particular day's records are unflattering, to hope the retention schedule handles the problem quietly. It is worth being direct about why that instinct is backwards.
A record showing a driver deep into their hours at the time of a crash is a bad fact. It is also a fact that can be contextualized, explained, and argued about. A record that went missing after the duty to preserve attached is a different category of problem. Courts can instruct juries that they may infer the destroyed evidence would have been unfavorable, which converts an argument about what the data showed into an assumption that it showed the worst. Sanctions are available on top of that. The carrier that preserves a difficult record is in a materially stronger position than the carrier that loses a neutral one.
This is also why the preparation work is worth doing before it is needed. A fleet that knows which systems hold what, that can produce native exports on request, and that has an actual written procedure for suspending automated deletion is not doing anything adversarial. It is doing the thing that protects it.
The useful version of this preparation is short. Confirm with your provider whether native-format export including edit history is available to you directly, and how long it takes. Find out whether your platform's automatic deletion can be suspended by an administrator or requires provider action, and how quickly that request is honored. Write down which systems outside the ELD contain crash-relevant data and who administers each one. Confirm that your retention configuration is at minimum meeting the six-month floor, and understand what happens to older records when it lapses.
Provider contract terms matter here too, particularly for carriers who have switched platforms or are considering it. The ELD contract red flags guide covers post-cancellation data deletion clauses, which can destroy historical records on a timeline the carrier does not control and may not have read closely. A hold cannot preserve data a former provider has already deleted under a contract term.
If you want to understand how your current setup handles record export, retention configuration, and audit trail preservation before you have a reason to need it, start a free 14-day trial of AI ELD and test the export function directly on your own data. For questions about retention settings or how records are stored, the support team is available around the clock.
And to repeat the point at the top, because it is the one that matters most: after a serious crash, this article is not your guide. Your insurer and your counsel are, immediately, before any decision about records is made.
eCFR. "49 CFR 395.8(k)(1): Retention of Records of Duty Status." Primary regulatory source for the six-month retention requirement covering records of duty status and supporting documents. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395
eCFR. "49 CFR 395.30(f): Edits and Annotations." Primary regulatory source for the requirement that original unedited records be retained alongside any edit and its annotation, establishing that edits layer onto rather than replace the underlying entry. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395
eCFR. "49 CFR 395.22: Motor Carrier Responsibilities, Backup Records." Primary regulatory source for the separate backup copy retention obligation running alongside the primary six-month requirement. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-395
eCFR. "49 CFR 382.303: Post-Accident Testing." Primary regulatory source for the eight-hour alcohol testing and thirty-two-hour controlled substances testing windows following a qualifying accident. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-382
eCFR. "49 CFR 390.15(b): Accident Register." Primary regulatory source for the accident register content requirements and the three-year retention period. https://www.ecfr.gov/current/title-49/subtitle-B/chapter-III/subchapter-B/part-390
BAM Injury Law. "ELD Data and the 6-Month Evidence Window: Preserving Commercial Truck Accident Evidence Before It's Gone." July 2026. Plaintiff-side source describing the preservation letter process, the day-one and day-two sending timeline, the native format production standard, and the instruction to refuse summary reports and screen captures. Cited here because it documents what carriers should expect to receive and be asked for. https://baminjurylaw.com/blog/eld-data-and-the-6-month-evidence-window-preserving-commercial-truck-accident-evidence-before-its-gone/
PI Law News. "How ELD Records Are Used in Truck Accident Cases." June 2026. Plaintiff-side source for the two-step process of preservation letter followed by subpoena or discovery request, and the confirmation that the duty to preserve can extend the obligation well beyond the six-month regulatory floor once litigation is reasonably foreseeable. https://www.pilawnews.com/post/how-are-eld-records-used-in-truck-accident-cases
HOV Law. "Truck Accident Black Box and ELD Evidence Explained." April 2026. Plaintiff-side source for the distinction between carrier-side server retention and the driver's local device copy covering the prior seven days plus the current day, and for the observation that event data recorder captures can be overwritten by subsequent events. https://www.hov.law/learn/truck-accident-black-box-evidence
Bateson Law. "Spoliation Letters in Trucking Accidents." June 2026. Source for the data hierarchy identifying systems beyond the ELD that fall within a litigation hold, including telematics, dispatch software, fuel card logs, maintenance reports, and internal communications, and for the operational steps of suspending auto-delete routines and notifying custodians. https://batesonlaw.com/spoliation-letters-trucking-accidents-lawyer-drafted/
Aguiar Injury Lawyers. "Truck Black Box Data Evidence." April 2026. Source for the adverse inference instruction as a consequence of destruction following a preservation demand, and for the confirmation that ELD events must be recorded in real time and cannot be cached and rewritten later. https://aguiarinjurylawyers.com/truck-talk/black-box-data/
AI ELD. "ELD Contract Red Flags." Source for post-cancellation data deletion clauses and the carrier's retention obligation surviving the end of a provider relationship. https://ai-eld.com/insights/eld-contract-red-flags
AI ELD. "ELD Reports Every Fleet Manager Should Review." Source for the edit report structure and the audit trail patterns examined during compliance review, applicable here to the discovery context. https://ai-eld.com/insights/eld-fleet-reports-guide