Business continuity software for consultants is a tool that lets you run business impact analyses, write continuity plans and track exercises for several client organisations from one workspace. For SME work, look for separate client workspaces, templates aligned with ISO 22301, plan exports your clients can own, and EU data hosting, because you will usually process client data as a GDPR processor.
This guide is for independent consultants and small advisory firms. It covers what sets your needs apart from an in-house team's, which parts of the business continuity management (BCM) lifecycle the tool should cover, how the main families of tools compare, and how to test a tool on a real client case before you commit. For the business side of running a continuity practice (engagement phases, pricing models, handover), see how to scale business continuity consulting engagements.
The 30-second version
- A consultant works for several organisations at once: client isolation, reusable templates and a clean handover matter more than for an in-house team.
- Check coverage against ISO 22301:2019 clause 8: BIA and risk assessment, strategies, plans, exercises, evaluation.
- Spreadsheets, a general GRC platform and dedicated BCM software each fit a different client portfolio.
- Software can link plan content to NIS2 or DORA requirements; it cannot make a client compliant.
- Plans hold personal data: check the processing agreement, the subprocessors and where data is hosted.
- A plan that cannot be read during an outage is not a plan: check exports and offline copies.
What does a consultant need from business continuity software that an in-house team doesn't?
An in-house business continuity manager runs one programme for one organisation. A consultant's work is different in four ways, and each one turns into a requirement for the tool.
- You manage several organisations in parallel. Each client's BIA lists its weaknesses, critical suppliers and staff contact details. The tool must keep each client in a separate workspace, with its own users and history, so that nothing leaks from one client to another.
- You repeat the same method. Impact scales, BIA questionnaires, plan structures and exercise formats are largely the same from one client to the next. The tool should let you reuse your own templates instead of rebuilding them for every engagement.
- You hand the plan over. At the end of the engagement the client has to run, update and test the plan without you. The tool must let you export everything, or transfer the workspace to the client.
- You bill by engagement. The cost of the tool has to fit your pricing: a price per user, per client or per plan changes your margin as the portfolio grows.
An in-house team rarely needs the first and third of these. A tool chosen for in-house use can therefore be a good BCM tool and still be a poor fit for a consulting practice.
Which parts of the BCM lifecycle should the tool cover?
Use the structure of ISO 22301:2019, clause 8 (Operation), as your checklist. ISO 22313:2020 gives guidance on how to implement each requirement, and the Business Continuity Institute's Good Practice Guidelines (2018 Edition) describe the same lifecycle from a practitioner's point of view.
| ISO 22301:2019 clause | What it requires | Software feature to look for |
|---|---|---|
| 8.2 Business impact analysis and risk assessment | Assess the impact of disruption over time, set priorities and recovery objectives, assess risks of disruption | BIA questionnaires sent to process owners, RTO, RPO and MTPD calculation, dependency mapping, risk register |
| 8.3 Business continuity strategies and solutions | Identify and select strategies and solutions to meet the recovery objectives | Strategy library, link from each strategy to the activities and resources it protects |
| 8.4 Business continuity plans and procedures | Document plans and procedures, including the response structure, warning and communication, and recovery | Plan generator built from the BIA data, contact directory, Word and PDF exports |
| 8.5 Exercise programme | Exercise and test the plans at planned intervals | Exercise planner, scenario library, post-exercise report |
| 8.6 Evaluation of business continuity documentation and capabilities | Evaluate the suitability, adequacy and effectiveness of the plans and capabilities | Corrective action tracking, review dates, version history |
Clause 8.1 (operational planning and control) and the rest of the standard (context, leadership, internal audit, management review) matter too, but they are mostly organisational. The features above are where software saves the most time. If you need a refresher on the standard, see ISO 22301 in 10 steps and the ISO 22301 checklist. For the BIA itself, see the business impact analysis page and the free BIA template.
Spreadsheets, GRC platform or dedicated BCM software: which fits SME engagements?
There are three broad families of tools. The values below are qualitative tendencies, not measurements: check each one against the offer you are actually considering.
| Criterion | Office templates (spreadsheet and word processor) | General GRC platform | Dedicated BCM software (SaaS) |
|---|---|---|---|
| Entry cost | Low | High | Moderate, often per user or per client |
| Multi-client isolation | Manual, by files and folders | Varies with the licence | Often built in, to be checked |
| BIA and RTO/RPO calculation | You build it yourself | Module sometimes optional | Generally built in |
| ISO 22301 clause 8 coverage | Depends on the template | Broad but generic | Focused on continuity |
| Exercise and action tracking | Manual | Built in | Built in |
| Offline access to the plan | Native (files) | Rarely | Varies: check exports or a mobile app |
| Reversibility for the client | Full | Complex | To be checked in the contract |
| Typical use case | One-off engagements, very small organisations | Clients already equipped with a GRC platform | Recurring portfolio of SMEs |
In practice:
- Few clients, or very small ones: a well-built set of office templates can be enough, provided you keep a single reference version. The cost shows later, in consolidation, version control and plan updates. See spreadsheet vs ResiPlan for a side-by-side view.
- A client already equipped with a GRC platform: work in its tool if it has a continuity module. Bringing a second tool into the client's environment creates two sources of truth.
- Several recurring engagements: dedicated BCM software usually pays off, because the BIA, plans and exercises live in one data model that you reuse from one client to the next.
Multi-client management: what to check before you commit
Ask for a demonstration, or a trial account, and check each point yourself.
- Isolated client workspaces. Each client's data is separated from the others, and a user invited by one client cannot see another client.
- Access rights per client and per role. A process owner can fill in their own BIA without seeing the rest; a client sponsor can approve; you keep administration rights.
- Templates you can copy between clients. Your impact scales, questionnaires and plan structures can be reused without copying the previous client's data.
- Deliverables in the client's name. Exports can carry the client's name and identity, or the tool offers white-labelling if you need it.
- Full export or transfer at the end of the contract. The client can take its plans, BIA, evidence and history in a usable format, or the workspace can be handed over to its internal team.
- A pricing model that matches your business. Per user, per client or per plan: model your cost for your current portfolio and for the one you expect in two years.
Does your client need to meet NIS2 or DORA requirements?
Start the engagement by establishing the client's regulatory status, because it changes what the plan must show.
- NIS2. Directive (EU) 2022/2555 (OJ L 333, 27.12.2022), Article 21(2)(c), requires essential and important entities to take measures covering "business continuity, such as backup management and disaster recovery, and crisis management". See NIS2 essential vs important entities and the NIS2 framework guide.
- DORA. Regulation (EU) 2022/2554 (OJ L 333, 27.12.2022), Article 11, requires financial entities to put in place an ICT business continuity policy, with ICT response and recovery plans that are tested. See the DORA framework guide.
- SMEs outside direct scope. Many SMEs are not entities under NIS2 or DORA. They can still be affected as suppliers: Article 21(2)(d) of NIS2 requires entities to address supply chain security, including their relationships with direct suppliers and service providers. In practice, an SME client can receive questions about its continuity plan from a customer that is in scope.
What this means for the tool: it should let you link plan content (BIA, strategies, exercises, actions) to the relevant requirements, so that you can show a client or its customer where each one is covered. Be wary of any tool, or any proposal, that promises to "guarantee compliance": software organises the evidence, but the measures are the client's.
Data protection: you will host your clients' sensitive data
Continuity plans contain emergency contacts, staff data and information about critical dependencies. When you process this data on your client's behalf, you generally act as a processor under Article 28 of the GDPR, which requires a processing contract with the client. The software vendor then becomes a sub-processor: under Article 28(2) you need the client's prior written authorisation, specific or general, to engage it, and under Article 28(4) the same data protection obligations must be passed on to it.
Before you put a client's data into a tool, check:
- Where the data is hosted, and the list of the vendor's own subprocessors.
- The vendor's data processing agreement, and whether it lets you meet your obligations to your client.
- The security measures required by Article 32. The article requires measures appropriate to the risk and cites, among others, encryption, the ongoing confidentiality, integrity and availability of systems, the ability to restore access to data after an incident, and regular testing. In practice, also ask about access control and activity logging.
Can the plan still be used when systems are down?
This criterion is often forgotten. A plan held only in a SaaS application may be unreachable during the very incident it is meant to handle: a network outage, a ransomware attack on the client's workstations, a lost identity provider.
Check:
- Offline exports: a PDF or Word version of the plan and the contact directory that the client can keep outside its own IT, or a mobile app that works offline.
- How offline copies stay current: who regenerates the export after each change, and how the previous version is withdrawn.
- Alternative channels for alerting staff and sharing procedures when email and the intranet are down.
- Consistency with ISO 22301 clause 8.4, which asks plans to cover warning and communication: the plan should say which channel is used when the usual ones fail.
How to run a trial with a real client case
A demonstration shows what the vendor chooses to show. A trial on a real case shows how the tool behaves with your method and your client. Four steps:
- Pick a pilot client that agrees to take part, ideally a recurring client that already knows your method.
- Run a BIA on 3 to 5 activities, with the real process owners filling in the questionnaire.
- Produce the plan for those activities and export it in the format the client will actually use.
- Run a tabletop exercise on that plan, then record the findings as corrective actions.
At each step, write down the time spent, the quality of the deliverable and how the client reacted. The grid below is a working tool to adapt to your practice, not a reference benchmark.
| Criterion | What to observe | Score (1 to 5) |
|---|---|---|
| Time spent | Hours from BIA launch to approved plan, compared with your usual method | |
| BIA collection | Did process owners complete the questionnaire without your help? | |
| Plan quality | Would you deliver the export as it is, or after heavy rework? | |
| Exercise support | Could you prepare, run and report on the exercise in the tool? | |
| Client buy-in | Did the client's team use the tool, and would it keep using it? | |
| Isolation and access | Did each person see only what they needed? | |
| Exit | Could you export everything in a usable format? | |
| Cost | Total cost for your current portfolio and for your target portfolio |
The tabletop exercise kit and the RTO/RPO calculator can help you prepare steps 2 and 4.
What ResiPlan offers consultants
ResiPlan is dedicated BCM software, so judge it with the same criteria as any other offer.
- Operator licence: one isolated workspace per client, with a single login to switch between them; tiers are set by the number of client workspaces. See ResiPlan for consultancies and the pricing page.
- BIA campaigns sent to the client's process owners, with RTO and MTPD calculation.
- Plans pre-filled from the BIA, with an AI first draft that the consultant reviews and approves.
- Tabletop exercises, with findings turned into tracked corrective actions.
- Word and PDF exports, and ISO 22301, NIS2 and DORA mapped to the work.
- Business data hosted in the EU.
- A 14-day consultant trial with two fictional demo clients, so you can test the workflow before you bring in a real client.
No software makes a client compliant or certifies it: it structures the work of the consultant and the client, it does not replace it.
FAQ
Is ISO 22301 certification required to use business continuity software?
No. Neither you nor your client needs to be certified to use business continuity software. ISO 22301 certification is a voluntary decision by an organisation, and an audit by a certification body. Software can help structure the work along the standard's requirements, but it neither replaces the audit nor grants a certificate.
Can I use the same software for all my clients without mixing their data?
Yes, if the tool gives each client its own isolated workspace, with separate users, roles and history. Check it during the trial: invite a test user to one client workspace and confirm that it cannot see any other client.
Does business continuity software make an SME NIS2-compliant?
No. NIS2 Article 21 requires entities to take measures; software can help document those measures, link them to the requirements and keep the evidence, but it cannot take them on the client's behalf. Many SMEs are not entities under NIS2 at all, although their customers may ask them about their continuity arrangements.
Who owns the continuity plan when my consulting engagement ends?
The client. The plan, the BIA and the evidence describe the client's organisation and decisions. Write into your engagement contract how the data is returned: a full export in a usable format, or the transfer of the workspace to the client's internal team.
Are spreadsheets enough for a small business continuity plan?
For a very small organisation and a one-off engagement, often yes, provided the plan stays readable, up to date and available offline. Spreadsheets become costly when you run several clients, when several people contribute to the BIA, or when you have to show an auditor who approved what and when.
Sources
- ISO 22301:2019, Security and resilience — Business continuity management systems — Requirements, clause 8.
- ISO 22313:2020, Security and resilience — Business continuity management systems — Guidance on the use of ISO 22301.
- Directive (EU) 2022/2555 (NIS2), Article 21(2)(c) and (d), OJ L 333, 27.12.2022.
- Regulation (EU) 2022/2554 (DORA), Article 11, OJ L 333, 27.12.2022.
- Regulation (EU) 2016/679 (GDPR), Articles 28 and 32.
- Business Continuity Institute, Good Practice Guidelines, 2018 Edition.