Power outage communication: reaching employees in the dark

When grid power fails, the tools you rely on for urgent notices often fail with it. Office Wi-Fi, desk phones, on-prem alerting servers, and even the digital signage in your lobby can all go dark in the same minute. Your people, however, still need direction — fast. A solid power outage communication plan answers one question before the lights flicker: how do we reach every employee when the building can't help us?

Why power outages break your usual notification stack

Most workplace alerting depends on infrastructure that lives inside the building you're trying to evacuate or shelter in. When utility power drops, on-premise notification servers run on battery for minutes, not hours. VoIP desk phones go silent the moment switches lose power. PA systems, ceiling speakers, and digital signs follow soon after. Even your incident commander's laptop is on a clock once the UPS hum stops.

Outages are also getting longer. The U.S. average customer experiences several hours of interruption a year, and major weather events routinely push that into days. Ready.gov's outage guidance reflects the same trend. Your communication plan has to assume the building will go quiet.

The 30-second rule for outage employee notification

The first message sets the tone. If staff don't hear from leadership inside 30 seconds of the lights dropping, they will fill the silence with rumor, social media, or a walk to the parking lot. A good outage employee notification does three things in one short message:

• Confirms what's happening (power is out at the main office).
• Directs the next action (stay at your workstation, evacuate to the south lot, work from home).
• Promises a follow-up time (next update in 15 minutes).

Build a power outage communication plan in five steps

1. Inventory the channels that depend on grid power. Desk phones, badge readers, PA, signage, on-prem alert servers — anything plugged into the wall is a single point of failure.
2. Map every employee to a personal mobile number. SMS and push travel over carrier networks, which usually outlast a building outage.
3. Define the trigger. Decide who can declare an outage event and authorize the first message. Don't wait for a committee.
4. Pre-stage messages. Drafting a calm, clear update by candlelight is hard. Templates remove that pressure.
5. Set a cadence. Every 15 minutes for the first hour, then every 30. Silence reads as panic.

Channels that survive when the office goes dark

The channels still working at minute one are the ones running on something other than your building's electrical panel. Build the plan around those.

Mobile push and SMS

A cloud-hosted mass notification platform that reaches employees by SMS and mobile app push will land on a phone even if your office network is down. The phone itself is on cellular data and battery. That's the channel that should always carry the first outage employee notification.

Personal email

Work email may be down if your mail server is on-prem. A pre-collected personal email list is a useful secondary channel for longer outages.

Voice call trees

For staff who don't read texts quickly — overnight teams, field crews, lone workers — automated voice calls remain a strong fallback. Pair them with our Lone Worker coverage if you have remote staff.

Roles and escalation: who tells whom

Most outage plans fail not because the technology breaks, but because no one knew who was supposed to push the button. Write the chain down:

• Primary on-call sends the first message within five minutes of the trigger.
• Backup on-call takes over if the primary doesn't acknowledge within five.
• Facilities lead owns building status updates (utility ETA, elevator status, HVAC).
• HR or operations lead owns workforce decisions (work from home, paid time, return-to-office).
• Executive sponsor approves the all-clear.

Silence during an outage doesn't read as calm — it reads as no one is in charge.

Test the plan before the storm hits

A power outage communication plan you've never sent live is a hypothesis, not a plan. Run a no-notice test once a quarter: pull the cord on a single floor or branch, send the templates from your crisis manager playbook, and time how long it takes every employee to acknowledge. Track the gaps and fix the contact list before the real event.

For deeper guidance on resilience drills, the Ready.gov Business framework is a solid starting point. It pairs well with a tabletop using your own templates.

What to do this week

• Audit your current notification path: which steps require building power?
• Confirm every active employee has a current mobile number on file.
• Draft three outage message templates and store them off-network.
• Schedule a 20-minute tabletop with your on-call rotation.
• Pick a date for your first no-notice test.

An outage will come. The question is whether your first message goes out in 30 seconds or 30 minutes. Start with the contact list, write the templates, and pick the channels that don't depend on the building. The lights will go out. The line to your people doesn't have to.