Logistics and distribution
Dashcam and telematics data in truck accident cases: retention and holds
By SourceX Editorial · Reviewed by Noah Loul ·
Short answer
Dashcam footage retention in trucking is set by company policy and vendor settings until a crash, claim or preservation letter triggers a litigation hold. From then on, every relevant clip, telematics record and log is preserved as it is. The firm rule: anything under a hold is preserved and excluded from licensing until counsel releases it.
Key takeaways
- Camera platforms delete or overwrite footage on a schedule, so a hold must reach the vendor platform, not only a policy document.
- A preservation letter, serious crash or claim notice can trigger a duty to preserve before any lawsuit is filed.
- A hold covers the whole record of the event: video, engine data, ELD logs, GPS, dispatch messages, inspections and the driver file.
- Anything under a hold stays out of licensing until litigation counsel releases it.
- A written retention policy applied consistently before any incident is easier to defend than ad hoc deletion.
How long should a trucking fleet keep dashcam footage?#
A trucking fleet should keep dashcam footage for the period its written retention policy sets, unless a hold requires longer. Dashcam video is mostly governed by that policy, the vendor's storage settings, insurer expectations and the duty to preserve evidence, rather than by one fixed rule, so counsel should confirm whether any specific rule applies to a given operation.
Most fleets hold two kinds of video. Event clips upload when a sensor or AI trigger fires, such as hard braking, a lane departure or a collision. Continuous footage stays on the device and is overwritten as storage fills, unless someone retrieves it first. Cloud retention for both depends on the plan and admin settings, so check the vendor's documentation rather than assuming. Samsara, for example, says its dash cams typically hold about 20 to 300+ hours of video locally and upload video to the cloud generally only on a safety event or a manual request, so the cloud archive is event-based rather than continuous.
Some related records do have federal floors. FMCSA guidance says carriers must keep records of duty status and supporting documents for six months, and 49 CFR 391.51 requires each driver qualification file to be kept for the length of employment plus three years. These are minimums, and a hold can require keeping records longer.
A workable written policy names each data type, from event clips to continuous footage to engine data, sets a routine period for each, and states that any trigger listed below suspends deletion. It also names who may change platform settings, so retention cannot drift when an admin switches plans or devices.
Keeping everything forever is not a safe default. Unlimited retention raises storage cost, driver privacy exposure and the volume of material that must be searched and reviewed in discovery.
What triggers a hold on dashcam and telematics data?#
A hold is triggered when litigation becomes reasonably foreseeable, which in trucking often happens at the scene, well before any lawsuit. Losing relevant evidence after that point is called spoliation, and courts can sanction it, including by instructing a jury that it may assume the missing footage was unfavorable.
| Trigger | What it signals | First step |
|---|---|---|
| Crash with injury, fatality or tow-away | Litigation is reasonably likely | Lock event and continuous video for the truck and the window around the crash |
| Preservation or spoliation letter | The other side has asked for specific evidence | Send it to counsel the same day; hold everything it lists |
| Insurer or claim notice | A claim exists even without a lawsuit | Match the claim to the truck, driver and date, then preserve |
| Police report or regulator inquiry | An official investigation of the event | Preserve what the inquiry may request, including logs |
| Cargo or property damage dispute | A commercial claim may follow | Preserve video at pickup and delivery plus POD records |
| Lawsuit served | A formal duty to preserve and produce | Confirm the hold scope with litigation counsel |
What a telematics hold should capture#
A telematics hold should capture the full record of the event, not only the clip the safety team has already watched. Claimants typically ask for the data around a crash as well as the crash itself, to test speed, hours, fatigue, maintenance and supervision.
Some of these records sit with vendors and some on devices in the truck. If continuous footage lives only on the camera, pull the truck from service long enough to download it before it overwrites.
- Event video from every camera on the truck, plus continuous footage for the surrounding window.
- Engine control module and telematics data: speed, braking, throttle, cruise control and fault codes.
- ELD logs, edits and annotations for the driver around the trip.
- GPS breadcrumbs and geofence events for the trip.
- Dispatch messages, load assignments and appointment times.
- Pre-trip and post-trip inspection reports and recent maintenance records.
- The driver qualification file, training records, coaching notes and safety scores.
- Calls and messages on company-issued phones or in-cab tablets.
Why vendor settings are the weak point#
Vendor settings are the weak point because the platform deletes footage on its own schedule, whatever the hold memo says. A notice sent to the safety team does nothing if the clip quietly expires in the cloud account or the device loop records over it.
Practical controls close the gap. Name an admin in each platform who can apply a retention lock or export. Export held footage with its metadata intact, record who exported it and when, and store the copy where it cannot be edited. Keep the original in the platform as long as the plan allows; the export is a backup, not a replacement.
Read the vendor contract as well. Some agreements describe what happens to data after cancellation or a plan change, which matters if the fleet switches providers while a claim is still open.
Holds and licensing: the rule#
Anything under a hold is preserved and excluded from licensing until litigation counsel releases it. That covers originals and copies, and it applies even if the footage would be de-identified before sharing, because altering, transforming or distributing held material invites arguments about integrity that no license is worth.
In practice, fleets that consider licensing use the claims register as a filter and exclude every truck, driver and date window tied to an open claim. That keeps the license scope defensible and avoids searching the same footage twice.
| Record status | Retention treatment | Licensing treatment |
|---|---|---|
| Under an active hold | Preserve as is; no deletion or editing | Excluded |
| Claim closed and hold released | Return to the normal retention schedule | Eligible for review like other records |
| Related to an open claim but not yet on hold | Ask counsel before any action | Paused until counsel decides |
| Routine records with no incident | Normal schedule | Eligible for rights and privacy review |
Illustrative: a regional flatbed carrier after a highway crash#
Illustrative: a fictional regional flatbed carrier runs road-facing and driver-facing cameras, ELDs and a TMS. One of its trucks is involved in a highway crash with injuries, and a preservation letter from the other driver's attorney follows soon after.
The safety director locks the event clip in the camera platform, then realizes continuous footage exists only on the device; the carrier pulls the truck to download it. Counsel issues a hold covering the driver's logs, engine data, dispatch messages, inspection reports and qualification file, and IT exports each with a record of who handled it.
Months later, leadership explores licensing road-facing event clips. The truck, driver and date window from the crash are excluded under the hold, along with all driver-facing video. The rest of the archive goes through privacy review, with faces, plates and audio removed.
How SourceX approaches held records#
Hold status is one of the first questions SourceX asks a fleet, ahead of any discussion of footage or formats. In the SourceX five-step transaction, the Rights step asks the fleet to confirm open claims and hold notices, and every truck, driver and date window they touch is carved out of scope. The SourceX Evidence Packet records that exclusion as part of the release authorization, and SourceX never asks a supplier to alter, copy or move held material.
Frequently asked questions
Can a preservation letter create a duty to preserve before a lawsuit?
It can. Courts generally ask when litigation became reasonably foreseeable, and a letter naming the incident and the evidence makes that hard to dispute. Treat the letter as a trigger, send it to counsel and stop deletion of everything it lists while counsel sets the scope.
Should we keep all dashcam footage just in case?
Usually not. Keeping everything raises storage costs, driver privacy exposure and discovery burden. A written policy that keeps routine footage for a set period and preserves anything tied to an incident is easier to explain and defend than unlimited or ad hoc retention.
Are coaching notes and safety scores part of a hold?
Often, yes. If they concern the driver or the behavior involved in a crash, they may be relevant to claims about training or supervision. Include them in the hold and let counsel decide what is produced; never edit or add to them after the incident.
Who should own a litigation hold at a fleet?
Counsel issues and scopes the hold, but someone in safety or risk should own execution: locking footage in each platform, downloading devices, tracking exports and confirming every custodian received the notice. Name a backup, because crashes do not keep business hours.
Does releasing a hold mean the footage must be deleted?
No. Release returns the records to the normal retention schedule. If that period has already run, the footage becomes eligible for deletion, and it can also be reviewed for other uses, including licensing after privacy preparation, once counsel confirms nothing else is pending.
Sources
- Samsara dash cams typically hold about 20 to 300+ hours of video locally, uploading to the cloud generally only on a safety event or manual request. Source
- Motor carriers must keep records of duty status and supporting documents, such as bills of lading, for six months under 49 CFR 395.8(k)(1). Source
- 49 CFR 391.51(c) requires each driver qualification file to be kept for the length of employment plus three years. Source
Related resources
See if your company qualifies
A short company assessment. No data uploads are needed.