← all systems · see it in The System
Business continuity
The capability of an organisation to continue delivering its products or services at pre-defined acceptable levels following a disruptive incident (src:wp:business-continuity-planning, quoting the BCI Good Practice Guidelines); the intended outcome of business continuity planning and disaster recovery executed together. Walked as continuity planners (NIST SP 800-34, ISO 22301, the BCI), disaster-recovery engineers and organisational-resilience researchers describe it: disruptive incidents and the dependencies they strike (people, processes, IT, facilities, suppliers) taken in; the business impact analysis that ranks critical processes and sets how long each may stop (MTD, RTO) and how much data may be lost (RPO); activation, relocation, workarounds, restoration and crisis communication when a disruption comes; tests, exercises and lessons learned that keep the plan current; and resilience (anticipate, cope, adapt) as the capability the practice builds.
Properties published scienceour proposal
Sourced fields, and our own readings.
| born at | mid to late 1970s (IT disaster recovery; BCM 'since the 1970s') |
| born precision | decade; government continuity planning older |
| boundary | Inside: the continuity programme (policy, business impact analysis, risk assessment of disruptions, strategies, plans, the teams and roles that run them, tests, training, exercises and maintenance), its records (the plan manual, call trees, vital records, backups and their offsite copies) and the arrangements made ahead (alternate sites, recovery contracts, workarounds). Outside: the disruptive events themselves, the organisation's day-to-day operations it protects, the suppliers, utilities and critical infrastructure it depends on, the customers and public it serves, insurers, regulators and standard setters, and the threat actors whose attacks it must survive. |
| nested level | A management practice inside organisations, a subset of risk management (src:wp:business-continuity-planning) and a component of emergency management and organisational resilience (src:nist-sp800-34r1); its IT part, disaster recovery, is itself a subset of business continuity (src:wp:it-disaster-recovery). In US government the same practice is continuity of operations (COOP), and continuity of government sits above it. |
| scale | social |
Measures (23) published science
| characteristic clock: plan review and capability test | 1 year |
| MTD for systems supporting mission essential functions (FCD-1) | <= 12 hours |
| COOP operation at an alternate site | up to 30 days |
| mobile site delivery | within 24 (often) hours |
| mirrored site availability | virtually 100 percent |
| mitigation return (BCP page) | 7 dollars of loss prevented per dollar |
| mitigation return (IT DR page) | 4 dollars saved per dollar |
| MSMEs not recovered within 14 days of flooding (Kigogo, Dar es Salaam, n=202) | 39.8 percent |
| MSME mean sales after/before flood (per-pass yield of the recovery) | 258,712 / 560,014 = 0.46 ratio (TZS) |
| MSMEs recovered within 9 days | 60.2 percent |
| stagnant water as main cause of delay | 63.18 percent of respondents |
| small businesses reopened six months after Pakistan's 2010 flood (Asgary et al. 2012, as reported) | 90 percent |
| companies without a tested plan going out of business within two years of a major disaster (Santangelo 2004, as quoted) | 80 percent (estimate) |
| ERNCIP survey: BCP at organisation level / department level / none | 53.39 / 29.66 / 11.86 percent of 118 |
| ERNCIP survey valid responses | 118 of 121 responses |
| critical external dependency: ICT / transport / electricity | 47.46 / 42.37 / 38.14 percent of participants |
| expected back-to-normal: days to weeks / months | 55.93 / 28.81 percent |
| COVID-19 response actions in 50 leading firms | 77 actions, 13 sub-areas, 5 areas count |
| ransomware attack rate 2023 vs 2021 | about 2 ratio |
| patients untreated after a cloud-platform breach (Yale New Haven Health) | over 200, for more than a week patients |
| recovery threshold (Hurricane Ida business network) | 85% of baseline visits for 3 consecutive days definition |
| hospital departments rated low risk (UBTH, 35 of 71 responding) | 0 departments |
| DR tiers (IBM 2012; SHARE 1992 had seven) | 8 (tier 0 to tier 7) tiers |
Open contentions (4) open contention
Where sources or readings disagree. Both stay on the map.
- C-1695 How much does a dollar spent preparing for disaster save?
booked: The map keeps both figures its sources give: seven dollars and four dollars.
the other reading: 7:1; 4:1 - C-1696 Do most businesses fail after a disaster?
booked: The map keeps the often-quoted 80% figure beside measured reopening rates of 60-90%.
the other reading: most firms without plans fail after a major disaster; most small businesses reopen but operate at a loss, with recovery depending on savings, aid, experience and age of business - C-1703 How do business continuity and disaster recovery relate?
booked: The map uses NIST's descriptions and notes that no agreed definitions exist.
the other reading: DR is a subset of BC; DR names BC when the cause is a disaster; BC is a subset of risk management; continuity is a component of emergency management - C-1723 What does organisational resilience mean?
booked: The map lists bouncing back, a capability to adapt, robustness, and an alternative to prevention, ruling none.
the other reading: outcome; meta-capability; robustness; alternative to prevention
Partners and parts published science
Built from / builds (11)
- Business continuity and disaster recovery
- Business impact analysis (BIA)
- IT disaster recovery
- Alternate sites
- Data backup and offsite storage
- Crisis management command structure
- Crisis communications plan
- Tests, training and exercises (TT&E)
- Business continuity management system (BCMS)
- Redundancy against other uses of resources
- Ransomware against continuity
Sits inside / holds (3)
Trades with (valence) (15)
- Insurance via sys:market · Business continuity mixed
- Security policy and governance via sys:written-record · Business continuity gain
- Human (Homo sapiens) via sys:human · Business continuity gain
- Government via sys:organization · Business continuity gain
- Law (rules and law) via sys:law · Business continuity gain
- Market and trade via sys:market · Business continuity gain
- Supply chain (production network) via sys:supply-chain · Business continuity mixed
- Incident response via sys:written-record · Business continuity gain
- Information security via sys:organization · Business continuity gain
- Risk management via sys:organization · Business continuity gain
- Organization via sys:organization · Business continuity gain
- Cloud computing via sys:information-system · Business continuity mixed
- Community (family, friends, neighbours) via sys:human · Business continuity gain
- Hazard via sys:hazard · Business continuity loss
- Critical infrastructure via sys:infrastructure · Business continuity gain
expressed by (22)
- Templating / Standardization
- Symbiosis/Co-Creation (Collaborative Specialization)
- Evolvability/Plasticity Engineering (Design for Future Variation)
- Distributed Autonomy/Decentralized Execution (Subsidiarity)
- Internal Coordination/Regulation
- Sensing/Scanning
- Mapping/Modeling
- Uncertainty Reduction/Learning
- Trail-Marking / Externalized Memory (Stigmergy)
- Surprise / Change-Point Detection
- Offline Simulation & Replay-Guided Planning
- Social Learning / Public Information Use
- Reactive Response
- Proactive Defense
- Self-Monitoring
- Validation of Effectiveness
- Enclave/Segregation
- Resilience & Repair
- Redundancy & Diversity
- Triage & Prioritized Allocation
- Quality Control & Error Correction
- Bridging Supply Gaps (Store & Dormancy)
floor filled by (16)
- Human (Homo sapiens)
- Government
- Supply chain (production network)
- Incident response
- Business continuity and disaster recovery
- Risk management
- Organization
- Business impact analysis (BIA)
- IT disaster recovery
- Alternate sites
- Crisis management command structure
- Crisis communications plan
- Tests, training and exercises (TT&E)
- Business continuity management system (BCMS)
- Hazard
- Critical infrastructure
Kinds (4)
Notes published science
- When ransomware took down a proton-therapy centre's systems, staff found the proton machines could still treat in stand-alone mode, ran their own webcams on cables under the treatment-room doors to watch patients, and were treating 40 patients a day by that Friday (src:siochi-2025-aapm).
- In flood-prone Kigogo, Dar es Salaam, the thing keeping most small shops shut wasn't broken equipment or lack of money but standing water: 63% named it as the main delay (src:sakijege-2024-msme).
- After Hurricane Ida, businesses didn't recover one by one: recovery spread like a contagion along networks built from where customers went before the storm, and shops and services acted as 'recovery multipliers' that pulled their neighbours back (src:liu-2024-recovery-diffusion).
Layers
The ways it takes in its world, where they meet, and how it acts back, each from L1 (where it meets the world) up.
business continuity as continuity planners and resilience researchers describe it: disruptive incidents and the organisation's dependencies, up to the continued delivery of its products and services (reader's view)
- L1: Disruptive incidents and the dependencies they strike: natural, technological and human-caused hazards; people, processes, IT, facilities, suppliers and documents
- L2: Detection and notification: outages identified, recovery teams called through the call tree; warnings received
- L3: Assessment: outage and damage assessed against activation criteria; risks assessed for likelihood and severity
- L4: Business impact analysis: critical processes ranked; MTD, RTO and RPO set
- L5: Activation and response: the plan invoked, operations relocated, restored or worked around, people protected, statements issued
- L6: The continuity programme: policy, plans, tests, training, exercises and maintenance (the BCMS)
- L7: Continued delivery of products and services at acceptable levels; resilience: anticipate, cope, adapt
the boardroom (shared floors)
- L4: Business impact analysis: critical processes and systems identified and prioritised; maximum tolerable downtime (MTD), recovery time objective (RTO) and recovery point objective (RPO) set; impact scenarios
- L5: Activation and response: the designated authority activates the plan when a criterion is met; the crisis command structure chooses among relocation, restoration, workarounds, communication and cooperation; recovery escalated and, at reconstitution, the plan deactivated
- L6: The continuity programme (BCMS): policy, strategies, plans, testing, training, exercises and maintenance in a plan-do-check-act cycle; the plan a living document
- L7: Continued delivery of products and services at acceptable levels through disruption; organisational resilience: anticipate, cope, adapt
way in: Customers' demand
- L1: Customer demand under disruption: irregular peaks and valleys (29.66%), steep decline (22.03%), rarely a steep surge
- L2: Inventory levels and customer purchasing behaviour monitored for impact on supply
- L3: Scenarios of demand and sales evolution defined with analytics and business intelligence
way in: Dependencies: the resources critical work runs on
- L1: Equipment, people (roles and responsibilities), suppliers and partners, technology (IT systems, communication), locations including backup and work-area recovery sites, documents and their offsite copies
- L2: Inventory: planners gather information about each resource
- L3: Critical activities and their dependencies (people, processes, vendors, technology, facilities) identified; single point dependencies named as threats
way in: Disruptive incidents: outages and disasters striking operations
- L1: Disruptive incidents: natural hazards (floods, storms, earthquakes, epidemics), technological hazards (utility disruptions, failures of systems and structures) and human-caused threats (cyber attacks, sabotage, war)
- L2: The outage or disruption identified; recovery teams notified through notification procedures and call trees
- L3: Outage assessment against the activation criteria: extent of damage, criticality of the system, expected duration longer than the RTO
way in: Early warnings and official guidance
- L1: A hazard developing outside: heavy rain over flood-prone ground, an epidemic spreading
- L2: Warnings received: official guidelines and recommendations (77.12%), a ward disaster management committee's early warning, the felt onset of heavy rain
- L3: Emergency monitoring through internal, inter-institutional and sector mechanisms (76.27%) and country-level public media (71.19%)
way in: Law, directives and standards
- L1: UK Civil Contingencies Act 2004; HSPD-20/NSPD-51 and FCD 1 (COOP); FISMA (contingency plans); ISO 22301; NFPA 1600
- L2: A formal contingency planning policy gives the authority and guidance to plan
- L3: Contingency planning controls selected for low, moderate or high impact systems (NIST SP 800-53 CP family)
- L4: Plan format and testing set by the FIPS 199 impact level
- L5: Formal assessment for accredited certification of the BCMS against ISO 22301
way in: Process owners' judgment of tolerable downtime
- L1: The mission/business processes in operation (payroll, customer service, clinical treatment)
- L2: Process owners, leadership and business managers consulted on acceptable downtime if a process or its data were unavailable
- L3: Impact categories (costs in staffing, overtime, fees; financial, operational, reputational, legal) given impact values
way in: Risk assessment of disruptions
- L1: Common threats: epidemic, earthquake, fire, flood, cyber attack, sabotage, storms, power, water and telecoms outages, IT outage, terrorism, war, theft, supplier failure, data corruption, misconfiguration
- L2: Internal and external threats identified; vulnerabilities and consequences analysed (no generator during a power outage)
- L3: Each risk assessed for likelihood and severity of impact and prioritised; impact scenarios documented
way in: Security incidents handed over by incident response
- L1: Cyberattacks on clinical and business systems: ransomware, a breached cloud platform reached with compromised credentials
- L2: Security personnel identify the malicious incident under the cyber incident response plan
- L3: Systems taken off the network or access removed to stop the spread; the normal workflow lost
way in: Suppliers, utilities and critical infrastructure
- L1: Suppliers and infrastructure services: ICT, transport and logistics, electric utilities
- L2: Changes in suppliers' service observed: transport and logistic issues, long delivery times, shortages of raw materials and personnel
- L3: The most critical external dependencies named (ICT 47.46%, transport 42.37%, electricity 38.14% of participants)
way in: Tests, training and exercises
- L1: A scenario-driven simulation of an emergency (a power failure in a data centre)
- L2: Tabletop discussion or functional exercise performed; staff act their roles
- L3: Timed rehearsals: recovery time actual (RTA) measured
- L4: Results written in an after-action report; lessons learned captured
- L5: Issues found are reintroduced to the analysis phase; corrective actions update the plan
way in: The state of recovered systems and data
- L1: Systems and data restored at the alternate site or in place
- L2: Validation data testing: recovered data complete and current to the last available backup
- L3: Functionality testing and concurrent processing at two locations until the recovered system is trusted
- L4: Recovery time actual set against the RTO
way in: The workforce: availability, health and felt risk
- L1: Staff availability, health and fear: health-care workers' fear and unwillingness to respond in outbreaks; staff unavailability
- L2: Mid-level managers' perceptions gathered by the hospital's business continuity team with a modified ILO risk-profile self-assessment
- L3: Departments rated low, medium or high risk across people, processes, profits and partnerships; none rated low
way out: Adapt: change the business itself
- L1: A new-to-business model: the core elements deliberately altered
- L3: Production converted (face masks, ventilators); new products and services
- L6: Strategy aligned and a portfolio of post-emergency actions and value-creation opportunities defined
way out: Communicate: crisis communications to staff, customers and the public
- L1: People told: patients told their care is being managed
- L3: Designated individuals as the only authority to speak; approved statements and press templates
- L5: The crisis communications plan invoked
way out: Cooperate: mutual support with other organisations
- L1: Support to public services, priority service to healthcare and emergency services (50.0%)
- L3: Partnering with nearby clinics with similar equipment; business-to-business staff sharing
- L5: Collaboration mechanisms chosen
way out: Prevent: preventive controls and mitigation before the event
- L1: Pre-disaster mitigation in place at the site (associated with recovery after floods)
- L3: Redundancy built: RAID, automatic failover, UPS, server clustering, mirrored systems; unused capacity, multiple sourcing, parallel processes
- L5: Preventive controls identified to reduce the effects of disruptions
way out: Protect people: first response and changed working conditions
- L1: Work shifts and smart working (80.51%), protective equipment (79.66%); teams rotated to the incubation period
- L3: Evacuation or shelter-in-place; equipment moved to safer ground
- L5: The occupant emergency plan executed first
way out: Relocate: move operations to an alternate site
- L1: Mission essential functions performed at the alternate site for up to 30 days
- L3: Operations moved to the alternate site; the mirrored site most expensive, the cold site cheapest and slowest
- L5: The DRP or COOP plan invoked for a disruption that denies the primary facility
way out: Restore: recover systems and data, then return to normal
- L1: Systems and data back in operation to the recovery point; normal operations resumed
- L2: Data validated against the last available backup; concurrent processing
- L3: Each affected system restored by its own contingency plan from backups
- L5: Recovery phase: recovery teams restore operations
way out: Work around: alternative and manual workflows
- L1: The service keeps being delivered: a proton centre back to 40 patients a day
- L3: Manual methods and stand-alone modes (paper orders, images on discs, phones, personal webcams)
- L5: Alternative workflows designed in advance by a working group for each stakeholder