BCM · ISO 22301 · SAMA BCM Framework · Saudi-built

Resilience that survives a real disruption.

Run BIAs, build ISO 22301-aligned recovery plans and prove resilience to any regulator — without spreadsheets, version chaos or untested tabletops.

The dedicated resilience product: BCM/Stack

GRC Vantage BCM dashboard — business impact analysis, continuity plans, crisis events, exercises and BCM reporting
The reality in Saudi BCM programmes

Spreadsheet BCM doesn't survive a real disruption.

53%

Of Saudi banks have a BCM programme that has not been tested against a real cyber-recovery scenario in the last 18 months.

1 in 3

BIAs are out of date the moment they are signed off because they live in standalone Word docs no one re-opens.

Hours, not weeks

What activating a documented BCP should take. Spreadsheet-based programmes routinely take days to find the right plan.

Capabilities

The full BCM lifecycle, in one place

Six disciplines that turn a paper plan into a tested capability.

Business Impact Analysis

Score impact across eight categories and six time bands, derive MTPD from your own intolerable thresholds, and record RTO, RPO, MAO and MBCO per process — with a consistency engine that blocks contradictory BIAs from approval.

Continuity plans built to ISO 22301 §8.4.4

Purpose, scope, activation criteria and authority, deactivation criteria, respond / recover / restore steps, RACI roster and a stakeholder communications matrix — versioned, approved maker-checker, and checked against the BIA they serve.

Dependency mapping

Upstream processes (hard, soft, batch), applications, locations, vendors with single-source flags and fallback vendors, products and resources by time band — rendered as a dependency graph and rolled up into recovery requirements per application and vendor.

Crisis & incident management

Declare a crisis, activate the plans it needs, keep an auto-timestamped timeline, decision log and sitreps; run incidents P1–P4 through triage to closure with a SAMA notification workflow and SLA clocks.

Exercise programme (ISO 22398)

Annual programmes measured against the five SAMA BCM scenario themes, seven exercise formats, scenario library, injects, observations, evidence and an after-action report with 28 / 60 / 90-day follow-up clocks.

Resilience risk & reporting

A 5×5 risk register linked to BIAs and plans, with tolerance verdicts (within RTO, exceeds RTO, exceeds MTPD) and plan-coverage status per risk, plus a reporting rollup across BIA, plans, exercises, crises, actions and risks.

Technical capabilities

What the platform actually does, module by module

Written for the BCM lead, the IT reviewer and the auditor who will be asked to evidence it. Every line below is a shipped capability, not a roadmap item.

BIA engine

Business impact analysis that derives its own numbers

The BIA is a structured record, not a questionnaire export. Recovery objectives are calculated from your impact thresholds and then held to them.

BIA record with RTO, RPO and MTPD bar and the impact heat-map by timeframe
A BIA: recovery objectives, approval state and the impact heat-map across six time bands.
  • Recovery objectives per process: RTO, RPO, MTPD, MAO and MBCO (hours and percentage), current RTO and recovery strategy (rebuild, manual workaround, failover, outsource).
  • Impact grid: eight categories (financial, operational, customer, regulatory, legal, reputational, health-safety-environment, staff welfare), each with its own intolerable threshold, scored 0–5 across six time bands from 0–3 hours to 3 days+, with optional financial loss and narrative per cell. Categories and bands are editable per organisation.
  • MTPD is derived as the upper bound of the first time band in which any category crosses its threshold, so the number is defensible to an inspector.
  • Guided questionnaire in five steps (process, impact, recovery, dependencies, result) with six weighted impact dimensions, a P1–P4 recovery priority, a recommended RTO of 4, 8, 24 or 72 hours capped by any regulatory deadline and by MTPD, and a recommended RPO by data criticality. Overriding a recommendation requires a written reason.
  • Dependencies: upstream processes typed hard, soft or batch; applications flagged critical; primary and alternate locations; vendors with criticality, single-source flag, fallback vendor and vendor RTO; products and services supported; resources (people, equipment, systems, data, facility) with quantities per time band.
  • Consistency engine: 31 checks (for example an RTO longer than MTPD, a critical process with no approved plan, a vendor RTO slower than the process RTO) run on every save; blocking findings stop submission and approval.
  • Workflow draft → in review → pending approval → approved, with reject, retire and reopen; approver must differ from author; every approval stores a versioned snapshot and the page shows the diff between versions; review cadence by criticality (6, 12 or 24 months) with automatic reminders.
  • Outputs: an eleven-section BIA report with two appendices as DOCX or PDF; a BIA dashboard with impact heat-map, processes past RTO, dependency RTO gaps, top vendor and application dependencies, and derived recovery requirements per application and vendor.
