SAMA · Qatar NIA · ISO 22301

Prepare. Respond. Recover. Continue.

Business continuity software for Saudi Arabia and Qatar. Assess risks, analyse business impact, manage continuity plans, coordinate crisis response and accelerate recovery, with SAMA- and NIA-ready evidence built in.

Mapped to the SAMA BCM Framework and ISO 22301

The lifecycle is mapped to every framework GCC regulators audit against

SAMA BCM
ISO 22301
NCA ECC
Qatar NIA
CBB · NESA
The BCM lifecycle

Govern. Analyse. Design. Implement. Validate. Improve.

BCMStack covers the full ISO 22301 / SAMA BCM Framework lifecycle in one workspace. Every stage feeds the next — and the audit log threads through all six.

1

Govern

BCM committee and decision register, approved policies and charter, training records.

2

Analyse

Risk assessment + Business Impact Analysis with configurable matrix.

3

Design

Continuity strategies, recovery options, IT-DR architecture choices.

4

Implement

Continuity plans (BCPs), DRPs, crisis and incident management, recovery activities & supplier playbooks.

5

Validate

ISO 22398 business continuity exercises and DR exercise drills, awareness & training, internal audit.

6

Improve

Improvement actions, management review, BCM reporting and SAMA regulatory submissions.

The full BCM lifecycle in one business continuity management system.

The 20-minute walkthrough covers the BIA questionnaire, plan approval, crisis events and the plans they activate, exercises with after-action reviews, and SAMA notification clocks — all from one workspace, one audit log.

How BCMStack covers the lifecycle

Six stages, six modules, one audit trail.

Each stage of the BCM lifecycle has the right module, the right approval flow, and the right SAMA / ISO clause mapped behind it. Below is what each pair of stages looks like inside the platform.

Govern & Analyse — set the frame, then size the impact

Set up the BCM committee and its decision register, approve the policy and charter, and record training. Then run the analysis layer: a configurable BIA impact matrix per tenant — categories × timeframes × per-cell severity — feeding a polymorphic risk register that links to processes, applications, vendors, locations and the organisation as a whole.

  • Govern: BCM committee · decision register · policy & charter approvals · training records
  • Analyse — BIA: RTO · RPO · MTPD · MAO · MBCO · resource × timeframe grids · versioned approvals
  • Analyse — Risk: 5×5 inherent vs residual · treatments · scenario library · top-10 view

Design & Implement — strategies become living plans

Choose a continuity strategy (active-active, warm standby, manual workaround), then author the BCPs and DRPs that operationalise it. Recovery steps, communications, scope links to BIA processes and a 5-tab execution surface that's actually usable mid-crisis — not a PDF nobody opens.

  • Design: continuity strategy options · IT-DR architecture · primary / alternative data-centre tracking
  • Implement — BCP: recovery activities · communications log · scope (processes, apps, vendors) · loss scenarios
  • Workflow: draft → in_review → pending_approval → approved → archived · versioned snapshots

Validate & Improve — close the loop, satisfy the regulator

ISO 22398-aligned exercises with MSEL injects and structured evaluator observations. Every observation links to an owner, a due date and an improvement action that survives the audit cycle — and rolls up into the SAMA annual test programme submission, due January.

  • Validate — Exercises: 7 types (tabletop / walkthrough / simulation / full-scale / drill / parallel / cutover) · MSEL inject library · DR-specific metrics · structured AAR
  • Validate — Audit: internal audit reviews · gap register · document-review enforcement
  • Improve: improvement actions tracker · management review · SAMA annual programme & results submissions
Already evaluating?

How BCMStack compares

Honest, technical, side-by-side comparisons against the platforms most often shortlisted in KSA and GCC RFPs.

Moving off SharePoint + Excel? See BCMStack vs spreadsheets →

Stage 6 · Improve — outputs

Reporting, exports and SAMA deadlines

Reports come from the same records your team works in. Export BIA reports to PDF or Word, plans to PDF and registers to CSV, and report across BIA, plans, exercises, crises, risks and improvement actions.

  • Exercise deadlines tracked from the test date: after-action review within 4 weeks, improvement plan within 2 months, retest within 90 days of a failed test
  • SAMA incident notifications on a clock, 4 hours by default, with alerts at half-time, 15 minutes out and breach; the incident can't close until it's submitted
  • Audit log of every change, with the user and IP address behind it
  • Read-only auditor role for internal audit and examiners
1
Database schema per customer — your data never shares tables with another tenant
4h
Default SAMA notification clock, with alerts at half-time, 15 minutes out and breach
5
Scenario themes tracked for test-programme coverage, counting only passed or partial tests
5
Roles, including a read-only auditor, with every change written to the audit log