What Should a Business Continuity Plan (BCP) Include? A Section-by-Section Structure

The sections of a business continuity plan: activation triggers, roles, task lists, a resource table, return to normal and the task card used during a disruption.
Technical summary
Technology
ISO 22301, BCP, DRP
Topic
The structure of the business continuity plan document
Level
Intermediate
Prerequisites
  • Approved BIA and RTO targets
  • Selected continuity strategies
In this article9 sections

During a disruption, nobody opens a thick business continuity plan and reads it from the start. What you see in the field is this: the plan sits on the file server, and the file server is affected by the outage too; or the plan is opened but doesn’t say who makes which decision. The business continuity plan (BCP) defines who makes which decision during a disruption, in what order and with what resources prioritized activities continue and how to return to normal. It isn’t a long text written for the audit; it’s a working tool kept to hand during a disruption. Below we explain the sections of a BCP, what each section should contain and the task card format to use in a crisis.

The difference between a BCP, a DRP and an incident response plan

These documents are often confused or someone tries to merge them into one file. The distinction is made with a single question: “What are we recovering?”

Document Focus Owner Typical content
Business continuity plan (BCP) Continuing business activities Business continuity manager, process owners Activation, roles, temporary working methods, resources
Disaster recovery plan (DRP) Restoring IT systems and data IT Recovery order, technical steps, verification
Incident response plan Detecting, containing and eradicating a security incident Information security / SOC Classification, containment, evidence, notification
Crisis management plan Strategic decisions and external communication Top management Crisis team, decision log, stakeholder communication

The documents reference each other; they don’t copy each other. In a ransomware incident, the incident response plan manages containment, the DRP brings back clean systems, and the BCP describes how orders and shipping continue while the systems are down. All three run at the same time. Their owners are different. For the procedure structure on the incident response side, see the article incident management procedure; for managing crisis decisions and external communication, the guide crisis management and communication plan.

Activation criteria and decision authority

The weakest point of most plans is the first hour. Everyone looks at the monitoring screen, waits to hear from the provider, says “it’ll be fixed soon”; nobody activates the plan. Meanwhile, half the RTO has gone. The activation section must close this uncertainty and include:

  • Triggers: Measurable conditions. For example, “ERP access has been down for more than 2 hours with no estimated recovery time”, “access to the building is blocked”, “a critical supplier has said it can’t deliver”. Triggers are calculated backwards from the RTOs in the BIA; the decision must be made at a point where enough time is left in the RTO for recovery.
  • Assessment step: Who receives the first notification, who does the first assessment and how long that takes.
  • Decision authority: The people authorized to activate the plan and the order of deputies. If authority is tied to one person, the plan locks up while that person is on a plane; define at least two deputies.
  • Activation levels: The distinction between partial activation (a single process or location) and full activation.
  • Record: The time of the activation decision, who made it and why. This is the timestamp needed to measure the delay between the start of the disruption and the activation decision, and the actual recovery time.

Roles and team structure

The team structure varies with the organization’s size, but roles must be written down. In a medium-sized company, a typical structure is: the crisis management team (strategic decisions and external communication), the business continuity coordinator (running the plan and tracking status), process recovery teams (for each prioritized activity) and the IT recovery team (running the DRP). In small companies, these roles can be combined in the same people; even so, each role’s duties are written separately.

For each role, the plan includes: the role’s purpose, primary and backup person, authorities (spending limit, off-contract agreements with suppliers, redirecting staff to a different location), who it reports to and how often. Contact details go not in the body of the plan but in a separate, up-to-date annex. If phone numbers are written into the plan body, the plan goes out of date with the first staff change. How to reach teams and keep the list current is explained in the guide call tree and emergency contact list.

Process-based recovery task lists

The core of the plan is the task lists written for each prioritized activity. A task list isn’t a narrative; it’s a sequence of steps with owners. Each list follows this structure:

  1. Target: The activity’s RTO and minimum service level (MBCO).
  2. First steps: Stopping or pausing affected work, recording transactions in progress.
  3. Temporary working method: How the work will be done while the system is down; manual forms, an alternative application, orders by phone, processing from another location.
  4. Checkpoints: What status is reported at what time.
  5. Dependency check: Confirming the status of the processes the activity takes input from.

The temporary working method is the most neglected section. A BCP written on the assumption that “IT will bring the system back” is really a copy of the DRP and is useless the day IT can’t bring it back. The technical detail of IT recovery steps belongs in the DRP and runbooks; for the structure of a technical runbook, see the article preparing a disaster recovery runbook. The BCP contains only the outcome expected from IT and how the work continues until that outcome arrives.

Resource requirements

At the end of each task list, the resources needed to run the activity at a minimum level are written against a timeline. The resources come from the BIA, but in the plan they must be more concrete:

