What it is (plain English)
Preparing the business to keep running through disruptions: analyzing which processes are critical and how quickly they must recover (business impact analysis), building and maintaining continuity plans, and coordinating response when something actually happens.
Problems it solves
- Continuity plans written once, filed away, and never tested or updated.
- No clear picture of which processes are critical and their recovery targets.
- Disorganized response when a real disruption hits.
- Plans disconnected from the actual risks and systems involved.
What must exist first
Platform Core Setup. Best paired with Risk Management (continuity addresses the risks that materialize) and CMDB/service data for impact analysis.
What the customer needs to provide
- Your critical business processes and their dependencies.
- Recovery objectives (RTO/RPO) where defined.
- Existing continuity/DR plans, however current.
- Roles and escalation for crisis response.
- Testing/exercise cadence expectations.
Where it can go next
Continuity draws on Risk Management; impact analysis uses CMDB Foundation/service data; crisis workflows coordinate response and can link to Health & Safety critical events.