A company vehicle does not establish who must pay or how much insurance applies. Learn how to separate responsibility, coverage, and records of lasting losses.
Digital information after a crash may exist on a phone, camera, vehicle, app, online account, business system, or public-agency system. Finding a possible source does not establish that a record exists, that it covers the collision, or that a person has authority to obtain it. Preservation starts by identifying the source, owner, time window, access path, and risk of change or deletion.
A useful digital-evidence inventory distinguishes the original source from exported copies, screenshots, summaries, and later annotations. It also records what each item can show and what would require technical or legal interpretation.
Map the source before collecting files
- Personal devices and accounts: photographs, videos, messages, call information, navigation records, receipts, and app activity
- Vehicle systems: dash cameras, event data recorders, infotainment systems, telematics, and fleet systems
- Third-party systems: nearby business cameras, doorbells, parking systems, rideshare or delivery platforms, and tow or repair records
- Public sources: transportation equipment, transit systems, emergency communications, and agency records
For each source, record the device or system, owner, custodian, account or vehicle, physical location, viewing direction when relevant, date and time range, time zone, likely retention or overwrite concern, contact path, request date, response, and follow-up. Do not assume that a visible camera records continuously or that a vehicle stores every event.
Preserve the native item and its context
The National Institute of Standards and Technology explains that digital evidence presents preservation issues beyond traditional evidence and emphasizes source documentation, integrity, access control, and retention. When an original file is available, keep it unchanged and create a separate working copy for viewing, clipping, redacting, labeling, or sharing.
Preserve the original filename, format, file size, creation and modification information available from the source, attachments, full conversation or recording context, export method, device or account, person who collected it, date collected, transfers, and storage location. A cryptographic hash may help compare file copies, but a matching hash does not by itself establish who created the file, what it depicts, or whether the source account and clock were reliable.
A screenshot can be a useful reference, but it may omit metadata, attachments, preceding messages, an edited caption, account information, or the system’s export history. Keep the screenshot labeled as a working or captured view and preserve the fuller source when lawfully available.
Use lawful access and a specific preservation request
Preserve material you own or are authorized to access. Do not guess another person’s password, enter a private account, alter a device, or direct someone to conceal or delete information. For a source held by a business, agency, platform, insurer, employer, or another person, identify the correct custodian and the available request or legal process.
A preservation request should identify the collision date, a reasonable time window, location, device or system if known, categories sought, and the requester’s contact information. Keep the exact request, delivery record, response, and any correction. A preservation request asks that material be retained; it does not necessarily require immediate disclosure and does not prove that responsive material exists.
Keep observation separate from interpretation
Describe directly visible facts before drawing conclusions. A video may show vehicle movement within the frame, but it may not establish speed, distance, the signal facing another approach, driver attention, events outside the frame, or medical causation. Vehicle data may require the correct system, event, retrieval method, units, calibration context, and qualified interpretation.
North Carolina Rule of Evidence 901 requires enough evidence to support a finding that an item is what its proponent claims. The rule includes examples involving a knowledgeable witness, distinctive characteristics, and evidence about a process or system. Saving a file is therefore different from establishing its source, completeness, meaning, and admissibility.
Distinguish preservation from lawsuit production
If litigation begins, formal duties and requests require separate review. North Carolina Rule of Civil Procedure 34 addresses requests to parties for documents, electronically stored information, tangible things, and inspection within the rule’s scope. It also addresses requested production forms and information in a party’s possession, custody, or control.
The related guide to document requests and electronic evidence explains that litigation stage. Rosensteel Fleishman Car Accident & Injury Lawyers provides information about consulting a Charlotte car-accident lawyer when a digital source may be lost, access is disputed, or formal preservation or production questions arise.
Sources
Additional Car Accidents Articles
A suspected mechanical problem is not the same as an established crash cause. Learn how vehicle records, sight lines, and a clear timeline help separate observations from conclusions.
When both drivers deny responsibility, the focus shifts to evidence rather than agreement. Separate observations from assumptions, document practical losses, and ask insurers to explain disputed decisions.
An app submission is only part of a crash claim. Review the applicable policy, separate documented expenses from unresolved losses, and preserve a record of what you submit.