In short

A continuity plan does not prove its value through page count. It becomes useful when, during an incident, people know which service to protect, when to activate the plan and how to recover. Seven decisions are enough to create that foundation, provided they work together.

Those decisions sit around three strong ideas: name the service the lifebuoy must protect, connect people and trigger points around it, then test the journey from incident to normal service. The rest of the document can follow later.

A simple picture

Picture the essential service inside a lifebuoy made of seven sections. Each section protects one part of the journey: what must continue, the minimum level, the acceptable interruption, the trigger, the person who decides, their deputy and the order of recovery.

One missing section leaves an opening. A lifebuoy left hanging on the wall and never tested may fail when people need it. The plan works when all seven decisions connect and the people involved have already tried to use them.

Seven navy sections form a lifebuoy around the essential service, shown as a teal centre, and protect it from an external impact.
A lifebuoy protects people only when it is complete and they know how to use it.

Idea 1 — Name what the lifebuoy must protect

The first decision names the essential service in practical terms: collecting payments, answering urgent customer requests or shipping priority orders. The second sets the minimum level to maintain. The third states how long an interruption can be accepted.

These choices separate what is essential from what is merely convenient. An SME might decide that its full customer portal can wait for two days, but priority orders must be accepted through a simple form within four hours. That sentence guides action better than a list of twenty applications all marked “critical”.

What the lifebuoy protects is not a piece of software. It is a service delivered to a customer, colleague or partner. Tools come afterwards as ways to keep that service going.

Idea 2 — Connect the trigger, the decision and the deputy

The fourth decision defines the point that activates the plan. It might be an outage lasting more than thirty minutes, two key people being absent together or the loss of an essential supplier. The fifth names the person who activates the plan.

The sixth decision names a deputy. This sounds obvious until the main person is the one who is unavailable. The deputy needs access to the right information and permission to decide, not just a name in a document.

These three sections should connect without an improvised debate: the trigger is reached, an identifiable person activates the plan, and somebody else can take their place. For a director, this chain creates calm. For a service head, it removes the need to wait for permission while the service gets worse.

A copper signal lights up while a hand inserts the main key into a gate and an identical deputy key remains ready on its hook.
When the signal is given, everyone should know who turns the key and who takes over if the first person is unavailable.

Idea 3 — Plan the recovery, then try the lifebuoy

The seventh decision sets the order of recovery and how people will be kept informed. Not everything returns at once. A team might restore the receipt of requests first, their processing second, and convenience features later. Customers and colleagues need to know what works, what remains limited and when they will hear more.

Consider a business where the person running payroll becomes unavailable three days before payment. A simple exercise quickly exposes the real questions: can the deputy reach the files, do they know the provider’s contact and can they approve the payment? One hour of practice reveals openings that ten pages of procedure may hide.

Testing need not disrupt the company. Walk through a plausible event around a table, ask each person what they would do and check the essential access. Then strengthen the weak sections.

An emergency kit lies open in daylight with its lamp switched on, two keys and a mechanism whose route a hand is checking.
Like an emergency kit, the plan should be opened and tested before the crisis, not discovered during the failure.

A practical start for leaders and service heads

Bring together a director, the head of the chosen service and their deputy for sixty minutes. Write one sentence for each of the seven decisions. Choose a likely incident and work all the way around the lifebuoy. Any answer that depends on “usually” or “I think so” becomes something to verify within the week.

Takeaway

A good continuity plan protects a clearly named service with seven connected decisions. It sets the minimum service, makes cover possible and prepares an orderly recovery. The lifebuoy becomes reliable when people have tested it, not when the document becomes thicker.

If your essential service still depends on unspoken assumptions, we can prepare the first lifebuoy with you.