Specialist Preparation Program in Business Continuity

Program facts

Study fee

Free

subjects

6

lessons

24

Estimated time

19 hours

Content last reviewed

22 October 2026

Access period

30 days

Study language

Arabic and English

About the program

Practitioners map service boundaries and measure disruption effects over time, then identify dependencies, recovery needs and feasible alternatives. They proceed through activation, communication, manual work and reconciliation, and practice exercise design and honest interpretation of results. Cases are fictional and specified; the program does not confer incident authority, standards certification or a claim about any particular organization.

Practical relevance

Learners produce checkable scope cards, impact tables and operating paths in training cases.

Why this program

Lessons connect calculations and decisions to a service output, with practice in impact analysis, alternative comparison and record checks within specialist authority.

What you will learn

• Create a testable service scope, stakeholder register and disruption-time delegation path.
• Perform time-based impact analysis identifying activities, dependencies and recovery needs without conflating time and data.
• Compare disruption scenarios, controls and alternatives against capacity, time and residual gap.
• Build an activation, communication, fallback and reconciliation sequence preserving outputs and records.
• Design a safe exercise, judge observed results and close a specific gap through a suitable retest.
• Triage an incident, track service time and capacity, and establish return and improvement conditions.

Who it is for

• Continuity and operations practitioners working within organizational authority who need applied tools for impact analysis and planning.
• Risk, quality and IT staff who take part in disruption impact analysis, exercises or response coordination.
• Operational team leaders who want an executable, verifiable plan rather than a paper document.

Curriculum

1. Subject 1 Open for free

   BCMS scope and specialist role

   Start with the beneficiary-visible service result, then define its start, end, channels and dependencies. An app or server is a resource, not the output. Record each stakeholder need and its source; separate verified contract text from an untested interview expectation. During disruption, the specialist proposes action and shows impact while the authorized owner approves activation and messaging. A name in a role matrix does not prove after-hours reachability. When a supplier or channel changes, revisit fallback capacity and linked records, and distribute the current version to the workers who will use it. A short deputy-reachability exercise can reveal a decision gap before it becomes a real delay.

   4 lessons · 2.5 hours

   1. Defining service and operational scope 40 min
   2. Stakeholders and obligations 42 min
   3. Roles and decision authority during disruption 42 min
   4. Controlling baseline records and review 38 min
2. Subject 2

   Disruption impact analysis and recovery requirements

   Analyze the product or service and then the activities producing its output. Trace ordinary and urgent cases so a human review or notification path does not disappear behind a system name. Calculate disruption effects at defined time points with a consistent denominator, operating period and request classes; backlog is arrivals minus completions over the same interval. Tolerance identifies when harm becomes unacceptable, while a recovery objective states when a defined capability should return, and a recovery point objective addresses the data gap. A visible screen does not establish transaction integrity. Test shared dependencies: a supplier sufficient for either of two services alone may fail under combined demand. Record remaining unknowns for owner decision or later testing.

   4 lessons · 2.5 hours

   1. Mapping activities and products 42 min
   2. Estimating impact over time 42 min
   3. Setting disruption limits and recovery objectives 42 min
   4. Dependencies and owner validation 38 min
3. Subject 3

   Risks and continuity solutions

   Define a scenario that removes a relevant capability but retains enough conditions to interpret the decision. Separate cause, event and service effect. Judge a preventive control by evidence that it works, not by its existence. Before comparing prices, identify an option that misses the time objective or required throughput, or label it a partial route with an explicit gap. Calculate capacity from completed output, the slowest stage and shared resources, not seat count. When demand changes or a supplier is late, recalculate backlog and identify where the recommendation changes. The owner approves strategy and residual risk; the specialist presents the comparison and conditions for using the alternative during an incident.

   4 lessons · 2.5 hours

   1. Testable disruption scenarios 38 min
   2. Preventive controls and residual gap 38 min
   3. Comparing recovery alternatives 42 min
   4. Testing alternate capacity and dependencies 38 min
4. Subject 4

   Building an executable plan

   Activate fallback from observed service impact and authorized decision even if the technical cause remains unknown. The situation log preserves effect time, facts, assumptions and the next decision. An executable sequence states each step's condition, output and failure path; do not announce an alternate channel before it completes a valid test case. A customer message states what is known, what the recipient can do and when to expect an update, while staff need different operating instructions. Manual work needs identifiers, states and a matching key before system return. A working app starts a transition: cutover point, test of new transactions and reconciliation of older work before saying all effects are over.

   4 lessons · 2.5 hours

   1. Activation criteria and situation log 38 min
   2. Response and recovery sequence 38 min
   3. Crisis communications and stakeholder messages 38 min
   4. Manual workaround, reconciliation and return 42 min
5. Subject 5

   Exercises and capability validation

   Give every exercise observable capability objectives and choose a format that can actually test them. A tabletop exposes delegation and role understanding; it cannot prove a live supplier's throughput. Timed injects reveal decisions, while synthetic data and a stop rule protect production. Keep observation, target and judgment separate. If the timing start is missing, the result is unverified rather than guessed pass or fail. Repair the cause with an owner, closure evidence and a narrow retest. Training attendance or a signed plan does not prove that records are no longer lost or a deputy can be reached.

   4 lessons · 2.5 hours

   1. Exercise objective and format 38 min
   2. Injects and exercise safety controls 38 min
   3. Observation and evidence-based results 40 min
   4. Corrective action and retest 38 min
6. Subject 6

   Live execution and continual improvement

   During an incident, triage confirmed effect, supporting sample, remaining time and fallback limits, then request a specific decision through delegation. Measure from service impact to first correct output, separately from discovery, server return and backlog clearance. When arrivals or fallback capacity change, calculate backlog period by period. Normal return is another decision requiring an end-to-end output test, old-work reconciliation and honest communication. Afterward, choose output measures instead of plan-page counts; check denominator definitions, record gaps and retest remedies before raising claimed capability. A known open gap is not a closed gap.

   4 lessons · 2.5 hours

   1. Incident triage and escalation 38 min
   2. Tracking recovery time and capacity 42 min
   3. Return to normal and post-recovery checks 38 min
   4. Performance review and system update 40 min

Subjects unlock in sequence as you progress.

Strengths

• Fictional but operationally specific service cases
• Time, backlog and capacity calculations with explicit assumptions
• Clear separation of analysis and activation authority
• Fallback and reconciliation sequence guarding against duplicate work
• Exercises judging output and exposing untested capability
• Capability updates based on incident evidence rather than plan count

Evidence basis

Broad methods draw on cited ISO and NIST publications; original fictional cases do not establish organizational conformity.

Assessment

Assessments follow the program blueprint and may use module assessments, a final assessment, or a combination, under the approved attempt policy.

Assessment attempts: 2 per assessment, 7 days apart

The pass mark is announced before the program is published.

Certificate

The credential confirms completion and successful assessment; it does not represent professional licensure unless explicitly and lawfully stated.

Every certificate has a public verification code. Verify a certificate

Verification example: a real issued certificate

Program questions