EVOPEDIA

← 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 atmid to late 1970s (IT disaster recovery; BCM 'since the 1970s')
born precisiondecade; government continuity planning older
boundaryInside: 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 levelA 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.
scalesocial

Measures (23) published science

characteristic clock: plan review and capability test1 year
MTD for systems supporting mission essential functions (FCD-1)<= 12 hours
COOP operation at an alternate siteup to 30 days
mobile site deliverywithin 24 (often) hours
mirrored site availabilityvirtually 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 days60.2 percent
stagnant water as main cause of delay63.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 / none53.39 / 29.66 / 11.86 percent of 118
ERNCIP survey valid responses118 of 121 responses
critical external dependency: ICT / transport / electricity47.46 / 42.37 / 38.14 percent of participants
expected back-to-normal: days to weeks / months55.93 / 28.81 percent
COVID-19 response actions in 50 leading firms77 actions, 13 sub-areas, 5 areas count
ransomware attack rate 2023 vs 2021about 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.

Partners and parts published science

Built from / builds (11)

Sits inside / holds (3)

Trades with (valence) (15)

expressed by (22)

floor filled by (16)

Kinds (4)

Notes published science

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)

  1. L1: Disruptive incidents and the dependencies they strike: natural, technological and human-caused hazards; people, processes, IT, facilities, suppliers and documents
  2. L2: Detection and notification: outages identified, recovery teams called through the call tree; warnings received
  3. L3: Assessment: outage and damage assessed against activation criteria; risks assessed for likelihood and severity
  4. L4: Business impact analysis: critical processes ranked; MTD, RTO and RPO set
  5. L5: Activation and response: the plan invoked, operations relocated, restored or worked around, people protected, statements issued
  6. L6: The continuity programme: policy, plans, tests, training, exercises and maintenance (the BCMS)
  7. L7: Continued delivery of products and services at acceptable levels; resilience: anticipate, cope, adapt

the boardroom (shared floors)

  1. 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
  2. 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
  3. 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
  4. L7: Continued delivery of products and services at acceptable levels through disruption; organisational resilience: anticipate, cope, adapt

way in: Customers' demand

  1. L1: Customer demand under disruption: irregular peaks and valleys (29.66%), steep decline (22.03%), rarely a steep surge
  2. L2: Inventory levels and customer purchasing behaviour monitored for impact on supply
  3. L3: Scenarios of demand and sales evolution defined with analytics and business intelligence

way in: Dependencies: the resources critical work runs on

  1. 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
  2. L2: Inventory: planners gather information about each resource
  3. 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

  1. 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)
  2. L2: The outage or disruption identified; recovery teams notified through notification procedures and call trees
  3. 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

  1. L1: A hazard developing outside: heavy rain over flood-prone ground, an epidemic spreading
  2. L2: Warnings received: official guidelines and recommendations (77.12%), a ward disaster management committee's early warning, the felt onset of heavy rain
  3. 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

  1. L1: UK Civil Contingencies Act 2004; HSPD-20/NSPD-51 and FCD 1 (COOP); FISMA (contingency plans); ISO 22301; NFPA 1600
  2. L2: A formal contingency planning policy gives the authority and guidance to plan
  3. L3: Contingency planning controls selected for low, moderate or high impact systems (NIST SP 800-53 CP family)
  4. L4: Plan format and testing set by the FIPS 199 impact level
  5. L5: Formal assessment for accredited certification of the BCMS against ISO 22301

way in: Process owners' judgment of tolerable downtime

  1. L1: The mission/business processes in operation (payroll, customer service, clinical treatment)
  2. L2: Process owners, leadership and business managers consulted on acceptable downtime if a process or its data were unavailable
  3. L3: Impact categories (costs in staffing, overtime, fees; financial, operational, reputational, legal) given impact values

way in: Risk assessment of disruptions

  1. 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
  2. L2: Internal and external threats identified; vulnerabilities and consequences analysed (no generator during a power outage)
  3. L3: Each risk assessed for likelihood and severity of impact and prioritised; impact scenarios documented

way in: Security incidents handed over by incident response

  1. L1: Cyberattacks on clinical and business systems: ransomware, a breached cloud platform reached with compromised credentials
  2. L2: Security personnel identify the malicious incident under the cyber incident response plan
  3. L3: Systems taken off the network or access removed to stop the spread; the normal workflow lost

way in: Suppliers, utilities and critical infrastructure

  1. L1: Suppliers and infrastructure services: ICT, transport and logistics, electric utilities
  2. L2: Changes in suppliers' service observed: transport and logistic issues, long delivery times, shortages of raw materials and personnel
  3. L3: The most critical external dependencies named (ICT 47.46%, transport 42.37%, electricity 38.14% of participants)

way in: Tests, training and exercises

  1. L1: A scenario-driven simulation of an emergency (a power failure in a data centre)
  2. L2: Tabletop discussion or functional exercise performed; staff act their roles
  3. L3: Timed rehearsals: recovery time actual (RTA) measured
  4. L4: Results written in an after-action report; lessons learned captured
  5. L5: Issues found are reintroduced to the analysis phase; corrective actions update the plan

