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
| Clause | Suggested policy intent |
|---|---|
| 1. Purpose | Commit to continuing priority products/services through disruption and improving organisational resilience. |
| 2. Scope | Define legal entities, business units, sites, services and exclusions; state how outsourced activities are treated. |
| 3. Policy objectives | Protect life/safety, meet obligations, preserve priority services, protect information/assets, recover within approved requirements and learn from disruption. |
| 4. Governance | Name executive sponsor, BCM owner, steering/governance forum and escalation route. |
| 5. Context and interested parties | Require consideration of internal/external issues, customers, regulators, suppliers and other relevant interested parties. |
| 6. Business impact analysis | Require a documented BIA method, approval, review and linkage to recovery requirements. |
| 7. Risk / disruption assessment | Define how disruption threats and vulnerabilities inform strategy without replacing BIA. |
| 8. Recovery objectives | Require approved MTPD/MAO, RTO, RPO and MBCO or equivalent measures where applicable. |
| 9. Continuity strategies | Require strategies for people, workplace, technology/data, suppliers and other resources; evaluate feasibility and cost/risk. |
| 10. Plans and procedures | Require actionable plans with activation, roles, workarounds, communications, recovery and return to normal. |
| 11. ICT / disaster recovery | Require technology recovery to support business priorities, with tested backup, restoration and reconciliation capability. |
| 12. Supplier resilience | Require critical supplier identification, due diligence, evidence, contractual expectations, concentration review and contingency/exit. |
| 13. Incident and crisis interfaces | Define escalation and coordination between operational incidents, cyber response, crisis management and BCM. |
| 14. Communication | Require internal/external communication ownership, approvals, fallback channels and regulatory/legal review where applicable. |
| 15. Exercise and testing | Require risk-based validation from walkthroughs to integrated exercises and technology recovery tests. |
| 16. Competence and awareness | Require role-appropriate training, alternates and general staff awareness. |
| 17. Documentation and records | Define document control, confidentiality, availability during outage, retention and evidence requirements. |
| 18. Performance and assurance | Require metrics, internal audit/review, management review and tracking of corrective actions. |
| 19. Exceptions and risk acceptance | Define who may approve deviations, expiry dates and compensating measures. |
| 20. Review and continual improvement | Require scheduled and event-driven review after material change, incident, exercise, audit or regulatory change. |
Example governance and responsibility matrix
| Role | Accountability |
|---|---|
| Board / executive management | Set risk appetite and expectations; receive material resilience risks and performance information. |
| Executive sponsor | Champions BCM, resolves cross-business issues and secures resources. |
| BCM function | Maintains methodology, coordinates BIA/plans/exercises, reports quality and gaps, supports assurance. |
| Business/service owner | Approves impact and recovery requirements; owns plan content, resources and business validation. |
| Technology / DR owner | Maintains recovery capability and evidence aligned to business priorities. |
| Supplier/procurement owner | Maintains continuity expectations, critical supplier evidence, concentration and exit actions. |
| Risk/compliance/legal | Advises on obligations, risk acceptance and regulatory communication. |
| Employees | Know notification, safety, escalation and continuity responsibilities relevant to their role. |
Minimum control schedule
| Control | Minimum evidence | Trigger for early review |
|---|---|---|
| BIA | Approved BIA, assumptions, objectives, dependencies, gaps | Process/service/material volume/regulatory or technology change |
| BCP | Current plan, contacts, role cards, controlled procedures | Incident, exercise finding, owner/site/supplier/system change |
| Exercise | Objectives, scenario, attendance, decisions, evidence, actions | Major plan change or material new risk |
| DR capability | Measured recovery time/point, technical + business validation | Architecture/security/cloud/supplier change |
| Supplier resilience | Assessment/evidence, contract expectations, concentration/exit | Renewal, criticality change, incident, supplier transformation |
| Management review | Decisions, performance, unresolved gaps, resource actions | Scheduled cycle or material deterioration |
BCM exception / risk-acceptance record
| Field | What to capture |
|---|---|
| Requirement not met | Example: target RTO 2h; demonstrated capability 4h |
| Business impact | What could happen during the two-hour gap? |
| Reason | Technical constraint, programme transition, supplier limitation, funding or other verified cause |
| Compensating controls | Manual service, priority routing, alternate supplier, extra backup, customer communication |
| Risk owner | Person with authority to accept the residual risk |
| Expiry date | Risk acceptance should not silently become permanent |
| Action / funding | Specific remediation, owner and milestone |
| Monitoring | Indicator 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
- ISO 22301:2019 — Requirements for a BCMS.
- ISO 22313:2020 — Guidance on applying ISO 22301.
- BCI GPG 7.0 — Professional practice structure for BCM.
BCM policy control schedule
| Control | Minimum policy statement | Evidence |
|---|---|---|
| Scope | The organisation defines BCMS scope based on products/services, legal entities, locations and dependencies. | Approved scope and exclusions |
| BIA | Critical services/processes are analysed using an approved method and reviewed after material change. | Current BIA and approval record |
| Recovery objectives | MTPD/MAO, RTO, RPO and MBCO are approved where applicable and reconciled with capability. | Requirement register + gap decisions |
| Strategy | Recovery strategies are selected on impact, feasibility, cost and dependency risk. | Strategy decision and funded actions |
| Plans | Continuity procedures contain activation, roles, workaround, communications and return-to-normal. | Approved plan |
| Technology / DR | Critical technology recovery supports business requirements and is periodically tested. | DR test evidence |
| Suppliers | Critical external dependencies are assessed, monitored and included in testing where material. | Supplier resilience evidence |
| Exercises | Plans and capabilities are validated through a risk-based exercise programme. | Exercise schedule + AAR |
| Assurance | Metrics, internal audit, management review and corrective action support continual improvement. | Dashboard, audit, review minutes, action register |
| Exceptions | Unmet requirements are owned, time-bound and formally risk accepted or remediated. | Exception/risk record |
Policy exception template
| Field | Example |
|---|---|
| Requirement | Customer portal service RTO ≤ 4 hours |
| Current capability | Last integrated recovery test achieved 6h 20m |
| Reason | Legacy database restore sequence |
| Business impact | Potential service unavailability beyond approved tolerance |
| Compensating control | Read-only status channel + priority manual support |
| Action | Database redesign and automated validation |
| Owner / due date | CIO / 31 Dec 2026 |
| Approval | Service owner + risk authority |
| Retest | Integrated 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.