ISO 22301 certification assesses a business continuity management system, or BCMS. It concerns how an organisation prepares for disruption, protects priority activities and develops the ability to continue or recover services. The most useful starting point is a business promise that could be broken: a missed payment run, unavailable customer service, interrupted distribution or loss of an essential facility.
ISO 22301:2019 is the current published edition at this review date, with a 2024 climate action amendment. ISO’s current record confirms the requirements standard. Certification concerns the assessed system and its boundary; it is not an assurance of uninterrupted service under every possible event. Buyers still need to examine the particular service, dependencies and recovery commitments they intend to rely on.
Decide which services the system must protect
List the products and services customers or other interested parties depend on. Identify which activities support them and who makes decisions when normal capacity is unavailable. This exercise is more useful than beginning with a collection of disaster scenarios. A different cause can interrupt the same critical dependency, and the business still needs a workable response.
Define the certification boundary clearly. A recovery arrangement covering one processing centre does not automatically cover a company’s entire international operation. Include relevant entities, sites, services and interfaces. Explain how shared technology, suppliers and support functions affect the boundary. If something essential sits outside the scope, establish how its availability or recovery is managed rather than simply omitting it from the diagram.
Use business impact analysis to expose priorities
Business impact analysis examines how disruption affects activities over time. It helps the organisation establish priorities and recovery needs. Ask what happens after a short interruption, after a full operating period and after an extended outage. Consider customer obligations, financial effects, legal requirements, safety implications and dependencies relevant to the activity.
Use actual operating information. A department may describe every task as critical, but payroll, inventory reporting and routine marketing work may have very different timing needs. Ask for the reasoning behind each priority and resolve contradictions between departments. The objective is an agreed basis for decisions under constrained conditions, rather than a spreadsheet where every row receives the highest rating.
Distinguish recovery targets from promises
A recovery time objective expresses a target for resuming an activity or resource at the required level. It needs to be supported by an achievable strategy. Where information recovery matters, clarify acceptable data loss and restoration arrangements as well. Avoid confusing a technology backup frequency with the time required to restore a functioning business service.
Compare internal targets with customer contracts. If a service contract requires recovery sooner than an essential supplier can support, the mismatch deserves management attention. Do not let sales material describe an untested target as a guaranteed outcome. A credible discussion explains the assumptions, dependencies and evidence behind a recovery claim, including the conditions under which the arrangement may be constrained.
Build a dependency map people can use
This original table helps connect recovery expectations with resources. It is not an ISO-mandated form or a complete continuity plan.
|
Priority activity |
Dependency to question |
Practical test |
|
Customer transactions |
Application, identity access and trained staff |
Can a representative transaction be completed? |
|
Distribution |
Stock, transport and dispatch information |
Can an alternative route support priority orders? |
|
Customer communications |
Contact details and authorised messages |
Can the right people issue an approved update? |
|
Financial processing |
Data, approvers and banking access |
Can the controlled process operate during disruption? |
|
Facilities access |
Safe premises and essential utilities |
Is an alternative arrangement genuinely available? |
Discuss the map with suppliers and operational teams. A named alternative is only a proposal until somebody confirms capacity, access, responsibilities and practical limitations. Shared dependencies can also undermine apparently separate recovery options.
Choose strategies before writing detailed plans
Possible approaches may involve alternative facilities, additional capacity, different suppliers, workarounds, remote work or recovery technology. The appropriate choice depends on the impact analysis and risks. Management should understand the cost and limitations of each option, including resources needed to sustain reduced operations for more than a brief exercise.
Challenge assumptions that look comfortable on paper. Can employees reach the alternative site? Does the supplier reserve capacity or merely offer it if available? Can manual work later be reconciled without creating errors? A continuity strategy should support a service at an agreed level, rather than simply show that an alternative address or backup server exists.
Make response arrangements usable under pressure
Plans should help people recognise an incident, escalate it, make decisions and coordinate action. Identify decision authority and deputies, including out-of-hours arrangements. Keep contact information available in a form that does not depend entirely on the system that may fail. Define how customers, staff, suppliers and other relevant parties receive appropriate updates.
Write instructions around decisions and actions. A long document describing every department can be difficult to use during a disruption. Separate concise response information from background analysis where that improves accessibility. Test whether someone unfamiliar with the drafting process can find the next step. Maintain appropriate security around sensitive contact details, operating dependencies and recovery information.
Exercise the capability, not only the meeting
A discussion exercise can reveal confused roles and assumptions. Other forms of testing may be needed to establish whether technology, facilities and operating workarounds function as intended. Choose exercise objectives deliberately. An exercise that never challenges the critical dependency offers limited evidence about recovery capability.
Record what was attempted, what happened and what needs to change. Follow actions through to completion and retest where necessary. A successful attendance sheet says little about whether a priority service could recover. Guidance supporting implementation is available in ISO 22313:2020; it supports understanding but is not the requirements standard used for ISO 22301 certification.
A fictional example: recovery blocked by one approval step
Imagine a fictional wholesale business whose order platform can be restored to a secondary environment. In an exercise, the technology team restores the application, but orders cannot be released because the authorised finance approvers lack access to the alternative service. The technical recovery result therefore does not establish business recovery.
A sensible response would review access, approval responsibilities, deputies and the end-to-end exercise design. The next test should follow a priority order through to dispatch or another defined service outcome. This fictional illustration shows why continuity evidence should cross departmental boundaries. It does not claim that a particular architecture or exercise frequency is required for every organisation.
Implement the management system around those findings
Assign sponsorship, obtain the standard and agree the system boundary. Establish the impact analysis and risk assessment approach, select strategies and develop response arrangements. Train participants in their roles and maintain the information on which the arrangements depend. Use the lessons from exercises and real disruptions to improve the system.
Internal audits should examine both management arrangements and implementation. Management review needs to address capability, changes, performance and resources. Ask whether business growth, acquisitions or supplier changes have altered the original assumptions. A plan can be current by document date while relying on capacity that no longer exists. Readiness for certification requires evidence that the system operates, rather than a recently purchased template pack.
Ask certification bodies about service and dependency coverage
Provide CB Name with the intended scope, sites, priority services and operating complexity. Explain important outsourced dependencies and the exercises already performed. Ask how the audit team will evaluate continuity arrangements and whether it has relevant experience. Verify the proposed issuer and accreditation for the service, rather than assuming approval follows from the provider’s other certifications.
Use the certification-body directory as a discovery resource and check approval through the relevant accreditation body. Compare audit plans and complete commercial terms. For a supplier’s existing certificate, use the verification guide, then request assurance relevant to your own dependency. The certificate alone does not settle whether the supplier meets your specific recovery requirement.
Understand costs and continuing responsibilities
Budget for analysis, internal time, exercises, training, recovery resources and external assessment. Technology costs can be significant, but people, facilities, suppliers and communications may also determine whether the strategy works. Separate spending needed to meet existing obligations from optional resilience improvements. There is no universally appropriate implementation period or fixed recovery investment.
After certification, update the system when services, staffing, technology, locations or critical suppliers change. Review whether exercise results support public claims. Maintain a useful distinction between incident response, technology disaster recovery and business continuity: they should connect, but restoring infrastructure alone may leave the service unavailable. A sound BCMS helps management understand and improve that wider capability.
Check whether the recovery arrangement can last
An exercise may show that a team can restart an activity briefly, while leaving unanswered whether reduced operations can continue. Consider staffing, consumables, supplier support, accommodation and the accumulation of unfinished work. Some workarounds create errors or additional effort that become significant only after several operating periods.
Ask who decides the order in which deferred work is restored. Returning to normal service can require careful reconciliation of manual transactions, data changes and customer commitments. Recovery is not complete merely because the main system is online. Include a controlled approach to resuming normal arrangements where that is relevant to the service.
Review these questions with the people who would run the workaround, rather than only its designers. Establish which assumptions can be tested and which remain uncertain. Management can then decide whether to invest, adjust a commitment or accept a documented limitation. This discussion often produces more useful evidence than adding another unlikely disaster scenario. It also helps procurement teams ask a supplier whether its recovery statement covers sustained service and return to normal operations, rather than a successful technical demonstration alone. Keep the answer tied to the actual service and agreed requirements, because recovery capability is not identical across every activity in an organisation.
References and information note
· ISO 22301: business continuity management system requirements
· ISO 22313: implementation guidance
· ISO: requirements and guidance management system standards
· NIST Cybersecurity Framework: complementary cybersecurity risk guidance
This guide provides general planning information. Recovery commitments, legal obligations and technical solutions require assessment of the actual organisation. The example is fictional. Certification does not guarantee uninterrupted operations. Direct factual clarifications to the contact page.
