Business Continuity Management Policy: What a BCM Policy Must Contain

A business continuity management (BCM) policy is the charter for your program. It answers three questions: what does the organization require, who is accountable, and by what authority? A good business continuity management policy does that in three to five pages, carries a top executive’s signature, and rarely changes.

Most of the policies I read do something else. As I said on Managing Uncertainty, Episode 332, “Most resilience policies I read either are a mission statement with a logo on it, or a 40-page plan pretending to be a policy.”

I recently reviewed a large global company’s business continuity policy against ISO 22301. It missed most of the standard’s policy requirements. Nowhere did it require anyone to exercise anything.

That policy wasn’t a small gap. It was the reason the program had nothing to stand on.

What a Business Continuity Management Policy Does

“A resilience policy is not your plan. It is the charter for your program.” Every Business Impact Analysis (BIA), every plan, and every exercise traces its legitimacy back to it. When a business unit leader asks why they have to update their plan this year, the answer is the policy.

That only works if three things are true:

  • It is short. Three to five pages. Anything longer is carrying standards or plan content that will go stale.
  • It states requirements, not aspirations. “Each business unit maintains a current plan” is a requirement. “We value preparedness” is a poster.
  • The right person signs it. “A policy signed by the BC manager has about as much authority as that BC manager has in the organization.” The CEO, or an executive with enterprise authority, signs it.
Old View New View
The policy is a statement of commitment The policy is a charter with requirements and authority
Longer means more thorough Three to five pages; the detail lives in standards and plans
The BC manager owns and signs it Top management signs it; the program manager maintains it
Exercises are encouraged Every plan is exercised at least annually, by requirement
Reviewed when audit asks Reviewed every year, and reported against every quarter

BCM Policy vs. BCM Framework

The two terms get used interchangeably. They are different documents doing different jobs, and you need both.

The BCM policy sets the rules: scope, ownership, roles, requirements, the standard you measure against, and how often it all gets reviewed. It changes rarely.

The BCM framework is how you meet those rules: the BIA method, risk assessment, recovery strategies, plan templates, the exercise program, training, maintenance, and reporting. It changes as the program matures.

I think about it as a three-layer stack:

Layer What it does
Policy Short, executive-signed, rarely changes. What is required, who is accountable, by what authority.
Standards Measurable requirements: how often the BIA is refreshed, what every plan must contain, how often plans are exercised.
Plans and procedures The operational documents teams actually run during a disruption.

When the policy tries to do the standards’ job, it becomes a 40-page document nobody reads. When it tries to do the plans’ job, it goes stale in six months.

What ISO 22301 Requires of a BCM Policy

ISO 22301, the international standard for business continuity management systems, covers the policy in clause 5.2. Top management must establish a business continuity policy that:

  • Is appropriate to the purpose of the organization
  • Provides a framework for setting business continuity objectives
  • Commits to satisfying applicable requirements
  • Commits to continual improvement of the business continuity management system

The policy must also be documented, communicated within the organization, and available to interested parties as appropriate.

That is the floor. A policy can meet every word of clause 5.2 and still fail to drive a program, which is why we build ours around seven elements.

The Seven Elements of a Business Continuity Management Policy

  1. Purpose and scope. Name what the program covers (business continuity, crisis management, IT disaster recovery) and where it applies: legal entities, geographies, subsidiaries. “Scope ambiguity is where programs quietly die.” The business unit that assumed it was out of scope is the one that has the disruption.
  2. Top management commitment. One clear statement that executives own the program and will resource it. “The CEO signed this” lands differently than “my team needs this for compliance.”
  3. Roles and authority. The executive sponsor, the program owner, plan owners, and who can activate a plan, declare a disaster, stand up the crisis team, and approve recovery spending. “If your policy doesn’t name decision makers, then you’re going to be negotiating it live at two o’clock in the morning in the middle of the major incident.” Our post on business continuity program roles and responsibilities covers who should hold each one.
  4. Program requirements. A BIA on a defined cycle. A current plan for every critical function. Every plan exercised at least annually. Training for everyone with a crisis role.
  5. Your yardstick. Name the standard or regulation you measure against: ISO 22301, the FFIEC handbook, the NIST Cybersecurity Framework, or the rules that apply to your industry. Our guide to business continuity regulations by industry lists the common ones.
  6. Review cadence and exceptions. Review the policy every year. Give business units a legitimate exception path, with a named approver and an expiration date. Without one, they don’t comply harder. They ignore you quietly.
  7. Measurement and reporting. Plan currency, exercise completion, and BIA coverage, reported to the steering committee or the board. “A policy that nobody reports against is a suggestion.” Our three key metrics for business continuity program success are a good place to start.

