Picture a Tuesday morning in February. The power blinked at 6:40, the network never came back, and by 8:15 there are two people standing in the office who disagree about what to do first.
One of them wants the file server. That is where the job files live, and nobody can work without them.
The other wants the phones. The main line is dead, the greeting is still promising a callback, and customers have been dialing a number that rings nowhere.
They are both right. That is the problem.
The order is the plan
Most small businesses have some kind of backup by now. Far fewer have a written answer to a simpler question: what gets fixed first?
That question is not technical. It is a question about your business. What do you lose in the first hour? The first day? The second day?
For a plumbing shop, a phone that does not ring is the whole business. For a dental office, it is the schedule, because an empty chair does not get billed. For a title company, it is the closing file that has to be on the table at two o'clock whether or not the server is happy. For a contractor in February, it might be the estimating files, because the bids going out this week are the work you will do in June.
The people who write about this for a living call it a business impact analysis. NIST's contingency planning guide builds the whole recovery plan on top of that step: identify what the business actually needs, set a target recovery time for each piece, then decide what gets restored in what order. The jargon is heavy. The idea is not. Which thing do you fix first, and how long can you stand to wait?
What your customers actually touch
Most of what matters fits on a short list.
The phone. The email. The files you need to do the work. The money, meaning invoices going out and payments coming in.
Most businesses also have one system their trade runs on. Dispatch software. Practice management. A point of sale system. An estimating program. You know which one yours is, because when it stops, people stand around in the hallway.
Rank those by what hurts first in your business. Not by what is easiest to fix. Not by what your IT person finds most interesting. By what keeps money moving.
For a lot of small shops the list starts with the phone and the email, and the file server comes third. That surprises people. It also makes sense once you say it out loud. Customers do not know your server exists. They know whether you answered.
Test the Tuesday, not the file
A backup test usually proves one thing. A file came back.
That is worth knowing. It is not the same as knowing you could run the business on Wednesday morning. Can you open the accounting file? Does the label printer work on the loaner machine? Does the phone system know to forward calls to a cell? Can you send an invoice, or only read one?
CISA's guidance for small businesses is direct about this. Scheduled recovery tests should verify the backup and also refine your recovery time and recovery point targets, which in plain terms means how long you were closed and how much work you lost. Those are the numbers that matter. If a test tells you the shop would be dark for two days, you have learned something a backup report will never tell you.
There is a cheap version of the test. Pick a quiet Thursday, restore one real folder to a spare machine, time it, then do one real job from that machine only. Whatever breaks will probably be a printer driver or a shared login. Better to find that on a Thursday than in the middle of a flood.
The hours before anything is restored
There is a stretch of time between "something is wrong" and "we are back up." The plan should cover it. Most do not.
Who calls the internet provider, and with what account number. Who calls the bank if payments look wrong. Who tells staff to come in or stay home. Which forms can be filled out on paper and keyed in later. Where the spare card reader is, and whose phone can run it as a hotspot. Where the printed customer list lives, because the customer list is on the system that is down.
None of that is IT. All of it is the difference between a bad morning and a bad month.
Why it is worth an afternoon
The research on small business recovery is not encouraging. FEMA figures cited in a peer-reviewed study of businesses after Hurricane Harvey put the share of small businesses that never reopen after a natural disaster at 40 to 60 percent.
A failed server is not a hurricane. The mechanism is similar, though. The business stops earning for long enough that it cannot catch up, and the owner runs out of patience and cash at the same time.
You cannot plan your way out of every bad day. You can decide, on a normal afternoon, what you would fix first. That takes one conversation. Making the same decision at 8:15 on a bad Tuesday, with two people arguing in a hallway, is a worse way to do it.
Call us at (906) 662-4481, or contact us for a free assessment.