BCM module · ISO 22301 · DORA · NIS2

Business Continuity Management (BCM).
From BIA to a tested plan.

ISO 22301, Article 11 of DORA and Article 21 of the NIS2 Directive require business continuity plans that are documented, up to date and tested. The BCM module in BCMLogic Next moves business impact analysis, emergency plans, scenarios and tests out of Word documents into a single database – linked to the real processes, resources and vendors of your organisation.

In brief

What is the BCM module in BCMLogic Next?

It is business continuity management software that takes the organisation through the full BCM cycle: business impact analysis (BIA), strategies and emergency plans, scenarios, tests and post-test recommendations. Process and resource data come from the Organisation module, so the RTO set in the BIA flows straight into the plans, and test results flow back into the analysis.

Key facts

BIA: step-by-step wizard – context, impact, RTO, RPO, MTPD, MAC, key assets, contracts, sub-processes, critical periods

Emergency plans: DR procedures, operational plans and process continuity plans in a phases-and-teams editor

Tests: schedule of scenario and procedure tests – internal and with vendors

Lifecycle: status workflow, versioning and plan version comparison

Standards and regulations: ISO 22301, DORA, NIS2
See it in action

What working in the BCM module looks like

Short recordings from the BCMLogic Next platform. Pick an area on the left – the next recording starts automatically when one ends.

BCMLogic Next · Business Continuity

BIA wizard: the process owner goes through the steps – context, impact, time parameters (RTO, RPO, MTPD, MAC) and key assets. Progress is shown on the left.
BIA parameters

RTO, RPO, MTPD and MAC – what you set in a BIA

Four parameters determine how fast and to what extent a process must recover. The timeline shows how they relate during a disruption.

Disruption
RTO
MTPD
RPO
operating at MAC
RTO exceeded
unacceptable loss

Example timeline of a process disruption. RTO, RPO and MTPD are set in the BIA for each process separately.

RPO – Recovery Point Objective

The maximum period for which data may be lost. It determines how often backups or replication must run.

RTO – Recovery Time Objective

The time within which a process or resource must be back in operation after a disruption. Recovery strategies and priorities follow from it.

MTPD – Maximum Tolerable Period of Disruption

The longest outage after which the impact on the organisation becomes unacceptable. RTO must be shorter.

MAC – Minimum Acceptable Configuration

The minimum set of resources – people, systems, locations, vendors – needed to keep a process running in emergency mode.

The BCM cycle

The full business continuity cycle in one system

Each stage builds on the previous one, so the plan never drifts away from the analysis and test findings do not stay in someone’s notes.

1

Business impact analysis (BIA)

For each process: financial, operational, regulatory and reputational impact, time parameters and the minimum resource configuration built from the resource and contract registers.

2

Strategies and emergency plans

Who, what, in which order and with which resources – measured against the RTO from the BIA. DR plans, operational plans, staff relocation plans.

3

Scenarios

Plans grouped into scenarios by type of event. A scenario specifies which plans to activate and in what order.

4

Tests and exercises

Schedule of scenario and procedure tests, tabletop exercises and vendor-involved tests – with the status of every test.

5

Recommendations and updates

Findings from tests and audits become tasks with an owner and deadline. Changes flow back into the BIA and the plans.

Requirements the module addresses
ISO 22301
BIA and risk assessment (8.2), strategies (8.3), business continuity plans (8.4), exercise and testing programme (8.5).
DORA – Article 11
ICT business continuity policy, response and recovery plans, regular plan testing.
NIS2 – Article 21(2)(c)
Business continuity, backup management, disaster recovery and crisis management.
Poland: amended KSC Act (2026)
Essential and important entities must implement their obligations, including continuity within the ISMS, by 3 April 2027.

This summary is for information only. The scope of obligations depends on the entity’s status and current legislation.

Module features

What the business continuity module includes

Ready-made screens and workflows based on methodologies developed over more than ten years of implementations. Use them as they are or adapt them to your own methodology in implementation workshops.

Comprehensive register

Processes and functions, services, resource requirements, organisational structure, crisis teams and backup locations in one repository.

Guided BIA

A configurable wizard covers process criticality, time objectives and the minimum acceptable resource configuration.

Continuity risk assessment

Risk assessed by process, resource (IT, people, locations, vendors) or unit – with potential losses linked to BIA data.

Versioned procedures

A repository of plans and procedures with a version comparator: differences between the current and draft version are visible before approval.

Scenarios and notifications

Scenarios based on event type, likelihood and impact. They can be linked hierarchically and trigger notifications.

