Insurance for Autonomous Physical Systems

Published October 18, 2026

Law checked through October 18, 2026.

Required insurance depends on the machine and operation. Texas automated vehicles must carry legally required coverage for their type and use; automated TNC rides have a specific Insurance Code provision; personal delivery devices require at least $100,000 in general liability coverage. Drone and other robot deployments need a separate review of applicable mandates, policies, exclusions, and contractual requirements. No single robotics policy or Texas insurance section supplies every needed coverage. [1; 2; 3]

Separate legal requirements from risk choices

The first step identifies the insured entities, equipment, activities, territory, people exposed, and potential losses. Bodily injury, property damage, cargo, damage to the robot, interruption, professional services, and data incidents may fall under different policy terms. A contract requiring insurance and a statute requiring it are distinct sources of obligation.

A recommended coverage schedule identifies each legal mandate and then the policy intended to satisfy it. It should also identify risks the business elects to insure beyond the mandate. The presence of a cyber or general liability policy should not be treated as proof that automobile or aviation liability is covered. The actual insuring agreement, definitions, endorsements, exclusions, limits, and conditions control.

Autonomous vehicles and passenger rides

Transportation Code § 545.455(b)(6) requires liability coverage or authorized self-insurance appropriate to the vehicle's type and use. Chapter 601 establishes Texas financial-responsibility requirements. Commercial trucking can also bring federal Part 387 requirements depending on the carrier and cargo. Driverless operation does not make those separate layers interchangeable. [1; 4; 5]

Insurance Code § 1954.003 treats an automated motor vehicle as a TNC driver for Subchapter B. The statutory coverage periods distinguish availability on the network from an accepted prearranged ride. A fleet should connect dispatch and trip records to those periods and examine coverage of the vehicle owner, platform, and contracted fleet operator. A personal-auto declaration page is not enough to establish that the commercial operation satisfies the chapter. [2]

Delivery devices and other mobile robots

Chapter 552A requires the business entity operating a personal delivery device to maintain the stated general liability coverage. That specific mandate does not apply automatically to every robot used inside a warehouse or hotel. Device classification must be determined before importing the chapter's insurance rule. [3, § 552A.0010]

For service or industrial robots, the policy analysis should describe actual operations, including sale, integration, maintenance, remote control, customer premises, and updates. Relevant questions include whether products and completed operations, professional services, contractual liabilities, and particular uses are covered or excluded. These are issues for reading the actual policies rather than assertions that every insurer uses the same wording.

Drone operations

Part 107 itself should not be presented as a universal liability-insurance mandate. Air-carrier operations can raise the separate requirements in 14 CFR Part 205, while customers, property owners, public contracts, or individual approvals may impose additional conditions. Hull and payload coverage address different losses from liability to people or property. [6; 7]

The business should identify aircraft, pilots, authorized operations, operating territory, payload, and any BVLOS or delivery authority when checking the policy. A policy written for a limited inspection service may not answer a later package-delivery model. The regulator's approval and the insurer's agreement to cover the activity are separate questions.

Workforce, contracts, and claims

Texas workers' compensation status affects employee injury remedies. Workers' compensation, employer liability, general liability, and a third-party product claim should not be collapsed into a single coverage assumption. A nonsubscriber's occupational injury arrangement is not automatically the statutory workers' compensation coverage that produces subscriber exclusive remedy. [8; 9]

An indemnity clause and additional-insured requirement also need separate analysis. Coverage may depend on an endorsement rather than the certificate alone. Construction projects can trigger Texas restrictions on indemnity and additional insurance, with statutory scope and exceptions. The agreement should not promise protection broader than the law permits or the actual policy provides. [10]

Information supporting an insurance review

A useful underwriting submission describes the task, operating limits, safety evidence, supervision, maintenance, software changes, claims history, data practices, and incident response. These are recommended materials for an informed discussion, not a prediction that every underwriter requests the same information. Material changes should be checked against disclosure, reporting, and consent provisions in the policy.

After an incident, notice to an insurer is distinct from notice to a regulator or affected individuals. The relevant policies may require prompt reporting, cooperation, preservation, and controls on admissions or voluntary payments. The business should identify those terms before a crisis and preserve factual evidence without assuming that a statutory report also satisfies an insurance condition.