
A backup communications plan needs more than a second device. The people expected to use it must understand the approved changeover process, know its limitations and have a way to practice with the partners involved.
It is easy to assume that a radio, a mobile phone and an internet messaging service provide three independent options. In practice, some alternatives may rely on the same power, backhaul, account access or facility. Those dependencies are a reason for qualified review, not a reason to improvise a new operational plan during an incident.
This article is a discussion guide for preparedness staff, communications leadership and authorized partners. It does not prescribe frequencies, access methods or incident procedures. Keep the real plan and sensitive system information in the organization’s controlled environment.
Bring the people who own the process
Include the communications lead, relevant operational supervisors, technology support and the partner organizations whose participation is necessary. Add appropriate continuity, accessibility and procurement representatives when their responsibilities are part of the question.
Set a narrow purpose for the meeting. “Review how our approved backup contact process is understood by partner coordinators” is manageable. “Solve every communications problem” is not. Identify which decisions the group can make and which require another authority.
Use the current approved documents as the starting point. If nobody can identify the authoritative version, resolve ownership and document control first. Testing a mixture of old personal notes and current procedures will create findings that are difficult to interpret.
Understand what PACE planning contributes
CISA’s PACE planning resource discusses primary, alternate, contingency and emergency communications options. It offers a framework for considering redundancy and the limitations of available methods.
The acronym is a planning aid. Naming four channels does not demonstrate that they are available, independent, interoperable or authorized for a particular task. Qualified local staff need to evaluate those issues against the organization’s actual requirements.
For this discussion, ask each responsible party to explain the purpose of an approved option and the conditions under which its use is directed. Keep detailed answers in the controlled plan. A public article or meeting recap should not become a list of internal access arrangements.
Start with the job that communication must accomplish
Choose one ordinary planning scenario: a routine coordination channel becomes unavailable and designated partners need to exchange an approved administrative update. Identify the task, participants and information type before discussing technology.
Ask what a successful exchange means. Does the sender need confirmation of receipt? Does the recipient need to acknowledge an assignment? Is a voice discussion necessary, or is a verified written update appropriate? The answer affects the requirements, but it should be determined by authorized staff.
Separate public messaging from internal coordination. A system suitable for telling residents where to find an update is not automatically suitable for exchanging sensitive operational information. Different tasks can require different controls.
Look for shared dependencies
| Area | Discussion question |
|---|---|
| Power and facilities | Could one facility or power problem affect several options? |
| Connectivity | Do alternatives share an upstream service or other dependency? |
| People | Is trained staff coverage available for the approved option? |
| Access | Can authorized users follow the approved access process when needed? |
| Partners | Have participating organizations confirmed how the process works together? |
| Information | Is the option approved for the sensitivity and format of the intended message? |
Mark unknowns as questions needing review. Avoid changing a blank cell to “available” because someone remembers using the service years ago. Availability is a current condition that the responsible team must verify.
Make the transition responsibility clear
Ask who has authority to direct a change, how that direction reaches the relevant users and how recipients confirm the new arrangement. The approved plan should make the responsibility understandable without relying on one experienced employee’s memory.
Discuss how staff learn that an alternative is unavailable too. A plan needs a process for reporting limitations and escalating unresolved issues. Do not assume that a message sent through a new channel was received merely because no error appeared.
Keep accessible communication in the discussion. Staff and partners may need approved accommodations or formats to participate reliably. Resolve those arrangements during planning, with the appropriate expertise, rather than making a person disclose a private need during an exercise.
Test understanding with a controlled exercise
Ask qualified exercise staff to design an appropriate discussion or test. Use clearly marked exercise information and an approved notification plan. Do not generate real public alerts, emergency calls or unannounced disruptions to see what happens.
FEMA’s HSEEP guidance provides an exercise and evaluation framework. Apply it at a scale suitable to the objective. A discussion about roles and handoffs may reveal a useful gap without requiring a live system test.
Record observations against the objective: could participants identify the current document, explain their responsibility and describe the approved confirmation step? Keep technical verification separate when it requires another exercise or specialist review.
Turn gaps into assigned work
A finding such as “backup communications need improvement” is difficult to complete. Write the specific issue, responsible owner, next action and evidence that would show it has been resolved. For example, a partner contact sheet may need its named owner confirmed through the approved channel.
Do not mark an issue complete because a new document was emailed. Check the relevant outcome. If the problem was that staff could not locate the current procedure, verify that authorized users can now find it in the intended place.
Where the review identifies a technology purchase, route it through the organization’s requirements and procurement process. The cheapest product or the most familiar brand may not meet the actual need. Training, support, interoperability and later maintenance belong in that discussion.
Keep public summaries at the right level
A general update can say that partner organizations reviewed communications continuity and assigned follow-up actions. It does not need to reveal coverage limitations, access details, internal contacts or the exact trigger points in the operational plan.
Similarly, keep sensitive exercise notes out of public photo albums and unrestricted shared folders. Agree on storage, access and retention before the meeting so that participants do not default to their personal accounts.
Our NG911 address data checklist addresses a different communications readiness issue. The accessible alert review can support a separate public-message discussion.
Revisit the plan when something changes
Changes in staff responsibilities, service providers, partner arrangements or facilities can affect a previously useful plan. Assign a review owner and appropriate triggers, alongside the organization’s required review schedule.
Retain the lesson from a real outage or exercise in the controlled improvement process. An informal story about how someone solved the last problem is useful context, but it should not quietly replace an approved procedure.
The practical goal is a team that understands its authorized options and knows how to identify the next unresolved dependency. A backup plan becomes more dependable through verified responsibilities, appropriate exercises and completed follow-up work.
Write a finding that can be closed
Compare two possible exercise notes. “The alternate channel was confusing” tells a later reviewer very little. “The partner coordinator could not identify where the current approved changeover instructions are maintained” describes an observable administrative gap.
The second note can lead to a specific action: the communications owner confirms the authoritative location, arranges any approved access correction and briefs the affected roles. A later check then verifies that the relevant authorized participants can locate the right instructions.
The action should not expose the document publicly or grant unnecessary access. The owner must use the established controls. Record the completion evidence at the level appropriate to the plan, with sensitive details kept in the controlled record.
If the issue actually concerns technical capability, route it to the technical reviewer instead of closing it with a document update. Clearer instructions cannot make an unavailable or unsuitable system perform a function it does not support.
By Sherry Wood for HUB911. Sources reviewed November 17, 2026. Examples and worksheets are editorial planning aids.