Week 8 · Friday
Practicing recovery
Run a short outage discussion, identify assumptions and missing steps, assign improvements, and arrange controlled tests of your business recovery plan.
Your outage plan says, “The office manager will contact customers.”
Where is the customer list? Can the manager reach it without the office computer? What happens if the manager is unavailable?
A short practice session can reveal those questions before an actual interruption. You can begin around a table with a written scenario and the plan you already have.
This week, we prepared for storm-related closures and considered power, internet, and payment-system outages. Today, connect those preparations to the decisions your team would make.
Start with a tabletop exercise
A tabletop exercise is a guided discussion about a hypothetical incident. People talk through what they would do, using their actual responsibilities and plans.
FEMA describes tabletop exercises as a way to examine a simulated emergency, identify strengths and weaknesses, and consider improvements to procedures. They can start with one scenario and introduce additional problems as the discussion progresses. FEMA: Exercise descriptions.
For a small business, the first version can be a thirty-minute conversation with the owner, someone who handles daily operations, and the person responsible for technology. If you work alone, write out your decisions and bring the unresolved technical questions to your provider.
A tabletop does not require switching off the internet, restoring a live database, or sending customers an emergency message. It helps you find decisions and dependencies that need attention.
Pick one task and define success
Choose a task narrow enough to examine properly: rescheduling today's appointments, accepting a new job request, or telling customers about a closure.
Write one practical objective. For example:
By the end of the discussion, we will identify who can notify today's appointment customers, how they would obtain the necessary information if the office were inaccessible, and what remains unverified.
This objective measures the discussion. It does not claim you can complete a real recovery within thirty minutes.
Bring the relevant contact list, account ownership notes, recovery card, and provider instructions. Use fictional customer details. Tell everyone that the session is an exercise, and keep any sample message clearly marked as a draft.
Try this thirty-minute scenario
The following scenario is illustrative. It is not a report of an actual local outage.
A storm has passed. Your team is safe, but the office is not accessible and its power and internet status are unknown. Several customers have appointments today. The usual office manager is unavailable. You need to decide what work can continue from another safe location.
Minutes 0 to 5: agree on responsibilities. Who can decide to keep the office closed? Who is the backup decision maker? Who will check staff availability and prepare a customer update?
Do not assume that everyone can work remotely immediately after a storm. Family needs, location safety, and access to basic services affect the plan.
Minutes 5 to 15: walk through the customer task. Where are the appointments? Who is authorized to view them? What device and sign-in method will they use? Can they use the approved communication channel away from the office?
Ask someone to point to the relevant instruction or record. “I think the owner has it” is an unresolved dependency, not a completed step.
Minutes 15 to 20: add a complication. The alternate location has power, but its internet is unavailable. Does your planned fallback support this exact task? If it does not, what limited update can you provide, through which available channel, and who decides when to try again?
Minutes 20 to 25: discuss returning to normal. The office becomes accessible after the appropriate safety checks. Who confirms the booking system is usable? How will appointment changes made elsewhere be reconciled? How will staff know which record is now authoritative?
Minutes 25 to 30: choose the follow-up actions. Capture the most useful findings and assign people to resolve them. A small number of clear actions is easier to finish than a long list of general intentions.
Record evidence, assumptions, and gaps separately
Use three simple labels during the discussion:
| Label | Meaning | Illustrative entry |
|---|---|---|
| Verified | You have relevant evidence for this limited point. | The backup manager signed in from the approved laptop during a separate test last week. |
| Assumed | The team expects it to work but has not checked. | The alternate connection should support the booking application. |
| Missing | There is no agreed arrangement or answer. | Nobody is assigned to reconcile appointment changes afterward. |
A previous successful login does not prove that tomorrow's connection or entire recovery process will work. Record the date and scope of the evidence.
If a step depends on a provider, write a specific question. “Can an authorized backup administrator restore access if the primary sign-in phone is unavailable?” is easier to answer than “Are we disaster ready?”
Turn findings into changes
An after-action review is a brief look at what worked, what was unclear, and what needs to change. An improvement plan assigns the follow-up work.
The EPA's exercise guidance, written for water utilities, uses this approach: collect the findings, agree on improvements, assign responsible people, and propose a timeline. The same organizing method is useful for this smaller discussion. EPA: After-action report and improvement plan.
Your action list can stay simple:
| Finding | Action | Owner | Due date | How we will check |
|---|---|---|---|---|
| Only one person can update the phone greeting. | Arrange appropriate backup access with the provider. | Named manager. | Choose a date. | Authorized backup person completes a controlled test. |
| Alternate connection is untested. | Schedule a sample booking-workflow check. | Named support contact. | Choose a date. | Record access, result, and limitations. |
| Temporary appointment changes have no owner. | Assign reconciliation responsibility and write the steps. | Named office lead. | Choose a date. | Walk through a fictional example. |
Keep the plan current when people, applications, providers, or locations change. Repeat a short discussion after meaningful changes and after the most important fixes.
Arrange a separate, controlled technical test
Talking about a backup connection is different from using it. Talking about restoring files is different from recovering a usable sample.
Choose a separate test with the responsible person. Agree on the scope, permission, sample data, expected result, and when to stop. Explain how normal operations will be protected and how the system will return to its original state.
For example, an authorized employee might use an approved device and alternate connection to open a non-sensitive sample record. A backup test might restore a sample into a separate location, as described in Week 7's restore exercise.
Record what was actually tested, the result, elapsed time, and remaining limitations. A successful sample test is useful evidence for that sample and setup. It does not certify every application or guarantee performance during a regional outage.
Your takeaway: Practice the decisions, name the gaps, assign the fixes, and verify important assumptions through controlled tests.
Test your knowledge
Ready to put this week's learning into practice? Visit the EdwardsCG Week 8 Knowledge Check.
Choose the eight-question check on storm readiness, outage fallbacks, and recovery practice, or the 24-question cumulative review covering one question from each article in Weeks 1 through 8. Each answer includes an explanation and related reading.
The check becomes available after Friday at 1 p.m. Eastern once all three articles are live and verified. If it is not available yet, return after publication and verification are complete.
Next week, we will look at the business information you collect, who should have access, how long to keep it, and what data location means. Follow the Small Business Learning Series.