Negligent Deployment, Premises Duties, and Shared Fault

Identify the conduct and responsible actor

A manufacturer may design the machine, an integrator configure it, a premises owner select the route, a contractor maintain sensors, and a fleet operator control dispatch. The plaintiff must connect the asserted duty and breach to the defendant and injury. A contract assigning maintenance is relevant evidence of the arrangement, but the existence of a contract does not automatically resolve every duty to an injured third party.

Possible factual questions include whether the robot was used outside its intended conditions, a known fault was ignored, a route was blocked, an update changed behavior, or supervision was inadequate for the assigned task. These are investigation questions, not conclusions that a robot's involvement proves negligence. Product defect theories require the separate Chapter 82 analysis. [1, §§ 82.001 through 82.005]

Activity and premises conditions

Texas distinguishes injury caused by contemporaneous activity from injury caused by a condition of the premises. The distinction can matter when a moving robot strikes someone, when a stationary robot blocks a route, or when charging equipment creates a floor hazard. The location of an injury alone does not determine the theory.

In Austin v. Kroger Texas, the Texas Supreme Court examined premises duties to an employee, open and obvious or known dangers, recognized exceptions, and separate employer duties involving instrumentalities. The decision did not concern robotics, but it shows why a warehouse injury requires precise identification of the duty and injury mechanism. Its general premises rule should not be applied without considering the decision's exceptions and the actual relationship of the parties. [4, 465 SW3d at 201 through 215]

The same precision matters for visitors. A warning sign, a restricted area, or the visibility of a robot can be relevant, but does not establish a universal defense to every claim about its movement. The analysis must identify the applicable duty and whether the asserted harm arose from activity, a premises condition, or a defect. An employer's separate duties should not be collapsed into a visitor premises analysis. [4]

Employer injuries require separate treatment

For a nonsubscriber action within Labor Code § 406.033, the employer loses specified common-law defenses, while the employee must prove negligence. Subscriber exclusive remedy under § 408.001 presents a different structure. A third-party manufacturer claim may proceed on a separate basis. The presence of multiple defendants does not justify applying the same defenses and allocation rules to every relationship. [3; 5]

Austin also explains that nonsubscriber restrictions do not remove the employee's burden to establish a duty. Thus, an employer's insurance choice and an alleged unsafe robot application must be analyzed together without treating either fact as automatic proof of liability. [4]

Proportionate responsibility

Chapter 33 generally bars a claimant's recovery when the claimant's percentage of responsibility exceeds 50 percent in an action within its scope. Section 33.003 addresses the allocation among the listed persons, subject to sufficient evidence. Section 33.004 sets procedures for designating responsible third parties, including timing and other limitations. A designation is not itself a judgment against that third party. [2, §§ 33.001 through 33.004]

Joint and several liability requires the applicable § 33.013 analysis, including its greater-than-50-percent rule and specified additional circumstances. The chapter contains scope provisions, exceptions, and definitions. A short statement that Texas always assigns each defendant only its exact percentage would omit important statutory conditions. [2, §§ 33.002, 33.011, and 33.013]

Autonomous software is not automatically a separate legal person to which a jury assigns a free-standing percentage. The claim and evidence should identify the responsible parties and conduct under the governing law. A fleet cannot necessarily remove its own responsibility merely by saying the algorithm made the decision, and a developer is not necessarily liable for every operator's later misuse. [1; 2]

Evidence connects control to causation

Incident reconstruction should preserve relevant versions, configuration, maintenance, alerts, sensor data, remote commands, route changes, and witness accounts. Texas preservation duties depend on the circumstances identified in Brookshire Brothers v. Aldridge, including reasonable anticipation of a claim and relevant material evidence. They do not require keeping every robot log forever. [6, 438 SW3d at 20 through 21]

The investigation should separate what the data establishes from what remains uncertain. A remote command recorded after contact may not explain the preceding behavior. A missing video stream does not alone prove a defect. Version and clock information can be essential to connect events across vendors and human actions. Those are recommended evidentiary practices, not a substitute for competent proof of the claim's elements.

Hypothetical shared fault

A retailer places a delivery robot on a route later narrowed by temporary displays. A maintenance contractor has also failed to complete an identified sensor repair. After an injury, the inquiry would examine route control, notice, maintenance obligations, machine behavior, and causation. Chapter 33 may then govern allocation if the action falls within its scope. It does not supply the missing proof that either party breached a duty.