Crisis communications logistics for executive assistants

Crisis coordination

Key takeaways

• Activate the authorized contact tree.
• Separate facts from assumptions.
• Protect approval evidence.

Operating data

Playbook

In a crisis, an executive assistant contributes disciplined logistics, not spokesperson authority. The assistant can maintain contact continuity, meeting access, version control, decision records, and follow-up while incident leaders and communications professionals determine facts, messages, and disclosure. Begin with an activation rule naming who may activate, coordinators, approved channels, participants, and fallback escalation.

If activation arrives from an unverified sender, authenticate it through a known path before sharing sensitive information. Open a time-stamped log with event time, source, verification status, owner, action, decision, and next check. Keep confirmed facts, unconfirmed reports, working assumptions, and approved messages in separate lanes so pressure never erases evidence boundaries.

The executive customer escalation brief offers a related source-discipline pattern, although crisis work may require legal, security, safety, privacy, or regulatory ownership. Match briefing cadence to the incident lead. Confirm participants, secure access, approved summary, decisions requested, unresolved facts, and next update. CISA incident response resources provide general guidance; the organization plan controls.

Maintain one approved-message register: audience, channel, approver, approval time, version, sender, release condition, and delivery evidence. Never combine drafts or reuse a statement for another audience without approval. When facts change, preserve the correction trail and make the superseding version unmistakable. Protect alternate contacts, distribution lists, accessibility contacts, and backup connectivity plans.

Route non-urgent dependencies through operations follow-through. At stand-down, read back open actions, communication triggers, custodians, access changes, and records to preserve. Revoke temporary permissions when authorized, archive the approved log, and schedule review. Measure missed contacts, approval ambiguity, version conflicts, and delayed corrections rather than message volume.