A One-Page BCM Policy Outline

If you are starting from scratch, this outline fits on one page and grows to three to five:

  1. Purpose: why the organization maintains a business continuity management program
  2. Scope: disciplines covered, entities, locations, and any exclusions with the reason for each
  3. Definitions: business continuity, crisis management, IT disaster recovery, critical function
  4. Policy statement: top management’s commitment, in two or three sentences
  5. Roles and authority: sponsor, steering committee, program manager, plan owners, activation and declaration authority
  6. Requirements: BIA cycle, plans, exercises, training, maintenance
  7. Standards and regulations the program aligns to
  8. Exceptions: how to request one, who approves, when it expires
  9. Measurement and reporting: what is reported, to whom, how often
  10. Review: annual review owner, approval, and effective date

The policy then points to your standards documents for the detail. The steering committee owns those. For how that governance runs day to day, see why good business continuity governance is critical to resilience.

Four Ways BCM Policies Go Wrong

  • The policy that’s secretly a plan. Call trees, recovery steps, and vendor lists inside the policy. It is out of date before it’s signed.
  • The missing exercise requirement. “If your policy does not require exercises, then you don’t have a resilience policy. You have a documentation policy.” Plans that are never tested are dusty things that sit on shelves.
  • The wrong signature. A policy signed below top management carries only the signer’s authority.
  • The time capsule. The policy names departments, executives, or systems that no longer exist. Nobody has opened it since the last reorganization.

Review Your BCM Policy This Week

You can test your current policy in under an hour:

  1. Read it cold. Can you find the scope, the requirements, and who has decision authority in five minutes? If not, neither can anyone else.
  2. Check it against ISO 22301 clause 5.2. Purpose, objectives framework, commitment to requirements, continual improvement, documented and communicated.
  3. Search it for the word “exercise.” If it isn’t there as a requirement, add it first. One sentence in a policy will drive more real capability than any plan template.

FAQs about BCM Policy

What does BCM stand for?

BCM stands for business continuity management: the program that keeps critical functions running through a disruption and recovers them afterward. It usually includes business continuity planning, crisis management, and alignment with IT disaster recovery.

What is the BCM program policy?

It is the same document as the business continuity management policy: the short, executive-approved charter that sets the program’s scope, roles, requirements, and reporting. Everything else in the program, from the BIA to the exercise schedule, takes its authority from it.

What is the BCM policy statement?

The policy statement is the two or three sentences inside the policy where top management commits to business continuity. It belongs in the policy, not instead of it. A statement with no requirements, roles, or reporting behind it is a mission statement.

What is the difference between a BCM policy and a business continuity plan?

The policy sets the rules for the whole program. A business continuity plan is an operational document for one business unit, site, or function: who does what, in what order, to keep a critical process running or restore it within its recovery time objective (RTO). The policy requires the plans. It never contains them.

Get the policy right and everything else in your program has something to stand on.

Keep Going

A few ways to go deeper if this was useful.

Bryan Strawser Avatar

About the author

Let’s build your Resilience Roadmap

Our team has spent two decades helping the world’s leading organizations prepare for and navigate disruption. We’ll bring that experience to yours.