When Systems Go Down: A Business Continuity Plan That Actually Works

Every business has a day when the systems stop. The question is whether it's an hour of inconvenience or a week of chaos. The difference is almost never luck. It's whether someone decided, in advance, how the business keeps working and how it gets back.

What actually takes small businesses down

It's rarely the dramatic stuff. The usual causes:

• Hardware failure: a server, a hard drive or a network switch that simply dies of old age.
• Accidents: a coffee spilled on a laptop, a file deleted by mistake, a cable pulled during cleaning.
• Power and weather: outages and surges from winter storms and summer thunderstorms, which are part of life in Northeast Wisconsin.
• Ransomware and hacked accounts.
• Someone else's outage: your internet provider, your phone system, or a cloud service you rely on.

Living in Northeast Wisconsin, I've seen how a single storm can take a business offline for a day.

What an hour of downtime costs

Downtime costs more than the repair bill. Work out your own number:

• People who can't work, times what an hour of their time costs you.
• Revenue per hour that depends on your systems: orders, bookings, billing.
• Customers who can't reach you, and the trust that costs. A missed delivery or a booking system that's down in peak season is remembered.

The downtime calculator on our Resources page does this arithmetic for you. Most owners are surprised by the answer.

Decide two numbers now

• How long can you be down? A few hours, a day, three days? That decides how fast recovery must be, and what it should cost.
• How much work can you afford to lose? Yesterday's? The last hour's? That decides how often you need to back up.

Everything else in the plan follows from those two answers.

Backups that actually work

• Keep at least three copies of important data, on two different kinds of storage, with one copy off site.
• Make one copy immutable or offline, so ransomware can't reach or delete it.
• Test a real restore every quarter. A backup that's never been restored is a hope, not a plan.
• Know how long a full restore takes. That number belongs in your plan.

The businesses that bounce back fastest are the ones that tested their backups before they needed them.

Your cloud data is your responsibility too

Moving to Microsoft 365 or Google Workspace doesn't mean your data is backed up the way you might assume. Microsoft keeps the service running, but deleted email and files are only recoverable for a limited time, and Microsoft's own service agreement recommends that customers back up their content. A separate backup of your Microsoft 365 email, OneDrive, SharePoint and Teams covers the deleted-by-mistake, the departed employee and the ransomware that syncs to the cloud.

AI and dashboards won't save you here

Modern tools, from AI assistants to real-time dashboards, are only as available as the systems behind them. When the network is down, they're down too. A continuity plan has to work on paper, with phone numbers and steps people can follow without a computer.

The one-page plan

• Who decides, and their backup.
• Who to call: IT provider, internet provider, insurer, key vendors. Printed, not only saved on the server.
• How you'll keep working for a few days: taking orders, answering phones, paying staff.
• Where the backups are, and how long a full restore takes.
• Who tells customers what, and when.

Cheap insurance against the common stuff

• Battery backup units on servers and network equipment, so a flicker doesn't become an outage.
• A second internet connection, even a cellular backup, for businesses that can't take orders without it.
• Spare laptops, or a fast way to get one, for the people who can't stop working.
• A local IT partner who can be on site when something physical breaks.

Test it

Once a year, walk through a scenario with the people in the plan: "The server died this morning. What happens next?" You'll find the gaps while they're free to fix.