Service Robot Insurance & Liability — What Facility Managers Must Know Before Deployment
At a glance: A 10-robot fleet typically adds $15,000–$30,000 to annual premiums — and the likeliest uninsured loss is an endorsement gap, not a robot failure. This guide maps five coverage lines to RFP clauses.

Illustrative example: a 600-room convention hotel. A delivery robot stops 12 centimeters short when a guest steps backward into its path — no contact, no injury. Three months later, the same robot clips a service cart: a few centimeters of judgement gap the path planner accepted, the cart topples, and a banquet server sustains a crush fracture. The adjuster's first question is the one nobody prepared for: "Does your commercial general liability policy contain a robotics exclusion?"
Most facility managers deploying service robots in 2026 have thought through floor surfaces, Wi-Fi coverage, and battery charging — the standards and maintenance topics that dominate procurement conversations. Almost none have verified that their insurance actually covers autonomous equipment operating in shared human spaces. That gap is the single largest unmanaged risk in service robot deployment today.

The Coverage Gap: Why an Existing Policy Probably Doesn't Cover Robots
Commercial general liability (CGL) policies were written for static equipment, human workers, and conventional premises risk. An autonomous robot navigating through a lobby at 2 AM fits none of those categories. Three specific gaps create exposure:
The "mobile equipment" exclusion. Most CGL policies exclude mobile equipment — a category originally designed for bulldozers and forklifts but increasingly applied to autonomous mobile robots. Facilities without a robotics endorsement may be effectively uninsured for robot-related third-party injury claims. Confirm in writing.
The "your product" and "your work" exclusions. If a robot malfunctions and damages guest property — a delivery spill on a designer suitcase, a cleaning unit's leaked solution on hardwood flooring — these exclusions may apply. The manufacturer's product liability policy becomes the relevant cover, but facilities that own robots outright can find a gap between the two policies, neither of which fully covers operational incidents.
The cyber gap. A cloud-connected robot is an IoT endpoint. A compromise of the robot's communication stack or the fleet platform is a breach vector that belongs under cyber liability, not general liability. Standard cyber policies may exclude operational technology — negotiate an IoT/OT endorsement that explicitly names autonomous equipment.
Carriers are responding: a growing number of commercial insurers now use robotics-specific questionnaires or endorsements at renewal. The trend is clear — autonomous equipment is moving from "covered by default unless excluded" toward "excluded by default unless endorsed."
The Five Coverage Lines a Robot Program Needs
| Coverage Type | Risk Scenario | Illustrative Annual Cost | Purchased By |
|---|---|---|---|
| Commercial General Liability with robotics endorsement | Third-party bodily injury or property damage from robot operation | $2,800–6,500 per $1M | Facility operator |
| Product liability | Injury or damage from design defect, manufacturing flaw, or software bug | Manufacturer's policy; $1,200–3,000 if self-carried | Manufacturer (primary) |
| Cyber liability | Breach via robot network connection, fleet platform compromise, PII exposure | $1,800–4,200 per $1M with IoT extension | Facility operator |
| Workers' compensation | Staff injury during interaction, maintenance, or manual override | Standard rates; classification may adjust premium | Employer |
| Equipment / inland marine | Physical damage from fire, water, collision, theft, vandalism | ~1.5–3% of replacement value per year | Owner |
Commercial general liability with robotics endorsement
This is the foundation. Without the endorsement, standard CGL definitions leave autonomous mobile equipment in a gray area that adjusters resolve against the policyholder. Three terms to negotiate:
- Coverage trigger. Occurrence-based coverage is strongly preferred over claims-made: a navigation error in March may not surface as a discovered injury until June.
- Aggregate limits. A single incident in a crowded venue can generate claims from multiple plaintiffs. Facilities running several robots in high-traffic environments should evaluate higher aggregate limits.
- Defense costs. Robotics claims often involve technical expert testimony and accident reconstruction. Outside-limits defense is worth the premium increment.
Product liability
Under a CapEx purchase, the manufacturer's product liability policy is the primary cover for design-defect claims. Under RaaS or operating lease, the vendor retains ownership and typically carries it — but the facility's operational negligence (charging dock placement, failure to keep corridors clear) can shift liability back. The contract must state which party's policy is primary per claim type.
Cyber liability
A fleet of 10 connected robots is 10 additional network endpoints, each with an operating system, a wireless stack, and a telemetry uplink. Confirm the IoT/OT endorsement explicitly covers autonomous mobile equipment, and that patching cadence and credential hygiene are contractual, not voluntary.
Illustrative Claim Scenarios
Scenario 1 — the obstacle-avoidance edge case (illustrative). A cleaning robot in a hospital corridor detects a visitor's rolling suitcase and stops; it does not detect the visitor's ankle a few centimeters behind the suitcase, outside the near-field blind spot. The next planning cycle initiates a slight turn to pass — and the drive wheel rolls over the foot. Fractured metatarsal, surgery, rehabilitation. The hospital's CGL covered the medical costs; the carrier added a robotics sublimit and required semi-annual safety audits.
Scenario 2 — the software-update cascade (illustrative). A hotel chain's delivery fleet receives an over-the-air firmware update that regresses the elevator-interface module. Three robots enter elevators as the doors close, damaging door mechanisms and sensor arrays. The vendor's product liability covered the robot damage; the hotel's property policy covered the elevator repairs minus a standard deductible. The deductible — and the uncovered robot-side learning curve — was the exposure a robotics-specific rider would have reduced.
Scenario 3 — the untrained staff member (illustrative). A night-shift worker finds a delivery robot stopped in a corridor, assumes it is malfunctioning, and pushes it toward the charging dock. The unit tips. Workers' comp claim, and an OSHA finding that the facility had not trained night-shift staff on robot interaction — only day-shift supervisors. A shift-coverage gap in the training program became a liability.
The pattern in every case: the damage is real, the amounts are material, and the coverage gap sits in the fine print nobody read before deployment.