Continuity plans · ISO 22301 §8.4.4

Plans that are checked against the BIA they serve

A plan that promises a faster recovery than its BIA allows, or that no longer covers the process scope, is flagged before anyone approves it.

Continuity plan detail with scope, team, recovery steps and versions
A continuity plan: ISO 22301 §8.4.4 header, recovery steps, team and versions.
  • Plan header to ISO 22301 §8.4.4: purpose, scope statement, activation criteria and authority, deactivation criteria, classification (internal, confidential, restricted), version label, target RTO and RPO.
  • Recovery steps in three phases (respond, recover, restore), each with owner, team, vendor and timeframe; a team roster with RACI and notification priority; a stakeholder communications matrix for seven audiences (staff, executives, board, customers, regulators, media, suppliers) with triggers on activation, H+1, H+4, H+24, daily and at resolution.
  • Scope links to processes, vendors and applications; references to the IT DR plan, crisis management plan, communications plan, vendor plans and regulatory playbooks; attached documents stored with per-tenant key checks.
  • Eighteen BIA-alignment checks: target looser than the BIA, recovery steps exceed the RTO, plan stale against a newer BIA, scope changed since approval, upstream process or critical vendor not covered. A drift banner appears on the plan the moment its BIA changes.
  • Workflow with maker-checker approval, versioned snapshots, archive and reopen; activation log with optional crisis link; PDF export; an optional AI first draft generated from an approved BIA (off by default).
Exercise programme · ISO 22398

Exercising measured against what SAMA expects you to rehearse

The programme is planned for the year and measured against the five SAMA BCM scenario themes, so the gap is visible before the inspection, not during it.

Exercise record with objectives, participants, injects, observations, evidence and AAR tabs
An exercise: scenario, format, governance roles and the objectives-to-AAR workflow.
  • Annual test programmes with planned coverage computed against five SAMA scenario themes: IT system loss, cyber, critical vendor unavailability, staff unavailability and workspace disruption.
  • Seven exercise formats (tabletop, walkthrough, simulation, full-scale, drill, parallel, cutover) across five categories (DR, BCP, crisis management, cyber, integrated), created through a guided wizard.
  • Scenario library with narrative, threat actor, initial conditions and complexity, reused across exercises; governance roles (sponsor, director, facilitator, evaluator lead) and an independent observer who may be internal audit, an external auditor or the regulator.
  • Weighted SMART objectives rated met, partial or not met; participants with invited, confirmed, attended and absent states; a master scenario event list of injects rated correct, partial, incorrect or missed; observations classed strength, improvement, issue, decision or question with severity; an evidence register.
  • DR-specific capture: target versus actual RTO and RPO, data integrity verified, failback completed, for parallel, failover, failback, cutover and backup-restore tests.
  • After-action report workflow (draft, submitted, approved or rejected) with service clocks: AAR due 28 days after the exercise, improvement plan 60 days, mandatory retest 90 days after a failed outcome. Due retests surface on the dashboard.
Crisis and incidents

A crisis record an inspector can read end to end

Every state change is timestamped by the system, decisions carry their rationale, and SAMA notification runs on a clock.

