You do not need a hurricane to lose a workday. A blown transformer, a construction crew, an ISP outage, even a “quick” power cut that turns into a long one can stop phones, payments, and access to files.

The goal of business continuity for a power outage is simple: keep the business operating at a safe, reduced pace, then return to normal without scrambling.

Start with the question that matters: what must keep working?

When the lights go out, you find out fast which parts of the business are truly time-sensitive. The mistake is treating every system as equally critical. That is how you end up spending money in the wrong places.

Pick 5 to 10 “must run” functions and be specific. For example: answer inbound calls, take card payments, access the job schedule, email customers, print shipping labels, dispatch technicians.

Then write down the dependencies for each function:

  • Power. Does it require electricity on-site, or can it be done from a laptop and a phone?
  • Internet. Can it work on a mobile hotspot, or does it require a stable wired connection?
  • Apps and logins. Can you sign in without the office network, and do you have MFA methods that still work?
  • Devices. Which exact devices need to be powered (modem, firewall, switch, one PC for printing, a POS terminal)?

Ready.gov’s business continuity planning guidance and their power outage toolkit are useful references here, because they push you to identify essential functions before you start buying gear.

Build a “minimum viable office” for the first 4 to 8 hours

Most growing businesses do not need to run everything during an outage. They need a smaller, deliberate setup that keeps revenue and customer communication moving.

A practical minimum viable office usually includes:

  • A small UPS for network gear. Put your modem, firewall/router, and one switch on battery backup so a short power blip does not drop everything. Ready.gov explicitly calls out UPS and standby generators as common mitigation strategies.
  • A plan for phones. If you use VoIP, assume desk phones may go down when power or internet drops. Decide now whether calls should forward to mobiles, to a call answering service, or to another location.
  • A “keep working” device kit. One charged laptop per key role, plus chargers, and a way to charge phones. This sounds obvious until you are hunting for USB-C chargers in the dark.
  • A printed cheat sheet. Include ISP support numbers, who calls whom, how to forward phones, how to switch the POS to offline mode if it supports it, and where the hotspot lives.

If you have a second site (even a small one), think about it as an alternate work location. NIST’s contingency planning guidance talks about alternate sites and alternate telecommunications as standard continuity concepts, even if you scale them down for a small business.

Plan for the “internet is down but power is on” day

This is the sneaky one. Your team is sitting at their desks, lights are on, but nothing cloud-based works.

Your best moves are usually redundancy and offline access:

  • Secondary internet. A business-class failover circuit is ideal, but many teams start with a dedicated 5G/LTE hotspot that is kept charged and tested. The key is having it ready before you need it.
  • Offline copies of the files you truly need. Cloud storage is great, until you cannot reach it. If you use OneDrive, you can mark specific folders as “Always keep on this device” so they are available offline. Do this for the small set of files that keep the business moving (price lists, job templates, critical spreadsheets, contact lists).
  • An offline “continuity pack.” Keep a local copy of essentials like your vendor list, customer service scripts, and key procedures. Store it somewhere it is reachable without your normal network.

Do not try to make everything available offline. Pick the 20 percent that saves the day.

Plan for the “power is out” day (and it might be out for a while)

Extended outages are where you want decisions made ahead of time. CISA’s resilient power guidance is written for critical facilities, but the mindset applies to normal businesses too: know what you must power, how long you must power it, and what you will do when you cannot.

A practical approach:

  • Decide what you will power, and what you will not. Network gear and one workstation is a very different load than the whole building.
  • Choose your “run time.” Do you need two hours to finish the workday cleanly, or two days to keep serving customers? This drives UPS sizing, generator needs, and where staff should work.
  • Protect sensitive equipment. Power coming back can be messy. Surges and brownouts can damage gear, so power protection is part of continuity, not a nice-to-have.
  • Have a relocation trigger. For example: “If power is still out at 11:00 a.m., customer calls forward to mobiles and admin works remote for the rest of the day.” A trigger prevents endless waiting.

Make outages boring: roles, comms, and a short test

Most outage pain is not technical, it is uncertainty. Who decides to send staff home? Who updates customers? Who talks to the ISP? Who confirms backups are still running?

Write down roles and keep them simple:

  • Incident lead. Makes the call on closing, relocating, or switching to reduced operations.
  • Customer comms owner. Updates your phone greeting, sends the customer email, posts the status message.
  • IT/operations owner. Switches internet failover, checks UPS status, confirms critical systems are stable.

Then test the plan in a low-stress way:

  • Do a 15-minute “pretend outage.” Unplug one non-critical workstation from the network and have someone follow the checklist.
  • Test the hotspot. Confirm you can connect, and that key apps work well enough.
  • Confirm offline files open. An offline copy that nobody can find, or that requires a VPN you cannot reach, is not helping.

NIST’s contingency planning guidance is clear that planning and testing go together. A plan you have not exercised is a guess.

A calm next step

If your business continuity plan for a power outage is currently “we will figure it out,” you are not alone. The fix is a short list of essential functions, a small amount of power and internet redundancy, and offline access to the files that keep revenue moving.

If you would like help putting a practical outage plan in place, the Flexnet Networks team can map your dependencies and build a setup your team can actually use.

Sources