Business Continuity Plan (BCP)
For demonstration and client adaptation • Version 1.0 • Last updated: 2025-08-12
Company Profile (ExampleCo): 50-person professional-services firm with one primary office and hybrid work. Core systems: Microsoft 365 (Exchange/Teams/SharePoint), QuickBooks Online, case/project system, cloud file storage, IdP (SSO/MFA), and VoIP telephony.
Document Control
- Plan Owner: COO • Continuity Coordinator: PMO Lead
- Approved by: CEO (Management Representative for ISMS)
- Next review date: [YYYY-MM-DD] (6-month cadence)
- Distribution: SharePoint “/ISMS/BCP/BCP-AUTH” (authoritative, read-only), PDF to managers
- Change log: Maintained in the header of the authoritative copy
ISMS Linkage & References (ISO 27001 Clauses 4–7)
- ISMS Scope ID: [ISMS-SCOPE-ID] • Context & Interested Parties: see ISMS §4
- Risk Assessment Reference (Clause 6.1): [Risk-RA-ID, method, date, owner]
- Risk Treatment & SoA (Clause 6.1.3): [SoA-ID] — controls applicable to continuity listed below
- Related Policies/Standards: Incident Response Policy, Backup & Restore Standard, Supplier Management Policy, Access Control Standard, Communications Policy
- Competence, Awareness, Communication (7.2–7.4): Roles require annual training; awareness delivered at onboarding + annually; comms workflow defined in §11
1) Purpose & Objectives
Ensure ExampleCo can prepare for, respond to, and recover from disruptive events (cyber, SaaS/ISP outages, facilities issues, severe weather, key-staff unavailability) while meeting client, legal, and contractual obligations.
Objectives (measured via KPIs in §16):
- Protect life and safety; maintain clear internal and client communications.
- Restore critical processes within RTOs and limit data loss to RPOs.
- Preserve confidentiality, integrity, availability during disruption per Annex A.5.29.
- Demonstrate ICT readiness for business continuity per Annex A.5.30 (tested backups, failovers, alternate services).
- Record evidence, lessons learned, and improvements.
2) Scope & Assumptions
Scope: All locations and remote workers; cloud and on-prem systems; interfaces with the Incident Response Plan (IRP) for cyber/operational events.
Included scenarios: ransomware/malware; primary ISP outage; SaaS outage (M365, CRM); office inaccessibility; regional disruption (power/weather); key-staff unavailability.
Assumptions: Managed laptops with MFA; third-party SaaS backups; vendor SLAs monitored; alternate connectivity available (LTE/5G).
3) Roles, Responsibilities & Competence
- Incident Manager (IM): COO (Deputy: Operations Director) — declares severity; coordinates response.
- Continuity Coordinator: PMO Lead (Deputy: HR Lead) — maintains plan; runs tests; after-action reviews.
- IT/DR Lead: IT Manager (Deputy: Senior SysAdmin) — technical recovery; workarounds; evidence capture.
- Communications Lead: Marketing Lead (Deputy: Executive Assistant) — internal/client communications, approvals.
- Facilities & Safety: Office Manager (Deputy: HR Lead) — physical safety, access, re-entry.
- Legal/Privacy: General Counsel (Deputy: Outside Counsel) — regulatory/contractual notices.
Competence & Awareness: Each role completes continuity/IR training annually; records stored in LMS. Awareness refreshers issued after exercises/incidents.
4) Severity Levels & Declaration
- SEV1 (Critical): Major service disruption impacting most staff/clients; executive engagement required.
- SEV2 (Major): Significant but contained disruption; degraded service for key teams/clients.
- SEV3 (Minor): Localized or short-lived issue.
Declaration flow: Detect & triage → IM declares SEV → Mobilize team (“#continuity-war-room” in Teams; phone/SMS for SEV1) → Internal update within 60 minutes → cadence every 2–4 hours or as material changes occur.
5) Risk Assessment Summary (links to ISMS RA & SoA)
Top risks from ISMS RA that drive RTO/RPO and strategies:
| Risk | Source | Inherent Rating | Treatment / Control (SoA Ref) | | --------------------- | ---------------- | --------------: | -------------------------------------------------------------------- | | Ransomware | Endpoints/e-mail | High | IR playbook, EDR, backups (daily), MFA, allow-lists (A.5.29, A.5.30) | | SaaS outage (M365) | Provider | Medium | Alt comms (phone/SMS), offline work SOPs, status monitoring | | ISP outage (HQ) | Network | Medium | LTE/5G failover, remote-work activation | | Office unavailable | Facility | High | Remote-work posture, loaner devices, call-forward | | Key staff unavailable | People | Medium | Deputy list, SOPs, cross-training |
6) Critical Processes & Recovery Objectives (Clause 8.1)
| Process | Owner | RTO | RPO | Recovery Strategy / Workarounds | | --------------------------- | ------------------- | --- | --- | -------------------------------------------- | | Client Comms & Deadlines | Operations Director | 4h | 60m | Templates; Teams/phone tree; deputy list | | Revenue Ops & Invoicing | Finance Lead | 8h | 4h | QBO export; manual invoicing; secure vault | | Case/Project Delivery | Practice Leads | 8h | 60m | Cloud repos; offline SOPs; alternate devices | | Identity & Access (SSO/MFA) | IT Lead | 2h | 15m | IdP restore runbook; break-glass accounts | | Telephony & Contact Center | IT Lead | 4h | 60m | VoIP failover; call-forward to mobiles |
Where targets cannot be met, record risk acceptance or compensating controls (owner, date).
7) Information Security During Disruption (Annex A.5.29)
- Access control in fallback: MFA on break-glass; least privilege; log exceptional access.
- Data handling: Encryption in transit/at rest persists; no personal e-mail/storage; redact sensitive data in ad-hoc channels.
- Logging & evidence: Preserve endpoint, IdP, and SaaS logs; store decision log; archive comms for audit/forensics.
- Manual workarounds: Define how confidentiality/integrity are preserved when using manual steps (who, where, how recorded).
8) ICT Readiness for Business Continuity (Annex A.5.30)
- Dependencies: apps (M365, case system, QBO), IdP/SSO, telephony, WAN/ISP, laptops, vendor status/SLAs.
- Alternate services: Secondary ISP; LTE/5G routers; phone/SMS comms; DR region or provider-level failover (if available).
- Recovery objectives: RTO/RPO per §6.
- Testing plan: See §15; acceptance criteria defined (RTO met %, restore success, comms drill time).
9) Continuity Playbook (At-a-Glance)
A. Internal Comms — update within 60 min; then every 2–4h.
B. Client Comms — trigger on client impact/missed SLAs/likely data exposure; use approved templates.
C. Workarounds — prioritize critical processes, remote-work posture, alternate comms if M365 down.
D. Evidence Capture — decision log, screenshots, restore reports, vendor tickets → audit folder.
10) Communications Plan & Snippets (Clause 7.4)
Internal (Teams):
“Declared SEV2 affecting Microsoft 365. Use phone/SMS for urgent comms. Client updates at 10:30. Next internal update by 11:00.”
Customer e-mail:
“We’re experiencing a disruption affecting [service/process]. Your data remains protected. We expect degraded service until [ETA] and will update you by [time]. For urgent needs, call [number].”
Status banner:
“Service disruption in progress. Next update by [time].”
Approval workflow: Draft → Comms Lead → Legal/Privacy (if regulatory/contractual) → IM approval → send/publish.
11) Backups & Restore Testing Summary
| System | Backup Method | Restore Test Type | Last Test | Result | | ------------------- | ------------------------------------ | ----------------------- | ---------- | ------ | | Microsoft 365 | Third-party daily + 30-day retention | Point-in-time restore | 2025-06-15 | Pass | | Case/Project System | Nightly snapshot + weekly export | Table-level restore | 2025-07-10 | Pass | | File Storage | Hourly snapshots + off-site copy | Granular folder restore | 2025-07-01 | Pass | | QuickBooks Online | Weekly export to encrypted vault | Test import/compare | 2025-06-27 | Pass |
Policy: Critical systems demonstrate quarterly restore success and documented RTO/RPO results (evidence in /ISMS/BCP/Evidence).
12) Supplier & Cloud Continuity (Annex A — Supplier Controls)
- Minimum continuity requirements in contracts: RTO/RPO targets, incident notice time, evidence on request.
- Critical suppliers & contacts:
- IdP (SSO/MFA): Support 1-800-555-0110 • status.idp-example.com
- VoIP: Support 1-800-555-0111 • status.voip-example.com
- Backups Vendor: Support 1-800-555-0112 • portal.backup-example.com
- MSP: On-call 1-800-555-0113 • mspportal.example
- Monitoring: Who checks status pages; who escalates if SLAs breached; where exceptions are logged.
13) Alternate Work Arrangements
- Remote-work activation: All staff remote; daily stand-ups at 09:00/15:00.
- Loaner laptops: Pre-imaged devices off-site; same-day ship.
- Telephony: Forward main line to call center/mobiles; update voicemail.
- Facilities re-entry: Coordinate with property management and Safety lead; record safety checks.
14) How We Operate the Plan (3 Steps)
- Assess (1–2 weeks): Interviews; process & asset mapping → Gap Report.
- Build (2–4 weeks): BCP/IRP documents; training deck; comms templates.
- Test (1 week): Tabletop exercise → After-Action Report; update plan.
(Timelines adjust by size/regulatory scope.)
15) Testing, Training & Maintenance
- Quarterly Tabletop: Rotate scenarios (SaaS outage, ransomware, facilities).
- Annual Full Restore Test: Prove RTO/RPO; retain evidence & results.
- Comms Drill (Call Tree): Twice per year; target <30 minutes completion.
- Plan Review & Update: Every 6 months or after change/incident.
- Training: New-hire onboarding + annual refresher for role holders.
16) Monitoring, KPIs & Evidence (Clause 9.1)
Track and review quarterly (inputs for management review §18):
- % Incidents meeting RTO/RPO (target: ≥90%)
- Backup/restore success rate (target: 100% quarterly)
- Exercises completed vs plan (target: 100% quarterly tabletop; 100% annual restore)
- Findings closed within SLA (e.g., 30/60/90 days based on severity)
- Supplier SLA exceptions (count/impact)
Evidence repository: “/ISMS/BCP/Evidence/[Year-Qtr]”
17) Internal Audit & Management Review (Clauses 9.2–9.3)
- Internal Audit: Semiannual audit of BCP/IRP controls; next due [YYYY-MM-DD].
- Last audit summary: [findings, severity, actions, owners, due dates]
- Management Review: At least annually; inputs include KPIs (§16), incidents, audit results, supplier issues.
- Decisions & Actions: Recorded with owners and due dates; tracked to closure.
18) Nonconformity & Continual Improvement (Clause 10)
- NCR Log Location: “/ISMS/BCP/NCR-Log.xlsx”.
- Corrective Action Template: cause → action → owner → due date → verification/effectiveness.
- Lessons Learned: Incorporated after incidents/exercises; tracked to closure in improvement backlog.
19) Appendices (Optional in Full Plan)
A) Contact lists (staff, deputies, emergency services)
B) Detailed recovery runbooks (per system/process)
C) Regulatory/contractual notice requirements
D) Vendor contracts & SLAs (continuity clauses)
E) Decision log & after-action report templates
F) Training & awareness records (role matrix, completions)
Executive One-Minute Summary
- What matters: People safe, clients informed, critical work continues.
- How: Declare severity → mobilize team → apply workarounds → restore using tested backups → communicate on cadence → capture evidence → improve.
- Targets: Meet RTO/RPO for critical processes; pass quarterly restore tests; complete quarterly tabletop; close findings on time.
End of ISO-Aligned High-Level BCP Example

