Interruption scenarios
Why continuity starts from how the business stops, not from each process in isolation.
The question comes before the answer
A scenario describes one way the business can be interrupted: data loss, system unavailability, loss of people, loss of a facility, failure of a critical supplier. A recovery strategy is the answer to a scenario.
Why not tie strategy to process
The alternative would be hanging each strategy off a process. The problem shows up in practice: "data loss" becomes twelve near-identical strategies, one per process, all saying restore from backup. The plan gets long and the same decision now exists in twelve places that have to be maintained together.
In the shape ISO 22313 proposes, data loss is one scenario with one answer that happens to cover twelve processes. One decision, one place.
Starting library
The platform ships a scenario library as a starting point, written into your organization the first time you open the screen. From then on it is yours: you can edit, remove, and add scenarios specific to your business. It is the same pattern as the default organizational risks — the starting content exists so you do not begin from a blank screen, not so it stays as it is.