Estimating what an IT outage costs your business
Build a downtime estimate from interrupted work, lost contribution, recovery costs and backlog, with clear assumptions and no double counting.

An outage affects different parts of a business at different times. A failed Internet connection might stop card payments immediately while another team can keep working from paper or offline records.
Estimate the effect on your own activities before comparing recovery options. A large company’s cost per minute won’t tell you what a small office loses when its scheduling system is unavailable.
Define a specific interruption
Choose a scenario, such as losing access to the booking system for half a working day. Record the affected locations, staff, customers and dependencies.
Distinguish complete failure from degraded service. If calls still work and some appointments can proceed, reflect that in the estimate. Include the time needed to reconcile work after service returns.
The Cyber Centre’s business continuity guidance connects disruption analysis with critical operations and recovery objectives. Use the business impact exercise to establish priorities with the people responsible for those operations.
Separate blocked work from lost sales
List work that stops and work that can continue through a workaround. Estimate the staff time affected, including the time spent using a slower fallback.
Then identify transactions that are lost permanently and those that are delayed. A sale completed the next day isn’t automatically lost revenue. For sales that won’t come back, count the margin you’d have kept (the sale price minus the costs you no longer incur), and have your bookkeeper or accountant confirm the method.
Treat staff effort and lost sales carefully. Adding both without considering what they represent can count the same business loss twice.
Include recovery and backlog
Record likely additional costs for technical work, replacement equipment, overtime, transaction reconciliation and customer communications. Check which costs an existing support agreement covers.
Include re-entering records created during the outage and checking that duplicated requests weren’t processed twice. A service can be online while its business backlog still needs attention.
Don’t assume insurance will pay the bill. Coverage, conditions, deductibles and exclusions need to be checked against your policy wording.
Keep uncertain effects separate
Lost future business and reputational effects are harder to price. Record the evidence and uncertainty instead of assigning an unsupported percentage.
An outage on its own doesn’t mean there’s been a privacy breach or that a fine will follow. If information may have been compromised, assess that separately as a possible privacy breach. Under PIPEDA, a breach that creates a real risk of significant harm must be reported to the Privacy Commissioner and the people affected.
Use a lower and upper estimate where the duration or volume is uncertain. State the assumptions beside the numbers so another person can review them.
Compare practical recovery options
Ask which option reduces a particular consequence: a tested restore, another Internet connection, a written manual process or a spare device. Include its setup, recurring cost and testing effort.
Check shared dependencies. Two connections may still rely on the same building power or physical route. Time a test restore to learn how long recovery takes.
Use the estimate to agree priorities for backup and continuity planning. Revisit it after an exercise or real interruption, when you can replace assumptions with observed effects.


