Insurance Broker Requirements Your Warehouse Customer Will Write Into the AMR Deployment MSA
A clean certificate can hide endorsement gaps that leave AMR makers uninsured.

A warehouse customer’s AMR deployment MSA requires more than proof of insurance. It requires policy terms that support the promised coverage, limits, additional insured status and waivers. An insurance broker for autonomous systems and robotics companies must review the actual endorsements and exclusions, because a complete certificate can conceal gaps that leave the maker’s contractual obligations uninsured.
Why warehouse customers write insurance requirements into AMR deployment MSAs
A warehouse operator introduces shared liability exposure when it deploys an AMR fleet among workers and equipment. Its existing general liability policy was not written specifically for that exposure. After an incident, responsibility may be disputed among the AMR maker, the software layer and the facility operator. Liability attribution is not settled law. The MSA insurance exhibit therefore gives the customer a contractual way to shift financial exposure toward the party deploying the technology.
That transfer is a normal part of how an enterprise manages risk and does not show hostility toward the maker. The exhibit usually begins as a technology-vendor template, with hardware-deployment requirements added. Its provisions reflect the customer’s procurement standards independently of any assessment of the maker’s existing insurance. This distinction explains a common mismatch. A policy package adequate for the maker’s previous business may not meet the obligations attached to its first warehouse deployment.
The standard coverage lines an AMR MSA insurance exhibit will name
General liability is the foundational line for bodily injury and property damage arising from the maker’s operations on the customer’s premises. Technology errors and omissions addresses a different exposure. It is designed for claims arising from failures in the software, navigation logic or sensor systems directing the AMR’s behavior. The customer is buying a technology-dependent outcome. Both lines may therefore appear in the exhibit, with their terms deciding how each responds.
Cyber liability is designed for losses arising from attacks on the networked fleet or its control platform. WiBotic’s Ben Waters notes that cybersecurity requirements are growing as diverse AMR fleets share infrastructure and charging systems. Equipment coverage serves a separate purpose again. Inland marine or equipment insurance covers the physical units deployed at the customer’s facility, while standard commercial property insurance is designed for fixed locations and not for mobile equipment working off the maker’s premises.
Umbrella or excess coverage supplies limits above primary coverage where its terms apply. The customer usually seeks this extra layer to reach the aggregate limits it requires. It does not replace the underlying coverage lines. Workers’ compensation and employer’s liability also enter the exhibit when the maker’s personnel visit for installation, maintenance or incident response. A single policy described as “business insurance” does not establish that all these requirements have been met.
Minimum limits and how enterprise MSA templates arrive at them
The required limits usually come from enterprise vendor-management templates, without a new calculation for each maker. When hardware is deployed with software, the requirements are higher than for software alone. A physical machine working among workers brings bodily-injury and property-damage exposure that a purely digital service does not have. General liability and umbrella requirements rise accordingly. The figures express the customer’s required financial protection, which may differ from the limits available under the maker’s current package.
There is no single authoritative limit schedule for AMR deployments. Requirements vary by customer and deployment size, with limits in the millions and higher layers supplied through umbrella or excess insurance. The comparison must remain line by line. A large combined limit does not establish compliance if a required primary line falls short. Per-occurrence and aggregate limits must also match the exhibit, including any required step-up above the primary policies.
How should an AMR maker review additional insured and waiver language?
Additional insured status gives the customer rights under the maker’s policy, within the terms of the endorsement. Certificate-holder status does not do the same job. The exhibit may require the customer to be an additional insured on both general liability and umbrella coverage. That requirement concerns whether the customer can make a direct claim under the policy after an incident. Naming the customer on a certificate is not enough to establish those rights.
Waiver of subrogation addresses what happens after an insurer pays. The customer wants the insurer to waive its right to recover from the customer, including where the customer contributed to the loss. That provision must appear in the policy endorsement. Primary-and-non-contributory wording addresses a separate question, requiring the maker’s coverage to respond first without contribution from the customer’s insurance, subject to the policy terms. Adequate limits do not resolve either requirement.
The practical review therefore moves from the certificate to the policy schedule and endorsement pages. A certificate shows policy information and limits, but it does not establish that the required wording is actually present in the contract of insurance. The endorsement pages supply the operative terms. The customer’s risk team may ask for those pages. For the maker, the distinction is between documenting a policy’s existence and demonstrating that it supports the MSA’s promised protections.
Why ISO CG 35 08 and the AI exclusion wave make a standard GL policy dangerous for AMR makers to rely on
ISO CG 35 08, effective January 1, 2026, is designed to remove bodily injury and property damage arising out of generative AI under the Products/Completed Operations Coverage Part. ISO CG 40 47, introduced at the same time, addresses bodily injury, property damage, and personal/advertising injury arising from generative artificial intelligence under CGL policies. Their scope requires careful reading. For an AMR collision or tip-over, the question is whether the injury or damage has the connection to generative AI specified by the endorsement. Autonomous navigation alone does not answer that question.
A certificate can list the required general liability limit and still leave these exclusions invisible. They appear on the policy’s schedule of forms. Additional insured status does not erase them either. If an exclusion applies to the incident and removes coverage, the insurer may deny the claim even when the insurance paperwork looks complete. The maker’s MSA obligation runs to the customer, while the exclusion governs its relationship with the insurer.
That separation is the central contractual risk. A denial under the policy does not extinguish the maker’s insurance obligation under the MSA. State regulators approved the overwhelming majority of carrier requests to file these exclusions, and the endorsements are appearing broadly at renewal across specialty and other carriers. The exclusion creates a gap if the actual forms exclude coverage for the deployed technology and the alleged cause of loss.
The cyber-physical and Tech E&O gaps that AMR MSA clauses expose
The Tech E&O line can fail at the boundary between software performance and physical harm. A navigation or task-allocation error that damages equipment or shuts down a facility is a technology performance failure. But the wording of software-only E&O may exclude bodily injury or property damage caused by the software’s output. That pushes the claim toward general liability. If the GL policy also contains an applicable exclusion, requiring both lines has not necessarily resolved the exposure.
The cyber line has its own boundary. A ransomware attack or malicious command injection that directs an AMR collision combines a network event with physical consequences. Cyber insurance limited to data and network costs does not establish protection for the resulting injury claim. A GL policy with a cyber exclusion also leaves network intrusion costs without coverage. The policies must be assessed against the same incident, because their gaps can coincide and leave no alternative route to recovery.
Fleet-level accumulation adds a different problem to the review. A software update or cloud outage can affect an entire fleet at once. Standard business interruption or property insurance is not structured to cover the customer’s production losses from a software-caused fleet shutdown. The separate policy names in the exhibit can hide how one loss cuts across software, equipment and warehouse operations at the same time.
What the safety logging and compliance documentation requirements in an MSA actually mean for coverage
Safety documentation connects the MSA’s operational provisions to the insurance claim. The insurer will examine the record when assessing the cause of loss and whether coverage applies. Simulation alone is not the whole record. AMR risk assessment frameworks need to be validated in the field, where robots work with workers and interact with the environment in which they are deployed. Documentation of that validation helps establish whether the operation met the applicable requirements at the time of the incident.
For the maker, the practical task is to maintain the records demanded by the MSA’s compliance provisions. These include pre-deployment risk assessments, obstacle detection validation, emergency stop test records and operational logs. Gaps can weaken the factual basis for a claim. An incomplete log can leave uncertainty over whether the loss arose from a covered cause or an excluded operational failure, without itself deciding the coverage outcome. The same documentation supports contractual compliance, gives underwriters information about the risk and provides evidence in a claims defense.
How a specialist broker approaches the MSA insurance exhibit differently from a generic broker
Specialist and generic brokerage differ in their review and placement processes. A standard commercial-lines submission may classify the maker as a technology vendor without examining autonomous operations. A specialist submission describes fleet size, deployment environments, safety compliance and risk management practices. Those details help underwriters decide what terms to offer. They also help the broker seek forms that spell out coverage for autonomous operations, without assuming that ordinary technology-vendor wording is enough.
The policy review must then test the exclusions identified earlier. A specialist examines the schedule for CG 35 08 and CG 40 47 and assesses how proposed coverage addresses the resulting gaps. The required endorsements receive the same scrutiny. Additional insured status, waiver of subrogation and primary-and-non-contributory terms should be confirmed before the certificate is issued.
Broker commissions are embedded in the premium whether a specialist or generic broker places the policy. Choosing a generic broker therefore does not inherently save the maker a separate specialist charge. The useful comparison is the coverage obtained. The quality of the submission affects both premium and terms, and even with specialist placement, the actual policy must be checked because a promise of coverage is not enough.
A practical checklist for reviewing the insurance exhibit before signing an AMR deployment MSA
Before countersigning, the maker should take seven questions to its broker. First, does the exhibit require additional insured status, waiver of subrogation and primary-and-non-contributory wording, and do the endorsement pages confirm all three? Second, does the GL schedule include CG 35 08, CG 40 47 or CG 40 48, which concerns Coverage B personal and advertising injury only? If so, what specialist endorsement or separate autonomous-operations policy addresses the gap?
Third, does Tech E&O address physical injury or property damage caused by the software layer, or exclude those claims and leave them to GL? Fourth, does cyber coverage cover the physical harm caused by a network intrusion, or just data and network costs? These questions need answers grounded in the wording. Fifth, does inland marine or equipment coverage apply while the units are deployed at the customer’s facility, or only while they are in transit?
Sixth, do each line’s per-occurrence and aggregate limits match the exhibit, including required umbrella or excess limits? Seventh, can the maker produce the required pre-deployment risk assessment, obstacle detection validation, emergency stop test records and operational logs? The broker’s answers should identify the relevant policy terms and unresolved gaps, so the maker can assess the obligations it is about to accept.


