Why the order is the method
Most plans that fail an exercise did not fail in the writing, they failed in the order. The plan was written before anyone knew which activities came first, so it carried recovery times the service owner never agreed to, and strategies that protect what is not critical. A methodology is not the shape of the document, it is the sequence of decisions that precede it.
The six steps below are the common ground between ISO 22301 and the UAE national standard AE/SCNS/NCEMA 7000. The vocabulary differs slightly; the sequence does not.
The six steps and what each one produces
| Step | The question it answers | Output | Who decides |
|---|---|---|---|
| 1 · Scope and context | Which entities, sites and activities are covered, and who the interested parties are | A signed scope statement with exclusions justified | Top management |
| 2 · Business impact analysis | What happens if this activity stops, and when the stoppage becomes intolerable | Prioritised activities with recovery times and dependencies | Activity owners |
| 3 · Risk assessment | What could stop these specific activities, and how likely it is | A risk register linked to the prioritised activities | Risk owners with the risk function |
| 4 · Strategies | How to close the gap between the recovery time needed and the one achievable today | One strategic option per prioritised activity, priced | Top management |
| 5 · Plan and procedures | Who does what in the first hour and the first day | A plan with named roles, department cards and contact lists | The continuity lead with departments |
| 6 · Exercise and improve | Does the plan work under pressure, and what broke | An exercise report with findings and closed actions | The continuity lead |
The output of each step is the input of the next. If the output does not exist, the step was not performed, whatever the steering slide says. Step two is covered in detail in business impact analysis, and the sections of the document itself in what a real business continuity plan contains.
The plan risk assessment: what exactly is assessed
The most common confusion is that the risk assessment repeats the impact analysis. Its job is different: the impact analysis ranks the activities, the risk assessment examines what threatens those activities specifically, not everything that could happen to the organisation.
| Dimension | Business impact analysis | Plan risk assessment |
|---|---|---|
| The question | What if the activity stops | What could stop it |
| The cause | Irrelevant, a stoppage is a stoppage | Central, because it decides the prevention |
| Output | Priority and recovery time | Likelihood and impact per threat to the activity |
| Use | Deciding what is worth protecting | Deciding where the protection goes |
Tie every risk to the activity it threatens, not to the organisation in general. A risk that touches no prioritised activity does not belong in the continuity plan; it belongs in the enterprise risk register.
Where risk management meets continuity
The two functions differ in timing, not in subject. Risk management works before the event to reduce its likelihood and impact; continuity assumes it happened and manages what follows. Three practical things join them: one register of activities and dependencies, one impact scale measured in money and time, and one committee that receives both sets of results. When the two streams run apart, a familiar contradiction appears: a risk marked acceptable in the register takes down a critical service in reality, because nobody compared the two on the same scale.
How to tell the method was really applied
- Every prioritised activity has a recovery time agreed in writing by the service owner, not by IT alone.
- At least one activity is explicitly described as non-critical: a list where everything is critical has not been prioritised.
- Every risk in the register names an activity, not a general heading such as reputation or people.
- Every strategy carries a written cost, because a choice without a price is not a choice.
- The last exercise left findings closed with dates, not a report saying everything went well.
- The plan was reviewed after the last reorganisation, not only after the last audit.
The full readiness checklist for an existing plan is in assessing a business continuity plan.
Frequently asked questions
What is a business continuity plan methodology?
An agreed sequence of six steps that produces the plan and lets you defend it: set the scope, run the business impact analysis, assess the risks to the prioritised activities, choose strategies, write the plan, then exercise and improve. The order is the methodology, and every step skipped shows up later in an audit.
How is the plan risk assessment different from the business impact analysis?
The impact analysis asks what happens if an activity stops and when the stoppage becomes intolerable, regardless of cause. The risk assessment asks what could stop it and how likely that is. The first sets priority and recovery times, the second decides where prevention goes.
How long does the full methodology take?
Eight to twelve weeks for a mid-size organisation starting from nothing, of which three to four are the impact analysis alone. The only honest shortcut is a narrower scope, never a skipped step.
Is a ready-made template enough instead of the methodology?
A template gives you the shape, not the decisions. A plan built on a template without an impact analysis contains recovery times nobody agreed to, and those are the first thing to collapse in an exercise. Fill the template in after steps two and three.
How do risk management and business continuity relate?
Risk management reduces the likelihood and impact of an event before it happens; business continuity assumes the event happened anyway and manages what follows. They share the activity register and the dependency map, which is why they are built together rather than in parallel.
Who owns the methodology inside the organisation?
The continuity lead owns the method, the activity owners own the content. When the continuity lead writes the plans on behalf of departments, the plan becomes their document alone, and the people who will execute it do not know it.