ADL Management Insight All articles
Operations & Growth

The Monday After the Server Room Flood: A Two-Hour Continuity Rehearsal for Small Teams

ADL Management Insight
The Monday After the Server Room Flood: A Two-Hour Continuity Rehearsal for Small Teams

Photo: Constanceofficiel, CC BY-SA 4.0, via Wikimedia Commons

Imagine the ordinary Monday morning: the kettle is on, the first calls are coming in, and the operations manager cannot get into the building. There has been a flood in the unit next door. The landlord says five working days, possibly longer. Payroll runs on Friday. Two staff have client meetings. The main server room is in the basement.

Most small teams have a continuity plan somewhere. It may have been written for a tender, an insurer or an accreditation. It probably lists emergency contacts and a few sensible actions. What it rarely does is prepare people to make decisions under pressure. A plan is not tested until the team has rehearsed the first two hours.

Why a folder is not a plan

The purpose of a tabletop exercise is not to produce another document. It is to expose assumptions. Who takes charge if the managing director is on a train? Who has the updated staff phone list? Can the business take orders without the main system? Which customers need to hear from us before they hear from someone else?

A two-hour rehearsal is enough to surface those questions. It should be run at least once a year, and it should rotate scenarios. Loss of premises, failure of a critical supplier and a week-long systems outage cover most of the practical ground for a UK SME.

Set the room and the rules

Invite the people who would actually be in the room: the managing director, operations lead, finance lead, sales lead and whoever manages IT or the office. If IT is outsourced, invite the provider or at least have their escalation contact available. Appoint a scribe so the discussion produces a record.

Assign four roles for the exercise: incident lead, deputy, communications lead and operations lead. The incident lead makes the call; the deputy covers absence; communications handles staff, customers and suppliers; operations works out what can still be delivered. The finance lead should also be present to deal with cash, payroll and insurance notifications.

Set ground rules. Assume the event has happened. Do not solve the whole recovery in the room; focus on the first 24 hours. No blame for identifying uncomfortable facts. Decisions are logged, not debated endlessly. If someone says the IT provider will fix it, ask how long that will take and what happens in the meantime.

The scenario: Monday, 7:30am

Read the scenario aloud. For loss of premises, it might be: the building is inaccessible for five working days, the phones are diverted to a closed line, and staff are already on their way in. For supplier failure, it might be: the main component supplier has gone into administration and holds your stock. For systems outage, it might be: email, accounts and the order system are unavailable, and the provider cannot give a restoration time.

Then ask the practical questions in sequence. Who declares the incident? How do staff know whether to come in, work from home or stand down? Who tells customers? Who contacts the insurer, landlord, bank or key supplier? What work can be done manually? What must wait? Which deadlines are genuinely fixed, and which can be moved?

Test the communication tree

A communication tree is only useful if it works from a mobile phone with no access to the office network. Write down who calls whom, in what order, and through which channel. Test the first thirty minutes in the exercise. Who has the current staff contact list? Who can send a message to all customers? Who speaks to the media if a reporter calls? Who informs the insurer and records the notification?

The exercise usually reveals that the contact list is out of date, that one person holds the only copy, or that the main channel depends on the system that has failed. Fix those issues while they are still theoretical. Keep a printed copy of critical contacts and make sure a second person can access the customer list.

Manual workarounds and the no-systems hour

For a systems outage, the team should identify the minimum manual process. Can orders be taken on a template and keyed in later? Can invoices be raised from a printed ledger? Can deliveries be scheduled from a paper list? Can staff approve spend without the finance system? Can the business access cloud services from a personal device without compromising security?

For premises loss, the questions are different. Is there an alternative workspace? Can the team work from home, and does that create data protection or insurance issues? Where are the paper records? Can stock be accessed? For supplier failure, the question is whether a second source exists and how quickly it could be activated.

The aim is not to design a perfect workaround. It is to find the one or two actions that would keep the most important work moving for a day or two.

Run the clock and debrief

Give the first hour to the scenario and the communication tree. Give the second hour to operational triage, decisions and debrief. At the end, ask three questions: what would we do first, what would we stop doing, and what would we need to buy or arrange before the next drill?

Convert the answers into a prioritised action list. Separate actions into those to complete within seven days, thirty days and ninety days. Examples might include updating the contact list, nominating a deputy incident lead, arranging an alternative workspace, identifying a second supplier, testing a backup restore, confirming insurance notification details or training a second person on payroll.

The output is not a new plan. It is a short, owned action list that makes the existing plan credible. Schedule the next rehearsal before the room empties. The test of continuity planning is not whether the document looks complete. It is whether the team can make sound decisions when the ordinary Monday morning has gone wrong.

All Articles

Related Articles

The Unwritten Proposal: A Bid-Selection Discipline for UK SME Leaders

The Unwritten Proposal: A Bid-Selection Discipline for UK SME Leaders

The Tools Nobody Filed: Auditing Unapproved AI Use in Your Business

The Tools Nobody Filed: Auditing Unapproved AI Use in Your Business

The Question Queue: Measuring and Reducing Interruption Load in UK SMEs

The Question Queue: Measuring and Reducing Interruption Load in UK SMEs