Executive Office Emergency Contact Tree

executive office emergency contact tree

Maintain an executive office emergency contact tree with clear activation authority, tested fallback channels, and controlled personal data.

Define activation authority

State which events can activate the tree and who makes that decision. Separate life safety alerts from business continuity updates and routine schedule changes. The assistant should know when to call emergency services, when to follow organizational response leadership, and when to wait for verified direction.

Build role-based branches

Organize contacts by response role such as executive leadership, safety, security, facilities, technology, communications, people operations, and travel. Name a primary and alternate for each branch. Avoid making one well-connected employee the only route to every critical function.

Protect personal details

Collect only approved phone numbers, channels, time zones, availability notes, and escalation roles. Restrict home addresses, family details, medical information, and personal numbers to a documented need. Store the tree in a governed location with offline access only when policy permits it.

Set message discipline

Prepare short templates for activation, status, action required, and all-clear messages. Every update should show its owner, time, audience, and next expected communication. Do not forward rumors or add casualty, cause, or business impact claims that the responsible function has not confirmed.

Test without creating alarm

Schedule announced exercises that verify reachability, alternates, acknowledgment, and fallback channels. Label test messages clearly and coordinate them with response owners. Record gaps without publishing personal contact details in the exercise report.

Maintain and retire entries

Review the tree after role changes, travel, reorganizations, and exercises. Remove departed staff and obsolete vendor routes promptly. Preserve only the activation records required by policy, then delete working exports and personal-device copies.

Design for unavailable technology

Document how the authorized response owner reaches critical roles when the primary directory, messaging tool, or company network is unavailable. Keep the fallback narrow, protected, and periodically refreshed. Do not create an uncontrolled personal contact archive merely because it is easier to open during an exercise.

Test whether alternates can reach external responders and essential vendors when company identity services, office phones, or normal device charging are unavailable.

Common questions

Should everyone receive every alert?

No. Route each message to the roles that need it for safety or response.

Can the tree live in a spreadsheet?

Use only a repository and offline method approved for the sensitivity and availability need.

How often should it be tested?

Follow the continuity owner's schedule and retest after material contact or process changes.

Source and service boundaries

Continuity planning can draw on C-suite assistant coverage and the office continuity handoff guide. Discuss resilient support with a coordinator. Preparedness reference: Ready.gov business guidance.