Cost Of Interruption Calculator
An hour of downtime is never just an hour. Revenue stops, wages keep running, customers wait, and the recovery bill arrives later. The true cost of an interruption is the sum of all four, and most businesses dramatically underestimate it until they add it up.
This calculator adds it all up: lost revenue, idle and recovery labor, and the follow-on costs of an incident. Pick a scenario preset for typical values or enter your own numbers, and see the cost per incident, the cost per hour, and the annualized impact if it keeps happening.
Scenario presets (optional, fills typical values)
Interruption details
Cost factors
Additional costs per incident
Breakdown per incident
Prevention ROI
Days convert at 8 working hours and weeks at 40. Productivity loss is valued on top of idle labor as a memo for the output that never happened; it is not added into the per-incident total.
Quick Answer
Key takeaways
- Per-incident cost = adjusted lost revenue + idle labor + recovery labor + follow-on costs. Frequency turns that into the annual figure executives act on.
- Labor is two lines, not one: $6,250 idled during the outage and $2,500 spent recovering in the worked example.
- The productivity loss row ($1,875 in the example) is a memo for lost output. It is deliberately kept out of the total so wages are not counted twice.
- A slow-burn version of the same problem, a decision that keeps slipping rather than a system that stops, prices differently: see the inaction model linked below.
How to use the cost of interruption calculator
Start with a preset if your incident resembles one of the five: IT outage, power outage, cyberattack, equipment failure, or supply-chain delay. Presets fill every field with typical values for that scenario, including the follow-on costs most people forget. Then replace the preset numbers with your own incident records: duration, people affected, how often it happens, and what the last one actually cost to clean up.
Leave the two multipliers at 1.0 unless you have a specific reason to raise them, and leave reputation at zero if you cannot defend a figure for it; the total stays credible, and credibility is the point. If the interruption is not an incident but a start date that keeps moving, that is a different model: the cost of delay calculator prices postponed projects, while the cost of doing nothing calculator prices the standing monthly loss from a decision never taken.
The formula, layer by layer
The model follows the structure downtime researchers use: revenue, people, recovery, and consequences, summed per incident and then annualized. The Uptime Institute outage research consistently finds most significant outages cost six figures or more once every layer is counted, which is what a revenue-only estimate misses.
Two judgment calls in the model are worth knowing before you quote the output. First, recovery labor uses the same head count and wage as idle labor, a simplification: if only a small response team does the recovery, lower the figure by entering recovery hours as the team’s total person-hours divided by the full head count, or accept a conservative overstatement. Second, the productivity loss percentage values lost output on top of wages and is displayed separately, never added, because adding both is the double count that makes downtime figures easy to dismiss. When a disruption causes physical damage or a total loss rather than lost hours, the accounting is different again, and the business casualty loss calculator covers that side.
Worked example: the 5-hour IT outage, priced in full
The calculator is pre-filled with the IT outage preset, and every figure below is what it returns.
| Layer | Calculation | Cost |
|---|---|---|
| Lost revenue | $10,000 x 5 hours | $50,000.00 |
| Idle labor | 50 staff x $25 x 5 hours | $6,250.00 |
| Recovery labor | 50 staff x $25 x 2 hours | $2,500.00 |
| Additional costs | $2,000 emergency + $1,000 overtime | $3,000.00 |
| Cost per incident | Sum of the four layers | $61,750.00 |
| Cost per hour | $61,750 / 5 hours | $12,350.00 |
| Annualized, twice a month | $61,750 x 2 x 12 | $1,482,000.00 |
| Productivity loss (memo only) | 30% of idle labor | $1,875.00 |
The prevention framing is the part to take into the budget meeting. Halving these incidents saves $741,000 a year, so a resilience project does not need to be perfect to pay: it needs to cost less than the share of $1,482,000 it actually removes. For a smaller operation testing whether it can absorb risks like this at all, the small business value calculator puts the interruption exposure next to what the whole business is worth.
What competing calculators miss
Competing downtime tools reviewed for this page typically ask for revenue per hour and duration, multiply them, and stop. That revenue-only figure understates the worked example by nearly $12,000 an incident, and the understatement grows with head count.
Miss 1: labor and recovery. Wages run during the outage and spike after it. This model prices both, separately, so you can see that recovery alone is $2,500 of the example incident.
Miss 2: follow-on costs. Emergency call-outs, overtime, compensation, data recovery, and penalties are itemized inputs here rather than a footnote, because on cyber and equipment incidents they rival the revenue loss.
Miss 3: the annualized, decision-ready view. A per-incident number informs; an annualized number budgets. The break-even prevention budget and the 50% reduction saving translate the incident directly into the spending it justifies, which is the only form in which downtime numbers usually change anything.
One honest caution: the multipliers and the reputation line are judgment inputs. Two people pricing the same incident can land apart if one prices reputation at $20,000 and the other at zero. Agree those inputs before the meeting, or present the total with them set to the conservative defaults.
Frequently Asked Questions
The full financial impact of one disruption: revenue lost while work is stopped, wages paid to people who cannot work, the labor of getting back up, and the follow-on bills such as emergency response, overtime, customer compensation, data recovery, and penalties. This calculator adds those layers per incident, then annualizes them at your incident frequency.
Multiply the per-incident cost by incidents per month, then by 12. The worked example costs $61,750 per incident and happens twice a month, which annualizes to $1,482,000. Frequency is doing the heavy lifting in that figure, which is why prevention that cuts incident count beats almost everything else.
Because it overlaps the idle labor line. The wages figure already prices the hours people were paid but could not work; the productivity loss row values the same hours again as lost output, shown as a memo so you can see the wider economic hit without double-counting it in the headline total. If your accounting treats lost output as the primary measure, read the two rows together and say so when you present the number.
They scale the revenue loss only. A multiplier of 1.5 models an outage at peak trading time, or on a system customers cannot work around, where the true revenue damage runs about 50% above the plain hourly average. Leave both at 1.0 for an average incident; raise them only when you can name the reason.
The hours your own staff spend restoring service after the interruption ends: rebooting and checking systems, re-entering lost work, catching up the backlog. It is priced at the same average wage and head count as the idle labor, for the recovery hours you enter. Vendor invoices for the same work belong in emergency response instead, not in both places.
The annualized interruption cost. If interruptions cost $1,482,000 a year and a backup system, maintenance contract, or redundancy upgrade costing less than that removes the incidents, it pays for itself. A fix that only halves the incidents is worth half the annualized figure, which is why the results also show what a 50% reduction saves.
Days convert at 8 working hours and weeks at 40 working hours, because the labor and revenue rates are working-time rates. A plant that runs three shifts should enter the duration in hours directly, or scale the revenue and head count to match the shifts actually affected.
Add This Calculator to Your Website
References
- Uptime Institute, “Research and Reports,” including the Annual Outage Analysis: survey evidence on how often significant outages exceed $100,000 in total cost. Uptime Institute: Research and Reports. Accessed October 2026.
- ITIC, “Hourly Cost of Downtime Survey”: enterprise survey data putting hourly downtime losses above $300,000 for most mid-size and large organizations. ITIC: Hourly Cost of Downtime. Accessed October 2026.
- Splunk and Oxford Economics, “The Hidden Costs of Downtime”: Global 2000 research valuing unplanned downtime at about $400 billion a year, including follow-on and reputational costs. Splunk: The Hidden Costs of Downtime. Accessed October 2026.
- US Small Business Administration, “Prepare for Emergencies”: continuity planning guidance for small firms pricing and preparing for disruptions. SBA: Prepare for Emergencies. Accessed October 2026.
- Ready.gov, “Business Continuity Plan”: the federal template for impact analysis and recovery planning that the prevention budget on this page supports. Ready.gov: Business Continuity Plan. Accessed October 2026.