Executive Support Incident Communication Plan

Define the support role before an incident

Executive support can keep leaders reachable, briefed, and consistent during an incident, but it should not become an unofficial command center. Before disruption, name the incident owner, communication owner, executive decision owner, qualified specialists, and the support tasks permitted at each severity. Those tasks may include maintaining the briefing schedule, confirming recipients, preparing a draft from approved facts, preserving decisions, and coordinating the calendar. State what support may not do: declare cause, assess legal exposure, give safety or technical advice, promise recovery, notify regulated audiences, or speak publicly without authorization. Urgency changes timing, not accountability.

Use one authorized incident source

Choose one approved incident record for current status, decisions, next update time, sources, and owners. Executive assistants should link to it rather than creating a parallel truth in a private briefing note. Record when each fact was verified and by whom. A message, screenshot, or verbal report can be evidence without becoming the current state until the authorized owner accepts it. If systems are unavailable, use the documented fallback and reconcile it later. The executive brief should identify gaps honestly so the leader does not mistake an old summary for a live operational picture.

Classify audiences by need

Map internal leadership, employees, customers, vendors, directors, regulators, insurers, media, and personal contacts only where relevant. Each audience needs an owner, channel, approval rule, timing requirement, and minimum necessary detail. Executive support may coordinate delivery while content owners retain substance. Avoid copying the largest distribution list in the name of transparency. Wider communication can expose security information, personal data, privileged advice, or a claim that has not been verified. A stakeholder who needs to know that a meeting is delayed may not need the incident location, affected system, suspected cause, or recovery estimate.

Separate facts, decisions, and message drafts

Maintain three visible categories in every brief: verified facts, decisions already authorized, and drafts or questions awaiting approval. Add a fourth category for disproved or superseded information when confusion is likely. Never smooth uncertainty into a coherent story merely to make the update easier to read. A draft customer line should not sit beside confirmed operational facts without a label. Cite the source and checked time for changeable claims. When leaders ask for interpretation, identify it as analysis and route specialist questions to the responsible function rather than treating executive confidence as evidence.

Build an approval path that survives absence

Create primary and backup approvers for each message class before the incident. State what the backup may authorize, how long delegation lasts, and where the decision is recorded. If nobody with authority is reachable, use the approved holding language or wait; do not invent permission from seniority or mailbox access. Test the route outside a real incident, including a unavailable executive, a conflicted owner, and a message whose legal or regulatory deadline differs from the normal cadence. Technical ability to send from an executive account must remain separate from authority to approve its content.

Protect sensitive incident detail

Use restricted channels for security findings, employee information, health details, customer data, credentials, privileged advice, and investigative material. The executive summary should contain only what the decision requires, with controlled references for authorized readers. Confirm recipients before attaching or forwarding. Do not paste sensitive logs into calendar descriptions or broad chat rooms. Track temporary access, exported files, and external participants, then remove them when the response ends. If a recipient receives information in error, preserve the event and follow the incident owner's containment route instead of attempting an informal deletion that destroys evidence.

Manage the executive calendar deliberately

Protect the incident decision cadence without cancelling every leadership commitment automatically. Identify meetings needed for response, meetings that can be delegated or deferred, external promises affected, travel constraints, and protected obligations. Calendar changes should cite the authorized operational decision and use audience-appropriate language. Keep preparation and recovery windows visible. When the executive is unavailable, route decisions through the named backup rather than adding more urgent meetings. A clear calendar can reduce interruption, but it does not prove the incident is under control; status must continue to come from the authoritative record.

Handle conflicting updates

When two credible updates conflict, preserve both with their sources, times, definitions, and owners. Ask the incident owner or qualified specialist to resolve the current statement. Do not choose the more reassuring number, the newest message, or the most senior sender automatically. If a scheduled update must go out first, state what is confirmed and what remains under review. Correct every active descendant after resolution: the executive brief, approved message, board note, meeting agenda, and status page as applicable. Contradictions are signals to route, not editorial problems for support to hide.

Rehearse a vendor outage

Imagine a critical vendor becomes unavailable during a customer event. Support verifies the vendor notice, opens the approved incident record, locates the operational owner, and prepares the executive's decision schedule. Engineering owns technical impact, customer leadership owns affected commitments, and communications owns released wording. A large customer requests an immediate recovery promise. The assistant routes that request with its deadline and relationship context but does not supply an estimate. Calendar changes use neutral language. When the vendor revises its statement, the team preserves the earlier version and updates only after the technical owner confirms the company's current position.

Close corrections and commitments

Track every external promise, requested follow-up, approved statement, correction, and next update with an accountable owner and acceptance evidence. A sent email is not closure if the recipient required acknowledgement or the content changed. When an incorrect statement has been released, preserve the original audience and version, route materiality to the authorized owner, and send the approved correction through the appropriate channel. Do not silently edit a shared document and assume readers will notice. Close temporary forwarding, groups, links, scheduling rules, and elevated access after the incident, while retaining required records under policy.

Run an after-action review

Review the event with the people who owned operations, decisions, communications, and executive coordination. Reconstruct a few pivotal moments: the first verified alert, an uncertain claim, an approval delay, an audience decision, and a corrected commitment. Identify whether the support plan lacked a source, backup, channel, boundary, or current contact. Improve the smallest control that addresses the evidence. HireExecutiveTeam executive support can operate leadership briefing and follow-through inside this model, while incident command and qualified functions keep substantive authority. The useful outcome is trustworthy coordination under pressure, not more messages or a polished retrospective that hides uncertainty.

Related resources

• Leadership team administration
• Executive support escalation path design
• Executive support communication charter

Frequently asked questions