What Happens When Your Systems Go Down

The Tuesday Morning Scenario

Your phone rings at 8:47am. It's your production manager. "The system's down. I can't access orders. Nobody can log in. What do we do?"

You call your IT support. They say they'll look into it. An hour passes. Then two. By 11am you're asking your team to write down orders on paper and figure out what's already in production from memory.

By 3pm you're calling customers to explain that their orders will be delayed. By 5pm you're calculating what this day has cost you — and realising you don't have a clear answer.

This scenario plays out in businesses like yours every week. And most of them don't have a plan for it.

The Cost of Not Being Prepared

When I ask business owners how much a day of downtime would cost, they usually underestimate by a factor of three. Here's what's actually lost:

Orders You Can't Process

Every order that comes in while your systems are down either doesn't get captured or has to be manually re-entered later. Some will be lost entirely. Customers who don't get order confirmations will call. Customers who don't get responses will buy elsewhere.

Production That Stops

Your production team can't work without orders, specs, and artwork. Even if you can manually re-create some information, the delay compounds across every job in progress. Despatch deadlines are missed. Overtime is required to catch up.

Data You Can't Recover

If the outage involves data loss — corrupted database, failed backup, ransomware — the cost becomes permanent. Order history, customer records, artwork files, pricing structures. Some of that data cannot be recreated.

Reputation You Can't Rebuild Quickly

Your customers don't care about your IT problems. They care that their orders didn't arrive. A significant outage can damage relationships that took years to build.

Why Most Businesses Don't Have a Plan

I've asked dozens of business owners why they don't have a disaster recovery plan. The answers are almost always the same:

• "It won't happen to us" — because it hasn't happened yet
• "Our hosting provider handles that" — they don't, not in the way you need
• "We don't have time to write a plan" — which is exactly why you need one
• "We'll figure it out when it happens" — you will, but it will cost ten times more than planning in advance

What a Good DR Plan Looks Like

A disaster recovery plan for a small or medium business doesn't need to be a 50-page document. It needs to answer four questions clearly:

1. What systems do we protect first? Not every system needs instant recovery. Prioritise based on business impact.
2. How fast does each system need to come back? Your recovery time objective (RTO). Hours, not days, for critical systems.
3. How recent does the recovered data need to be? Your recovery point objective (RPO). Can you lose an hour of data? A day? A week?
4. Who does what when it happens? Clear roles. No ambiguity. Everyone knows their job.

And one more thing: test it. A DR plan that has never been tested is a wish, not a plan. Schedule a test day. See what breaks. Fix it. Test again.

What You Can Do Today

You don't need a full audit to start improving your resilience. Here are three things you can do this week:

1. Find your backups. Do you know where your backups are stored? When they last ran? Whether they can actually be restored? Find out. Today.
2. Identify your critical path. What's the one system you cannot operate without for more than a few hours? That's your priority.
3. Write down the recovery steps. Who do you call when the system goes down? What do they need access to? Write it down and put it somewhere accessible even when the network is down.

These three steps will put you ahead of most businesses in your sector. A full disaster recovery plan — tailored to your technology stack, your business model, and your risk tolerance — is what comes next.