The crash sequence
The person or organization likely to possess, control, administer, or physically hold the item—and the basis for that belief.
Truck evidence preservation
A form demand for “all black-box data” can miss the truck, trailer, electronic log, provider account, camera, dispatch platform, load file, repair work, and agency records. Useful notice is specific, proportionate, and tied to reasonably anticipated issues.
The crash-specific starting point
A useful review starts with the actual vehicles, trip, companies, location, records, and injuries. The crash label alone does not decide which rules apply or what the evidence can prove.
Preservation is more reliable when the requesting lawyer knows what likely exists and who may possess or control it.
Evidence before assumptions
Identify the crash sequence and the exact truck, trailer, trip, load, companies, and records before selecting a legal theory.
The person or organization likely to possess, control, administer, or physically hold the item—and the basis for that belief.
The precise item, vehicle, device, account, native format, event type, date range, metadata, audit history, and documentation needed to interpret it.
The realistic loss mechanism: repair, overwrite, later event, account expiration, routine deletion, recycling, sale, salvage, weather, scene cleanup, or fading memory.
The access path: voluntary exchange, public-records request, authorization, inspection agreement, discovery, subpoena, expert protocol, protective order, or court order.
Evidence map
Preservation is more reliable when the requesting lawyer knows what likely exists and who may possess or control it.
Start with verified identifiers: date, time, exact place, report number, driver, carrier legal and trade names, federal numbers, tractor and trailer vehicle-identification numbers, plates, unit numbers, load, shipper, broker, tow company, storage site, insurer, and known vendors. Record what is unknown. A notice should not accuse an uninvolved company or describe a system as present merely because similar fleets use it.
Divide the evidence by source. Vehicle evidence can include the tractor, trailer, cargo, securement, tires, brakes, lights, coupling, modules, cameras, and post-crash changes. Digital evidence can include native logs, backups, edits, telematics, event or engine data, video, dispatch, messages, lawfully obtained phone material, account records, and provider data. Paper and business records can include qualification, inspection, maintenance, repair, load, broker, shipper, drug and alcohol, insurance, and claim files where relevant.
Public and third-party evidence needs its own plan. Crash reports, photographs, body or dash camera, 911, radio, fire, emergency medical, roadway, work-zone, toll, weather, tow, salvage, hospital, commercial video, and witness records are not necessarily controlled by the carrier. Identify the correct custodian, request law, authorization, subpoena route, privacy restriction, exemption, and retention practice.
Legal decision points
A letter can identify relevant material and document notice. The preservation duty and remedy come from governing law and facts, not from the sender's caption.
Determine when litigation was reasonably anticipated, by whom, and for which evidence. Evaluate relevance, proportionality, possession, custody, control, burden, privilege, privacy, safety, routine systems, and whether preservation is feasible. A recipient should not be told to keep years of unrelated fleet material without a supported connection. An overbroad demand can obscure the few items at genuine risk.
Federal Rule of Civil Procedure 37(e) addresses electronically stored information lost because a party failed to take reasonable preservation steps. It applies when the information should have been preserved for litigation and cannot be restored or replaced through additional discovery. The rule distinguishes prejudice-based measures from the most severe measures, which require intent to deprive. It does not govern every state case or every piece of physical evidence.
Oklahoma procedure and case law require separate attorney review. Patel v. OMH Medical Center discusses an independent spoliation tort but does not decide whether Oklahoma recognizes that claim. It is not a complete sanctions guide. The forum, evidence type, preservation duty, discovery rule, court authority, culpability, relevance, prejudice, and requested remedy must be identified under current law.
A careful review must distinguish a preservation request from a legal duty, federal Rule 37(e) from Oklahoma procedure, electronically stored information from physical evidence, and a missing record from sanctionable loss.
Retention rules
Regulatory retention is evidence-specific. It is not a single clock for every item generated by a truck or trucking company.
For covered drivers and carriers, federal rules address retention of records of duty status and supporting documents, and the electronic-logging framework includes a separate backup. The commonly cited six-month period is important to those records. It should not be represented as the retention period for engine-control events, heavy-vehicle event data, high-resolution telematics, camera video, dispatch messages, phone records, maintenance material, broker files, or provider-side tools.
Some data can change through ordinary use: a later qualifying event, new diagnostic history, repair, software work, module replacement, account settings, camera overwrite, or vehicle return to service. Other records are retained for longer regulatory or business periods. Determine the actual system and written practice. A vendor's marketing page is not proof that the crash account had a feature or that the provider still possesses it.
Regulatory retention and litigation preservation can overlap without being identical. A company should not be told that the expiration of a regulatory minimum permits destruction of evidence subject to another preservation duty. Likewise, the letter should not claim to create permanent retention, possession, or control. State the event, issues, reason, scope, and anticipated access steps plainly.
Execution
A sent letter does not establish that the right recipient received it, understood it, located the evidence, or agreed to an inspection.
Track the recipient, address, transmission, delivery, acknowledgment, objections, preservation response, vehicle location, repair plans, vendor identity, and responsible contact. Update the notice when new identifiers emerge. Preserve the correspondence in native form. Do not treat silence as agreement or delivery. If immediate physical access is needed, seek a written standstill, inspection protocol, or appropriate court relief rather than rely on broad language.
For an inspection or download, define the participants, notice, qualifications, scope, tools, power source, non-destructive method, photographs, native files, digital fingerprints, backups, chain of custody, confidentiality, and treatment of unexpected data. Address destructive testing separately. Keep the source file and analyst report distinct. Document unavailable data and limitations without altering the system to search for a preferred result.
Continue ordinary claim work. Locate witnesses, obtain treatment, preserve the claimant's devices and vehicle when relevant, maintain photographs and expenses, notify insurers as required, and evaluate filing or governmental notice periods. A preservation dispute should not distract from limitations, service, jurisdiction, coverage, medical causation, or damages. No letter pauses those deadlines.
Legal-information boundary
The analysis depends on applicable law, anticipated litigation, relevance, proportionality, possession, custody, control, reasonable steps, loss, and replacement. It also depends on prejudice, intent or culpability, discovery posture, and evidence type. A letter alone does not establish those facts.
ELD retention, other trucking records, private video, electronic systems, public records, governmental notice, insurance, injury, death, and lawsuit deadlines can differ. Sending or requesting a letter does not toll or extend any period.
FAQ
It is a focused notice identifying a collision, likely evidence, custodians, systems, scope, and foreseeable loss. It can document notice and request reasonable preservation, but it is not a subpoena, discovery order, or automatic sanction.
As soon as the event and likely evidence can be identified well enough to send a reliable, targeted request. Practical urgency varies by vehicle plans, video, data systems, scene change, and witnesses; no single seventy-two-hour legal deadline governs those sources.
No. The federal six-month provisions commonly discussed concern covered records of duty status and supporting documents. Engine data, telematics, video, messages, provider systems, and other records may follow different rules and practices.
No. The forum, duty, control, reasonable steps, relevance, replacement, prejudice, intent or culpability, evidence type, and requested measure matter. Federal Rule 37(e) imposes specific requirements for lost electronically stored information.
Only supported likely custodians or controllers, which may include the carrier, driver, owner, lessor, broker, shipper, loader, maintenance provider, insurer, tow yard, ELD or telematics provider, camera owner, or public agency. The list should follow the evidence map.
These materials frame the general trucking, evidence, roadway, and procedure questions identified in the guide. They do not establish that a rule applies, that a company is liable, or that a particular record exists.
Addison Law Firm is based in Oklahoma City and evaluates selected serious truck-crash matters arising in Oklahoma. This information is general, does not promise representation or an outcome, and does not create an attorney-client relationship.
Start with the crash record
Bring the report, truck and trailer identifiers, company names, photographs, tow location, load information, existing data reports, witness contacts, and insurer communications. A focused inventory comes before the demand.