Purpose

Review, audit and improve the BCM program and retain reliable evidence of its design and operation.

Steps

#ActionDetailsEvidence
1Collect current recordsBIA, risk, plan, incident, training, exercise, supplier, corrective-action recordsRecord collection
2Review BCM programAt least annually and after material disruption, failed exercise, or significant change; periodic reviews triggered by system changes, new regulations, mergers, relocations, major incidents; conduct Annual Board Review of updated BCM plansBoard review minutes
3Reassess proportionalityWhether scope, controls, and automation remain proportionate to Bitkaya’s size, complexity, and riskProportionality assessment
4Arrange annual auditIndependent internal and external BCM audit; findings documented and actions followed up; appropriate independenceAudit report
5Present results to BoardReview and audit results, material risks, overdue actions presented to management and BoardBoard presentation
6Assign corrective actionsOwners, priorities, due dates; track to verified closureCorrective-action register
7Update BCM documentsPlans, procedures, controls, training based on lessons learnedUpdated documents
8Retain records securelyApproved versions and evidence with controlled access and retrievable history: BCM policy/plans/sub-plans, training attendance/materials, test scripts/results/corrective plans, incident reports/root cause analyses/regulatory reportsRecords archive
9Re-assess proportionalityAnnually in Compliance Review and Audit cycle, or on operational growth, new services, new jurisdictions/regulatory regimes, or technology/outsourcing changes; adjustments ensure BCM stays fit-for-purpose and cost-effectiveProportionality review record

Records

  • Annual management and Board review
  • Internal or external audit report
  • Corrective-action register and closure evidence
  • Lessons-learned reports
  • Approved BCM documents and version history

Relationships

Assurance

Runtime effectiveness results are maintained in Odoo and assessed through the Hermes workflow tracked in ISS-HERMES-001. This note defines design, ownership, evidence expectations and testing method; it does not contain a manually maintained operation, evidence or overall effectiveness rating.

  • Frequency: annual and event-driven

History

  • 2026-07-26: Created from sections 14, 15 and 16 of the approved Business Continuity Manual.