Estimate downtime cost without counting the same loss twice

Estimate the business effect, not a dramatic headline

Downtime cost is the incremental effect of a disruption compared with normal operation. It can include wasted labour capacity, genuinely lost gross profit and exceptional recovery costs. It should not automatically include all revenue generated during the affected hours. Some orders are delayed and completed later, some work can continue, and some costs would have been paid anyway.

Use a transparent range rather than a false-precision single figure. The purpose is to make a better decision about prevention and recovery. An exaggerated estimate can justify unnecessary spending, while ignoring staff time and recovery work can make a useful backup or support arrangement look uneconomic.

Calculate affected labour separately

Start with the number of affected staff, loaded hourly cost, duration and disrupted share of work. Loaded cost can include relevant employment overheads, but use a figure agreed with finance. If staff can do other productive work for half the outage, use a partial-disruption assumption rather than treating everyone as completely idle.

For illustration, eight staff at an assumed A$45 per hour for three hours with 50% disruption represent A$540 of affected labour capacity. That is not necessarily an extra cash payment. It may represent lost capacity while wages continue. Keep the label clear so the result is not presented as a bank-account loss or guaranteed recoverable profit.

Use lost gross profit carefully

Estimate sales that are permanently lost because of the outage, then apply an appropriate margin or contribution measure. Do not count sales merely deferred to the afternoon as lost for good. Consider cancellations, perishable work and customer alternatives. Use the business's evidence where available rather than assuming every potential sale disappears.

Check what your margin measure already includes. If direct labour is included in the cost base, adding the same labour again can double count it. For example, A$2,000 of genuinely lost revenue at an assumed 30% gross margin is A$600 of gross profit before considering overlap. Ask the accountant or finance owner to choose a consistent approach for your business.

Add exceptional recovery costs

Include external support, emergency equipment, overtime, transaction repair, extra delivery or other costs caused by the incident. Exclude ordinary monthly fees that would have been paid anyway unless the comparison specifically assesses a different contract. Record whether an amount is an invoice, estimate or unresolved exposure.

Some impacts, such as reputational damage and future customer loss, are difficult to measure. Keep them as separate qualitative risks or clearly labelled scenarios rather than hiding a speculative multiplier in the base case. An insurer's payment may reduce the eventual net loss, but coverage, excess and claim acceptance need confirmation. Do not assume insurance makes continuity work unnecessary.

Compare resilience investments with scenarios

Calculate a modest, realistic and severe incident using different durations and affected shares. Then assess which part a proposed investment can actually prevent. Backup internet may reduce connectivity disruption but not a failed application or power outage. Faster support may reduce response delay without guaranteeing immediate resolution.

For illustration, a A$600 annual measure that reliably avoids A$300 of cost twice a year roughly covers its fee before other effects. If it only prevents one incident in five years, the cash case is weaker unless the downside risk is unacceptable. Those are assumptions, not probability estimates. Use incident records and supplier evidence to judge likely benefit rather than inventing precise failure rates.

Keep a practical decision record

Keep a loss worksheet for actual incidents with three separate labels: observed cost, estimated capacity effect and uncertain future impact. Record what was recovered later, such as delayed orders completed the next day, so the original estimate can be corrected. Ask the same finance owner to review significant incidents for consistency. Over time, this evidence makes prevention decisions more credible and helps identify whether outages are frequent minor interruptions or rare severe events. Do not let a dramatic one-off scenario silently become the assumed loss for every future hour offline.

Use the result to prioritise

Use the downtime cost calculator with visible labour, margin and recovery inputs. Keep one base case that avoids overlap and show uncertainty. Record actual disruption after future incidents so the estimate improves. Include causes, duration, work affected and extra invoices.

Combine the calculation with a continuity plan and tested fallback arrangements. A useful analysis identifies the most valuable function to restore and the cost worth paying to protect it. The objective is a proportionate decision, not the largest possible estimate of what an hour offline might cost.