Plan and prepare
Write a compact contact card for the people and services you would most need to reach if your phone were unavailable. Include names, roles, phone numbers, and an agreed alternative contact. Use numbers that can be dialed directly rather than relying only on app usernames or saved address-book entries.
Keep the card focused. A personal version may contain private contacts, while a community version should list role contacts whose owners agreed to distribution. Avoid printing the entire membership directory for every volunteer. Add the date last checked and a brief description of when each contact should be used.
Use a clear process
For a group, draw a small call tree showing who passes routine updates to whom. Limit each person's assigned contacts to a number they can realistically reach. Agree on an acknowledgment and what happens if someone is unavailable. A backup should know the role before their number is printed on the tree.
Rehearse with an unmistakably labeled test message during a prearranged period. Ask recipients to repeat the key information rather than forwarding an increasingly shortened version. Record only whether contact succeeded and which details need correction. Do not place practice calls to emergency numbers or create messages that could be mistaken for a real alert.
Worked example
For example, a four-person project can name one primary publisher and one backup, then assign each of them two routine contacts. The message should contain the same short facts for every recipient: what changed, when it applies, what action is requested, and where questions go. A recipient confirms receipt to their assigned caller instead of starting several overlapping reply chains. If the main publisher is unavailable, the backup follows the same list. This arrangement is small enough to test and makes a missed contact visible without distributing everyone's personal details to the whole network.
Decisions and exceptions
Keep a master change record when numbers or responsibilities change. The person maintaining it should confirm the new detail with its owner, date the update, and identify which card holders need a replacement. Do not depend on someone noticing an edited online document when the purpose of the card is to work offline. If a role rotates, consider a stable organizational contact route where appropriate, while still recording the current responsible person privately. Make clear which contact is for routine project matters and which established number is used for an actual emergency.
Check and improve
During a test, note how long the complete chain takes and where wording changes. A missing acknowledgment may mean a wrong number, an unavailable device, an inaccessible format, or simply a poorly chosen test time. Ask before deciding. Revise the sequence so participants know whether to retry, use an alternative, or notify the coordinator. Keep a readable spare card with the project materials and protect private copies appropriately. Repeat a short check after membership changes, because a beautifully printed card becomes a liability when it confidently points people toward contacts who no longer hold the role.
Solo and community application
Alone, carry a readable copy and keep another in a known place with your preparedness materials. A community team can maintain one controlled master and replace outdated copies after a contact change. Ask recipients to dispose of superseded private cards appropriately instead of leaving them on public noticeboards.
Reference guidance
Ready.gov recommends planning contacts and communication methods ahead of emergencies. The card and call-tree arrangement here is a small operational extension. Check whether the system depends on one coordinator's phone or one messaging account, and give participants an agreed route that still works when that person is absent.