Skip to content

Does business interruption insurance cover a robot software failure?

By , CEO, Rayon · Last reviewed

Usually not on its own. The standard ISO business income form pays only when operations stop because of direct physical loss of or damage to property, and it limits loss from corrupted electronic data to a small additional coverage. A robot fleet that stops because of a software fault, with nothing broken, tends to fall between property, equipment breakdown and cyber cover, and the RaaS contract's service credits rarely make up the difference.

Running robots under a RaaS agreement or SOW? Send the contract and your certificate, and we come back with quotes for what it asks you to carry. Get a quote

What does the standard business income form need before it pays?

The ISO Business Income (and Extra Expense) Coverage Form, CP 00 30, pays the actual loss of business income from a necessary "suspension" of operations during the "period of restoration." The suspension "must be caused by direct physical loss of or damage to property" at premises described in the declarations [1]. That is the trigger. No physical loss or damage, no claim under the main insuring agreement.

The form then deals with data directly. Business income "does not apply when a 'suspension' of 'operations' is caused by destruction or corruption of electronic data, or any loss or damage to electronic data," except under a separate additional coverage [1]. The form defines electronic data to include computer programs and software used with "electronically controlled equipment" [1]. A robot's navigation stack, fleet manager and firmware fit that description.

Two more provisions matter for short outages. The period of restoration for business income starts 72 hours after the physical loss or damage [1], so a stoppage that is fixed in two days may produce no payable loss even when the trigger is met. And the cause of loss has to be covered: the ISO special causes of loss form, CP 10 30, excludes mechanical breakdown, artificially generated electrical current that disrupts equipment, and "delay, loss of use or loss of market" [2].

What does the "Interruption of Computer Operations" coverage give back?

CP 00 30 adds a narrow additional coverage for a suspension "caused by an interruption in computer operations due to destruction or corruption of electronic data due to a Covered Cause of Loss" [1]. Read its limits closely:

  • The limit. $2,500 for all loss in a policy year, unless a higher limit is shown in the declarations, regardless of the number of interruptions, premises or computer systems [1].
  • The causes. Where the special form applies, it is limited to the "specified causes of loss" and collapse [1]. It does include a virus, harmful code or similar instruction designed to damage or disrupt a system [1].
  • The carve-out. There is no coverage for an interruption related to manipulation of a computer system "by any employee" or "by an entity retained by you or for you to inspect, design, install, maintain, repair or replace that system" [1].

That last clause deserves attention in a robotics deployment. A RaaS vendor that pushes updates and maintains the fleet is plausibly an entity retained to maintain the system. A bad update from that vendor is an obvious way for a fleet to stop, and the form's wording points away from coverage for it.

Can equipment breakdown cover fill the gap?

Partly, and only where there is a breakdown. ISO's Equipment Breakdown Cause of Loss endorsement, CP 10 46, adds "breakdown" of "covered equipment" as a covered cause of loss. Writing about the 2013 ISO filing, Christopher Boggs summarized the definitions: breakdown means failure of pressure or vacuum equipment, mechanical failure, or electrical failure including arcing, and covered equipment includes "computer equipment," described as programmable electronic equipment used to store, retrieve and process data [3]. He also notes that when business income is included, the endorsement does not add limit; the loss is subject to the time element limit in the form [3].

Read the definition of breakdown before relying on it for software. Chubb's published businessowners sample policy is a useful example. Its Equipment Breakdown Protection coverage pays for direct loss caused by "mechanical breakdown or electrical failure to pressure, mechanical or electrical machinery and equipment," and then says that does not mean any "malfunction including but not limited to adjustment, alignment, calibration, cleaning or modification" [4]. A robot whose map is corrupted, whose sensors are miscalibrated by an update, or whose behavior changes after a model is retrained has malfunctioned, but nothing has broken. Its Electronic Data additional coverage in that sample is $10,000 per policy year unless the declarations show more [4].

So equipment breakdown is the right place for a burned-out drive motor or a failed controller board, and the business income that follows. It is not built for a fleet that stops because the software told it to.

Where does cyber cover fit?

Stand-alone cyber policies are the usual place to look for cover of outages with no physical damage. J.S. Held's playbook, written with Lockton, says cyber business interruption began with malicious attacks but now "is routinely available for outages that are not the result of an outside attack," often called system failure coverage, and that "most stand-alone cyber policies also cover, or provide an option to cover, nonmalicious system failures" [5]. It adds that waiting periods of eight to 48 hours are typical [5].

