Document control determines which version of a continuity plan or recovery instruction is authoritative, who approves revisions, and how current copies reach the people who need them. During a network or identity outage, an up-to-date central document is insufficient if the on-call team can access only an obsolete offline version. Maintain an approved master, a traceable revision register and a distribution method that can be exercised without the main repository.
Prove that controlled copies remain current
In a hypothetical night-shift activation, responders discover conflicting contact numbers in an offline plan and the normal document repository is unavailable. The duty lead checks the copy's version and effective date against the controlled distribution register, verifies the authorized escalation chain through an independent channel and records the obsolete copy for withdrawal. Where verification is impossible, the team escalates the uncertainty rather than treating the instructions as current.
Evidence from the retrieval test
- Document state: Approved version, revision rationale, effective date, owner and approval record.
- Distribution: Current custodians, issued copies, access permissions, offline availability and recall method.
- Performance: Time to retrieve the correct plan and an authorized contact without depending on the plan author or primary identity system.
At handover, record which copies have been verified, which remain unaccounted for, the temporary communication path and the person responsible for withdrawing obsolete instructions.
Control revisions, access and offline distribution
Maintain one authoritative current version for each plan and supporting runbook, with an approval trail that identifies the approver, effective date, revision rationale and superseded version. Define whether a change requires full approval or can follow an emergency amendment path. The control register should also record which locations, teams, contractors and on-call roles need access. An offline copy is not simply a convenience: it is a managed document with a named custodian, issue date, permitted storage location and withdrawal process. Personal contact details and operational secrets should be protected according to applicable access and retention rules; do not assume everyone entitled to activate a plan is entitled to every confidential annex.
Changes to service dependencies require corresponding updates to contacts, recovery prerequisites, decision authorities and alternate arrangements. For example, replacing a communications provider can make an old activation checklist unusable even though its policy version number remains current. Trigger a review after material supplier, organization, system or site changes, and verify that related quick-reference cards and staff instructions carry the compatible revision.
Controlled copies during a loss of systems
Distribute only the minimum sensitive content needed by responders. When offline copies are essential, define how the custodian replaces obsolete copies, confirms retrieval and protects passwords or personal contact details.
For an exercise, disconnect access to the document repository. Ask the on-call responder to retrieve the applicable, current plan, locate an authorized deputy and identify the latest restoration instruction without relying on the author. Record any mismatch between paper, mobile and portal versions; update the controlled distribution register and remove superseded copies.
Acceptance and retrieval evidence
Measure the time for an on-call responder to find the correct plan without support from its author. Include an out-of-hours test in which the main repository, VPN and identity provider are unavailable. The reviewer should record which copy was retrieved, how its authority was established, whether associated contacts and procedures matched the approved version, and which documents could not be accessed. Close discrepancies by correcting distribution, updating custodians and retesting retrieval. A successful document review alone is not evidence that offline copies were usable in the tested condition.
Before an incident is stood down, reconcile any emergency amendments and annotations into the controlled master. Retain superseded versions according to established records requirements while preventing obsolete instructions from remaining in operational use. Revoke temporary access issued for the event, confirm that distributed teams have current copies, and record unresolved exceptions with expiry and an accountable owner.
Related reading for BCM Document Control
- Business Continuity Risk Appetite and Acceptance
- Business Continuity Program Charter Guide
Approval evidence and expiry — BCM Document Control
The acceptance record should identify the exact scope and expiry. If a named delegate is absent, test whether another authorized person can retrieve the evidence and execute the action without relying on private credentials. Use version history, effective approvals, controlled distribution, offline copy expiry and rapid retrieval testing for responder documents.
Reopen a policy decision — BCM Document Control
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. Control continuity plans and records through ownership, versioning, approvals, access, distribution, retention and obsolete-copy handling.
Use a decision-rights register to distinguish the business owner, the BCM coordinator, the relevant technical authority and the person permitted to accept a time-bounded exception. Decision packets should show the affected business service, unacceptable-impact boundary, proposed measure and evidence that justified the choice. Challenge the following failure directly: A current document in the central repository cannot help responders who are offline with unapproved older versions.
Potential weakness in accountability and decision evidence
A current document in the central repository cannot help responders who are offline with unapproved older versions.
Validate the accountability and decision evidence decision
Use version history, effective approvals, controlled distribution, offline copy expiry and rapid retrieval testing for responder documents.