Continuity overview

What this domain solves

Continuity answers a specific question: when the operation is interrupted, what does the organization do. The reference is ISO 22301, and the material leans on the BIA — that is what says how much each hour of downtime costs and what the maximum tolerable period of disruption is for each object.

The plan is read, not written

This is the central rule and it changes how the work operates. In Aranis's continuity plan, only roles and free text are typed by a person. Scope, recovery requirements, bottlenecks, dependencies, strategies, and the restoration sequence are all fetched from what already exists on the platform.

The consequence is deliberate: to change a number in the plan, you change the thing the number describes. It is what stops the plan from becoming a parallel document that was accurate in March and quietly aged.

The chain that holds it up

Continuity does not work alone. It reads the BIA, which is anchored to products and services, which are sustained by business processes, which depend on assets and suppliers. If that chain is not mapped, the plan has nowhere to pull its numbers from — which is why Organizational Risk usually comes first.

What makes up the domain

Interruption scenarios describe the ways the business can stop. Recovery strategies are the answers to those scenarios. The plan assembles everything into a generated document. Coverage shows where an answer is missing, or where it exists but has not been rehearsed. And the action plan receives whatever is missing as tracked work.