Use your downtime costs to decide what needs recovery first
8 October 2026
Estimate downtime costs using your own labour, revenue and recovery inputs, then set practical recovery priorities for your Australian business.
Datto published a vendor article on 22 December 2025 encouraging managed service providers to use downtime costs when discussing business continuity and disaster recovery. For Australian owners and finance leaders, the useful question is not how convincing a sales presentation sounds. It is whether your own numbers justify the proposed recovery capability.
Datto’s article takes a provider sales perspective. The approach below takes the buyer’s side: estimate disruption using evidence, make uncertainty visible, and choose recovery priorities before comparing products.
Start downtime costs with a specific business scenario
There is no single hourly loss figure that describes every outage. Losing access to accounting software during a quiet afternoon differs from losing order processing before dispatch closes.
Define a scenario before opening a spreadsheet:
- Affected service: for example, order entry, payment processing or shared documents.
- Timing: ordinary trading, payroll processing, month-end or a peak ordering period.
- Extent: one team, one site or the whole business.
- Duration: several plausible interruption periods, not one assumed recovery time.
- Workaround: what staff can safely continue, and for how long.
Use scenarios such as an unavailable server, a failed internet connection or a compromised account. Each has different dependencies and recovery steps. A backup may help recover a server but will not itself restore an internet connection.
Keep a separate record for each scenario so unrelated impacts do not become one inflated headline number.
Calculate labour disruption from actual staffing inputs
Ask payroll or finance for the employment cost of affected roles. Use a consistent hourly basis that includes agreed employer costs, such as superannuation, without adding overheads already counted elsewhere.
A practical capacity calculation is:
Disrupted labour value = affected staff × loaded hourly employment cost × affected hours × productivity reduction
Calculate this by team where rates or impacts differ. Staff who can switch to useful work should not be treated as fully idle. Record whether that alternative work genuinely reduces disruption or merely shifts a backlog to tomorrow.
This is a measure of paid capacity affected, not automatically an additional cash expense. Ordinary wages would usually have been paid regardless of the outage.
Track incremental expenses separately: approved overtime, temporary staff or external processing support. If overtime clears the backlog, avoid describing all delayed work as permanently lost as well.
Have team leaders validate the productivity assumptions. A finance-approved hourly rate is only useful when the affected headcount and working hours are credible.
Separate lost revenue, delayed revenue and lost contribution
Revenue exposure is not the same as financial loss. Some customers abandon a purchase; others order later. A delayed invoice may create a cash-flow problem without reducing the eventual sale.
Use sales records to identify the affected channel and trading period, then estimate:
Revenue at risk = expected sales during the interruption × proportion of sales activity affected
Next, divide that exposure into sales expected to be recovered, sales genuinely lost, and sales whose outcome remains uncertain.
For profitability decisions, finance can estimate:
Lost contribution = permanently lost revenue − variable costs avoided on those sales
Use your own margin structure rather than applying a generic percentage. Record additional freight, discounts or customer credits separately, checking whether they are already reflected in the sales estimate.
Show delayed receipts in a cash-flow view. Only include financing costs where there is a supportable basis.
Keep labour capacity and lost contribution visible as separate measures. Adding both wholesale can count the same operational impact twice. Downtime costs become more credible when finance reconciles overlaps rather than simply adding every line.
Add recovery expenses without inventing consequences
Recovery can continue after a system becomes accessible. People may need to reconcile transactions, re-enter records, verify access and contact customers.
Collect supported estimates for:
- External technical recovery work outside existing service inclusions.
- Replacement equipment or temporary connectivity.
- Additional staff time needed to rebuild or reconcile records.
- Specialist incident response or legal advice where the scenario warrants it.
- Contractual credits supported by actual customer agreements.
Do not assign arbitrary amounts to reputational harm, regulatory penalties or future customer departures. Describe these as unquantified risks unless there is a defensible basis for estimating them.
Also distinguish gross exposure from possible insurance recovery. Coverage, excesses, exclusions and claims decisions need separate review; an assumed payout should not make a recovery gap disappear.
For cyber incidents, restoration is only part of the response. Containment and checking that systems are safe may affect the timeline. Our first-24-hours ransomware response guide explains the immediate decisions to plan for.
Build a worksheet that exposes assumptions
A useful downtime costs worksheet should let another person trace each input to its owner and evidence.
| Input | Evidence to use | Person to validate it | |---|---|---| | Affected staff and hours | Rosters and process maps | Operations lead | | Loaded employment cost | Payroll records | Finance lead | | Sales exposure | Trading and channel reports | Sales and finance | | Recoverable sales | Order history and customer commitments | Sales lead | | Recovery expenses | Service terms and scoped estimates | IT and finance | | Workaround capacity | Documented procedure and test results | Process owner |
Create lower, central and higher-impact estimates by changing stated assumptions. Do not label these as probabilities unless you have evidence for the likelihoods.
Model different durations individually. Costs may rise sharply when a dispatch deadline is missed or a manual process reaches capacity. Multiplying one hourly figure indefinitely can conceal those thresholds.
Turn downtime costs into recovery priorities
Rank business services first, then map the technology they require. Recovering a server has little practical value if staff still cannot sign in or reach the application.
Agree two targets for each critical service:
- Recovery time objective (RTO): the target elapsed time to restore the required service level after disruption.
- Recovery point objective (RPO): the target maximum age of data you can accept recovering, expressed as time.
These are planning targets, not promises. Ask what testing demonstrates about actual capability.
Include dependencies such as identity, networking, databases, supplier access and key staff availability. Define a minimum acceptable operating mode, who authorises it, and when temporary records must be reconciled.
Safety, legal obligations and customer commitments may override a purely financial ranking. Owners should approve those exceptions explicitly.
Our guide to protecting data across Microsoft 365, laptops and servers can help identify data locations that need to be included in this mapping.
Compare recovery proposals against evidence
Ask each provider to explain which scenario its proposal addresses, which systems are covered, and what remains your responsibility. Check recovery testing, support availability, restore dependencies and any additional charges against the written scope.
Compare the current recovery position with the proposed one using the same assumptions. Without a defensible incident likelihood, present the comparison as exposure reduction rather than a precise annual return on investment.
A successful backup job does not establish that a complete business service can recover within your target. Request a test that includes application checks and sign-off by the people who use it. Update your downtime costs after tests, system changes and changes in trading patterns.
Tech Engine can help review your managed IT, cyber security and recovery arrangements against business priorities. To discuss your current gaps, call 1300 088 324 or email sales@techengine.au.
Want this applied to your business?
Request an AI Blueprint and we will map the processes worth automating first.
Request an AI Blueprint