way in: The state of recovered systems and data

  1. L1: Systems and data restored at the alternate site or in place
  2. L2: Validation data testing: recovered data complete and current to the last available backup
  3. L3: Functionality testing and concurrent processing at two locations until the recovered system is trusted
  4. L4: Recovery time actual set against the RTO

way in: The workforce: availability, health and felt risk

  1. L1: Staff availability, health and fear: health-care workers' fear and unwillingness to respond in outbreaks; staff unavailability
  2. L2: Mid-level managers' perceptions gathered by the hospital's business continuity team with a modified ILO risk-profile self-assessment
  3. L3: Departments rated low, medium or high risk across people, processes, profits and partnerships; none rated low

way out: Adapt: change the business itself

  1. L1: A new-to-business model: the core elements deliberately altered
  2. L3: Production converted (face masks, ventilators); new products and services
  3. 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

  1. L1: People told: patients told their care is being managed
  2. L3: Designated individuals as the only authority to speak; approved statements and press templates
  3. L5: The crisis communications plan invoked

way out: Cooperate: mutual support with other organisations

  1. L1: Support to public services, priority service to healthcare and emergency services (50.0%)
  2. L3: Partnering with nearby clinics with similar equipment; business-to-business staff sharing
  3. L5: Collaboration mechanisms chosen

way out: Prevent: preventive controls and mitigation before the event

  1. L1: Pre-disaster mitigation in place at the site (associated with recovery after floods)
  2. L3: Redundancy built: RAID, automatic failover, UPS, server clustering, mirrored systems; unused capacity, multiple sourcing, parallel processes
  3. L5: Preventive controls identified to reduce the effects of disruptions

way out: Protect people: first response and changed working conditions

  1. L1: Work shifts and smart working (80.51%), protective equipment (79.66%); teams rotated to the incubation period
  2. L3: Evacuation or shelter-in-place; equipment moved to safer ground
  3. L5: The occupant emergency plan executed first

way out: Relocate: move operations to an alternate site

  1. L1: Mission essential functions performed at the alternate site for up to 30 days
  2. L3: Operations moved to the alternate site; the mirrored site most expensive, the cold site cheapest and slowest
  3. 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

  1. L1: Systems and data back in operation to the recovery point; normal operations resumed
  2. L2: Data validated against the last available backup; concurrent processing
  3. L3: Each affected system restored by its own contingency plan from backups
  4. L5: Recovery phase: recovery teams restore operations

way out: Work around: alternative and manual workflows

  1. L1: The service keeps being delivered: a proton centre back to 40 patients a day
  2. L3: Manual methods and stand-alone modes (paper orders, images on discs, phones, personal webcams)
  3. L5: Alternative workflows designed in advance by a working group for each stakeholder

Sources (16) published science

Business continuity planning (Wikipedia, via Wikimedia Enterprise snapshot 2026-11-01)
Swanson M, Bowen P, Phillips AW, Gallup D, Lynes D (2010). NIST SP 800-34 Rev. 1, Contingency Planning Guide for Federal Information Systems. doi:10.6028/NIST.SP.800-34r1 (behind its links)
Duchek S (2020). Organizational resilience: a capability-based conceptualization. Business Research 13, 215-246. doi:10.1007/s40685-019-0085-7 (behind its links)
Liu C-F, Hsu C-W, Mostafavi A (2024). Dynamics of Post-disaster Recovery in Behavior-dependent Business Networks. arXiv:2409.12357 (behind its links)
Galbusera L, Cardarilli M, Giannopoulos G (2021). The ERNCIP survey on COVID-19: Emergency & Business Continuity for fostering resilience in critical infrastructures. Safety Science 139. doi:10.1016/j.ssci.2021.105161 (behind its links)
Siochi RA, Balter P, Hedrick S, et al. (2025). AAPM working group on cybersecurity report 438: A white paper on cybersecurity management for business continuity in radiology and radiation therapy. J Appl Clin Med Phys 26. doi:10.1002/acm2.70358 (behind its links)
Continuity of government (Wikipedia) (behind its links)
IT disaster recovery (Wikipedia) (behind its links)
Sakijege T (2024). Disaster recovery and business continuity: A case of MSMEs in Dar es Salaam. Jàmbá: Journal of Disaster Risk Studies 16. doi:10.4102/jamba.v16i1.1714 (behind its links)
Margherita A, Heikkilä M (2021). Business continuity in the COVID-19 emergency: A framework of actions undertaken by world-leading companies. Business Horizons 64. doi:10.1016/j.bushor.2021.02.020 (behind its links)
Ndubuisi et al. (2024). COVID-19 and Health-care Business Continuity in Africa: Perceptions of Risks and Vulnerabilities by Mid-level Management Staff in a Tertiary Care Hospital. Annals of African Medicine 24. doi:10.4103/aam.aam_145_21 (behind its links)
ISO 22301 (Wikipedia) (behind its links)
Hanson & Straub (2026). Cyber insurance, audit, and policy: review, analysis and recommendations. arXiv:2602.03127 (behind its links)
Chief information security officer (encyclopedia) (behind its links)
U.S. critical infrastructure protection (Wikipedia, via WME; redirect from Critical infrastructure protection) (behind its links)
Edelman GM, Gally JA (2001). Degeneracy and complexity in biological systems. PNAS 98. doi:10.1073/pnas.231499798 (behind its links)