Crisis event with timeline, decisions, sitreps and tasks
A crisis event: auto-timestamped timeline, decision log, sitreps and activated plans.
  • Crisis events coded CR-YYYY-NNN with commander, scribe and communications lead; eight crisis types (natural disaster, technological, operational, cyber, security, health, supply chain, reputational) and four severities; an exercise flag so drills are never confused with live events.
  • Auto-timestamped timeline of every change; decision log with rationale and decision-maker; situation reports with next-update-due; task board; impacts by type (financial, operational, customer, legal, regulatory, reputation); impacted locations; recovery resources and activities; communications log.
  • Activate the continuity plans a crisis needs directly from the event, and launch a live call-tree campaign that writes to the same timeline.
  • Incidents coded INC-YYYY-NNNN with P1–P4 severity, eight-state lifecycle from detected to closed with history, response actions by phase (triage, containment, eradication, recovery, post-incident), a RACI response team, affected processes, applications, assets, locations and vendors, and two-way escalation to a crisis event.
  • SAMA incident notification: a classification suggestion from configurable thresholds (customers affected, financial impact, personal or card data, RTO breach), a draft → approve → submit → acknowledged workflow with maker-checker and admin-only submission, and an SLA watcher (high 4 hours, medium 24 hours) that warns at 50 percent elapsed, 15 minutes before, at breach and hourly after.
  • Close-out captures root cause, lessons and closure reason; improvement actions carry a red-amber-green status across crises and incidents.
Call trees and notification

Call trees that prove who was actually reached

A notification campaign is only evidence if you can show who confirmed, how fast, and who could not be found.

Call trees list with scope and status
Call trees at organisation, department or plan scope, ready for a test or live campaign.
  • Call trees at organisation, department or plan scope, built in a visual tree builder; campaigns launched as a test or from a live crisis.
  • Relay magic links by email: each relay records reached, no answer, wrong number or unreachable for the people below them; a branch-stall watcher escalates after 20 minutes of silence.
  • Independent verification: callees receive a single-use token and confirm whether they were in fact contacted, so a relay's report is marked verified or contradicted.
  • Public confirmation pages work without a login and carry a bilingual drill banner in English and Arabic.
  • Close-out metrics on every campaign: reach rate, median and 95th-percentile confirmation time, verification rate and stale contacts.
  • Email delivery today; SMS, WhatsApp and voice are provider integrations on the roadmap and are logged, not sent, until then.
Resilience risk register

Risks that know whether a plan covers them

Each risk is traced to the processes it reaches and judged against their RTO and MTPD, so the register answers the question the board asks: are we covered?

Resilience risk dashboard with heat map and top risks
The resilience risk register dashboard: heat map, top risks and treatments.
  • 5×5 likelihood and impact matrix with written descriptors for every level; bands low 1–4, medium 5–9, high 10–14, critical 15–25; a warning when a critical residual risk is accepted.
  • Residual scoring derived from the best key control: an effective control reduces likelihood by two, a partially effective one by one, and an effective corrective or compensating control also reduces impact. Manual overrides require a reason.
  • Treatments typed mitigate, accept, transfer or avoid, each tied to a continuity plan or a control; critical assets, business objectives, a top-10 view and a heat-map dashboard.
  • Seeded content: a scenario library and over seventy risk templates with thirty-two controls typed preventive, detective, corrective, directive or compensating; control assessments record design and operating effectiveness, samples, exceptions, remediation and evidence.
  • Risk-to-BIA traceability: each risk's exposure path to a process (direct, vendor, application, location, department, upstream) with a tolerance verdict (within, exceeds RTO, exceeds MTPD) and plan coverage (covered, too slow, not approved, uncovered); the platform proposes scenario families from a BIA's dependency profile. Exposure informs; it never silently changes a score.
Governance, security and operations

Built for a regulated organisation's control environment

