Structured, versioned, linked — and flagged when reality drifts
Plans built on consistent templates, versioned and accessible from the platform — not a shared drive. Every plan linked to the process, strategy, and team it depends on.
Plan Library
Versioned · linked · drift-watched
5
Sections
3
Linked
1
Drift
Versioned
Every plan
1
Source of truth
Live
Drift detection
0
Lost plans
Most organisations have continuity plans. The problem isn't writing them — it's finding them at the moment of disruption. Plans buried in shared drives or sitting on someone's laptop — when that person is on leave, the plan is gone. The first hour is spent searching, not executing.
Plans also drift from reality. A plan written two years ago references systems that have been replaced, teams that have reorganised, contacts who have left. At the moment of disruption, the team follows a plan that no longer matches the world.
And plans that aren't structured consistently are plans that confuse. Every plan with a different format — the incident team spends the first hour figuring out how to read the plan, not executing it.
The old way
Buried plans
Lost in shared drives and inboxes
Stale content
References to systems and people that no longer exist
Inconsistent structure
Every plan a different format
No version control
Which version is current?
The NexusEdge way
Consistent structure
Same template, every plan
Versioned & accessible
Current version, always findable
Linked to reality
Plan connected to process, strategy, team
Drift detection
Flagged when upstream changes
ResilienceLab structures every continuity plan with a consistent template — invocation, response, recovery, restoration, reconstitution — so the incident team knows exactly where to find every section. The structure is enforced, not suggested.
Plans are versioned and accessible from the platform, not a shared drive. The current version is always the current version. When a plan is updated, the previous version is preserved — no "is this the latest?" at 2am.
Every plan is linked to the process it protects, the strategy it executes, and the team that runs it. When any of those change, the plan is flagged for update — drift is detected and surfaced, not discovered during disruption.
Consistent sections — invocation, response, recovery, restoration, reconstitution — enforced across every plan.
Every plan versioned, with the current version always identifiable and accessible.
Every plan linked to the process, strategy, and team it depends on — drift flagged automatically.
Plans flagged for update when upstream processes, strategies, or teams change.
A plan you can't find is a plan that doesn't exist.
Schedule a demo and discover how Continuity Plans transforms your BCM programme.