For a robot fleet, three questions decide whether that helps:

  • Is system failure included? Some policies cover only security events. Others cover non-malicious failures by option, and some forms limit outages that affect many unrelated organizations [5].
  • Is the robot fleet a "computer system" under the policy? Cyber definitions are usually written around IT. Whether robots, their controllers and the vendor's fleet-management cloud fall inside the definition is a wording question to put to the insurer in writing.
  • Is the vendor's system covered? If the outage starts in the RaaS vendor's cloud or update service, you need dependent business interruption (see below).

What about contingent business interruption on the RaaS vendor?

Two kinds exist, and they work differently.

Property dependent-property cover. ISO's CP 15 08 extends business income to a suspension caused by direct physical loss of or damage to a "dependent property," including a contributing location that delivers materials or services to you [6]. It still needs physical damage, now at the dependent property, and it says coverage does not apply "when the only loss to 'dependent property' is loss or damage to electronic data" [6]. A software outage at the vendor will not usually reach it.

Cyber dependent business interruption. J.S. Held describes it as cover for computer outages, from security events or system failures, at other organizations that disrupt the policyholder's business, and notes that its scope varies: some forms reach only IT providers, others may extend to providers of outsourced business services [5]. Corvus's 2021 description of its own contingent business interruption cover is an example of the narrower shape: loss caused by interruption of the computer system of an "Outsourced Service Provider" caused by a privacy breach, security breach or administrative error at that provider [7]. Whether a robot vendor counts as an outsourced service provider, and whether a bad software release is an "administrative error," depends on the policy's definitions.

What does the RaaS contract give you?

RaaS agreements answer downtime with service levels. Foley Hoag's October 2026 analysis says providers typically commit to uptime (giving "95% of scheduled operating hours" as an example), response times and time to repair, with remedies that commonly include "service credits, fee reductions, and termination rights for chronic underperformance" [8].

Look at what the credit is measured against. Allied Universal's published terms for its subscription security robots credit the client's account "for the hours in which Robot Services were suspended" when on-site maintenance takes more than 48 hours [9]. The same terms exclude consequential damages, including "loss of profits or use," and make no representation of availability [9]. A credit like that returns part of the subscription fee for the hours lost. It does not pay for the orders you missed, the overtime you ran, or the customer chargebacks that followed.

The contract can also move outage risk onto you. Allied Universal makes the client responsible for internet connectivity and for security measures to prevent unauthorized access [9]. If the fleet stops because your network failed, that may be your problem under the contract and outside the vendor's service levels.

What should an operator check?

  • Your business income form, edition and declarations: is there a higher limit for Interruption of Computer Operations than the $2,500 default?
  • Whether equipment breakdown is on the policy, whether it covers the robots (owned or leased), and what it says a breakdown does not include.
  • Whether your cyber policy covers system failure, whether the robots and the vendor's platform are within its definition of computer system, and what the waiting period is.
  • Whether cyber dependent business interruption reaches the RaaS vendor.
  • The RaaS service levels: what is measured, what the credit is worth, and whether chronic failure gives you a way out.
  • Your extra-expense plan: how you would keep shipping with the fleet down, and what that would cost.

None of these lines will respond to every robot outage, and some outages will not be insured at all. The point is to know which ones before they happen. A 3PL should read this beside 3PL insurance requirements with warehouse robots. Rayon reads your property, equipment breakdown, cyber and RaaS documents together and works with your current broker on what to add. A free deployment risk review is the place to start.

Sources

  1. ISO CP 00 30 10 12, Business Income (and Extra Expense) Coverage Form
  2. ISO CP 10 30 09 17, Causes of Loss – Special Form
  3. Christopher J. Boggs, ISO Commercial Property Changes – Part 4 – New Endorsements, MyNewMarkets (Mar 2013)
  4. Chubb, Businessowners Policy sample (Equipment Breakdown Protection; Electronic Data)
  5. J.S. Held, Cyber Business Interruption Playbook: A Guide to Response & Recovery (with Lockton)
  6. ISO CP 15 08 10 12, Business Income from Dependent Properties – Broad Form
  7. Corvus Insurance, Contingent Business Interruption and Cyber Insurance Coverage (updated Sep 2021)
  8. Foley Hoag, Robotics-as-a-Service: Structuring Licensing Agreements for Robotics Companies (Oct 2026)
  9. Allied Universal, Robot Machine-as-a-Service (RMaaS) Terms

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.