Colour theme
Book a consultation

Eight gaps to test in a continuity plan

Test a continuity plan for missing safety arrangements, priorities, dependencies, workarounds, recovery evidence, deputies, instructions and updates.

A red wrong-way road sign topped with an amber warning light

A continuity plan can look complete until someone tries to use it without the usual building, email account or technician. A review should test whether it still works without them.

Use these eight gaps to structure a discussion exercise. Choose a plausible disruption, use fictional information and record what participants can and can’t do.

1. Staff safety is assumed

Check how staff receive emergency instructions and how someone confirms they’re safe. Include people working remotely or outside ordinary hours.

Make sure the plan matches your building’s fire and evacuation procedures and any instructions from local emergency services. Don’t ask staff to enter an unsafe location to retrieve equipment.

2. Every service has the same priority

Ask business owners which work must continue, which can pause and how the impact changes over time. Include your own deadlines, such as payroll dates, contract commitments and tax filings.

The Cyber Centre’s continuity-plan guidance starts with critical operations. Use your own impact assessment to justify the recovery order.

3. Alternatives share the failed dependency

Check whether the backup contact list, alternate application or remote workspace needs the same identity service, Internet connection or building.

Walk through access while that dependency is unavailable. If staff can’t reach the alternative while the main system is down, it won’t help.

4. The temporary workflow hasn’t been tried

Ask staff to do an everyday task the way the plan says they would during an outage, such as taking an order on paper. Include an exception and a customer enquiry.

Check access, staffing, record handling and workload. Decide how paper or temporary records will be entered once the systems are back.

5. Recovery is inferred from a dashboard

Ask how you know the restoration plan will work. A successful backup job only tells you the backup ran. Check that the application, its configuration and staff access can be restored together.

Use the Cyber Centre’s IT recovery guidance to review the technical recovery work. Test safely and record what the exercise didn’t cover.

6. A critical task depends on one person

Choose a scenario in which the usual coordinator or technician is unavailable. Ask the deputy to find the information they need and get sign-off from the person who’d normally give it.

Our guide to assigning continuity decisions covers who has authority to act. Set up the access deputies will need now, the same way you’d grant anyone else access, so they aren’t waiting for it during an outage.

7. Instructions skip the first decision

Check who activates the plan, who is contacted first and what staff do while the cause is investigated. Include the method for issuing an update.

Replace phrases such as restore service promptly with a named action and the information needed to carry it out. Don’t promise customers a recovery time that depends on a supplier you haven’t confirmed.

8. The plan has no maintenance owner

Review contact details, supplier commitments and the date of the last exercise. Compare the plan with systems and staffing changes since then.

Assign each gap to an owner and set a follow-up date. After the work is completed, repeat the relevant test and record the result with the current plan.


Featured Image Credit