Autonomous Fleet Operations
Available through: your broker, on a non-admitted basis
Who buys it
Operators of 10 to 500 autonomous vehicles. This is fleet cover for the business running the vehicles, not cover for the vehicles themselves and not cover for the technology that drives them.
Written for
- Robotaxi fleet operators and their fleet partners
- Autonomous delivery van operators
- Hub-to-hub autonomous trucking carriers
- Campus, airport and industrial shuttle operators
Not written for
- Individual car owners, and personal auto of any kind
- AV developers' own product liability
- Primary auto, which this sits above rather than replaces
Coverage
| Coverage | What it covers | Basis |
|---|---|---|
| Excess auto liability | Third-party bodily injury and property damage from autonomous operation, above your primary auto limit or self-insured retention. | Third party |
| Software recall and fleet grounding | Lost revenue and extra expense when a software defect, a manufacturer stand-down or a regulator grounds your fleet. | First party |
| Remote assistance error | Liability arising from instructions given by remote assistance or teleoperation staff. | Third party |
| Operational design domain | Incidents that happen while the vehicle is outside its approved operating domain are covered, not excluded. | First partyThird party |
| Cyber-physical | Bodily injury and property damage caused by a cyberattack on the vehicle or on fleet systems. | First partyThird party |
| Sensor and compute damage | Physical damage to lidar, radar, cameras and onboard compute, including calibration after repair. | First party |
| Regulatory proceedings | Defense costs in federal crash-reporting and defect investigations, and in state permit suspension actions. | Regulatory |
| Incident response | Crash reconstruction, data preservation and crisis communications after a serious incident. | First party |
One fleet policy, rated per vehicle with a per-autonomous-mile component. Indicative cover for a line in development, not a schedule of insurance and not an offer to quote, and the policy wording governs in every respect.
Underwriting
What we ask for
- Fleet size and vehicle types
- SAE automation level
- Operational design domain: cities, roads, speeds, weather, time of day
- AV technology provider
- Remote assistance model and staffing ratio
- Primary auto program and retention
- Permits held
- Crash and incident history
What we read
- Autonomous miles
- Interventions and remote assistance events per 1,000 miles
- Reportable crashes
- Software release history
What moves price
- Operational design domain complexity
- Miles and exposure per vehicle
- Intervention rate trends
- Safety driver present or not
- The primary limit or retention we sit over
- Technology provider concentration
Standards we reference
- SAE J3016 automation levels
- NHTSA's Standing General Order on crash reporting
- State AV permits, including California DMV requirements and its $5M insurance or bonding requirement for AV manufacturers
Rated: Per vehicle per year, plus a per-autonomous-mile component. No site visit for standard accounts. Large or unusual fleets get a remote risk review.