You don't need an outage to find out whether your business is ready for one. The evidence is sitting in plain view on an ordinary Tuesday.
Nobody chooses to be unprepared. You're running jobs, covering payroll, and keeping customers happy, and preparation is the only thing on that list with no deadline attached. It loses to everything that has one, and it keeps losing until something breaks.
Here are the five signs we see most often when we walk into a new environment around Deer Park, La Porte and Pasadena. Each one comes with a test you can run yourself this week, without calling anybody.
1. Every conversation you've ever had about recovery started with an outage
Recovery planning gets triggered. It rarely gets scheduled. Something goes down, everyone asks the same three questions — are the backups good, how long will this take, who's handling it — and once the systems come back those questions go away for another year.
The test: open your calendar and look back twelve months. If there's no meeting, no note, and no email about backups, restore times, or what happens if a system is gone for a day, then you have no plan. Whatever the last emergency taught you is sitting in one person's head, and it leaves when they do.
2. Ask three employees what to do when the network is down and you get three answers
The first half hour of an outage is the most expensive half hour, and it usually gets spent on confusion rather than on the problem.
The test: walk the floor and ask three people, with no warning, "systems are down right now — what do you do in the next five minutes?" You're listening for whether they agree on who gets called, whether they should keep working on paper, and what they tell the customer already on the phone. If the three answers don't match today, they won't match during the outage either.
3. Your written plan names a system you no longer run or a person who no longer works here
Plans go stale in specific, predictable ways. The VPN got replaced. The line-of-business software moved to the vendor's cloud. The phone system changed. The controller retired, and her cell number is still the second line on the page.
The test: open the document and check the first ten names and numbers against your current payroll, then check the system list against what you actually run. A stale plan costs you twice. Somebody follows it, it fails, and only then does the improvising start — later than if there had been no document at all.
4. You know the backups are running. You can't say when one was last restored.
This is the one that surprises owners the most. A green dashboard tells you a job finished. It says nothing about whether the data inside it is complete, current, or usable.
Three ways a backup reports success and still can't save you:
The backup was configured around a folder path, and the database moved out of that path during an upgrade eighteen months ago. The job has been backing up an empty directory and reporting success every night since.
The restore works, but it works at a speed nobody has measured. A volume that takes nine hours to come back is a different business decision than one that takes forty minutes, and you should know which one you own before you need it.
Your Microsoft 365 data — email, SharePoint, OneDrive, Teams — is not backed up because everyone assumes Microsoft is doing it. Microsoft is not doing it. Retention and backup are different products, and only one of them is included.
The test: pick the one system that would stop you invoicing. Ask for a single file from last month to be restored, and time it end to end. The first restore you ever run should not be the one you're running under pressure.
5. The outage ends and nobody writes anything down
When it's over, everyone is tired and relieved and goes back to the work that stacked up while the systems were down. The lesson evaporates with the adrenaline.
That's why the same scramble repeats. Nothing was captured: what actually broke, what was tried that didn't help, what finally worked, how long each part really took, and the one change that would have cut the whole thing in half.
The test: ask for the notes from your last significant outage. If there aren't any, you'll run that same outage again from the same starting point, and it will take just as long the second time.
Where this leaves you
Scoring badly on these doesn't mean the business is badly run. It usually means the people who would have to write the plan are the same people keeping the place open.
The fix is smaller than it sounds. One printed page carrying names, phone numbers, the order things come back, and the first five steps covers most of it. One tested restore tells you whether the rest of it is real.
We've written up what belongs on that page and what each item looks like when it actually works: [link to incident response plan post].
If you'd rather not grade your own homework, book a 10-minute preparedness call. We'll run these five tests against your environment and tell you straight which ones you fail.
Found This Article Helpful?
Stay updated with our latest IT insights and solutions.