Business Continuity Planning Calculator – Assess Your Recovery Readiness

Most businesses assume they could get back on their feet quickly after a serious IT failure. Few have tested that assumption. Our Business Continuity Planning Calculator helps you put numbers on it: how long you could be offline, what that would cost and what recovery targets your IT needs to meet.

How to use the calculator

  • List your critical activities, such as taking orders, serving patients, running payroll or answering customers.
  • Estimate how long each can be down before it causes real harm.
  • Enter your expected downtime and the likely impact.
  • Review the recovery needs the tool suggests.
  • Compare them with what your current backups and infrastructure can deliver.

The result is a starting point. Confirm the targets with the people who run each part of the business, because they know what really breaks when something stops.

Key terms in simple language

Term

What it means

Question it answers

Business impact analysis (BIA)

A review of which activities matter most and what happens if they stop

What hurts most if it stops?

Maximum tolerable period of disruption (MTPD)

The longest an activity can be down before the damage becomes unacceptable

How long can we really cope?

Recovery time objective (RTO)

The target time to restore a system or service

How quickly do we need it back?

Recovery point objective (RPO)

The maximum amount of data you can afford to lose, measured in time

How much work can we afford to redo?

Minimum business continuity objective (MBCO)

The minimum level of service that is acceptable while you recover

What counts as "working" in the meantime?

Your RTO should always be shorter than your MTPD. The gap between them is your safety margin.

What a good continuity plan includes

  • The risks you have identified and how likely they are
  • A business impact analysis with agreed RTO and RPO for each critical system
  • Recovery strategies, such as off-site backups, cloud services and alternative ways of working
  • Named people with clear responsibilities, and up-to-date contact details
  • A communication plan for staff, customers and suppliers
  • Dependencies on suppliers, internet providers and software vendors
  • Step-by-step recovery procedures that someone other than the author can follow

Test it

A plan that has never been tested is a guess. Restore a backup to see how long it really takes. Run a short table-top exercise where the team talks through a scenario, such as a ransomware attack on a Friday afternoon. Test failover arrangements where you have them. Update the plan after any significant change to your systems, premises or suppliers. International standards such as ISO 22301 describe good practice for business continuity management and are a useful reference if you want a formal framework.

How IT infrastructure supports continuity

Off-site or cloud backups, resilient internet connections, protected power, secure remote access, endpoint security and well-maintained servers all shorten recovery and reduce how often you need it. See how our IT infrastructure and support solutions can help, or use the IT Downtime Cost Calculator to put a price on the risk.

Frequently asked questions

A documented approach to keeping essential operations running, or restoring them quickly, during an unexpected disruption.

RTO is about time: how fast you need a system back. RPO is about data: how much recent work you can afford to lose.

The maximum tolerable period of disruption. It is the longest an activity can be unavailable before the consequences become unacceptable, and your RTO should sit inside it.

Yes. Smaller businesses often have fewer resources to fall back on, which makes a simple, tested plan more valuable.

At least once a year, and whenever your systems, premises, suppliers or risks change.

Use the calculator to find out where you stand, then close the gaps before an incident does it for you.