Ask Two Different Planning Questions
Contingency planning asks how an organization will respond to a plausible emergency scenario. Business continuity planning asks how its essential functions will keep operating during disruption. They connect, but a response plan does not automatically keep payroll, communications or purchasing available.
Use the service-chain explanation before comparing the two. The comparison below uses one fictional flood setting so that differences follow from the questions, rather than from unrelated examples.
Separate the Plans in a Fictional Flood Scenario
| Dimension | Contingency Planning | Business Continuity Planning |
|---|---|---|
| Starting question | If flooding isolates Lakeside, how will the organization respond? | If staff, premises or systems are disrupted, which essential functions must remain available? |
| Main focus | Anticipated needs, response roles, coordination and readiness | Organizational dependencies, minimum functioning and recovery priorities |
| Fictional preparation | Agree who checks needs, who coordinates with authorities and what triggers response | Identify authorized payment deputies, safe staff contact routes and access to essential records |
| Evidence to test | Scenario assumptions, available response capacity and current coordination | Whether the fallback actually works when the usual person or system is absent |
| What it does not establish | That the office and all internal systems will remain usable | That the organization has the mandate or capacity to meet every emergency need |
Neither column is a compulsory universal template. Real owners, applicable duties, safety procedures and response arrangements determine the plan.
Find the Gap Between Them
Lakeside's fictional contingency plan names a supplier for an emergency delivery. Its usual payment authorizer is away and the bank requires that person's action. The goods may exist, yet the order cannot proceed as assumed. A continuity exercise exposes the authority dependency. It cannot simply bypass the bank's controls; responsible owners must establish a permitted arrangement.
In the opposite direction, an organization may restore email and purchasing successfully while having no agreed role in the municipal flood response. A functioning office does not prove that an intervention is needed, coordinated or safe. The contingency discussion must connect organizational capacity with the actual emergency and responsible public mechanisms.
Test a Shared Failure, Then Reconnect
Suppose the backup supplier and primary supplier both rely on the same flooded road. Listing two suppliers does not resolve that dependency. The continuity team records that its fallback is unverified; the response team revises its assumption about arrival times. Neither promises that another route is safe without current specialist confirmation.
The useful output is two linked decisions: a scenario-specific response arrangement and an organizational continuity arrangement supporting it. Assign the owners and recheck assumptions when personnel, access, authority or essential systems change. Include staff safety and duty of care through the responsible process, using the existing security reference.
Use the continuity-priority tutorial to practice this connection without inventing technical minimums.
Source and Applicability
IFRC's contingency-planning page, What Is Contingency Planning and Contingency Planning vs Business Continuity Planning, supplies the distinction. Its page points to the 2025 National Society guide; this comparison relies on the inspected definitions, not uninspected procedures in that guide. Consulted October 29, 2026. UN-Habitat's urban-services overview adds system context, not emergency operating instructions. No fictional fallback is field-validated.
