Hurricane Season Is Over. Now Test Whether Your Business Could Have Run Without the Office
Every June, South Florida businesses review their hurricane plans. Every November, most of them stop thinking about it. That's backwards. The weeks after the season, when nothing is threatening and nobody is rushing, are the best time to find out whether your business could actually operate if the office were closed, dark, or unreachable for a week.
The official Atlantic season closes November 30. Use the time between now and then to run a real test, not a mental one.
The Tension: "We're in the Cloud" Isn't a Test
Moving email, files, and accounting to cloud services removed a lot of risk. It also created a comfortable assumption: if the data lives online, the business can run from anywhere. Sometimes that's true. Often there are gaps nobody has found yet:
- The only person who can approve a new login is the person whose phone is dead.
- The point-of-sale or phone system depends on equipment sitting in the office.
- Backups run every night, but nobody has ever tried to restore a file from them.
- The domain registrar account belongs to a former employee or an old web designer.
None of these show up on a normal workday. They show up when you need them most.
Start With Two Plain-Language Questions
Continuity planners use two terms worth borrowing. You don't need the jargon, just the questions behind it:
- Recovery time objective (RTO): How long can this system be down before it seriously hurts the business? Hours? A day? A week?
- Recovery point objective (RPO): How much recent work could you afford to lose? The last hour? The last day?
Answer both for each critical system. Ready.gov's continuity planning guidance walks through identifying critical business functions and the resources they depend on, which is a useful way to decide what to test first.
The Post-Season Continuity Test
Run each check from somewhere other than the office, ideally on a weekday, with the people who would actually do the work.
1. Remote Login
Have several employees sign in to every critical system from home, on the device they'd really use. Confirm multifactor prompts reach phones that work without office Wi-Fi, and that at least two people can reset passwords and add users.
2. Team Communications
If email went down, how would you reach your team? Keep a current contact list outside your main systems, agree on a backup channel, and decide who sends updates to staff and customers.
3. Domain, DNS, and Email
Confirm who can log in to your domain registrar and DNS provider, that the account isn't tied to a former employee or vendor, and that renewal and billing details are current. If you lose control of your domain, you can lose email and your website with it.
4. Payments and Phones
Can you take a payment if the office terminal is unreachable? Can your main number be forwarded to cell phones, and does someone besides the owner know how? Test both, don't just read the settings.
5. A Sample Backup Restore
Pick a real file, a folder, and if possible a full system or database, and restore it from backup to a different location. Time it. Check that the restored copy opens and is recent enough to meet the RPO you set. A backup you've never restored is a hope, not a plan.
6. Vendor Contacts
List your internet provider, phone provider, IT support, software vendors, and payment processor, with account numbers and support lines stored somewhere reachable offline. Note which ones you'd need to call first.
7. Power and Internet Failover
Know what keeps working when power or internet fails: a battery backup for the network, a cellular hotspot, a second provider. Confirm someone knows how to switch over, and that critical people can work from a location with power.
Run a One-Hour Tabletop Exercise
Gather the key people and walk through a scenario out loud: the office is closed for five days after a storm, and staff are scattered. Go hour by hour. Who notices first? Who calls customers? How do you run payroll? Where does each person work from?
Write down every moment someone says "I'm not sure" or "only Maria knows that." Those are your real gaps. The Florida Division of Emergency Management at FloridaDisaster.org offers state preparedness resources that can help shape realistic scenarios for your area.
Turn Findings Into a 30-Day Fix List
The test only matters if it changes something. Within a week, sort every gap into a short list:
- Fix now: single points of failure in access, like one admin or a domain owned by the wrong person.
- Fix this month: failed or untested restores, missing contact lists, phone forwarding nobody knows how to use.
- Plan for next season: larger purchases like failover internet or battery backup.
Give each item an owner and a date. Then put next year's test on the calendar now, for the same weeks.
FAQ
We're a small office. Is this overkill?
No. Smaller teams often have more single points of failure, because one person knows the logins, owns the accounts, and handles the vendors. A half-day test scales down well.
Can our IT provider just handle this?
They can run the technical checks, but only your team can say which systems matter most and how long you can go without them. Do the tabletop exercise together.
Why test now instead of before next season?
Because fixes take time. Finding a gap in November leaves months to close it. Finding it in August doesn't.
Test It While It's Quiet
Being in the cloud is a strong start. Knowing it works, from home, without the office, under pressure, is the actual plan. For more practical guides on running technology in a small business, browse Learn, and catch up on recent posts in our blog.
