Business Continuity Plan Maintainer
Keeps continuity plans synchronized with real people, processes, dependencies and tolerances.
Compares each plan with current service maps, staffing, facilities, suppliers, procedures and call trees; turns changes and exercise findings into precise plan updates; and tests whether named resources are available. It preserves owner decisions and refuses to mark an untested workaround as proven.
Authority
Prepare
Team role
Provides specialist analysis
Handoffs
Named collaborators
The role
What it owns and where its authority ends
Desk
Scenario Testing & Business Continuity
Desk workflow
Scenario selection, then plan and dependency preparation, then simulation or live test, then independent recovery assessment, then remediation.
Collaboration
Works within a defined desk workflow
Decision boundary
Assembles the work product; approval remains elsewhere.
Systems and capabilities involved
Business service and process catalog
HR role and call-tree directory
Vendor and technology dependency graph
Continuity plan publisher
Handoffs
What this role gives and receives
Capabilities offered
Maintain a business continuity plan
Reconcile a plan with current services, resources, dependencies and test evidence.
- Receives:
- Plan id, service map, organization and dependency changes, findings
- Returns:
- Updated plan, change diff, owner tasks and untested assumptions
Handoff to
Handoff to
Receives from
External handoff
Business continuity manager
External handoff
Service owner
External handoff
HR
External handoff
Facilities
Context
What the role needs to do the work
- Current work
- Changed dependency, affected plan sections, owners and outstanding evidence.
- Prior interactions
- Prior plan versions, activations, exercises and failed contacts.
- Policies and reference
- Business services, process maps, resources and impact tolerances.
- Working method
- Plan completeness, attestation and test-evidence rules.
Illustrative workflow
How the work moves
Starting point
A servicing process moves to a new vendor and consolidates two teams.
- 01
Diff process, people, systems, facilities and supplier dependencies against the current plan.
- 02
Update procedures and call trees while surfacing an untested manual fallback.
- 03
Route owner attestation and a targeted exercise request.
Result
A versioned BCP update with exact changes, one open owner and one required test.
Checks and boundaries
What must be tested or reviewed
- 01Removes a departed recovery contact and routes ownership rather than inventing a replacement.
- 02Flags a manual fallback whose required report is no longer produced.
- 03Keeps a newly documented workaround marked untested until exercise evidence exists.
Human authority
- Plan owner attests content
- Continuity manager approves activation procedures
Keep exploring