Why these mistakes keep happening
Business interruption (BI) claims now average more than $950,000, 70% higher than the average property damage claim. Yet, many continuity teams are still planning for outdated failure modes. You're modeling downtime based on historical norms that no longer apply, and your insurance strategy hasn't adapted to the structural changes driving these costs.
The issue isn't ignoring BI risk, but assessing it through an outdated lens. Supply chains are more fragile, restoration timelines are longer, and the impact of each additional day offline is growing faster than your loss projections account for.
Here's where teams consistently go wrong, and how to correct course before your next incident exposes the gap.
Mistake 1: Treating supply chain delays as someone else's problem
Why it happens: Your continuity plan focuses on your own recovery timeline. You've mapped your Recovery Time Objective (RTO) for critical systems, identified alternate facilities, and documented your restoration sequence. Supply chain dependencies appear as a separate line item, managed by procurement or operations.
The consequence: When a fire shuts down your production line, you find that replacement parts for specialized equipment now take four months instead of six weeks. Your insurer covers every day you're offline, but your Business Interruption Coverage limit was calculated assuming the old timeline. The claim balloons past your sub-limit before you're halfway through restoration.
The fix: Map your critical supplier dependencies into your BI exposure calculation. For each key production asset, document lead time for replacement parts, number of alternative suppliers globally, and whether those suppliers share common dependencies. Build these extended timelines into your BI limit adequacy review. If your current limit assumes 60 days of downtime but analysis shows 120 days is realistic, you're underinsured by half.
Mistake 2: Calculating BI limits based on direct revenue loss alone
Why it happens: The standard formula looks clean: daily revenue × estimated downtime period = BI limit needed. Your CFO approves because the math is straightforward and the premium is manageable.
The consequence: Fire and explosion account for more than 40% of total BI claim value, with the average claim now exceeding $950,000. But your BI limit is $500,000 because you only modeled lost sales. You didn't account for compounding costs: expedited shipping, penalty clauses, increased labor costs, or tariff surcharges on replacement materials.
The fix: Expand your BI exposure model to include extra expense coverage for logistics and overtime labor, contractual penalties, increased cost of materials due to tariffs, and extended indemnity periods for ramp-up time. Review your BI limit annually against these expanded categories, not just against last year's revenue.
Mistake 3: Assuming natural catastrophe BI ends when the building reopens
Why it happens: Your disaster recovery plan focuses on facility restoration. Once the roof is repaired and power is restored, you mark the incident closed.
The consequence: Hurricane Helene struck in September 2024, and many BI claims remain unresolved because businesses are still recovering. The cascading effect extends beyond physical damage. When infrastructure like roads and utilities stays offline for months, your facility might be operational, but your suppliers can't deliver and your logistics can't ship. Your BI claim stays open, compounding the loss.
The fix: For natural catastrophe scenarios, model BI exposure in three phases: direct facility restoration, infrastructure recovery, and supply chain normalization. Document the critical infrastructure your operation depends on. Establish early contact with infrastructure authorities to get realistic restoration timelines, and communicate those timelines to your adjuster immediately. Don't let your insurer close the claim based on your facility status if the broader ecosystem hasn't recovered.
Mistake 4: Ignoring the cyber-BI intersection in your coverage structure
Why it happens: You treat cyber incidents as IT problems covered under your Stand-Alone Cyber Policy, and BI as a property insurance matter. The two seem separated in your insurance program.
The consequence: Ransomware, cloud outages, and flawed software updates are now significant drivers of large BI losses. When a ransomware attack takes down your production systems, you file a cyber claim for the extortion payment and forensics, but the 14 days of lost production falls into a coverage gap. Your cyber policy has a 12-hour waiting period for Business Interruption Coverage, but your property Business Interruption Coverage excludes cyber causes of loss.
The fix: Review both your cyber and property policies for Business Interruption Coverage triggers and exclusions. Identify the gap: does your cyber policy's Business Interruption Coverage have adequate limits for extended outages? Does your property policy contain exclusions that bar BI claims from ransomware? If you're reliant on cloud infrastructure, model a 72-hour outage scenario and determine which policy would respond. Adjust your cyber BI sub-limits or negotiate affirmative cyber coverage in your property program to close the gap.
Mistake 5: Using outdated waiting periods that no longer match reality
Why it happens: Your Business Interruption Coverage has a 48-hour or 72-hour waiting period because that's what you've always carried. It keeps your premium manageable and seems reasonable for most incidents.
The consequence: The average value of BI claims rose by more than 30% annually in the past two years, driven largely by extended recovery timelines. Supply chains are fragile, and restoration takes much longer than it used to. Your 72-hour waiting period made sense when parts arrived in a week. Now, when each claim is getting significantly more expensive because downtime stretches for months, that waiting period is eliminating coverage for exactly the incidents that would benefit most from early intervention funding.
The fix: Model your BI waiting period against realistic restoration scenarios, not historical averages. For critical operations with complex supply chains, consider reducing your waiting period to 24 hours or eliminating it entirely, even if it increases your premium. The goal isn't to file claims for minor incidents; it's to ensure coverage responds when a major event triggers the extended downtime that's now driving claim severity. Balance the premium increase against the risk of self-insuring the first several days of a months-long outage.
Prevention checklist
Before your next policy renewal, complete these steps:
- Map supply chain dependencies for critical assets and document realistic replacement timelines under current market conditions
- Expand BI limit calculation to include extra expense, contractual penalties, tariff impacts, and extended ramp-up periods
- Model natural catastrophe BI in three phases: facility, infrastructure, and supply chain recovery
- Review cyber and property policies for Business Interruption Coverage gaps; confirm which policy responds to ransomware-driven downtime
- Assess whether your current waiting period aligns with realistic restoration timelines for your most critical operations
- Document the percentage of rebuilding costs in your property exposure that could be subject to tariff inflation
- Establish a process to communicate infrastructure recovery timelines to your adjuster during natural catastrophe claims
- Schedule annual BI limit adequacy review that incorporates supply chain analysis, not just revenue projections
Your BI exposure isn't static. The factors driving claim severity have shifted structurally, and your coverage needs to shift with them.
