Why a Broker's Default Is the Wrong Starting Point
Many cyber renewals arrive with the business interruption section already filled in. It's often half the policy aggregate, sometimes a flat USD 1 million, and the explanation is usually "that's what we normally see." Nobody has checked whether that figure would cover a ransomware attack that takes your ERP down for three weeks. Your cyber business interruption limit should come from a scenario you can defend to your CFO and your board. A peer benchmark alone won't do that.
The worksheet has nine steps, grouped into five working stages. You need a finance lead who can pull monthly gross profit, an IT or security lead who will give honest recovery times, and the current policy wording. Plan for two working sessions. The output is one limit with a reason behind it, plus a list of sublimits and definitions to negotiate.
- Map the systems that generate revenue.
- Estimate how long the outage lasts, phase by phase.
- Calculate gross profit at risk per week.
- Add the slow recovery after systems come back.
- Price extra expense.
- Price data and system restoration.
- Check waiting periods and the period of restoration.
- Test sublimits and dependent business interruption.
- Stress-test, round and decide.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Steps One and Two: Find What Stops Revenue and for How Long
List the systems whose loss stops orders, production, billing or service delivery. Typically that's ERP, e-commerce, manufacturing execution, scheduling and identity infrastructure such as Active Directory. Ransomware that encrypts the domain controllers can halt all of them at once. For each system, write down what the business can still do manually and for how many days.
Then estimate the outage in phases, and resist a single optimistic number. Your IT team's recovery time objective is what they're aiming for. In a real event, recovery also waits on forensics, insurer approval and clean-rebuild work. Use the table as a template and replace the illustrative ranges with your own figures.
| Phase | What happens | Illustrative range for a mid-size firm |
|---|---|---|
| Detection and containment | Isolate the network, engage incident response, preserve evidence | 1-4 days |
| Investigation and decision | Scope the encryption, check backup integrity, decide whether to rebuild or decrypt | 2-7 days |
| Rebuild and restore | Rebuild identity, restore critical systems in priority order | 1-3 weeks |
| Ramp-up | Systems work but run at reduced capacity while backlogs clear | 2-6 weeks |
If your backups have never had a full restore test, use the top of each range. Tested immutable or offline backups shorten the rebuild phase, and underwriters will ask whether you have them.
Steps Three and Four: Gross Profit at Risk and the Slow Recovery
Cyber BI wordings measure loss in different ways. Many US-style forms pay net income plus continuing normal operating expenses. UK, Commonwealth and many European and Asian forms use a gross profit definition: turnover minus specified working expenses. Both aim at the same thing, which is revenue you lost minus costs you didn't pay because you weren't trading. For a gross profit calculation for cyber, take annual revenue excluding VAT, GST or sales tax, subtract the variable costs that stop during an outage (materials, freight, commissions), and divide by 52. Payroll usually continues, so leave it in.
Adjust for seasonality. A retailer hit in November loses far more per week than one hit in February, so use your peak-quarter weekly figure, not the annual average.
Hypothetical example: Say a 250-person distributor has USD 60 million in revenue, and variable costs equal to 65% of revenue stop when trading stops. Gross profit at risk is about USD 21 million a year, or roughly USD 400,000 a week. Three weeks fully down plus three weeks at half capacity is 4.5 lost weeks, or about USD 1.8 million.
Step four covers the tail. Some customers leave, and others send orders elsewhere for a while. If revenue runs 10% low for two months after restoration, that's roughly USD 350,000 more. Check whether the policy has an extended period of indemnity that covers this. Many cyber policies don't by default.
Steps Five and Six: Extra Expense and Restoration Cost
Extra expense coverage pays for costs you take on to keep trading or shorten the outage. Common items are overtime, temporary staff for manual order entry, expedited shipping for key accounts, rented hardware, temporary cloud environments, and outside IT contractors working around the clock. For the example distributor, USD 250,000 to 600,000 is a sensible assumption. Ask operations what they'd actually spend to protect the top 20 customers.
Restoration cost, sometimes called data restoration or digital asset cover, pays to rebuild, re-image and restore systems and data. It's often a separate insuring agreement with its own limit, so don't count it twice. A realistic ransomware downtime cost also includes items that sit elsewhere in the policy: incident response, forensics, legal counsel and any extortion payment. Payment is restricted or subject to sanctions screening in many jurisdictions. Make sure each cost appears exactly once in your model.
- Restoration of systems and data: USD 300,000-800,000 in this example, depending on how much must be rebuilt
- Hardware replacement after firmware damage ("bricking"): confirm it's covered, because many wordings exclude or sublimit it
- Outsourced IT provider rates during an incident: check whether they're on the insurer's approved panel
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Steps Seven and Eight: Waiting Periods, Sublimits and Dependencies
A limit can be big enough and still pay little if the definitions work against you. This table sets out the terms that most often drain value and what to ask for.
| Term | Red flag | What to aim for |
|---|---|---|
| Waiting period | A long wait (a day or more) for a business that loses revenue within hours | Often several hours to 12 in many markets; larger risks may accept longer in exchange for premium savings |
| Period of restoration | Ends when systems are restored, before revenue recovers | A period long enough for your ramp-up phase, or an extended indemnity period for the tail |
| Cyber BI sublimit | BI capped well below the aggregate and below your scenario | BI at full limit, or a sublimit at least as large as your scenario |
| Dependent BI | Small sublimit, or named providers only | Covers outages at the cloud, SaaS and logistics providers you rely on, at a meaningful sublimit |
| System failure | Only malicious attacks covered | Non-malicious outages included, even if sublimited |
Look closely at any cyber BI sublimit that shares the aggregate with ransom, breach response and liability. If one ransomware event consumes USD 1 million on response and extortion, your BI recovery comes out of what's left. Multinationals face another issue. Some countries, including Brazil, India and several Gulf states, restrict or require locally admitted insurance, so confirm with your broker that BI losses at foreign subsidiaries can actually be paid under the master program.
Step Nine: Stress-Test and Set the Number
Add up the base case for the example distributor. Lost income of about USD 2.15 million, plus extra expense of USD 250,000-600,000, plus restoration of USD 300,000-800,000, gives roughly USD 2.7-3.6 million. Now run a severe case: double the rebuild phase and assume a peak-season hit. If that pushes the total past USD 5 million, you've found your tail risk.
For most mid-size companies, the right business interruption limit sits between the base and severe cases. Below the base case, you're self-insuring something likely to happen. Above the severe case, you're paying for capacity you'd struggle to justify. Typical 2026 market pricing for added BI limit or a removed sublimit runs from the low thousands to the tens of thousands of USD a year per extra USD 1 million, but it varies with your controls, industry, region and contract. Get carrier quotes to confirm.
The decision rule: if your current cyber business interruption limit is below your base case, take this worksheet to your broker before renewal and ask for quotes at both the base and severe figures. Have a licensed broker or coverage counsel confirm how your policy defines loss before you sign.