Start hereSet scope and assess business impact
~112 days leftOpen step
Guide library
Certification Global

ISO 22301

ISO 22301:2019 business continuity management systems

Find what must keep running, plan recovery and prove that your recovery arrangements work.

Who it applies to

Organizations building or certifying a business continuity management system within a defined scope.

What you’ll produce

A business continuity management system with evidence of exercises, improvements and any external assessment.

A recovery objective is a requirement to test. An exercise result that misses the objective needs a decision and follow-up.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What do we need the certification to cover?
Confirm the applicable edition, sites, products or service boundary and the certification route. Budget for assessment, changes needed to pass, and maintaining certification.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor unresolved scope questions, controls without evidence, findings that need a retest and the next assessment or renewal date.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

ISO 22301 kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Set scope and assess business impact · Continuity manager + business owners [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Ask the appropriate assessor or program contact what scope they will review, what evidence they need, and which dates and fees they can confirm in writing.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Which services cause unacceptable impacts when interrupted?
  • Which dependencies could fail together and leave the recovery plan without a workable option?

Worked scenario

A warehouse assumes its order system can restart in four hours. A recovery exercise finds orders return in three hours, but label printing takes seven. The team logs the true service recovery time and gives printer failover an owner.

What to read next

  • APRA CPS 230

    Check sector-specific operational resilience and reporting for Australian regulated entities.

Practice reviewing an evidence packet
The whole journeyabout 112 days across 4 steps
  1. 01Set scope and assess business impactContinuity manager + business owners · ~21 days
  2. 02Choose strategies and write usable plansBusiness owners + continuity lead · ~35 days
  3. 03Exercise recovery and document the resultsExercise lead + service owners · ~28 days
  4. 04Review and assess the systemManagement + internal auditor · ~28 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 10 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Set scope and assess business impactContinuity manager + business ownersBefore selecting recovery solutionsSet a start dateScope statement; Business impact analysisOpen
Choose strategies and write usable plansBusiness owners + continuity leadBefore relying on arrangementsSet a start dateContinuity plan; Exit plansOpen
Exercise recovery and document the resultsExercise lead + service ownersAt planned intervals and on material changeSet a start dateExercise report; Recovery evidence; Corrective-action registerOpen
Review and assess the systemManagement + internal auditorBefore any external certification and on the review cycleSet a start dateInternal audit report; Management review minutes; Certification decisionOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Set scope and assess business impact

    Who Continuity manager + business owners When Before selecting recovery solutions

    Identify activities, impacts over time and key dependencies. Agree priorities, recovery objectives and minimum operating levels.

    What to produce

    Scope statementMemo

    Gather first

    • Service inventory and architecture
    • Customer commitments and contracts
    • Applicable criteria or legal text

    How to prepare it

    1. Write the exact decision this memo supports. Name the legal entity, service, environments and dates. Attach a boundary diagram and state which people, vendors and processes can affect the scope.
    2. List the exclusions next to the inclusion list. Give a reason for each one and describe any shared service that crosses the boundary.
    3. Review the draft with service owners and the person making the decision. Freeze the approved version and add a review date or trigger for changes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Decision
    Cover the hosted billing service for the April to June review.
    In scope
    Production billing API, hosting, releases and production access.
    Excluded and why
    Internal HR tool. It has no access to billing systems or data.
    Dependencies
    Cloud hosting and corporate identity provider.
    Approval
    Service owner approves after checking the architecture and contract.

    Check before handing it over

    A reviewer can use the memo to classify a named system and see how shared dependencies are handled.

    Give the approved scope and any open questions to whoever will map requirements, select samples or review the engagement.

    Business impact analysisSpreadsheet

    Gather first

    • Process maps
    • Transaction volumes and legal or contractual obligations
    • Service owners and recovery records

    How to prepare it

    1. Interview each process owner about what fails when their service stops. Record impact over useful time intervals and distinguish customer, legal, safety and financial effects.
    2. List the people, sites, technology, information and providers needed to recover. Agree the maximum tolerable disruption, target recovery time, acceptable data loss and minimum service level.
    3. Check that upstream and downstream targets fit together. Ask the accountable executive to approve the priorities and record which dependencies need testing.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Operation
    Fulfil urgent medicine orders
    Impact as disruption grows
    Manual work can cover the first two hours. Missed dispatch after six hours affects treatment schedules.
    Dependencies
    Stock data, label printers and courier booking
    Recovery target
    Resume priority shipments in four hours with no more than 30 minutes of lost order data.
    Owner and approval
    Warehouse director approves. Continuity team checks the targets during the next exercise.

    Check before handing it over

    Each target links to an observable impact and to the actual resources needed for recovery.

    Give the approved priorities to the people planning recovery and testing suppliers.

  2. 02

    Choose strategies and write usable plans

    Who Business owners + continuity lead When Before relying on arrangements

    Select recovery resources and alternatives. Write activation, communications, handoffs and fallback instructions and confirm supplier arrangements.

    What to produce

    Continuity planMemo

    Gather first

    • Approved business impact analysis
    • Staff and supplier contact lists
    • Recovery procedures and technology dependencies

    How to prepare it

    1. Write when the plan is triggered, who declares it and how staff learn which version is active. Put first-hour actions near the top.
    2. Describe the workarounds and recovery steps by service. Specify dependencies, checks before restoration, fallback if a supplier is unavailable and criteria for returning to normal.
    3. Run a timed exercise without relying on the usual owner. Record achieved service and data recovery against targets and assign any fixes.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Trigger
    Order system down for 30 minutes with no confirmed recovery time
    First actions
    Incident lead opens a log. Dispatch lead starts the emergency order queue.
    Recovery sequence
    Recover database, reconcile recent orders, verify labels, resume priority dispatch.
    Fallback
    Use backup printer and call the alternate courier contact.
    Return to normal
    Service owner signs off after reconciliation and successful shipment test.

    Check before handing it over

    Someone covering the primary owner can activate the plan and verify recovery with the written instructions.

    Give controlled copies to responders and suppliers and update the record after each exercise.

    Exit plansMemo

    Gather first

    • Approved scope
    • Governing requirements and risks
    • Teams, service dependencies and review gates

    How to prepare it

    1. State the objective, scope, accountable owner and conditions that trigger action. Translate commitments into tasks with periods, thresholds and evidence.
    2. For each task set the input, decision rule, output and handoff. Include escalation for failures and approvals for exceptions.
    3. Walk through one real case with owners and reviewers. Approve the version, schedule review, and check that promised tasks have operational records.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Purpose
    Identify failed production backup jobs and restore service data.
    Scope
    Production billing databases and backup vault
    Activity and timing
    On-call reviews daily job alerts and runs a quarterly restore test.
    Evidence and exception
    Keep job records and restore test output. Page the service owner if a job fails.
    Owner and approval
    Operations lead owns. Service owner approves.

    Check before handing it over

    A person who receives the plan can tell when to act, what to check and where to save the result.

    Give the approved plan to the people responsible for operation. Add dated checkpoints to the working calendar.

  3. 03

    Exercise recovery and document the results

    Who Exercise lead + service owners When At planned intervals and on material change

    Test disruption scenarios and compare actual service restoration and data loss to objectives. Record decisions, workarounds and fixes.

    What to produce

    Exercise reportMemo

    Gather first

    • Approved scenario and participant roles
    • Goals and scoring criteria
    • Event timeline and expected records

    How to prepare it

    1. Prepare a scenario and timed new information that tests decisions, handoffs and evidence. Assign a facilitator and separate observer.
    2. During the exercise, note what participants actually did, the timestamps and where expected responses failed. Distinguish simulated actions from real ones.
    3. Write a short after-action summary with owners, deadlines and a retest plan. Attach the scenario, attendance and evidence references.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Scenario
    Simulated export leak found at 09:20 UTC
    Objective
    Reach operational and legal leads and classify the incident within the exercise target.
    Observed behavior
    Engineering preserved logs. Initial escalation went to an inactive mailbox.
    Action and owner
    Privacy operations updates the routing list before 2026-12-01.
    Retest
    Repeat the handoff in the next on-call drill.

    Check before handing it over

    An absent participant can see what was tested, what happened and why an action was assigned.

    Send approved findings to action owners and file the record for governance or assessment.

    Recovery evidenceSpreadsheet

    Gather first

    • Control descriptions and test request
    • Source system records
    • Defined period and evidence access rules

    How to prepare it

    1. Create a register keyed by control, requirement or request. Export native records with the filters, timestamps and operator details needed to interpret them.
    2. Link to a restricted copy of each artifact. Note time zone, scope, date range, export method and whether the evidence shows design or actual operation.
    3. Test the links using the reviewer’s permissions. Flag missing periods or evidence and track a follow-up instead of filling in records retrospectively.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Evidence ID
    EV-021
    Control or request
    AC-04, October administrator review
    Period and scope
    1 to 31 Oct 2026 UTC, production tenant
    Source and capture
    IAM export filtered to active elevated roles
    Link or record ID
    Restricted workpaper EV-021 plus ticket IAM-114
    Reviewer and status
    Security assurance, verified

    Check before handing it over

    A reviewer can open the right file, reproduce the population filter and see who performed or approved the real task.

    Send the index and access instructions to the assessor. Keep sensitive files in the approved evidence store.

    Corrective-action registerSpreadsheet

    Gather first

    • Finding, risk or test exception
    • Root-cause analysis
    • Named owner, due date and expected evidence

    How to prepare it

    1. Record the observation and link the exact test or requirement. Describe the business effect and investigate why the issue was able to happen.
    2. Separate immediate containment from the permanent fix. Give each action an owner, date, verification method and any required approval for deferral.
    3. Retest against the original failure once the fix is live. Record who accepted the outcome and keep unresolved issues visible.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Finding or risk
    F-008, a departed contractor retained production access
    Cause and effect
    HR event never reached IAM. Admin access remained active.
    Action and owner
    Revoke access and alert on failed HR sync. IAM lead.
    Due and status
    2026-11-28, in progress
    Closure test
    Simulate departure and verify access disappears within policy
    Approver and evidence
    Risk owner, ticket IAM-114 and retest results

    Check before handing it over

    The closure test addresses the original problem and has a dated result from an independent reviewer where required.

    Send open items and decisions to governance, audit or the assessor on the applicable cadence.

  4. 04

    Review and assess the system

    Who Management + internal auditor When Before any external certification and on the review cycle

    Check objectives, performance, findings and controls. If seeking certification, agree scope and close assessor findings.

    What to produce

    Internal audit reportMemo

    Gather first

    • Approved test scope and criteria
    • Population and sample records
    • Test approach, results and reviewer requirements

    How to prepare it

    1. State objective, dates, scope and the method before describing results. Record the tester, any independence requirements, and how samples were selected.
    2. For each item, compare what should have happened with what the evidence shows. Describe impact and link the evidence or recorded exception.
    3. Add limitations, obtain review and give each finding an owner and a date. Retain the underlying samples and calculations with the signed version.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Test objective
    Check that production role removals happen within the internal deadline.
    Method and population
    All September departures. Test each privileged account.
    Expected result
    Remove access within one business day.
    Observed result
    11 on time. One late by two days, ticket IAM-114.
    Finding and follow-up
    F-008. Retest the next departure and verify alerting.

    Check before handing it over

    Someone who did not run the test can reproduce the result and tell a finding from a scope limitation.

    Give management the findings and evidence links. Share observations with an external reviewer where the engagement calls for it.

    Management review minutesMemo

    Gather first

    • Agenda or decision request
    • Current performance measures and findings
    • Proposed actions and participants

    How to prepare it

    1. Write what decision is needed and list the reports or records the decision maker reviewed. Capture the date, people and decision authority.
    2. Record the decision, alternatives considered, any remaining risk and exactly who will do what by when.
    3. Send notes for factual review. File the approved record and add actions to the working tracker so progress reaches the next review.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Item
    Approve a fix for the missing access-removal retry.
    Inputs reviewed
    September test results and IAM incident root-cause notes.
    Decision
    Approve automatic retry plus daily reconciliation.
    Action and due date
    Platform lead to ship and test by 2026-11-28.
    Residual risk and follow-up
    Manual review remains until rollout. Check at December meeting.

    Check before handing it over

    The minutes identify the person who approved each action and the date the decision will be revisited.

    Give owners the actions and add the approved record to the relevant audit or governance file.

    Certification decisionIssuer document

    Gather first

    • Correct portal or issuer contact
    • Approved scope and submission record
    • File access and sharing requirements

    How to prepare it

    1. Confirm which issuer or portal supplies this record and who can retrieve it. Gather the submission reference, holder name, scope and expected date.
    2. When the document arrives, verify recipient, scope, dates, version, conditions and any required verification link. Escalate discrepancies to the issuer.
    3. Save the original in the approved location. Record renewal or response actions and limit distribution to authorized recipients.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Document expected
    Issuer’s final decision or confirmation
    Reference
    Official portal or case ID
    Received and verified by
    Compliance coordinator, 2026-11-10
    Scope and conditions
    Matches the agreed service boundary and version. Follow-up recorded separately.
    Location and access
    Restricted evidence folder, named reviewers only

    Check before handing it over

    The original can be traced to the issuer and its scope and date match the engagement or application.

    Send the verified record or approved summary to decision makers. The download is a tracking sheet for the original document.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes