Does the CG 40 47 generative AI exclusion apply to a client's robots?
By Siddansh Bohra, CEO, Rayon Insurance · Last reviewed
Not to robots as such. CG 40 47, CG 40 48 and CG 35 08 exclude injury or damage "arising out of" generative artificial intelligence, defined as a machine-based learning system or model trained on data that can create content or responses. A robot running programmed motions is generally outside that definition; a robot whose movements come from a learned model, and any policy carrying a broader carrier-written AI exclusion, is where to look closely.
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
What do the three ISO forms remove?
Verisk's ISO unit published the three forms as optional endorsements with a January 2026 edition date [4]. Each is one page.
| Form | Attaches to | Removes |
|---|---|---|
| CG 40 47 01 26 | Commercial General Liability Coverage Part | Bodily injury and property damage under Coverage A, and personal and advertising injury under Coverage B, arising out of generative AI |
| CG 40 48 01 26 | Commercial General Liability Coverage Part | Personal and advertising injury under Coverage B only |
| CG 35 08 01 26 | Products/Completed Operations Liability Coverage Part | Bodily injury and property damage arising out of generative AI |
For a client running robots on its own floor, CG 40 47 is the one that matters. The general liability policy is where a claim lands when a robot injures a visitor, a contractor's worker or a customer's driver, or damages someone else's property. The insuring agreement in CG 00 01 pays sums the insured becomes legally obligated to pay as damages because of bodily injury or property damage to which the insurance applies [8]. CG 40 47 narrows "to which this insurance applies". CG 40 48 leaves Coverage A alone and only touches Coverage B, so it does not reach a robot collision. CG 35 08 sits on a separate products/completed operations coverage part, which matters more to an integrator or reseller whose finished work or product is out in the world than to the operator.
How does the ISO definition work?
All three forms use the same definition: "a machine-based learning system or model that is trained on data with the ability to create content or responses, including but not limited to text, images, audio, video or code" [1] [2] [3]. The trade association for independent agents reports that Verisk based it on existing government and NAIC definitions [4].
Read it as three tests that all have to be met:
- A machine-based learning system or model. Software that learns, rather than software that only follows instructions written by a person.
- Trained on data.
- With the ability to create content or responses. The list after "including but not limited to" is open, so text, images, audio, video and code are examples, not limits.
The trigger is "arising out of", with no exception for human review and no carve-back in any of the three forms [1] [2] [3]. The existing guide on what CG 40 47 removes from a contractor's policy covers the same wording from the construction side.
Which robots are generally outside it?
Conventional industrial robots are programmed, not trained. OSHA's Technical Manual defines an industrial robot as a reprogrammable, multifunctional manipulator that moves material, parts or tools "through variable programmed motions", and says most robot systems are set up by a trained programmer using a teach pendant in manual mode [6]. A welding arm repeating a taught path, or a palletizer working a pattern its integrator wrote, does not fit a definition that starts with "a machine-based learning system or model that is trained on data". Our view is that the exclusion generally does not reach those robots.
Two caveats are worth putting to the client:
- Learned components inside a programmed robot. A programmed robot may still use a trained model for one task, such as recognizing a part or a pallet. Ask whether it does. Whether a perception model that classifies an image "creates content or responses" is not settled by the form. If a claim turns on that component, expect argument.
- Code written with AI tools. The definition names code as an example of output [1]. If the robot's program or the site's control logic was drafted with a generative AI coding tool, an insurer with CG 40 47 on the policy has an argument that a resulting injury "arises out of" generative AI, the same point the contractor guide makes about AI-drafted commissioning scripts.
Which robots does the wording start to reach?
Robots that decide their own motions with a model trained on data. The clearest example is a vision-language-action (VLA) model. Google DeepMind describes its RT-2 model as a VLA model that learns from both web and robotics data, takes camera images as input, and outputs robot actions represented as tokens, "similar to language tokens", processed by standard natural-language tokenizers [7]. That is a machine-based learning model, trained on data, producing responses. Our view is that an insurer with CG 40 47 on the policy has a credible argument that a bodily injury claim caused by a movement such a model chose is excluded. No court has decided the point.
Between those two ends there is a range: AMRs that plan routes with rules-based navigation, robots that use reinforcement-learned grasping, humanoids marketed as running foundation models. You will not settle where a given robot falls from the brochure. Ask the vendor or integrator, in writing, what decides where the robot moves.
What about carrier-written "absolute" AI exclusions?
ISO's forms are not the only AI exclusions in the market. The independent agents' association reported in October 2025 that some surplus lines carriers had already implemented generative AI exclusions of their own [4]. Those wordings are not standardized, and some are much broader than ISO's.
One published example, set out in full by the law firm Hunton Andrews Kurth, was written by one insurer for its D&O, E&O and fiduciary liability products, not for general liability [5]. It removes any claim "based upon, arising out of, or attributable to" "any actual or alleged use, deployment, or development of Artificial Intelligence by any person or entity", and separately "any product or service sold, distributed, performed, or utilized by an Insured incorporating Artificial Intelligence" [5]. Its definition is not limited to generative AI: "any machine-based system that, for explicit or implicit objectives, infers, from the input it receives, how to generate outputs such as predictions, content, recommendations, or decisions that can influence physical or virtual environments" [5].
Two phrases in that definition matter for robots: "infers, from the input it receives" and "decisions that can influence physical ... environments". A robot that reads its sensors and decides how to move could be argued to fit, whether or not anything generative is involved. We have not found a filed general liability or umbrella endorsement using that wording, and we are not saying one exists. The point is that a carrier-written AI exclusion on any of the client's policies needs its own definition read, because the ISO analysis above does not carry over.
Who decides whether the exclusion is on the policy?
The insurer. All three ISO forms are optional [4], so two clients with the same base form can end up with different answers. The trade association reported that Verisk saw strong carrier interest and expected quick adoption [4]; which insurers have actually filed the forms, and in which states, is a question for state rate and form filings, not secondary reports.
What to check on the renewal
- The forms schedule on the GL quote and policy, for CG 40 47, CG 40 48 or CG 35 08, and for any non-ISO endorsement with "artificial intelligence" in the title.
- The umbrella or excess policy. It may follow the primary policy's exclusions or carry its own AI exclusion.
- The definition in any carrier AI exclusion. Does it say "generative"? Does it reach systems that "infer" or "make decisions"? Does it apply to AI used "by any person or entity", which would include the robot vendor's software?
- The robot. Programmed path, rules-based navigation, or a learned or VLA model making motion decisions? Can the vendor update the model over the air after installation?
- The contract. Read the insurance exhibit of the RaaS agreement or integrator SOW. If it requires the operator's insurance to carry no non-standard exclusions, whether an optional ISO AI exclusion breaches that clause is a question for counsel reading the contract. The other clauses to read are in the insurance clauses in a RaaS contract.
What can you do if it is there?
Ask the underwriter, in writing, how they read the exclusion against the robot as described, and whether they will remove it or schedule a carve-back for bodily injury and property damage from the named robot operation. Some will, some won't. The answer belongs in the file either way. The rest of the program is covered in placing cover for a client deploying robots. Specialist markets offering affirmative cover for bodily injury and property damage from reliance on AI outputs were reported launching in late 2025 [4]; whether one fits an operator's robot fleet depends on that market's own wording.
If you have a client with a learned-model robot, or a carrier AI exclusion you are not sure how to read, send us the account. We read the policy against the robot and the contract, write back what moved, and tell you where your existing markets can fix it by endorsement. The account stays yours.
Sources
- ISO CG 40 47 01 26, Exclusion: Generative Artificial Intelligence
- ISO CG 40 48 01 26, Exclusion: Generative Artificial Intelligence (Coverage B Only)
- ISO CG 35 08 01 26, Exclusion: Generative Artificial Intelligence (Products/Completed Operations)
- Big "I" Virtual University (Independent Insurance Agents & Brokers of America), Verisk to Roll Out New General Liability Exclusions for Generative AI Exposures (Oct. 21, 2025)
- Hunton Andrews Kurth, The Continued Proliferation of AI Exclusions (May 28, 2025)
- OSHA Technical Manual, Section IV, Chapter 4: Industrial Robot Systems and Industrial Robot System Safety
- Google DeepMind, RT-2: New model translates vision and language into action
- ISO CG 00 01 04 13, Commercial General Liability Coverage Form
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.