Skip to content

For manufacturers, 3PLs and fulfilment operators

Your robot contract moved risk onto you. Here's how to see it.

When you lease robots as a service or have an integrator build a cell, the contract decides who pays when something goes wrong: an injured employee, a damaged robot, a stopped line. Those contracts are written by the vendor or integrator, and many put more of that on you than you would expect. Your insurance was set up before the robots arrived. We read the two side by side.

Get a quote

What a robot contract can move onto you

  1. IndemnityYou may agree to defend and pay for the vendor's losses, including some caused by the robot itself.
  2. Limitation of liabilityIn published vendor terms we reviewed, the vendor's liability is capped at twelve months of fees, while the customer's indemnity to the vendor sits outside the cap.
  3. Insurance requirementsLimits you must carry, the vendor named as additional insured, a waiver of subrogation, coverage that must be primary.
  4. The leased robotYou may be responsible for damage to equipment you don't own, from the day it arrives.
  5. DowntimeA service credit refunds part of the fee. It doesn't pay for the orders you couldn't ship, and business income insurance on the standard form needs physical damage first.

Where it shows up

At renewal, an application asks about automation, or an underwriter adds an exclusion you didn't notice. Or at a claim, when the vendor's insurer, your insurer and your workers comp carrier each point to the contract. We look for it before either.

Who it's for

  1. Manufacturers running their first cobot cell or robot line.
  2. 3PLs and warehouses adding autonomous mobile robots, often under RaaS.
  3. E-commerce brands running their own automated fulfilment.
  4. Anyone renegotiating a RaaS agreement at renewal.

Your broker stays your broker

We read the contract and the program, and we share the read-back with your broker if you want us to. If a new policy is needed and your broker's markets can't write it, we quote that one policy. The rest of your program doesn't move.

Send your certificate and your robot contract.

Your certificate of insurance lists every policy and limit you carry. The RaaS agreement or SOW shows what they now have to answer for. Send both and we come back with quotes for the gap. Prefer a read-back first? The free deployment risk review is on the home page.

  1. 1Upload your certificate and contractThe ACORD 25 your broker already sends out, plus the RaaS agreement or SOW if there is one.
  2. 2We read themEvery policy, limit and renewal date, against what the contract asks for.
  3. 3You get quotesFor the cover that closes the gap, with what differs marked.

Questions

It depends on the policy, the robot and the contract. Your general liability, workers comp, property and business interruption policies may each respond to part of a robot loss, subject to their terms. The contract can change which one, and can add obligations none of them were bought for. That is what we check.

Not as a rule. ISO's generative AI exclusions, CG 40 47, CG 40 48 and CG 35 08, are aimed at generative AI. A robot running fixed, programmed logic is generally not caught. Robots driven by learned models, and broader AI exclusions some insurers write, are what to check.

No. We work alongside your current broker.

Risks located in Illinois today. For other states, send it anyway and we'll tell you before doing any work whether we can place it.