Robot Evidence, Logs, and Litigation Holds

Identify evidence before it disappears

Robots often distribute information across onboard storage, fleet platforms, cloud analytics, mobile devices, and vendor systems. A map or configuration existing at the time of the event may be replaced by the next update. An incident response should therefore identify the relevant systems and overwrite cycles promptly. This is a practical preservation method rather than a direction to retain every routine record permanently.

The evidence inventory should distinguish original data, derived reports, video exports, model versions, calibration, alert histories, and human communications. A dashboard screenshot may omit the raw sequence or processing assumptions. Clock settings, time zones, device identity, and export methods can matter when information from different sources must be aligned.

Texas preservation duties

Brookshire Brothers v. Aldridge explains the Texas duty in terms of when a party knows or reasonably should know there is a substantial chance a claim will be filed and that evidence in its possession or control will be material and relevant. The decision also addresses the judicial analysis of spoliation and remedies. It is not a robot-specific holding, and its conditions should not be replaced with a rule that every malfunction requires unlimited retention. [1, 438 SW3d at 20 through 26]

A litigation hold should identify the incident, custodians, systems, information to preserve, and process for suspending ordinary deletion where necessary. It should include relevant updates and vendor communications, not merely the most favorable camera angle. The hold can evolve as the investigation identifies additional material evidence. The actual duty and proportional scope require the claim and facts.

Federal electronically stored information

Rule 37(e) addresses ESI that should have been preserved in anticipation or conduct of litigation, is lost because reasonable steps were not taken, and cannot be restored or replaced through additional discovery. The rule distinguishes measures addressing prejudice from the more severe measures requiring intent to deprive another party of the information's use. The standard is not strict liability for every missing file. [2, Rule 37(e)]

Rules 26 and 34 separately address discovery scope and production, including possession, custody, or control. A contract with the cloud vendor can be important to obtaining information, but the contract alone does not decide every discovery question. Data should be preserved in a usable form together with information necessary to understand it. [2, Rules 26 and 34]

Vehicle recording devices and access

Texas § 545.455(b)(2) requires the specified manufacturer-installed recording device for an automated motor vehicle. Section 547.615 addresses recording devices, disclosure, access, and exceptions. Those provisions should be analyzed separately from Chapter 550 collision duties and from broader litigation preservation. The required device is not necessarily a complete archive of every camera, lidar return, or cloud decision. [3; 4]

Federal Part 563 addresses covered event data recorders and specified data requirements. The Driver Privacy Act of 2015 provides separate ownership and access rules with exceptions. An investigator should distinguish an EDR download from other telemetry and identify the authority, consent, or process supporting the requested access. A vehicle's involvement in a crash does not make all data public. [5]

Vendor access, privacy, and confidential information

Deployment agreements should address prompt preservation, export formats, documentation, technical assistance, and the survival of access after termination. Otherwise, a business may discover that it can view a dashboard but cannot obtain the information needed to reconstruct the event. Recommendations about contractual access do not authorize a party to bypass privacy, privilege, security, or lawful disclosure restrictions.

Public agencies have additional public-information and retention obligations. Vendor possession does not automatically make information outside Chapter 552. Confidentiality and exceptions require record-specific analysis. A public-records request, litigation hold, and ordinary retention schedule are different processes and should be coordinated rather than treated as substitutes. [6, §§ 552.002, 552.101, and 552.110]

Hypothetical incident reconstruction

A service robot strikes a visitor shortly after a map change. Relevant evidence may include the old and new maps, approval history, software version, sensor calibration, remote instructions, and the physical scene. A later successful demonstration does not establish what configuration existed at the incident. The preservation record should document collection and any known gaps without silently treating reconstructed information as an original contemporaneous log.