Tests and recommendations

Plan tests of any combination of procedures, processes and resources, and track post-audit recommendations in a dedicated workflow.

What this means in practice

A process owner who does a BIA once a quarter does not need to know the system. The wizard – or a conversation with the Expert GRC assistant – guides them with questions, suggests resources used in similar processes and ends with a summary for approval. The BCM team gets consistent data instead of spreadsheets in different formats.

Related modules

Business continuity draws on data from the whole platform

BCM does not work in isolation. The same processes, resources and contracts feed risk assessment and vendor oversight.

Organisation

Structure, process and asset registers, plus What-If analysis: what stops working when a specific system or vendor fails.

Organisation module →

Risk management

Business continuity risks in the risk register, with controls, treatment plans and KRIs.

Risk module →

Vendor management

Contracts identified in the BIA as essential for a process, assessed against DORA, NIS2 and continuity requirements.

Vendor module →

Online demo

See a BIA and an emergency plan on data similar to yours

In the demo we walk through the BIA of a selected process, an emergency plan and the test schedule – and show how BIA results translate into risk and vendor data.

Book a demo →

Live walkthrough

About 30 minutes with a BCMLogic expert, focused on your questions and your sector.

Your methodology

We look at how impact scales, wizard steps and workflow can match the methodology your organisation uses.

FAQ

Frequently asked questions about business continuity management

Answers to the questions we hear most often from BCM, risk and security teams.

What is business continuity management (BCM)?
Business continuity management (BCM) is the process that allows an organisation to maintain or quickly restore critical processes after a disruption – an IT failure, cyberattack, or loss of a location, staff or vendor. It covers business impact analysis (BIA), continuity strategies and plans, testing and continual improvement. The framework for a business continuity management system is set out in ISO 22301.
What is a BIA and how do you carry it out in BCMLogic Next?
A business impact analysis (BIA) determines how an interruption to a process affects the organisation over time and what its recovery requirements are. In BCMLogic Next the process owner goes through a wizard: process context, impact (financial, operational, regulatory, reputational), RTO, RPO, MTPD and MAC, key assets, vendor contracts, sub-processes and critical periods. The result is stored in the BCM register and becomes the basis for emergency plans.
What is the difference between RTO, RPO and MTPD?
RTO (Recovery Time Objective) is the time within which a process must be back in operation. RPO (Recovery Point Objective) is the maximum period for which data may be lost. MTPD (Maximum Tolerable Period of Disruption) is the longest outage after which the impact becomes unacceptable – RTO must be shorter than MTPD. MAC, the minimum acceptable configuration, completes the picture by defining the resources needed to operate in emergency mode.
What business continuity requirements does DORA impose?
Article 11 of DORA requires financial entities to have an ICT business continuity policy, response and recovery plans, and regular testing of those plans; Article 12 requires backup policies and restoration procedures. BCMLogic Next keeps these elements in one place: the BIA, plans, test schedule and test findings are linked to processes and ICT resources.
Does NIS2 require business continuity plans?
Yes. Article 21(2)(c) of the NIS2 Directive lists business continuity – including backup management, disaster recovery and crisis management – among the mandatory cybersecurity risk-management measures. In Poland, the amended National Cybersecurity System (KSC) Act has applied since 3 April 2026, and essential and important entities have until 3 April 2027 to implement their obligations, including an information security management system.
How should business continuity plans be tested?
Plans are tested on a schedule: from document reviews, through tabletop exercises, to technical recovery tests. In BCMLogic Next the schedule covers tests of scenarios and individual procedures, including tests involving vendors. Each test has a status, and findings go into a recommendations register with an owner and deadline, then into BIA and plan updates.
How do we move existing BIAs and plans from Word or Excel into BCMLogic Next?
Existing documentation is the starting point for implementation workshops. Processes, resources and parameters from previous analyses are transferred into the platform registers, and plans are recreated in the phases-and-teams editor. The scope and method of migration are agreed individually during the demo and implementation.
What should ISO 22301-aligned BCM software include?
Business continuity management software should include a register of processes and resources, a BIA with time parameters, continuity risk assessment, plans and procedures under version control, a testing programme and tracking of corrective actions. An audit trail – who changed what and when – is also essential. BCMLogic Next covers all of these in one module linked to risk and vendor management.
Next step

A business continuity plan that works on the day of the disruption

We will show how BCMLogic Next connects the BIA, plans, tests and vendors into one process – and how to keep it current without assembling documents by hand before every audit.

Book a demo →