Source First 24 hours 1–3 days Where it comes from
Staff 2 people (orders) 4 people Sales support team, backup list
Application and data Customer list (offline copy) ERP order module Encrypted portable copy, DR environment
Equipment 2 laptops, mobile line Printer, label printer Spare equipment cabinet
Workplace Remote Backup office Alternative site agreement

The values in the table are examples. The workplace column depends on which option will be used in a site loss scenario; the options are compared in the article alternative workplace strategy. Writing only “spare equipment” in the plan isn’t enough; where the equipment is, who has the key and the date of the last check are written down too. A situation you may come across: the spare laptops sit in the cabinet but haven’t been updated for months, the VPN client is an old version and its certificate has expired. That’s why there’s a check date.

Return to normal

Return to normal doesn’t start when the disruption ends. It defines the controlled move from the temporary method back to normal working when systems or the site come back; an uncontrolled move creates a second disruption. This section covers:

  • Who decides to return to normal and which conditions must be met (e.g. the process owner performing a verification transaction in the application).
  • Entering records produced with the temporary method (manual forms, orders received by email) into the system, preventing duplicate records and reconciling.
  • Identifying and reprocessing transactions in the data loss window.
  • The logistics of moving back from the alternative site to the main site.
  • Closing the plan, a post-incident review meeting and improvement actions.

Making the plan usable: task cards

During a disruption, nobody reads a 40-page document from start to finish. That’s why, in organizations aiming for information security and business continuity compliance, the plan is designed in two layers: a reference document (justifications, dependencies, annexes) and task cards of no more than one page for each role. Task cards are kept on paper too; the disruption may also hit the file server where the plan is stored. A sample card:

TASK CARD – Order Recovery Lead
Rev: 3   Last checked: [date]   Plan section: 4.2

TRIGGER   : Business continuity coordinator announces "order plan active"
TARGET    : Take priority customer orders within 8 hours

FIRST 30 MINUTES
[ ] Reach team members (annex A: contact list)
[ ] Open the offline customer and price list (location: annex C)
[ ] Record pending orders (form SF-01)

FIRST 4 HOURS
[ ] Inform priority customers with a prepared message (approved template M-02)
[ ] Take phone orders using form SF-01
[ ] Report status to the coordinator every 2 hours

RETURN TO NORMAL
[ ] Enter SF-01 forms into the ERP, check for duplicates
[ ] Hand the reconciliation report to the coordinator

AUTHORITY : Revising delivery dates for priority customers
BACKUP    : [full name]

Whether the card works becomes clear in a tabletop exercise: can the participant explain their task just by looking at their card? If phrases open to interpretation, such as “if necessary” or “as appropriate”, remain on the card, it’s rewritten. Instructions open to interpretation aren’t followed in a crisis.

Common mistakes and maintenance

  • Embedding people’s names in the plan: The plan goes out of date as staff change. Roles go in the plan, people in an annex.
  • Writing for a single scenario: The plan isn’t written for “fire” or “cyber attack” but by type of impact: loss of building, loss of systems, loss of staff, loss of a supplier.
  • No triggers: If it isn’t clear when the plan is activated, the delay eats up the RTO.
  • No maintenance calendar: The plan is reviewed at least once a year and when organizational or system changes occur; a revision number and distribution list are kept.

To prepare the plan together with the BIA, see the business continuity plan and BIA service page; to prepare the recovery plan on the IT side, see the disaster recovery plan (DRP) service page. The requirements for plans within the management system are defined in clause 8.4 of ISO 22301:2019.

Frequently asked questions

Can the BCP and DRP be combined in a single document?

In small organizations they can be combined, but the sections must stay separate. The BCP describes how business activities will continue; the DRP describes how IT systems will be brought back. As their owners and update frequencies differ, keeping them separate makes maintenance easier.

How many pages should a business continuity plan be?

There’s no fixed page count. The sections used during a disruption must be short. Reference information is kept in annexes; task cards of no more than one page per role are the part of the plan actually used.

Should the plan also be kept on paper?

Yes. A disruption can affect the file server, email or cloud access where the plan is stored. Task cards and the contact list are kept on paper or accessible offline, with care taken to protect personal data.

How can you tell whether the plan works?

Through exercises. Participants being able to carry out their tasks using only their task cards in a tabletop exercise, and the temporary working method really being applicable in a functional exercise, show the plan is usable. The gaps found turn into a plan revision.

Support

Contact us for support or a discovery session on this topic.

Contact form
[email protected]

Eretek Compliance

We work with you on compliance with ISO 27001, IATF 16949, TISAX and similar standards, covering risk assessment, control design, documentation and audit preparation.

Knowledge Center

Other articles