Emergency Contact Trees for Executive Assistants

executive office emergency contact tree for assistants

During an evacuation, severe weather event, or building outage, the executive office should not improvise who calls whom. A useful contact tree tells people where to get verified instructions, who checks on the executive's immediate party, and how to report an unresolved safety concern. It is a communication aid, not a substitute for the organization's emergency plan.

Begin with the official incident owner

Identify facilities, security, safety, or another role authorized to issue instructions. The assistant should pass on verified direction and report executive-office status, not create a competing command channel. Put emergency services ahead of internal notifications when life or safety requires it, and make that priority explicit in the written procedure.

Use roles before personal names

Build the tree around current responsibilities such as floor warden, executive assistant, travel lead, and people operations. Attach contact details through the controlled directory so a departure does not leave an old number embedded in several files. Keep home addresses, family contacts, and medical information out of the general tree.

Define the message and acknowledgment

A call or text should state the verified event, immediate instruction, source, time, and how the recipient confirms receipt. Avoid speculation and copied social posts. The tree needs a fallback when a person does not answer, plus a clear point where the caller stops retrying and reports the gap to the incident owner.

Test without staging an emergency

Run a scheduled notification drill with a plain test message. Measure whether contacts are current, acknowledgments arrive, and backups understand their role. Do not surprise staff with realistic danger language. Record failures, update the directory, and test the corrected branch rather than declaring the whole exercise complete after the first successful call.

Score the drill by unresolved contacts

The useful number after a test is not how many messages were sent. It is how many people received verified instructions within the expected window and which branch stopped. Check wrong numbers, unclear acknowledgment language, unavailable backups, and delayed escalation. Give each failure to the role that maintains the directory or emergency plan.

Test the repaired branch again without replaying the entire exercise. Staff should recognize the message as a drill, and personal contact details should remain inside the controlled system. If the executive office repeatedly creates its own exceptions, bring them to the incident owner. A separate informal tree will become less reliable each time the organization changes.

Contact-tree rules to agree before a drill

Should the executive be at the top of the tree?

Usually the official emergency owner should lead instructions. The executive's place depends on the organization's plan and incident role.

Can personal phones be included?

Use only contact data the organization is authorized to maintain, with suitable access controls.

How often should the tree be tested?

Follow the emergency-plan schedule and retest after material role, office, or contact changes.

Emergency planning guidance for accountable communication

OSHA's emergency action plan material identifies communication and accountability as plan elements. The executive-office tree should fit inside that larger program. Organizations that need disciplined executive-office coordination can review our C-suite assistant service. The executive assistant hiring resource helps define continuity duties, and teams may contact us to discuss coverage across locations. Source: OSHA emergency action plan guidance.