What this is
What is a business continuity plan?
What is a business continuity plan?
A document that identifies the operation's critical processes, states how long each can be down before harm becomes unacceptable, and sets out the people, systems, suppliers and premises arrangements that keep them running or bring them back inside that time. It is built against a business impact analysis and reviewed at a stated interval, typically annually.
Who owns a business continuity plan?
Senior management, because the decisions in it — which processes are critical, what downtime is tolerable, what alternative supplier is authorised — carry cost beyond what a single function can approve. Maintenance is usually delegated, but sign-off sits with the level that can actually commit resource to it.
How is a business continuity plan different from an emergency response plan?
An emergency response plan covers the first hours of an event: who does what during a fire, spill or medical emergency. A continuity plan covers what happens after, over the following days and weeks, to keep the operation trading. Sites with only the response plan can manage the event but have not planned the recovery.
Scope
When is a business continuity plan required?
The plan is the whole-operation instrument covering people, suppliers, systems and premises together. It is not the record of a single drill, and not the instructions for the first hour of an event.
Use this template when
- A first business continuity plan is being written for a site or operation
- The annual review interval has been reached
- A change has occurred to a critical process, single-source supplier, key person or site that the current plan does not reflect
- A new site is being brought into the continuity programme and needs its own plan
- An exercise, debrief or real event has raised an action that changes the plan's arrangements
Do not use it for
- A single emergency event, where the immediate response belongs in the site's Emergency Response Plan
- A practice evacuation or fire drill, recorded in its own drill record, not folded into the continuity plan
- A single hazard's contingency in isolation, such as an ammonia release response, which has its own dedicated plan
- A supplier contract negotiation, which the plan references by outcome rather than documents in full
- Recording a specific test's results, which belongs in the exercise or continuity exercise record linked back here
Compliance mapping
Which ISO 22301 requirements does this satisfy?
ISO 22301 does not prescribe a plan format. It requires that critical activities and their tolerable downtime be established through analysis, that arrangements protect them, and that those arrangements be exercised.
| Clause | Requirement | Where it lands |
|---|---|---|
| ISO 22301 cl.8.2.2 | Business impact analysis identifying critical activities, resource dependencies and maximum tolerable downtime | Critical dependencies |
| ISO 22301 cl.8.2.3 | Risk assessment of threats capable of disrupting prioritised activities and dependencies | Critical dependencies |
| ISO 22301 cl.8.4.2 | Response structure defining roles, alternative staffing and supplier dependency arrangements | People, suppliers and systems |
| ISO 22301 cl.8.4.3 | Warning and communication procedure for staff, customers and other interested parties | People, suppliers and systems |
| ISO 22301 cl.8.4.4 | Documented plans and procedures enabling recovery within the tolerable period | Header |
| ISO 22301 cl.5.3 | Roles, responsibilities and authorities for the continuity programme assigned | Header |
| ISO 22301 cl.8.5 | Exercise programme testing the plan at planned intervals, outcomes used to correct it | Testing |
| ISO 22301 cl.9.1 | Monitoring, measurement and evaluation of continuity performance | Testing |
What it does not cover
- Emergency Response Plan, which sets out who does what during the event itself, rather than how the operation recovers over the days that follow.
- Business Continuity Exercise Record, which captures what happened during a specific test of this plan, rather than being the plan tested.
- Emergency Debrief Report, which captures lessons from a real event or drill and feeds a change back into this plan, but is not itself a continuity arrangement.
- A single-hazard contingency, such as an ammonia release response or fire risk assessment, which addresses one hazard's response rather than the whole operation's recovery.
- Supplier and vendor contracts, which the plan references as the authorised alternative but does not itself constitute.
Global
Business Continuity Plan requirements by country
Business continuity is close to universally voluntary in law, and close to mandatory in practice wherever customers or insurers expect evidence that an operation can survive disruption.
NFPA 1600; DHS PS-Prep
No general statutory duty to hold a plan outside regulated sectors such as banking.
Adoption is driven by customer due diligence and sector regulators, not a single federal mandate.
Civil Contingencies Act 2004 (public Category 1 responders); ISO 22301 for the private sector
Statutory duties apply to public responders; private operators adopt the standard contractually.
A private site has no legal duty to hold a plan, but food, pharmaceutical and finance customers routinely require one.
ISO 22301
Certifiable standard requiring business impact analysis, documented plans and a tested exercise programme.
Auditors examine whether tolerable downtime figures came from analysis, and whether the plan was actually exercised.
How to complete it
How to complete a business continuity plan, step by step
Most of what makes a continuity plan defensible sits outside the fields a template prompts for — in whether the numbers came from analysis and whether the arrangements were ever tested.
A figure entered because it sounds reasonable is not a business impact analysis. It should come from what actually happens if the process stops — stock spoiling, a contractual penalty, a regulatory deadline — and different processes on the same site will tolerate very different lengths of outage.
Identifying a single-source supplier or a key-person dependency is half the work. The plan is only useful if it also names the alternative supplier or stand-in, and states that the alternative has actually been approved rather than merely considered.
A refrigeration or ammonia dependency does not behave like a generic IT outage — stock can be lost within hours, not days — and scoring it on the same scale as slower-moving risks under-resources the arrangement that most needs one.
An annual review date checks the wording. Only an exercise — even a tabletop walkthrough — checks whether the alternative supplier can scale, the backup site has capacity, and the named stand-in knows the role. Reviewed but never exercised means proofread, not tested.
What auditors find
Most common business continuity plan findings
A continuity plan almost always exists once a programme is established. The findings concern whether its numbers came from analysis and whether its arrangements were ever checked.
| Finding | Clause | What fixes it |
|---|---|---|
| Maximum tolerable downtime not defined for one or more critical processes. | ISO 22301 cl.8.2.2 | Derive a specific figure per process from the consequence of it stopping, not a blanket site figure. |
| Single-source supplier identified with no alternative supplier approved. | ISO 22301 cl.8.4.2 | Name and approve the alternative before the dependency is recorded as managed. |
| Key person dependency identified with no alternative staffing arrangement. | ISO 22301 cl.8.4.2 | Name who can perform the role and confirm competence, not just a job title. |
| Plan not tested within the stated interval. | ISO 22301 cl.8.5 | Schedule and run at least a tabletop exercise, and record the date against the plan. |
| Ammonia, cold chain or other site-specific contingency scored as passed with no arrangement behind the score. | ISO 22301 cl.8.2.3 | Attach the actual arrangement — the backup refrigeration, the alternative cold store — not a scored answer alone. |
| Action raised from a review or test left without an owner, date or CAPA reference. | ISO 22301 cl.9.1 | Assign an owner and CAPA reference when the action is raised, and verify it before closing. |
Case in point
Case in point: the plan that had never lost power
A dairy site held a continuity plan naming backup refrigeration as the contingency for a power failure, scored as passed at every annual review for three years. The plan had never been exercised — reviews consisted of the owner reading the document and re-signing it.
A transformer fault took the site off grid for eleven hours. The backup generator started, but had never been load-tested against refrigeration plant added the previous year, and tripped within forty minutes. Product across three cold stores was lost before mains power returned. The generator existed, the plan named it, and neither fact was worth anything because nobody had run the two together.
The template
The template, field by field
The form exactly as it installs. Every field, option, score and conditional rule is editable, and the links to other templates come with it.
4 sections
- Reference
- SAF-075
- Archetype
- Plan
- Record ID
- BCP-2026-000
- Scoring
- Not scored
- Direction
- n/a
- Singleton
- No
- Basis
- ISO 22301
- Links
- Links Site, Vendor
- Tags
- Emergency, Continuity
- Sections
- 4
- Fields
- 37
- Follow up fields
- 3
- Repeating sections
- 0
- Links out
- 3
Header
9 fieldsPlan ID*
Auto sequence. Format BCP-2026-000.
The record's own ID. Other templates point at this value.
Status*
Drives who this goes to next.
- Planned2 pts
- In progress2 pts
- Complete3 pts
- Deferred0 pts
- Open0 pts
- Closed3 pts
- Overdue0 pts
Site*
Site ID*
Format SITE-000.
Links to FDN-001 Site ID
Plan Version*
Issue Date*
Next Review Due*
Plan Owner*
Approved By*
Critical dependencies
8 fieldsCritical Processes Identified*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Maximum Tolerable Downtime Defined*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Ammonia Refrigeration Contingency*
Losing refrigeration in a meat or dairy plant destroys stock within hours.
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Cold Chain Contingency Defined*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Backup Power Arrangements*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Water Supply Contingency*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Effluent Contingency*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Steam Or Boiler Contingency
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
People, suppliers and systems
7 fieldsKey Person Dependencies Identified*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Alternative Staffing Arrangements*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Single Source Suppliers Identified*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Alternative Suppliers Approved*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Alternative Production Site Available
- Yes2 pts
- No0 pts
- N/Aexcluded from denominator
Customer Communication Plan*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Data And Records Backed Up*
- Pass2 pts
- Partial1 pt
- Fail0 pts
- N/Aexcluded from denominator
Testing
13 fieldsPlan Tested In Last 12 Months*
- Yes3 pts
- No0 pts
Last Test Date
Next Test Due*
Plan Document
Document ID
Format DOC-0000.
Links to FDN-008 Document ID
Action Required*
Raise the action record, then enter its reference here.
- No2 pts
- Yes0 pts
Priority
- High0 pts
- Medium1 pt
- Low3 pts
CAPA ID
Format CAPA-2026-00000.
Links to FDN-014 CAPA ID
Action Owner
Plan Owner*
Signature*
Site Manager*
Second Signature*
SAF-075 · record IDs look like BCP-2026-000 · Links Site, Vendor
Open in KnowellaRun it with agents
From a document you fill in to a programme that runs itself
The plan is a document. What actually fails is the surrounding machinery: the supplier that changed and was never fed back in, and the alternative arrangement that existed on paper only.
Holds the plan against the site, supplier and equipment registers, flags when a linked record changes, and routes the review to the plan owner.
Watches supplier, staffing and site records for events that should trigger an unscheduled review, and raises it rather than waiting for the annual date.
Connects the plan's alternative staffing arrangements to the competency records confirming the named stand-in can perform the role.
This template lives in KnowSafe — safety and compliance. Incidents, hazards, permits, inspections and the critical controls behind them.
Meet KnowSafe→Glossary
Business Continuity Plan definitions and key terms
- Business impact analysis
- The process of identifying critical activities and the impact their disruption would have over time, producing the maximum tolerable downtime figures the plan is built around.
- Maximum tolerable downtime
- The longest period a critical activity can be disrupted before consequences become unacceptable, used to set how fast recovery must be.
- Critical activity
- A process whose loss would, within its tolerable downtime, cause unacceptable harm — the unit the whole plan is organised around.
- Single point of failure
- A supplier, person, system or piece of equipment with no alternative, whose loss stops a critical activity outright.
- Exercise
- A planned test of the plan's arrangements, from a tabletop discussion to a full simulation, used to find gaps a paper review cannot.
FAQ
Frequently asked questions about business continuity plan
How is a business continuity plan different from a disaster recovery plan?+
Disaster recovery usually refers to IT and data systems recovery specifically, while continuity covers the whole operation: people, suppliers, premises and systems together. A continuity plan should reference the disaster recovery plan rather than duplicate it.
Does every site need its own plan?+
Where sites have materially different critical processes, suppliers or dependencies, yes. A plan written for one site and reused for another carries assumptions — which supplier, which backup arrangement — that may simply be wrong for the second site.
What counts as testing the plan?+
Anything from a tabletop discussion to a full simulation involving the alternative site or supplier. What matters is that an assumption gets challenged by someone other than the person who wrote it, not the exercise's format.
Who should be involved in writing the plan?+
Senior management for the resourcing decisions, and the people who run the critical processes for the dependency detail. A plan written by a single function in isolation reliably misses dependencies only the process owner would know to name.
How often does the plan need reviewing?+
At the stated interval, typically annually, and immediately when a critical process, supplier, site or key staffing arrangement changes. The interval is a backstop for changes nobody flagged; the change itself is the trigger that matters.
What should trigger an unscheduled review?+
A new single-source supplier, a new critical process, a key person leaving, a change to refrigeration, power or IT infrastructure, or any finding from an exercise or event that showed an arrangement did not work as written.
Keep going
Related templates and programmes
Industries this is written for
Programmes this belongs to
Used together in Emergency Preparedness
Contractor Emergency Drill Participation
Records contractor involvement in an evacuation or emergency drill, including whether they were accounted for
Site Resilience and Continuity Plan
Sets out how the site keeps operating or recovers after loss of power, refrigeration, water, IT, key equipment or people
Business Continuity Exercise Record
Records a test of the continuity plan, what worked and what did not
Environmental Spill Drill Record
Records a practice spill response, timed from discovery to containment
Emergency Response Plan
Sets out what happens in a fire, medical emergency, spill, power failure or evacuation, including who does what
Evacuation Drill Record
Records a practice evacuation, including clearance time, headcount and anything that went wrong
More in Emergency
Emergency Response Plan
Sets out what happens in a fire, medical emergency, spill, power failure or evacuation, including who does what
Evacuation Drill Record
Records a practice evacuation, including clearance time, headcount and anything that went wrong
Fire Drill Record
Records a fire specific drill, including alarm activation, route use and warden performance
Emergency Equipment Inspection
Checks alarms, extinguishers, spill kits, defibrillators and emergency stops are present and working
Muster Point Check
Checks assembly points are marked, reachable and safe to stand in
Emergency Contact Register
Holds emergency contacts for the site, including services, key staff and neighbouring operations
Written and reviewed by
Siddarth Singh
Founder & Chief Executive Officer, Knowella
Certified Safety Professional and industrial and systems engineer with more than a decade inside food supply chain, freight and manufacturing operations. This page was written against the current text of the standards it cites, not against secondary summaries of them.
- Certified Safety Professional (CSP), Board of Certified Safety Professionals
- MBA, University of Chicago Booth School of Business
- MS and BS, The Ohio State University, Industrial and Systems Engineering
- Six Sigma Black Belt
Sources and last review. Reviewed 16 August 2026 against:
- ISO 22301:2019 clauses 5.3, 8.2, 8.4, 8.5 and 9.1
- NFPA 1600, Standard on Continuity, Emergency and Crisis Management Programs
- UK Civil Contingencies Act 2004, Category 1 responder duties
- DHS Voluntary Private Sector Preparedness Accreditation Program (PS-Prep)
This page is general guidance, not legal advice. Confirm requirements with your jurisdiction’s regulator.