
A continuity record is useful only if the right authorized people can locate a current, usable version when the normal arrangement is unavailable. Saving copies is part of the work. Knowing which copy matters, who may use it and how access is restored are equally important.
Organizations often discover the gap during an absence or disruption. The file exists, but only one person knows its location. A backup colleague has access to the folder but not the current version. A printed binder contains familiar information that has not been checked for years.
This article provides an administrative review for continuity planning. Technology recovery, cybersecurity, records retention and access decisions require the responsible specialists and the organization’s actual policies. Do not use a general checklist to create new access, move sensitive files to personal accounts or bypass security controls.
Start with the essential function
Ask leadership which functions the organization needs to sustain and what records those functions depend on. Begin with one function so the review remains manageable. A record’s importance comes from the work it supports, not simply its age or file size.
For example, a routine service coordination function may depend on a current responsibility list and approved contact process. Another function may need an agreement or a particular authoritative record. Keep the actual details within the appropriate controlled plan.
FEMA’s Continuity Guidance Circular discusses planning and exercising continuity capabilities, including access to records needed for essential functions. Use that framework alongside the requirements specific to your organization.
Identify the authoritative copy
For each selected record, document its owner, approved location, version information and review trigger. Make clear which copy controls when an email attachment differs from a shared folder version.
Do not create another unofficial master because the existing location is inconvenient. First ask whether the approved system can provide the necessary access and recovery arrangement. A duplicate list can quickly become less dependable than the problem it was meant to solve.
If an offline or printed copy is part of the authorized plan, define how it is updated, protected and withdrawn when superseded. A binder should not be assumed current merely because someone knows where it is kept.
Ask who needs access for the function
List the responsible roles and the backup roles, then have the appropriate access owner review what each needs. Avoid broadening access to everyone on a planning group simply to make the exercise easier.
Check whether the backup arrangement depends on an individual’s personal account or device. If it does, route that issue to the organization’s technology and security staff. Sharing a password is not a continuity plan.
Keep access requirements and actual authorization separate. A worksheet may identify a business need, but it does not itself grant permission. Use the established approval process for any change.
Look at the whole retrieval path
| Question | What the reviewer should establish |
|---|---|
| Why is it needed? | The essential function and decision it supports. |
| Which version controls? | The authoritative location and current owner. |
| Who may use it? | The authorized primary and backup roles. |
| What could interrupt access? | Dependencies requiring specialist review. |
| How is access recovered? | The approved support and recovery process. |
| How is success checked? | A suitable test of usable access to the correct record. |
Keep the answers in the controlled continuity records. Publicly sharing the dependency details can create unnecessary exposure and is not needed to explain that a review took place.
Test with a suitable, authorized method
Agree on the objective and boundaries before testing. A simple discussion may be enough to reveal that the backup person does not know which system holds the record. A technical recovery test needs the appropriate specialists and its own approved plan.
Use non-sensitive sample material when it can answer the question. If an actual record must be involved, confirm the participants and handling arrangements first. Do not email the file to an outside address to see whether someone can open it.
Record what was tested, by whom and what the outcome establishes. “The backup staff member located the correct current document through the approved process” is meaningful. “Backups are fine” is too broad to support.
Separate backup completion from recovery success
A system report saying a backup job ran is not the same as demonstrating that the required record can be recovered and used. Ask the technology owner what verification is appropriate and how the result is documented.
The relevant test may involve completeness, currency, readability and authorized access. Different records and systems have different requirements. Avoid inventing a universal recovery time from a general article or another organization’s experience.
If a gap is found, give it an owner and a next review point. Do not conceal the uncertainty by changing the planning worksheet to “complete” before the responsible team has resolved it.
Review agreements and contact information
A continuity file can depend on outside providers or partner arrangements. Check whether the relevant contract, service contact and support process are current. Confirm the official route through the organization’s normal business records.
Record the distinction between a provider’s general marketing claim and the service actually purchased. A company may offer several levels of support; the organization needs to know which terms apply to its own arrangement.
Keep private contacts and contract details appropriately restricted. A public resource directory is useful for discovery, but it should not replace the organization’s internal agreement and authorized contact record.
Use a simple example to reveal the gap
In a fictional community organization, one coordinator manages the current approved service contact list. During a planned absence, the backup colleague finds three versions in email but cannot identify which controls.
The review establishes one authoritative location, assigns responsibility for updates and confirms the backup colleague’s access through the approved process. The old copies are handled under the organization’s records practices, with clear indications where needed that they are superseded.
The improvement is not just a new folder. It is a shared understanding of which record to use and how that record stays current.
Keep the review connected to real changes
Useful triggers include a change in responsibilities, a new system, a revised agreement, a provider change or an exercise finding. Keep any required periodic review too. A calendar date alone will not identify the effect of a major change made between reviews.
Update the continuity plan through its normal process and check whether affected staff need a briefing or exercise. A record can be technically current while the people expected to use it still follow the old arrangement.
Our public works preparedness checklist provides a related organizational review. The accessible alert checklist can inform a separate discussion about the public-facing information a continuity process supports.
For a later practice session, use qualified exercise staff and an objective that checks the specific gap. The goal is dependable authorized access to the right record, with enough evidence to know what was actually verified.
Check the handoff during a normal absence
A planned absence can reveal ordinary record problems without simulating a major disruption. Through the organization’s normal arrangements, ask the backup role to locate the current non-sensitive example record and identify the responsible owner.
If they need to ask the absent colleague which attachment is current, record that dependency. Resolve the document-control question through the approved process. Do not ask the colleague to share credentials or move the file to an unapproved service.
Keep the outcome specific. The check may establish that the backup person can find a selected record under normal conditions. It does not prove the organization can recover every system during an outage.
Use that distinction when reporting progress to leadership. Small verified improvements are valuable, but they should be described at the level actually tested. A clear limitation helps the next reviewer decide what still needs a technical recovery test or a different exercise.
By Sherry Wood for HUB911. Sources reviewed November 17, 2026. Examples and worksheets are editorial planning aids.