An 8-Hour or 12-Hour Waiting Period? How the Cyber Downtime Clock Really Works
A 12-hour waiting period can cost you nothing or six figures, depending on how long the outage runs and how your policy combines the clock with the retention. Here's the math, worked through before renewal.
The three dials that decide what a downtime claim pays
At renewal, your broker offers a choice: keep an 8-hour waiting period on business interruption, or move to 12 or 24 hours for a lower premium. It looks like a small trade. It isn't. The cyber insurance waiting period is one of three settings that together decide what a business interruption claim pays, and you can't judge it alone.
The three settings:
- The waiting period. How many hours your systems must be down or degraded before business interruption cover responds. Cover for security failures is commonly quoted somewhere around 6 to 12 hours. System failure and dependent business interruption (outages at your cloud, SaaS or payment providers) often carry longer clocks, sometimes 12 to 24 hours or more.
- The monetary retention. The dollar deductible. Depending on the wording, it applies to the business interruption loss alone, to the whole claim, or not at all.
- The period of restoration. The window in which lost income counts. It runs from the start of the interruption until systems are restored, or should have been with reasonable speed. It is usually capped, often at a few months, and sometimes extended for customers who are slow to return.
A short waiting period helps most with short outages. A long period of restoration helps most with long ones. The monetary retention can quietly cancel out both. The rest of this piece shows how they combine, using hypothetical numbers you can swap for your own.
Time retention vs monetary retention: two structures that pay very differently
Before comparing 8 and 12 hours, find out how your wording treats those hours. Two structures exist in the market, and the same outage can produce very different payouts under each.
The waiting period as a time deductible
Here the waiting period works like a deductible measured in hours. If the outage lasts 30 hours and the waiting period is 12, you can claim lost income only for hours 13 through 30. You absorb the first 12. This is the more common structure, and it makes every extra waiting hour a direct cost: hourly loss multiplied by the added hours.
The waiting period as a qualifying period
Here the waiting period is only a trigger. Once the outage passes the threshold, loss counts from hour zero. A 12-hour qualifying period on a 30-hour outage pays for all 30 hours. Under this structure, the length of the clock matters only for outages that end near the threshold.
How the monetary retention stacks on top
The time retention vs monetary retention question is the second thing to pin down. Some policies apply the waiting period instead of a monetary retention for business interruption. Some apply both. Others apply whichever is greater. A $25,000 or $50,000 deductible stacked on a 12-hour time deductible is a very different deal from the 12-hour clock alone, especially for mid-size companies whose hourly loss is in the low thousands.
Also ask whether incident response costs such as forensics, legal and restoration erode the monetary retention first. If they do, the retention is often spent by the time business interruption is calculated, and only the waiting period really bites.
Terminology differs by market. US-style forms tend to say "period of restoration" and "waiting period." London-market and Commonwealth wordings more often say "indemnity period" and "time excess." Local policies in continental Europe, India, the Gulf and Southeast Asia may translate these terms differently again. Read the definitions, not the headings.
Three outage timelines under 8-, 12- and 24-hour clocks
Here's a hypothetical case. Say a 150-person distribution company loses about $6,000 per hour while its order and warehouse systems are down, counting lost net profit plus continuing operating expenses. Its policy carries a $25,000 monetary retention that applies to the business interruption loss, and we assume no incident response costs have eroded it. Real hourly losses are never flat. Treat these figures as illustrations, not benchmarks.
- Timeline A: A ransomware detonation is contained quickly. Systems are back after 10 hours. Loss: $60,000.
- Timeline B: Encrypted servers are restored from backups over 30 hours. Loss: $180,000.
- Timeline C: A full outage of 96 hours ($576,000), then seven days of partial operation at about $1,500 per hour of lost income ($252,000). Loss: $828,000.
| Scenario | Clock | Payout: time deductible + retention | Payout: qualifying period + retention |
|---|---|---|---|
| A: 10-hour outage ($60,000 loss) | 8 hours | $0 (2 hours = $12,000, below retention) | $35,000 |
| A: 10-hour outage | 12 hours | $0 (not triggered) | $0 (not triggered) |
| A: 10-hour outage | 24 hours | $0 (not triggered) | $0 (not triggered) |
| B: 30-hour outage ($180,000 loss) | 8 hours | $107,000 | $155,000 |
| B: 30-hour outage | 12 hours | $83,000 | $155,000 |
| B: 30-hour outage | 24 hours | $11,000 | $155,000 |
| C: 11-day event ($828,000 loss) | 8 hours | $755,000 | $803,000 |
| C: 11-day event | 12 hours | $731,000 | $803,000 |
| C: 11-day event | 24 hours | $659,000 | $803,000 |
The table shows three things.
Short outages are mostly uninsured under any clock. In Timeline A, even an 8-hour time deductible pays nothing once the $25,000 retention applies. Only a qualifying-period wording with a short clock pays anything. If most of your realistic outages last under a day, whether the retention stacks on the waiting period matters more than the clock itself.
The 12-to-36-hour band is where the choice matters most. In Timeline B, moving from 8 to 24 hours under a time-deductible wording cuts the payout from $107,000 to $11,000. That's a $96,000 swing, exactly 16 extra hours at $6,000. Ransomware recoveries from usable backups can plausibly land in this range.
In long events, the clock is a fixed cost. In Timeline C, the gap between 8 and 24 hours is still $96,000, but that's under 12% of the loss. Here the period of restoration cap, any extended period, and the overall business interruption sublimit decide whether you're made whole.
The rule of thumb: extra waiting hours × your realistic hourly loss = the extra money you keep at risk on every qualifying event. Compare that number with the premium saving you're offered.
Where the period of restoration starts, stops and gets cut short
The period of restoration gets less attention than the waiting period, but it often decides the bigger claims. Check four points in the definition.
When the clock starts
The best wordings start both the waiting period and the period of restoration when the interruption actually begins. Weaker ones start at discovery or at notification to the insurer. If an attacker quietly breaks your systems at 2 a.m. Saturday and nobody notices until Monday morning, a discovery-based clock can erase a whole weekend of loss before cover begins.
When the clock stops
Many policies end the period when systems are restored, or could have been with due diligence. That's not the same as when revenue recovers. Timeline C's seven days of partial operation are covered only if the wording counts degraded performance, not just total outage, and runs until business returns to pre-event levels. An extended period of indemnity, where offered, covers customers who drift away after systems come back. Lengths vary by insurer.
The cap
A cap of roughly 90 days may be enough for many office-IT recoveries. Manufacturers, healthcare providers and logistics firms with complex operational technology often argue for 180 days or more, because rebuilding industrial systems takes longer than restoring office IT.
Voluntary shutdown
Containment often means shutting systems down yourself before the attacker finishes. Confirm that a precautionary shutdown, made on reasonable advice from your incident responder, triggers the waiting period. Without that language, the hours you spend preventing a worse loss may not count.
System failure coverage for non-malicious outages, such as a botched patch, a failed migration or a configuration error, frequently has its own longer waiting period, a lower sublimit, or both. So does dependent business interruption tied to a provider's outage. For companies that run on cloud services, this is often where the real downtime risk sits, so review those clocks separately.
Choosing your clock at renewal: a decision rule and a wording checklist
Start with your own numbers. Ask finance for a defensible hourly figure covering lost net profit and continuing expenses, by business line if revenue is uneven across the week. Your broker or a forensic accountant can help put it in policy terms. Then estimate how long a realistic outage would last, based on your backup restoration tests rather than vendor promises.
Then apply this rule. Under a time-deductible wording, take the longer clock only if the annual premium saving exceeds the extra waiting hours multiplied by your hourly loss, multiplied by the realistic chance of a qualifying outage in a year. For most mid-size companies with hourly losses above a few thousand dollars, moving from 8 to 24 hours fails that test, because the premium reduction is usually modest. Savings vary widely by insurer, region and loss history, so get firm quotes rather than relying on any general figure. A company with low hourly loss, well-tested backups and a high retention anyway can reasonably accept a 12-hour clock.
Before you sign, put these questions to your broker in writing:
- Is the waiting period a time deductible or a qualifying period?
- Does the monetary retention also apply to business interruption, and do incident response costs erode it first?
- Does the clock start at interruption, discovery or notification?
- Does partial degradation count, or only total outage?
- Are voluntary shutdowns covered?
- What are the separate clocks and sublimits for system failure and dependent business interruption?
- What is the period of restoration cap, and is there an extended period of indemnity?
- Are forensic accounting costs for preparing the claim covered?
Red flags include a clock that resets for each affected system, a waiting period that applies per provider for dependent business interruption, and restoration defined by IT recovery alone. Policy terms, tax treatment of claim proceeds and regulatory requirements differ by country, so have a licensed broker and your own advisers review the final wording.
Your next step: calculate your hourly loss this week, then ask your broker to quote the 8- and 12-hour options side by side.
Frequently asked questions
Is a shorter cyber insurance waiting period always worth paying for?
No. If your monetary retention also applies to business interruption and exceeds your loss over the first few hours, a shorter clock may add nothing on short outages. It earns its cost when your hourly loss is high and your realistic outages last 12 to 36 hours. Multiply the extra hours by your hourly loss and compare the result with the premium difference.
What's the difference between a waiting period and a period of restoration?
The waiting period is how long an outage must last before business interruption cover responds. Under many wordings, those hours are also excluded from the claim. The period of restoration is the full window in which lost income counts, usually running until systems are restored and subject to a cap. The first mostly affects short events. The second decides long ones.
Does system failure coverage use the same waiting period as a cyberattack?
Often it doesn't. Non-malicious outages and dependent business interruption from third-party providers frequently carry longer waiting periods, lower sublimits or both. Check each insuring agreement's clock separately in the declarations or schedule, and ask your broker to confirm in writing.
Written by the Guard Policy Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.