Emergency Communication Plan: A Guide for Organisations

What is an emergency communication plan?

An emergency communication plan is a documented set of rules and resources that governs how an organisation notifies its employees during an emergency. It defines the alert channels available, the audiences who receive each type of alert, the message templates prepared in advance, the roles authorised to send alerts, and the criteria that trigger a notification.

The emergency communication plan is specifically concerned with the notification layer: getting the right message to the right people through the right channels quickly. It is not a crisis communication strategy, which covers the broader question of how the organisation manages and communicates about an incident over time. It is not a business continuity plan, which covers how the organisation maintains or restores operations. It sits alongside both of those documents and is the operational tool that activates the notification function when either of them calls for it.

An emergency communication plan that exists only as a document is not a plan. It is a record of intentions. The plan has value only when the channels it describes have been tested, the templates it contains have been approved, the roles it assigns have been accepted, and the criteria it defines have been agreed.

How an emergency communication plan differs from a crisis communication plan

The two documents are closely related and are often confused. The practical distinction is this: an emergency communication plan covers the alert and notification layer, while a crisis communication plan covers the full communication response.

An emergency communication plan answers: who needs to be notified, through what channels, with what message, and within what timeframe? A crisis communication plan answers: what is our overall communication strategy for this incident, who is the spokesperson, what do we say to external stakeholders, and how does our communication evolve as the situation develops?

In practice, the emergency communication plan is activated first. It handles the immediate notification to employees. The crisis communication plan governs everything that follows. Organisations that have only one of these documents tend to either communicate quickly but inconsistently, or consistently but too slowly.

The components of an emergency communication plan

Alert tiers and trigger criteria

The plan should define the categories of emergency that exist within the organisation and the criteria that place an incident in each category. A three-tier model is common: Tier 1 for immediate threats to life or safety, Tier 2 for significant operational disruption, and Tier 3 for urgent but non-critical notifications. Each tier has a defined channel combination, a defined audience, and a defined response time.

Trigger criteria matter because they remove ambiguity at the moment of highest pressure. If the plan specifies that a confirmed fire alarm in any occupied building is automatically a Tier 1 alert, the person responsible for sending the alert does not need to make a judgement call. The decision has already been made.

Authorised senders and escalation paths

The plan must name who is authorised to send each tier of alert. Sending an organisation-wide emergency notification without authorisation creates confusion and erodes trust in the alert system. Restricting that authority too tightly creates bottlenecks when the authorised person is unavailable.

A practical approach is to define a primary sender and at least one deputy for each tier, with a clear escalation path if neither is reachable. For Tier 1 alerts in particular, the time to first notification is often the most important metric, so the escalation path should be short.

Audience mapping

Not every alert needs to reach every employee. A site-specific evacuation alert should go to employees at that site. An IT outage affecting one regional office should notify that office's users first. A cybersecurity incident requiring employees to disconnect from the network needs to reach every device user simultaneously.

Audience mapping defines which employee groups receive which alert types. In practice, this is most effectively managed through integration with Active Directory or SSO, so that audience groups reflect the organisation's live directory rather than a manually maintained list that may be out of date. Heed integrates with Active Directory and SSO to enable targeting based on existing directory structure.

Channel assignments by tier

The plan should specify which channels are used for each alert tier. A common assignment is: Tier 1 uses all available channels simultaneously, including full-screen desktop alerts, SMS, voice alerts, and digital signage. Tier 2 uses desktop alerts and SMS. Tier 3 uses a single channel appropriate to the employee population affected.

The channel assignment for each tier should account for scenarios where primary channels may themselves be unavailable. An IT outage alert cannot rely solely on systems that depend on the affected network. The backup channel for each tier should be identified and tested.

Pre-approved message templates

Templates are one of the highest-value components of an emergency communication plan. A template that has been drafted, reviewed, and approved in advance allows an authorised sender to initiate communication within seconds of a trigger criteria being met. The time spent drafting a message during an incident is time employees are not receiving information.

Each template should include: the type of incident it covers, the action employees are required to take, the location or audience it applies to, and a placeholder for any specific details that are not known in advance. Templates should be reviewed at least annually and updated following any incident where the existing template proved inadequate.

Acknowledgement requirements

For certain alert types, particularly compliance notifications and Tier 1 safety alerts, the plan should specify whether acknowledgement is required and what action is taken if an employee does not acknowledge within a defined timeframe. Heed's Emergency Alert System supports acknowledgement tracking, allowing communications teams to see in real time which employees have confirmed receipt and to escalate follow-up to those who have not.

Update cadence

An initial alert that is not followed by updates creates anxiety and speculation. The plan should specify how frequently updates will be sent during an active incident, even if the update is simply to confirm that the situation is ongoing and that more information will follow. Defining this in advance prevents the communications team from having to decide whether to send an update under pressure.

Testing and maintenance

An emergency communication plan should be tested at least annually and following any significant change to the organisation's structure, systems, or risk profile. Testing should cover the technical function of each channel, the accuracy of audience groups, the relevance of existing templates, and the familiarity of authorised senders with the platform and procedures.

A tabletop exercise is an effective way to test the decision-making layer of the plan: whether the trigger criteria are clear, whether the escalation path works when the primary sender is unavailable, and whether the templates cover the scenarios the organisation actually faces. Technical testing confirms the channels work. A tabletop exercise confirms the people can use them correctly under pressure.

Following any incident or exercise, the plan should be reviewed against what actually happened. If the trigger criteria were ambiguous, clarify them. If a template was inadequate, rewrite it. If the escalation path failed, fix it. The plan should be demonstrably better after each review than it was before.

Regulatory and sector considerations

Several sectors impose specific obligations that an emergency communication plan must address.

Financial services firms regulated by the FCA and PRA are required to maintain operational resilience arrangements that include staff notification during disruptions. The emergency communication plan should be documented as part of the firm's business continuity and incident response framework, with evidence that it has been tested.

Healthcare organisations operating under NHS England frameworks are required to maintain major incident communication procedures. The emergency communication plan sits within the wider major incident plan and should be reviewed as part of the organisation's annual preparedness cycle.

Government and public sector bodies operating under the Civil Contingencies Act are required to maintain warning and informing arrangements. An emergency communication plan that covers internal staff notification is part of meeting that obligation.

For organisations in these sectors where data governance and network independence are requirements, the notification system underpinning the plan should support on-premises deployment, ensuring the alert infrastructure is not dependent on external connectivity that may be affected by the incident itself.

The relationship between the emergency communication plan and other documents

The emergency communication plan does not stand alone. It should be referenced by and consistent with the organisation's business continuity plan, its incident response procedures, its crisis communication plan, and any sector-specific regulatory frameworks it operates under.

For the broader crisis communication framework, see the Crisis Communication Plan guide. For guidance on the technology that executes the notification function, see the Emergency Alert System guide. For operational incident response procedures, see the Incident Response Communication guide.