Segregation of duties, an audit log of every change and a reminder engine that runs on Riyadh time.

  • Roles: organisation admin, BCM manager, department head (scoped to the department), viewer and auditor, with view, create, edit, delete, approve and manage permissions per module and dedicated permissions for incident classification, escalation and SAMA notification.
  • Maker-checker enforced on BIA, plan, risk and SAMA notification approvals, switchable per organisation when a small team needs it off.
  • Every change, successful or refused, is written to an audit log with user, input and IP address.
  • Reminder engine with a daily 06:00 Riyadh sweep: BIA and plan reviews, after-action reports, improvement plans and retests, actions due, vendor contract expiry, document expiry and stalled approvals. Each reminder is sent once and logged.
  • AI assistance is off by default and enabled per feature; it drafts a BIA from a one-line description, a plan from an approved BIA, a SAMA notification and report commentary, and can run on a local model inside your environment. The BIA calculations and consistency checks are deterministic and never depend on it.
  • Tenant isolation at the database-schema level with tenant-checked file storage; over eight hundred automated unit and integration tests run against the code.
BCM lifecycle · ISO 22301

From governance to tested capability — year on year.

01Govern

Board-approved BCM policy, named owner, defined scope.

02Analyse

BIA across every critical process, with RTO / RPO and dependencies.

03Plan

BCP, IT DRP, Crisis Management Plan — version-controlled, owned, exercised.

04Test

Tabletop, walkthrough, technical recovery, full simulation.

05Improve

Lessons learned feed the next BIA, plan and risk register. Year-on-year improvement.

For the BCM lead

A continuity programme defensible to SAMA, the Board and any auditor.

GRC Vantage gives the BCM function a connected lifecycle — every BIA linked to recovery plans, every plan linked to tested exercises, every exercise linked to corrective actions. One source of truth, year-on-year improvement visible to the Board.

  • BIA updated continuously, not annually-then-forgotten
  • Recovery plans owned, version-controlled and rehearsed
  • Cyber-BCM scenarios (ransomware, wiper) treated as first-class
  • BIA reports, plan PDFs and exercise records generated from live data, not authored by hand
4–6 wk

Typical time for a first-pass BIA across 30–50 critical business services using the pre-built templates and dependency mapper.

2 h

Plan activation from incident declared to response team mobilised — versus days for paper-based programmes.

Reference

Frequently asked questions

Which standards is GRC Vantage's BCM module aligned to?
Plans are structured to ISO 22301 §8.4.4 and activation to §8.5; the exercise programme follows ISO 22398; annual exercise coverage is measured against the five SAMA BCM Framework scenario themes; the SAMA incident-notification workflow and its SLA clocks are built in. Alignment is in the structure and the records, not a certification claim.
Can we host the platform inside Saudi Arabia?
Deployment and hosting are agreed per engagement and stated in writing in your proposal, including the region. Ask us before the demo and we will answer in the proposal rather than on this page.
Is the platform usable outside banking — government, healthcare, energy, telco?
Yes. The BIA engine, plans, exercises and crisis management are sector-neutral; impact categories, time bands and thresholds are editable per organisation. The SAMA-specific parts (scenario-theme coverage and the incident-notification workflow) are there when you need them and ignorable when you do not.
How long does a typical BIA take to set up?
Most organisations complete a first-pass BIA across 30–50 critical business services within four to six weeks using the guided questionnaire and the dependency model, with the consistency engine catching contradictions as you go.
Does the BCM module integrate with our risk register?
Yes. Each risk is traced to the processes it reaches, judged against their RTO and MTPD, and shown with the plan that covers it or the reason none does. Recovery gaps from the BIA can be raised as risks, and treatments can be tied to a specific continuity plan.
Can we run tabletop exercises inside the platform?
Yes. Plan the exercise, assign roles and participants, run injects from a master scenario event list, record observations and evidence, and complete the after-action report through its approval workflow. Improvement areas are captured in the report; the 28, 60 and 90-day follow-up clocks keep them from being forgotten.
Is the interface available in Arabic?
Not yet. The BCM application runs in English today; call-tree confirmation pages carry a bilingual drill banner, and advisory, demos and documentation are delivered in Arabic or English. Arabic interface work is on the roadmap; ask us for the date.
Get started

Bring your BCM programme out of Word documents.

See GRC Vantage's BCM module live with your BIA. Demos delivered in English or Arabic from Riyadh.