How Long Will Your Cyber Policy Pay Lost Income? The Indemnity Period Explained
Your systems come back in ten days, but revenue takes three months to recover. Whether the policy pays for that gap depends on three clauses most buyers never read closely.
Why the claim can stop before the damage does
The question that decides most cyber business interruption claims isn't whether you were hit. It's when the policy stops counting. A ransomware attack that takes your order system offline for ten days can depress revenue for three months afterward. Customers move to a competitor, sales cycles stall, and partners hold back orders until they trust you again. If your wording ends the cyber business interruption indemnity period on the day systems are restored, most of that later loss is yours to absorb.
Three mechanisms set the length of cover:
- The waiting period: the hours of outage you absorb before income cover starts.
- The period of restoration: the window from the start of the outage until systems are, or reasonably could have been, back to their prior state.
- The extended indemnity period: an optional tail that keeps paying after restoration while revenue climbs back toward normal.
A calculation formula, usually lost net profit plus continuing expenses, then decides how much is paid inside that window. Get the window wrong and a well-calculated loss still goes largely unpaid. Get the formula wrong and a long window pays less than you expected. This piece covers both, then runs a hypothetical recovery timeline to show the difference in dollars.
How the period of restoration starts, stops and gets capped
Most cyber forms define the period of restoration along similar lines, whether they're London market wordings, North American carrier forms or policies from regional insurers in Europe, India, the Gulf or Southeast Asia. The differences sit in the details, and the details decide the claim.
The start trigger
Cover usually starts when the interruption begins, normally the moment systems degrade rather than when you discover the cause. It becomes payable only once the waiting period has passed. Waiting periods commonly run from a few hours to 24 hours, with roughly 8 to 12 hours typical for mid-market buyers. Some insurers trade a shorter waiting period for a higher monetary retention, so compare the two together.
The end trigger
This is the clause to read twice. Common formulations include:
- The date systems are restored to the same or equivalent functionality as before the event.
- The date systems could have been restored with reasonable speed and diligence. This lets the insurer cut the period short if it argues you were slow.
- A fixed outer limit, whichever comes first. Figures in the range of 90 to 180 days are common, and some larger programs negotiate longer.
The "could have been restored" language matters most for organizations with old infrastructure or thin IT teams. If your realistic rebuild takes three weeks but the adjuster's forensic expert says ten days was achievable, the gap becomes a dispute.
The outer cap
A 120-day maximum sounds generous until data must be rebuilt from partial backups, or a regulator in the EU, UK, Singapore or elsewhere requires an investigation before certain systems go back online. Ask your broker whether regulatory or law-enforcement holds extend the period or simply count against it.
Extended indemnity: paying for the customers who haven't come back
The period of restoration covers the outage. The extended indemnity period covers the hangover. It begins when the period of restoration ends and runs for a fixed number of days, commonly 30 to 180, or until revenue returns to its pre-event level, whichever comes first.
Not every policy includes it. Some carriers build in a short tail as standard. Others offer it only as an endorsement, and smaller-business packages often leave it out. Where it's available, it's frequently subject to the same business interruption sublimit as the main cover, so a long tail doesn't help if that limit is already exhausted.
How much tail you need depends on how sticky your revenue is:
- Subscription or contracted revenue (SaaS, managed services, B2B supply contracts) often recovers quickly because customers are locked in. The real risk is churn at renewal, which may fall outside any reasonable tail. Thirty to 60 days is often enough.
- Transactional and e-commerce revenue leaks to competitors during the outage and returns slowly. Ninety days or more is a sensible starting point.
- Reputation-sensitive sectors such as payments, healthcare services and professional services handling client data can face a long recovery curve after a publicized breach. Consider 120 to 180 days if the market offers it.
On cost, adding a tail is usually a modest loading on the BI portion of the premium rather than a large one. Pricing varies widely by insurer, region and loss history, so ask for it quoted as a separate line and confirm the figure with your broker.
The cyber business interruption calculation: net profit, continuing expenses and extra expense
Inside the indemnity window, most wordings pay the reduction in net profit before tax that the interruption caused, plus continuing normal operating expenses such as payroll, rent and software subscriptions you still pay while revenue is down. In practice that works out close to lost revenue multiplied by your contribution margin, adjusted for costs you saved while offline.
Adjusters and forensic accountants argue over several adjustments:
- The baseline. Most policies look at the same period in prior months or the prior year. Seasonal businesses should check whether the wording allows a trend adjustment. A retailer hit in November shouldn't be measured against an average month.
- Saved costs. Shipping, payment fees and cost of goods you didn't spend get deducted.
- Deferred versus lost revenue. If customers simply delayed orders and placed them a week later, the insurer will argue no loss occurred. Keep records showing orders were actually lost.
- Proof. Many policies cover the cost of a forensic accountant to prepare the claim, sometimes under a separate sublimit. Use it.
Extra expense coverage
Extra expense pays the reasonable costs of reducing the loss: overtime, temporary cloud capacity, manual workarounds, outsourced call centers, and sometimes expedited shipping to make up missed orders. The key limitation is that it's usually payable only within the indemnity period, and often only to the extent it reduced the BI loss. A customer win-back campaign in month three may or may not qualify. That depends on whether you bought an extended period and how the clause is written.
A hypothetical recovery timeline, priced three ways
This is a labelled hypothetical, not a real claim. Say a mid-size online distributor normally takes in $60,000 a day in revenue at a 45% contribution margin, or $27,000 of contribution a day. Ransomware hits at 02:00 on Day 0. The policy has a 12-hour waiting period. Systems are fully restored on Day 10, but customers return gradually.
| Phase | Days | Revenue vs. normal | Lost contribution |
|---|---|---|---|
| Waiting period | First 12 hours | 15% | $11,475 (uninsured) |
| Outage (period of restoration) | Day 0.5 to Day 10 | 15% | $218,025 |
| Early recovery | Days 11 to 40 | 70% | $243,000 |
| Late recovery | Days 41 to 100 | 90% | $162,000 |
| Total economic loss | Day 0 to Day 100 | $634,500 |
Now apply three policy structures, all with an adequate BI limit:
| Structure | BI paid | Uninsured share of loss |
|---|---|---|
| A: Period of restoration only | $218,025 | About 66% |
| B: Plus 30-day extended indemnity | $461,025 | About 27% |
| C: Plus 90-day extended indemnity | $623,025 | About 2% |
Under Structure A, the policy pays only about a third of the actual income loss, even though the outage itself was fully covered. Structure B closes most of the gap. Structure C covers everything except the waiting period. Extra expense follows the same logic. Assume, hypothetically, $180,000 of incident overtime and temporary infrastructure. It's likely paid under all three structures, but post-restoration win-back spending has a chance only under B or C.
Two caveats. First, a monetary retention would usually be deducted on top of the waiting period. Second, if the adjuster argues systems could have been restored by Day 7, the window shifts earlier. A pays less, and B and C also stop paying sooner, so the tail's value depends on how the end trigger is worded.
What to check before you sign, and the decision rule
Take these questions to your broker, and get answers in writing against the actual wording rather than a summary of cover:
- What exactly triggers the end of the period of restoration, and does it include "could have been restored" language?
- What's the outer cap on the period of restoration, and do regulatory or law-enforcement holds extend it?
- Is an extended indemnity period included, offered by endorsement, or unavailable? What does each option cost?
- Does the BI sublimit, not just the overall aggregate, cover a realistic 90-day loss?
- Is extra expense payable during the extended period, and does it require proof that it reduced the loss?
- Does the same structure apply to dependent business interruption (outages at your cloud, payment or logistics providers) and to non-malicious system failure, or are those shorter and lower?
- Is claim-preparation cost covered, and under what sublimit?
Red flags: a period of restoration that ends at "restoration of systems" with no tail available; a BI sublimit that's a small fraction of the aggregate for a revenue-dependent business; a waiting period over 24 hours; and dependent BI limited to named providers only.
Availability differs by region. Extended periods are well established in London and North American markets. In parts of Latin America, Africa and Asia, local admitted policies may offer shorter tails, with broader terms reached through international programs or reinsurance. Tax treatment of BI proceeds also varies by country, so involve your tax adviser and a licensed broker or coverage counsel before you finalize anything.
The decision rule: before renewal, have finance model how long revenue would take to return to 90 to 95% of baseline after a ten-day outage. Set your extended indemnity period to at least that length, then confirm the BI sublimit covers the whole curve.
Frequently asked questions
What is the difference between the period of restoration and the indemnity period in cyber insurance?
The period of restoration is the time from the start of the outage until systems are, or reasonably could have been, restored. The indemnity period is the total window during which lost income is payable. It equals the period of restoration plus any extended indemnity period you've bought. With no extended period, the two are the same and cover usually stops when systems come back.
How long should an extended indemnity period be?
Match it to how long your revenue realistically takes to recover, not how long IT takes to rebuild. Contracted or subscription businesses often manage with 30 to 60 days. Transactional, e-commerce and reputation-sensitive businesses usually need 90 to 180 days. Model it with your finance team and confirm what's available with a licensed broker.
Does cyber business interruption cover lost revenue or lost profit?
Most wordings pay lost net profit plus continuing operating expenses, not gross revenue. In practice that's close to lost revenue multiplied by your contribution margin, minus costs you saved during the outage. Check the definition in your policy, because some forms use gross profit or different baseline and trend rules.
Is extra expense covered after systems are restored?
Usually only if it falls within the indemnity period. Without an extended period, that typically means it isn't covered once systems are restored. Many policies also require the expense to have reduced the business interruption loss. Ask your broker whether post-restoration costs such as customer win-back campaigns qualify under your wording.
Written by the Sentinel Underwrite Ops editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.