Template

Business Continuity Management Policy Template

A practical 20-clause BCM policy structure with governance, recovery objectives, BIA, continuity strategy, plans, DR, supplier resilience, exercises, assurance and exception management.

A BCM policy is the management mandate for the programme. It should establish purpose, scope, governance, responsibilities, minimum requirements, assurance and improvement without becoming a 100-page procedure. The detailed methods for BIA, plan writing, exercises and reporting can sit in standards/procedures referenced by the policy.

BCM policy template: 20 clauses

ClauseSuggested policy intent
1. PurposeCommit to continuing priority products/services through disruption and improving organisational resilience.
2. ScopeDefine legal entities, business units, sites, services and exclusions; state how outsourced activities are treated.
3. Policy objectivesProtect life/safety, meet obligations, preserve priority services, protect information/assets, recover within approved requirements and learn from disruption.
4. GovernanceName executive sponsor, BCM owner, steering/governance forum and escalation route.
5. Context and interested partiesRequire consideration of internal/external issues, customers, regulators, suppliers and other relevant interested parties.
6. Business impact analysisRequire a documented BIA method, approval, review and linkage to recovery requirements.
7. Risk / disruption assessmentDefine how disruption threats and vulnerabilities inform strategy without replacing BIA.
8. Recovery objectivesRequire approved MTPD/MAO, RTO, RPO and MBCO or equivalent measures where applicable.
9. Continuity strategiesRequire strategies for people, workplace, technology/data, suppliers and other resources; evaluate feasibility and cost/risk.
10. Plans and proceduresRequire actionable plans with activation, roles, workarounds, communications, recovery and return to normal.
11. ICT / disaster recoveryRequire technology recovery to support business priorities, with tested backup, restoration and reconciliation capability.
12. Supplier resilienceRequire critical supplier identification, due diligence, evidence, contractual expectations, concentration review and contingency/exit.
13. Incident and crisis interfacesDefine escalation and coordination between operational incidents, cyber response, crisis management and BCM.
14. CommunicationRequire internal/external communication ownership, approvals, fallback channels and regulatory/legal review where applicable.
15. Exercise and testingRequire risk-based validation from walkthroughs to integrated exercises and technology recovery tests.
16. Competence and awarenessRequire role-appropriate training, alternates and general staff awareness.
17. Documentation and recordsDefine document control, confidentiality, availability during outage, retention and evidence requirements.
18. Performance and assuranceRequire metrics, internal audit/review, management review and tracking of corrective actions.
19. Exceptions and risk acceptanceDefine who may approve deviations, expiry dates and compensating measures.
20. Review and continual improvementRequire scheduled and event-driven review after material change, incident, exercise, audit or regulatory change.

Example governance and responsibility matrix

RoleAccountability
Board / executive managementSet risk appetite and expectations; receive material resilience risks and performance information.
Executive sponsorChampions BCM, resolves cross-business issues and secures resources.
BCM functionMaintains methodology, coordinates BIA/plans/exercises, reports quality and gaps, supports assurance.
Business/service ownerApproves impact and recovery requirements; owns plan content, resources and business validation.
Technology / DR ownerMaintains recovery capability and evidence aligned to business priorities.
Supplier/procurement ownerMaintains continuity expectations, critical supplier evidence, concentration and exit actions.
Risk/compliance/legalAdvises on obligations, risk acceptance and regulatory communication.
EmployeesKnow notification, safety, escalation and continuity responsibilities relevant to their role.

Minimum control schedule

ControlMinimum evidenceTrigger for early review
BIAApproved BIA, assumptions, objectives, dependencies, gapsProcess/service/material volume/regulatory or technology change
BCPCurrent plan, contacts, role cards, controlled proceduresIncident, exercise finding, owner/site/supplier/system change
ExerciseObjectives, scenario, attendance, decisions, evidence, actionsMajor plan change or material new risk
DR capabilityMeasured recovery time/point, technical + business validationArchitecture/security/cloud/supplier change
Supplier resilienceAssessment/evidence, contract expectations, concentration/exitRenewal, criticality change, incident, supplier transformation
Management reviewDecisions, performance, unresolved gaps, resource actionsScheduled cycle or material deterioration

BCM exception / risk-acceptance record

FieldWhat to capture
Requirement not metExample: target RTO 2h; demonstrated capability 4h
Business impactWhat could happen during the two-hour gap?
ReasonTechnical constraint, programme transition, supplier limitation, funding or other verified cause
Compensating controlsManual service, priority routing, alternate supplier, extra backup, customer communication
Risk ownerPerson with authority to accept the residual risk
Expiry dateRisk acceptance should not silently become permanent
Action / fundingSpecific remediation, owner and milestone
MonitoringIndicator or event that forces re-evaluation

Policy wording to avoid

  • “All systems must have zero downtime.” It is generally unrealistic and not business-prioritised.
  • “All plans are tested annually” without defining what constitutes validation, scope or success.
  • “BCM owns business recovery.” Business/service owners must remain accountable for their requirements and decisions.
  • “The vendor is responsible for continuity.” Outsourcing does not remove the organisation’s dependency or accountability to its stakeholders.
  • Copying ISO clause text into a policy instead of designing controls that work in the organisation.

Official references and further reading

BCM policy control schedule

ControlMinimum policy statementEvidence
ScopeThe organisation defines BCMS scope based on products/services, legal entities, locations and dependencies.Approved scope and exclusions
BIACritical services/processes are analysed using an approved method and reviewed after material change.Current BIA and approval record
Recovery objectivesMTPD/MAO, RTO, RPO and MBCO are approved where applicable and reconciled with capability.Requirement register + gap decisions
StrategyRecovery strategies are selected on impact, feasibility, cost and dependency risk.Strategy decision and funded actions
PlansContinuity procedures contain activation, roles, workaround, communications and return-to-normal.Approved plan
Technology / DRCritical technology recovery supports business requirements and is periodically tested.DR test evidence
SuppliersCritical external dependencies are assessed, monitored and included in testing where material.Supplier resilience evidence
ExercisesPlans and capabilities are validated through a risk-based exercise programme.Exercise schedule + AAR
AssuranceMetrics, internal audit, management review and corrective action support continual improvement.Dashboard, audit, review minutes, action register
ExceptionsUnmet requirements are owned, time-bound and formally risk accepted or remediated.Exception/risk record

Policy exception template

FieldExample
RequirementCustomer portal service RTO ≤ 4 hours
Current capabilityLast integrated recovery test achieved 6h 20m
ReasonLegacy database restore sequence
Business impactPotential service unavailability beyond approved tolerance
Compensating controlRead-only status channel + priority manual support
ActionDatabase redesign and automated validation
Owner / due dateCIO / 31 Dec 2026
ApprovalService owner + risk authority
RetestIntegrated DR/business validation after remediation

Potential weakness in accountability and decision evidence

A completed approval field does not establish that a failure has been corrected or that a recovery arrangement works.

Validate the accountability and decision evidence decision

Sample decisions back to approval authority, dated operating evidence, exception expiry and verification of corrective-action effectiveness.

Further reading: BCI Good Practice Guidelines, Edition 7.0. This reference offers related guidance; the examples above are practical illustrations rather than quotations or universal requirements.