Waiver of Subrogation Clauses for Autonomous Vehicle Operators
Boilerplate waivers can forfeit far more recovery for AV operators than for ordinary fleets.

Subrogation is the right an insurer acquires after paying a claim to stand in the insured's shoes and pursue recovery from the party actually responsible for the loss. Waiving that right contractually means the insurer pays and has no recourse. For autonomous vehicle operators, that waiver carries consequences far beyond what the same clause imposes on a conventional fleet operator, because the pool of parties who might bear responsibility for an AV incident is broader, harder to identify, and more valuable to pursue.
In a conventional vehicle accident, fault analysis is relatively bounded. The relevant variables are driver behavior, road conditions, and perhaps one or two other parties. Decades of negligence case law supply a settled framework for attributing fault, and the pool of potential tortfeasors is narrow enough to identify before a policy is even written.
AV operations dismantle that bounded picture. Long, Zhao, and Cai's 2026 analysis maps four distinct liability regimes across jurisdictions: driver liability, system liability, manufacturer/operator liability, and composite approaches. The legal framework for attributing fault remains unsettled, and it varies by where the incident occurs. Because AV incidents expand the pool of potential tortfeasors to include fleet owners, manufacturers, software developers, and component suppliers, and because fault in these systems is provable through data rather than narrative, the insurer's subrogation rights become both more valuable and far harder to navigate. A specialist broker familiar with autonomous systems operations, such as Risklytics, can help an operator decode exactly which parties a given waiver language forecloses before the contract is signed, ensuring that the underwriting submission itself reflects the true scope of the liability web surrounding the deployment.
Why enterprise and government contracts require waiver of subrogation clauses as standard boilerplate
Waiver of subrogation clauses appear in enterprise and government contracts not because counterparties have analyzed AV-specific risk, but because they are standard procurement boilerplate. The same language appears whether the operator is a delivery robot company or a conventional trucking firm. No one at the customer's procurement desk has thought through what these clauses mean for an autonomous system. The clause simply ships with the contract template.
The typical formulation bundles waiver of subrogation with primary and non-contributory status. The operator's policy pays first, the insurer cannot seek contribution from the customer's carrier, and the insurer explicitly waives recovery rights against the customer, even if the customer's own instructions, integration choices, or operational specifications contributed to the incident. That last phrase is the one that matters for AV operators, though it was written without them in mind.
Enterprise procurement teams treat "Primary/Non-Contributory and Waiver of Subrogation" as a checkbox, verified before contract execution. An operator who cannot produce the endorsement does not move forward. The commercial pressure to comply is immediate and real, and it lands on firms that may not yet understand what they are giving away.
Government contracts add a further layer. Insurance requirements embedded in deployment permits and operating agreements may specify coverage minimums, additional insured status, and waiver endorsements as conditions of the operating license itself, not merely as contract terms a party can negotiate. CSG South's 2025–2026 AV legislation review documents that vehicle insurance reform bills have been introduced in multiple states, though several have died in committee. The regulatory floor for what an AV operator must carry, and on what terms, is shifting in real time across jurisdictions. A waiver endorsed today may sit on top of coverage requirements that change mid-contract.
Why signing a waiver of subrogation costs an AV operator more than it costs a conventional fleet operator
When a conventional fleet operator waives subrogation against an enterprise customer, the insurer's forfeited recovery opportunity is real but bounded. The likely tortfeasors are few, the claim amounts are relatively predictable, and the customer's causal contribution is usually limited to things like premises conditions or loading errors. The waiver costs something, but the insurer can price that cost with reasonable confidence.
For an AV operator, the customer's causal contribution to an incident can be far larger and harder to separate. The customer may have specified the operational design domain, dictated geofencing parameters, integrated the AV into its own software environment, or issued operational instructions that constrained how the system behaved. Each of these is a live subrogation target that a waiver forecloses. The customer's choices are not incidental to the operation. They are constitutive of it. Whether those choices contributed to a given incident is often unknowable at contract signing, which is precisely why signing away the right to investigate that contribution is costly. Operators placing coverage with carriers who explicitly understand autonomous hardware deployments gain a critical advantage: the policy language and underwriting submission are built from the ground up to account for this multi-party liability structure, rather than retrofitted onto generic commercial auto language. Risklytics's placement approach reflects this distinction.
The scale of what is being waived has also grown. RISKWORLD 2026 presenters noted that verdict expectations in AV product liability cases are rising toward the billions. The recovery opportunity an insurer is being asked to waive is no longer a minor line item. It is a material financial decision buried in boilerplate.
How waiver of subrogation interacts across the multiple coverage lines an AV operator carries
An AV operator typically carries several distinct policies: general liability, technology errors and omissions, cyber, inland marine and equipment, and commercial auto. Each may be written by a different carrier, and each may be subject to a separate waiver of subrogation endorsement. A waiver on one policy does not automatically apply to another. That simple fact creates the coordination problem.
General liability waiver endorsements are the first item enterprise procurement checks, but GL explicitly excludes professional services. If a customer's claim arises from a software decision or an algorithmic failure, the GL waiver is irrelevant, and the technology E&O policy governs. Whether that policy carries a matching waiver is a separate question, and it is one few operators think to ask.
Cyber coverage introduces a specific gap. When a waiver of subrogation is in place on GL but not on the cyber policy, or vice versa, the operator faces uncoordinated exposure in an incident with both a bodily injury component and a software manipulation component. AV incidents can generate both simultaneously. Matthiesen, Wickert, and Lehrer identify cyber security as a growing dimension of AV claims, referencing the 2015 wireless compromise of a vehicle's braking and steering system. A cyber-physical incident of that kind produces exactly the multi-line coverage question where waiver coordination matters most.
Technology E&O is written on a claims-made basis, which introduces retroactive date and tail coverage considerations that interact with waiver endorsements. If an operator switches carriers mid-contract, the waiver on the old policy may not carry over, and the new carrier's position on waiver endorsements may differ. Inland marine policies covering sensor arrays, LiDAR units, and compute hardware in transit between test and deployment sites are a property line, not a liability line. Subrogation rights on those policies run to whoever damaged the equipment, and a waiver endorsement on a GL policy does not extend to the inland marine carrier's recovery rights unless the inland marine policy is separately endorsed. The waiver problem runs through every line the operator carries, and the gaps between lines are where the exposure lives.
What the evolving liability and regulatory landscape means for how waiver exposure will grow
The liability rules governing AV incidents are not settled, and the direction of travel is toward greater operator and manufacturer exposure. Long, Zhao, and Cai identify blurred boundaries of liability, underdeveloped mechanisms for evidence production and fact-finding, imbalanced allocation of liability, and fragmentation of the rules governing liability determination as the defining institutional problems. The practical consequence is that the recovery chains insurers can pursue are expanding as case law develops.
As those recovery chains expand, the value of the right that a waiver of subrogation forfeits grows with them. A clause signed today under settled assumptions may foreclose recovery paths that are created by court decisions or new legislation that enters into force during the contract term. CSG South's review records that vehicle insurance reform bills are pending or recently enacted across multiple states in the 2025–2026 sessions, several specifically addressing autonomous vehicles, including their insurance and liability requirements. The minimum coverage floor and the legal structure of AV liability are both in motion. A waiver endorsed under one regulatory regime may have different implications under its successor.
RISKWORLD 2026 speakers observed that it will take years for case law to address all of these factors. Operators signing long-term enterprise or government contracts are therefore agreeing to waive rights in a liability landscape that will look materially different by the contract's end. And commercial deployment is accelerating regardless. NHTSA authorized commercial deployment of Zoox robotaxis under a temporary exemption in July 2026, and California's regulatory activity shows that government contracts for AV operations are a present reality, not a future scenario. The exposure is scaling now, against a legal backdrop that has not caught up.
What an AV operator must verify before agreeing to a waiver of subrogation clause
Before agreeing to any waiver of subrogation, an AV operator should work through five distinct verification questions, each corresponding to a structural risk identified above. First, confirm that every relevant policy line carries a matching waiver endorsement, not just the GL policy the procurement team asked about. A waiver on GL that is absent from the cyber or technology E&O policy leaves gaps that AV incidents, which commonly span multiple coverage lines, will fall into.
Second, map the counterparty's actual causal exposure before signing. Document which operational parameters, integration specifications, or usage instructions the customer is dictating. Those are the facts that determine whether the waiver is forfeiting a meaningful recovery right or a nominal one.
Third, check whether the contract's waiver language is bounded or open-ended. A well-drafted waiver limits the insurer's forfeited recovery rights to claims arising from the customer's own negligence, and does not extend to product liability claims running through third parties. An unbounded waiver can inadvertently shelter upstream manufacturers or software providers.
Fourth, align the waiver with policy language at the claims-made and retroactive-date level. A switch in carriers mid-contract can strand a waiver endorsement on the old policy while the new policy carries no equivalent language. The contract and the policy must be read together, not separately.
Fifth, assess the contract term against the regulatory environment. Given that state AV insurance reform bills are active across the country, a multi-year government contract with a waiver locked in at signing should include a renegotiation or notification mechanism for material changes in the applicable liability or insurance regulatory framework. These five steps are verification work, not negotiation work. They determine whether the clause being signed means what the counterparty's template says it means, on every policy line that could respond to an incident.
Why AV operators need a specialist broker to manage waiver of subrogation across their full program
The verification framework described above requires someone who can read every policy in the program, not just confirm that a waiver endorsement was requested. The work is to confirm that it was granted, that it is consistent across lines, and that the language actually does what the contract demands. That is not the standard order of operations in a commercial insurance placement.
A generic broker placing an AV operator into standard commercial auto or technology business owner's policy forms is not positioned to identify the cross-line waiver coordination problem, because the forms themselves were not written with autonomous hardware in mind. The submission that produced those forms described a conventional tech business, not a company operating machines in the field. Submission quality is the mechanism that determines whether the endorsement holds. An AV operator whose submission documents its operational design domain, sensor configuration, software versioning, and human-override protocols gives an underwriter the information needed to write a waiver endorsement that is both appropriate and priced correctly. A generic submission produces a generic endorsement that may not hold at claim time.
Risklytics reads the policies themselves before they bind. That specific practice, a licensed broker reviewing every policy for AV operators, is the only way to catch a waiver gap between the GL and the cyber policy, or an endorsement the carrier granted in form but limited in substance through exclusionary language elsewhere. Broker commissions are built into the premium whether a specialist or a generalist places the policy. Choosing a specialist does not add expense. Choosing a generalist transfers the risk of an inadequate waiver endorsement, or an uncaught cross-line gap, entirely to the operator, and that risk has been the subject of this entire argument.


