How to Set Up Business Continuity Testing
A recovery plan that has never been tested is closer to a set of assumptions than a safeguard. When a cyber attack, power failure or building incident stops normal work, the question is not whether your plan looks complete. It is whether people can use it under pressure. To set up business continuity testing properly, you need to test the people, processes, suppliers and technology that keep your organisation moving.
For a school, that could mean maintaining safeguarding communications and access to pupil information. For a business, it may mean keeping customer service, finance or production operational while core systems are unavailable. The right test gives senior leaders evidence, not false reassurance.
Start with the services you cannot afford to lose
Business continuity is wider than IT disaster recovery. Disaster recovery focuses on restoring technology after a failure. Continuity planning considers how the organisation continues to deliver its essential services while that recovery is happening.
Begin by identifying your critical activities and agreeing how long each can be interrupted. A payroll system might have a recovery time objective of 24 hours, whereas email for a customer-facing team may need to be restored much sooner. A school may decide that its MIS, telephony and internet connectivity each require different recovery priorities.
Avoid treating every system as equally urgent. That approach makes recovery costly and unfocused. Instead, speak to department leads, finance, operations, HR and IT about the practical impact of an outage. Ask what work stops, what can be done manually, who needs to make decisions and which third parties are essential.
Document the result in plain language. Your continuity plan should make clear:
- which services are critical and their acceptable downtime
- who owns recovery decisions and how deputies are contacted
- where staff work if a site or system cannot be used
- what suppliers, passwords, licences and access routes are required
- how you will communicate with staff, customers, parents, governors or regulators
These details turn a technical recovery document into an operational plan that people can follow at 7.30am on a difficult Monday.
Choose the right business continuity test
A full, unannounced shutdown test is rarely the right starting point. It can create unnecessary disruption, particularly for small teams, schools and organisations with limited tolerance for downtime. Testing should be proportionate to risk, but it must be realistic enough to expose weaknesses.
A tabletop exercise is usually the best first step. Gather the people who would manage an incident and present a scenario: ransomware has encrypted a file server; your office is inaccessible after a flood; a key cloud supplier has an outage; or a phishing attack has compromised a senior colleague’s Microsoft 365 account. Work through what happens in the first hour, first day and following days.
This test quickly reveals uncertainty around authority, contact details and communications. It is also a useful way to involve non-technical leaders, because the focus is on decisions and service delivery rather than server specifications.
Technical recovery testing goes further. Your IT team or managed service provider may restore a backup into an isolated environment, fail over connectivity, recover a virtual server, test access to cloud data, or confirm that staff can work securely from another location. The objective is to prove recovery times and data recovery points, not simply confirm that a backup job reports as successful.
For mature arrangements, consider a live simulation. This may involve moving a small team to remote working for a day, using an alternative communications channel, or operating a key process from a secondary location. Plan it carefully and keep a clear rollback option. A live exercise provides valuable evidence, but it needs stronger change control than a tabletop discussion.
How to set up business continuity testing without disrupting operations
Set clear objectives before choosing a date. A useful objective might be: “Prove that the finance team can access the applications and files needed to process payments within four hours if the office network is unavailable.” That is more valuable than a vague instruction to “test disaster recovery”.
Create a scenario based on your real risks. UK organisations commonly face ransomware, accidental deletion, broadband failure, supplier outages, severe weather, hardware faults and loss of access to premises. Include the complications that happen in real incidents: an unavailable decision-maker, a staff member on holiday, a mobile number that is out of date or a supplier contract that does not cover the response you expected.
Assign an exercise lead who can keep the test moving and an observer who records decisions, timings and gaps. Participants should know whether the test is announced and what boundaries apply. For example, a technical exercise might state that production data must not be altered and normal customer support must continue.
It is sensible to notify a small group of leaders in advance, even where the wider test is a surprise. The aim is to learn safely, not to catch colleagues out. In education settings, ensure safeguarding leads and senior leadership understand the scenario and escalation route.
During the exercise, measure what matters. Did the incident team receive the alert? Could they access the plan without relying on the affected systems? Were backups recoverable and free from malware? Did multi-factor authentication, emergency accounts and alternative internet connections work as expected? Were messages to staff clear and approved quickly?
Keep a timeline. The difference between “we restored it” and “we restored it within the agreed target, with the correct data and access controls” is the difference between a comforting story and a usable result.
Test communications as carefully as technology
Many continuity plans fail at the human point. Staff may have access to systems but no clear instruction on whether to work remotely, use personal phones or contact customers. Senior leaders may be waiting for technical updates that never arrive in a format they can act on.
Prepare communication templates for common incidents, then test them. Include internal updates, customer or parent communications, supplier notifications and a holding statement for social media where appropriate. Templates should not make promises you cannot keep. It is better to say that you are investigating an issue and will provide a timed update than to promise a resolution before you understand the scale of the problem.
Also check where these templates are stored. If they live only on a network drive that is unavailable during a ransomware incident, they are of limited use. Store controlled copies in a secure, accessible location and make sure the incident team knows how to reach them.
Turn findings into improvements, not paperwork
A test is successful when it identifies issues early. Missing contact information, unclear recovery ownership and an untested backup are all valuable findings if they lead to action. Treating them as failures to hide defeats the point.
Hold a short review immediately after the exercise, while details are fresh. Ask what worked, what delayed recovery, what assumptions proved wrong and what should change before the next test. Give each action an owner and deadline, then report progress to the leadership team or governing body.
Some improvements will be simple, such as updating call trees or adding an alternative internet connection. Others may require investment: immutable backups, a secondary firewall, improved endpoint security, a cloud migration or additional Microsoft 365 recovery controls. Prioritise these against the impact of the services they protect, rather than the loudest concern in the room.
Breathe Technology often sees the biggest gains come from joining technical recovery testing with clear leadership procedures. A backup can be technically sound, but it only protects the organisation when the right people know who can authorise restoration, communicate the situation and keep essential work going.
Set a testing rhythm that reflects your risk
Testing once and filing the results away is not enough. Systems change, staff leave, suppliers change their services and new threats emerge. Review the continuity plan after significant technology changes, office moves, mergers, incidents and changes to key personnel.
As a practical baseline, run a tabletop exercise at least annually and test critical technical recovery processes on a planned schedule. Higher-risk services may need more frequent checks. For example, organisations heavily dependent on cloud collaboration may test Microsoft 365 account recovery and secure access more often than a rarely used legacy application.
Make testing part of normal operational governance, not an annual compliance chore. A short, focused exercise can give finance directors, school leaders and IT teams far more confidence than a lengthy plan that no one has practised. When disruption does arrive, that confidence becomes calmer decisions, clearer communication and a faster route back to normal service.