Who Pays? Purchase vs. Lease vs. RaaS
The acquisition model directly determines who bears insurance responsibility.
Capital purchase (CapEx)
The facility owns the robot and carries all five lines: CGL with robotics endorsement, equipment coverage, cyber, workers' comp, and contingent product liability in case the manufacturer's policy leaves gaps. Illustrative annual cost for a 5-robot fleet: $8,000–$18,000, depending on facility type, claims history, and limits. Model it into the ROI — most procurement spreadsheets omit it entirely.
Operating lease
The lessor carries equipment coverage. The facility carries CGL, cyber, and workers' comp; product liability is typically the manufacturer's, but the lease should confirm it in writing. Check whether the lease requires naming the lessor as an additional insured — that can raise premiums.
Robot-as-a-Service (RaaS)
The vendor owns the robot and typically carries equipment and product liability. The facility carries CGL, cyber, and workers' comp — and the RaaS contract should explicitly indemnify the facility for vendor-side defects. The most dangerous RaaS contracts are silent on indemnification. Before signing, require a certificate of insurance naming the facility as additional insured — requested minimums are commonly $2M general liability, $2M product liability, and $1M cyber liability.
Insurance Clauses Your RFP Should Carry
Well-structured RFPs specify door widths, Wi-Fi signal strength, and elevator integration protocols. They rarely specify insurance requirements — an omission no amount of operational planning can close.
| RFP Requirement | What to Ask | Red Flag If |
|---|---|---|
| Vendor insurance certificate | COI naming buyer as additional insured, with 30-day cancellation notice | Vendor cannot produce a COI within 5 business days |
| Product liability minimums | $2M per occurrence, $4M aggregate | Vendor offers less, or calls product liability "not applicable" |
| Cyber minimums | $1M with IoT/OT endorsement | Cloud-connected platform with no cyber coverage |
| Indemnification | Mutual indemnification with carve-out for vendor's sole negligence | Unilateral indemnification in the vendor's favor |
| Subrogation waiver | Mutual waiver of subrogation for property damage | Vendor refuses — their insurer could sue you after paying a claim |
| Contractual liability | Coverage broad enough to back the indemnity obligations | COI shows no contractual liability |
What Carriers Want Before They Quote
Carriers increasingly require structured risk assessments before quoting coverage for autonomous equipment. Five factors:
- Safety certification documentation — ISO 13482 or UL 3300 certification for each robot model deployed.
- Formal staff training program — documented training for everyone who interacts with robots, with completion dates and refresher schedules.
- Incident reporting protocol — a written procedure for near-misses and actual incidents, with root-cause analysis and corrective action.
- Environmental risk assessment — a documented survey of high-risk zones (narrow corridors, blind corners, floor transitions, high-traffic intersections) with mitigation per zone.
- Fleet management and remote monitoring — real-time monitoring, remote-stop capability, and audit-log retention of at least 90 days.
Facilities that present all five criteria normally remain on standard terms. Facilities that cannot may face surcharges or declination — pushing them into the surplus-lines market, where premiums are multiples of standard rates.
Illustrative Cost Ranges by Fleet Size
| Fleet Size | Annual Premium Range | Per-Robot | Key Cost Driver |
|---|---|---|---|
| 1–2 robots | $4,000–8,000 | $2,000–4,000 | Minimum endorsement premiums |
| 3–5 robots | $8,000–18,000 | $2,000–3,600 | Aggregate limits; cyber endorsement |
| 6–10 robots | $15,000–30,000 | $1,500–3,000 | Multi-site exposure premium |
| 11–20 robots | $25,000–55,000 | $1,250–2,750 | Cyber scaling; equipment schedule |
For multi-site programs, model insurance per site rather than per robot — each facility introduces environmental risk factors that carriers price independently.

Six Actions to Take Before the Robots Arrive
Insurance is the backstop. Mitigation is what stops claims from reaching it.
- Request the vendor's risk assessment documentation. ISO 13482 requires manufacturers to identify every reasonably foreseeable hazard. If the supplier cannot produce it, the product has not been through a structured safety evaluation — and your carrier will price accordingly.
- Walk the facility with your insurance broker before deployment. Identify the highest-risk zones and document mitigation for each. Demonstrating proactive risk management frequently improves underwriting terms.
- Require a contractual incident-response SLA. Telemetry and video data within 24 hours, written incident analysis within 48. The first 72 hours of evidence collection determine the trajectory of a claim.
- Train every shift, not just supervisors. Night-shift and weekend staff need the same robot-interaction training as day-shift leads. Keep attendance records — carriers ask after an incident.
- Disclose robot deployment proactively at renewal. Mid-term discovery can trigger a coverage review; renewal disclosure lets the broker negotiate from a position of transparency.
- Refresh the vendor's certificate of insurance annually as a condition of continued operation. Coverage carried at signing may be reduced by renewal.
Robot insurance is the difference between a processed claim and an uninsured loss coming out of the operating budget — and the time to close the gap is before the robots arrive, not when the adjuster calls. AOMAN FUTURE ships per-market compliance documentation with every deployment, so your broker can price against real documents: the AOMAN D1 delivery robot, AOMAN C1 floor scrubber, AOMAN C2 Pro compact cleaner, and AOMAN G1 guidance unit. Contact us with your coverage questions.
