Plans

BCP Maintenance Cycle

Keep plans current through event-driven updates, scheduled reviews, ownership attestations, dependency checks and exercise feedback.

Keep plans current through event-driven updates, scheduled reviews, ownership attestations, dependency checks and exercise feedback. The acceptance record should identify the exact scope and expiry.

Two levels of readiness for BCP Maintenance Cycle

A documented procedure to trigger targeted updates after process, provider, contact or system changes is not proof that the team can execute it under realistic demand. Validate staffing, access, timing and the observed outcome. Where plans are reviewed annually while technology dependencies change monthly, the gap may surface before the plan's expected activation point. Identify the signal that should prompt an earlier intervention.

Readiness under test: Use change log, owner validation, document version and exercised changes. Evaluate the information at the relevant date and system boundary, then challenge it with an exercise where new identity platform removes access assumed in all approved plans. The test should show how the operator recognizes an exception, changes the operating mode and tells affected users what service remains available.

For BCP Maintenance Cycle, return-to-service approval must explicitly resolve the condition where plans are reviewed annually while technology dependencies change monthly. Confirm the previously unmet decision—trigger targeted updates after process, provider, contact or system changes—with dated change log, owner validation, document version and exercised changes, not only a technical completion status.

Related reading for BCP Maintenance Cycle

Prove BCP Maintenance Cycle capability

If a named delegate is absent, test whether another authorized person can retrieve the evidence and execute the action without relying on private credentials. Evidence should address the selected control rather than generic readiness: Use material change triggers, accountable attestations, dated dependencies and recent test findings to keep plan instructions current.

The operating context matters for BCP Maintenance Cycle. At the next management review, reconcile overdue actions with the risk register and funding decisions. A closed workflow item without a verified outcome should remain a capability exception. Sample recent changes, not only decisions made at the annual review. An example of material exposure is: Changing a plan's review date without validating contact and system dependencies creates false assurance.

Acceptance evidence for BCP Maintenance Cycle

Use material change triggers, accountable attestations, dated dependencies and recent test findings to keep plan instructions current.

Boundary of the demonstrated result — BCP Maintenance Cycle

Changing a plan's review date without validating contact and system dependencies creates false assurance.

Review at three levels

  • Monthly or automated checks: contacts, links, call lists and referenced resources.
  • Change-triggered review: affected procedures, dependencies, recovery strategies and authority paths.
  • Periodic assurance: full owner attestation plus exercise evidence that the plan still works.

Track each material statement to an owner and source where practical. Version history should explain what changed and why. A plan should not be marked current merely because a reviewer changed the date; completion requires evidence that assumptions and recovery capability remain valid.

Use this BCP Maintenance Cycle guidance as an implementation baseline, then tailor thresholds, roles, evidence and escalation to the organization's operating model and applicable obligations. A useful completion test is whether a different competent person can understand the decision, reproduce the reasoning from the retained evidence and know what action is required when the stated condition is not met.

Maintain the BCP when the operating model changes

An annual review date is a minimum control, not a maintenance strategy. Use event-driven triggers so the plan is reviewed after changes to critical processes, applications, locations, suppliers, organization structure, contact details, recovery targets, regulation, exercises or incidents.

Additional review: Review at three levels

  • Monthly or automated checks: contacts, links, call lists and referenced resources.
  • Change-triggered review: affected procedures, dependencies, recovery strategies and authority paths.
  • Periodic assurance: full owner attestation plus exercise evidence that the plan still works.

Track each material statement to an owner and source where practical. Version history should explain what changed and why. A plan should not be marked current merely because a reviewer changed the date; completion requires evidence that assumptions and recovery capability remain valid.

Related BCM.Center resources: BCP Activation and Stand Down · BCM Policy Governance.

Handover and acceptance for BCP Maintenance Cycle

The handover should identify exactly what is still degraded after the immediate response to plans are reviewed annually while technology dependencies change monthly. Operations needs a single owner for remaining service restrictions, outstanding transactions or dependent teams, and an agreed condition for returning responsibility to normal management. If there is no safe or feasible method to trigger targeted updates after process, provider, contact or system changes, do not conceal that limitation behind a general “recovered” status.

Prepare the next-shift brief from change log, owner validation, document version and exercised changes. Mark observations, assumptions and unresolved exceptions separately. Include when the relevant information was collected, because a state that was correct at the first recovery checkpoint may change after traffic returns or demand accumulates.

Ask an independent reviewer to challenge the claim under this variant: new identity platform removes access assumed in all approved plans. The reviewer should identify what would invalidate the previous approval, who would authorize a change to the operating mode, and which customers, staff or suppliers need an updated instruction. Corrective actions need a tested outcome, not merely revised wording.