How does a broker place insurance for a client deploying robots in a warehouse?
By Siddansh Bohra, CEO, Rayon · Last reviewed
Start with the contract, not the robot. The RaaS agreement or integrator statement of work sets the indemnities, the insurance requirements and who carries the risk of damage to the equipment, and those terms decide what changes on the GL, workers comp, property and business interruption policies. Read the contract, then read each line against it.
Have a client putting robots on the floor? Send us the account and we read the contract against the program. The account stays yours. Send us the account
Why the contract comes first
A client buying a robot outright has mostly a property and operations change. A client taking robots under a robotics-as-a-service (RaaS) agreement, or having an integrator install them under a statement of work, has signed a contract that may also move liability. These are the clauses to read first:
- Indemnity. Who indemnifies whom, for what, and whether the client indemnifies the vendor for the vendor's own negligence.
- Limitation of liability. Whether the vendor's liability is capped, and at what.
- Insurance requirements. Lines, limits, additional insured status, primary and noncontributory wording, waiver of subrogation, and any clause about non-standard exclusions.
- Damage to the equipment. Whether the client is responsible for loss of or damage to the robots while they are on site.
- Uptime and service credits. What the vendor owes when the fleet is down, and whether that is a credit against fees or compensation for lost production.
None of these is new to a commercial broker. What is new is that they arrive in one document the client may not show you unless you ask. Ask for the agreement and its insurance exhibit at the first mention of robots. Each clause is taken apart in the insurance clauses in a RaaS contract.
General liability
Contractual liability. CG 00 01 excludes bodily injury and property damage the insured is obligated to pay by assuming liability in a contract, except liability assumed in an "insured contract" [1]. The insured contract definition includes "that part of any other contract or agreement pertaining to your business ... under which you assume the tort liability of another party to pay for 'bodily injury' or 'property damage' to a third person or organization" [1]. An indemnity running from the client to the robot vendor will often be tested against that definition. Whether a specific clause fits it, and whether a state anti-indemnity statute limits it, is a legal question for counsel reading the contract.
Injury to the client's own employee. The employer's liability exclusion in CG 00 01 removes bodily injury to the insured's employees, but it does not apply to liability assumed under an insured contract [1]. That exception is what lets the GL policy, subject to its terms, respond when a vendor sued by the client's injured worker turns to the client under the indemnity.
Damage to leased robots. CG 00 01 excludes property damage to personal property in the care, custody or control of the insured [1]. If the RaaS agreement makes the client responsible for damage to the robots, the GL policy is not where that obligation is met. It belongs on property or inland marine cover.
Generative AI exclusions. If CG 40 47 is on the policy, it removes bodily injury and property damage arising out of generative AI [5]. It does not exclude robots, but a robot whose motions come from a model trained on data is where the wording starts to bite; see whether the CG 40 47 exclusions apply to robots.
Classification and exposure. Tell the underwriter what has changed in operations. A material change the insurer learns about after a claim is a worse conversation than one at mid-term.
Workers compensation and employer's liability
An employee injured by a robot is a workers compensation claim in the ordinary way. The added exposure is the third-party-over action: the employee sues the robot vendor or integrator, and the vendor turns to the client.
Part Two of the standard policy, WC 00 00 00 C, pays damages "for which you are liable to a third party by reason of a claim or suit against you by that third party to recover the damages claimed against such third party as a result of injury to your employee" [2]. Part Two also excludes "liability assumed under a contract" [2]. So a vendor's claim for contribution may sit in Part Two, while a vendor's claim under a contractual indemnity is the GL policy's question, through the insured contract exception above. Workers comp exclusive remedy and third-party-over rules vary by state; have counsel read the indemnity against the law of the state where the robots work.
Check the employer's liability limits against the contract and the umbrella's schedule of underlying insurance.
Property and equipment
Find out who owns the robots. If the client owns them, they are business personal property or equipment and need to be on the schedule at a value that reflects replacement cost, including integration. If the vendor owns them under a RaaS agreement and the contract puts the risk of loss on the client, the client needs cover for property of others in its care, at the value the contract uses. Read the contract's definition of loss: theft, breakdown, operator error and software-caused collision can be treated differently. For a 3PL client, read it beside warehouse legal liability; see 3PL insurance requirements with warehouse robots.
Equipment breakdown cover is worth checking on its own terms, including how it treats electronic data and controls.
Business interruption
The ISO Business Income (and Extra Expense) Coverage Form, CP 00 30 [4], pays for loss from a "suspension" of operations that "must be caused by direct physical loss of or damage to property" at the described premises [3]. The same form says it will not pay business income loss when a suspension is caused by destruction or corruption of electronic data, except under the Interruption of Computer Operations additional coverage, which carries its own limit shown in the declarations [3].
A robot fleet stopped by a software fault, a failed update or a vendor outage, with nothing physically damaged, does not meet the form's physical loss trigger. The client's remedy for that is in the RaaS agreement's service credits and in any cyber or system failure cover, not the property policy. Read the service credit clause with the client so they know the size of the gap. The covers that can respond without physical damage are in business interruption for a robot software failure.
Cyber
Robots that connect to the client's network or to the vendor's cloud for fleet management and software updates add operational technology to the cyber exposure. Check whether the client's cyber policy covers business interruption from a system failure as well as an attack, whether it extends to systems the client does not own but depends on, and whether it excludes operational technology or bodily injury and property damage. Wordings differ widely, so read the one on the policy.
Umbrella and excess
Check three things: that the robot contract's limits requirements are met across primary and umbrella; that the umbrella's schedule of underlying insurance matches the primary policies as now endorsed; and whether the umbrella carries its own AI or contractual liability restrictions that the primary does not.
Certificates
A certificate of insurance does not change the policy. The ACORD 25 says it "does not affirmatively or negatively amend, extend or alter the coverage afforded by the policies below", and that if the certificate holder is an additional insured, "the policy(ies) must be endorsed" [10]. If the RaaS agreement requires additional insured status for the vendor, the endorsement has to be on the policy before the certificate says so. Marketplaces make the same demand of sellers; Amazon's seller insurance requirements are one example.
What to ask the client
- The RaaS agreement, integrator SOW or site-access agreement, with its insurance exhibit.
- Who owns the robots, and what the contract says about damage to them.
- Make, model, number of units and the task.
- Where they work: fenced cell, shared aisles, or alongside people.
- What decides how they move: programmed paths, rules-based navigation, or a learned model.
- How software is updated, and who can push updates.
- The integrator's risk assessment, and which standard it follows.
What underwriters and loss-control reps are likely to ask
OSHA says there are currently no specific OSHA standards for the robotics industry [6]. That leaves the consensus standards, and the risk assessment written for the installation, as the documents an underwriter or loss-control rep can ask to see. Know which standard applies:
- ISO 10218, through ANSI/A3 R15.06-2025. The US industrial robot safety standard, harmonized with ISO 10218-1:2025 and ISO 10218-2:2025, covering the robot, its integration into a robot cell, and use of the cell [8].
- ISO 3691-4:2023. Safety requirements for driverless industrial trucks and their systems; ISO's own examples include automated guided vehicles and autonomous mobile robots [7].
- ANSI/A3 R15.08. Industrial mobile robots, in three parts: the individual robot, integration of IMR systems, and, in Part 3 published in 2026, the continued safe use of IMR applications by users [9].
A standard named in a vendor brochure is not the same as a risk assessment written for the client's site. Ask for the site document. Whether compliance changes terms is the underwriter's call; it does help them see the risk. Each standard, and the questions that follow from it, is in ISO 10218, ISO 3691-4 and R15.08: what underwriters ask.
When to bring in a specialist
When the contract asks for something your markets will not write by endorsement: cover for leased robots at contract value, an AI exclusion the incumbent will not remove, a contractual indemnity broader than the GL will follow, or business interruption from a robot outage with no physical damage. Those are placements, not paperwork.
If one of your accounts is putting robots on the floor, send us the account. We read the contract against the program, write back each requirement and the policy that may respond to it, subject to that policy's terms, and say where your existing markets can close a gap by endorsement. You keep the account and the renewal.
Sources
- ISO CG 00 01 04 13, Commercial General Liability Coverage Form
- NCCI WC 00 00 00 C, Workers Compensation and Employers Liability Insurance Policy
- ISO Business Income (and Extra Expense) Coverage Form
- Ericksen Krentel, Business Interruption Insurance: Hope for the Best, Prepare for the Worst (identifies the form as CP 00 30 10 12)
- ISO CG 40 47 01 26, Exclusion: Generative Artificial Intelligence
- OSHA, Robotics: Overview
- ISO 3691-4:2023, Industrial trucks — Safety requirements and verification — Part 4: Driverless industrial trucks and their systems
- ANSI Blog, What Is ANSI/A3 R15.06-2025 / ANSI/A3 R15.06-3-2025?
- A3 Store, ANSI/A3 R15.08 Industrial Mobile Robots, Parts 1, 2 and 3
- ACORD 25, Certificate of Liability Insurance (sample published by NYC Department of Buildings)
How these articles are written and checked. General information, not legal advice or an interpretation of your policy. Policy forms and endorsements control. Form numbers are © Insurance Services Office, Inc. and are cited for reference.