Scope and business-impact discussion
Scope, evidence and responsibilities agreed before work starts.
ISO 22301 · BUSINESS CONTINUITY
Plan for disruption before it chooses the timetable.
Connect essential activities, dependencies and recovery priorities to practical continuity arrangements. The aim is a programme your people can understand, exercise and improve—not a plan that sits unread.
Illustrative artwork · not client premises or a completed engagement
MAKE THE SYSTEM USEFUL
Understand the disruption.
Prepare the response.
A recovery document may focus on IT while people, premises and suppliers are equally important. Start by understanding the activities that matter and the resources they depend on.
WHAT WE CAN AGREE TO DELIVER
01
Scope and business-impact discussion
02
Dependencies and recovery-priority planning
03
Continuity arrangements and role clarity
04
Exercise, review and improvement planning
START WITH THREE QUESTIONS
01 Which activities must continue during disruption?
02 What dependencies and existing recovery plans are known?
03 When were arrangements last exercised?
No confidential documents needed at first contact.
HOW THIS ENGAGEMENT TAKES SHAPE
A management system, not a document exercise.
01
Understand the scope
Scope and business-impact discussion
02
Review what exists
Dependencies and recovery-priority planning
03
Build the next actions
Continuity arrangements and role clarity
THE OUTPUT, NOT JUST THE CONVERSATION
A clearer picture of the support.
A useful engagement should leave you with agreed outputs and a practical next step. These are example deliverables, not client results.
Dependencies and recovery-priority planning
Scope, evidence and responsibilities agreed before work starts.
Continuity arrangements and role clarity
Scope, evidence and responsibilities agreed before work starts.
Clear boundaries from the start.
We confirm suitable technical expertise, sector requirements, independence and evidence access before accepting work. Consultancy supports your management arrangements; it does not grant certification, regulatory approval or a guaranteed result.
No. Continuity planning improves preparedness but cannot remove every disruption. We agree realistic objectives, dependencies, responsibilities and the evidence needed to test the arrangements.
The standard, organisational scope, locations, current arrangements, evidence availability and work packages. We clarify these before providing a written proposal.
Where appropriate, yes. Shared processes and review arrangements can be coordinated while keeping each standard’s requirements clear.
THE STANDARD / NOT A FOW CREDENTIAL
ISO 22301 — Business continuity
ISO 22301 concerns business continuity. The official publication reference below identifies the edition and scope; the engagement confirms what applies to your organisation.
Publication checked 25 September 2026. Applicable amendments and any certification transition arrangements must be confirmed for the engagement; no deadline is inferred here.
START A CONVERSATION
What does your management system need next?
Tell us what you are working towards, what already exists and where you need support. We will use that to clarify the scope—not sell you an off-the-shelf answer.
No sensitive records needed at first contact.