Business continuity

A business continuity plan people can use under pressure

A continuity plan is useful when it helps people make decisions during a difficult day. If it takes an hour to find the right page, it is too complicated.

Start with critical services

List the services the organization must continue or restore. Describe them in business terms: receive customer orders, pay staff, provide clinical access, answer support calls, or operate a production line.

For each service, record how long it can be unavailable, the minimum acceptable level of operation, key people, systems, data, premises, equipment, and suppliers.

Set recovery priorities

Not everything can be restored at once. Agree the order before an incident. Priorities should reflect safety, legal duties, customer impact, financial loss, and dependencies between services.

Write down decision roles

Name who can declare an incident, approve emergency spending, communicate with staff and customers, contact insurers and authorities, and decide when service is safe to resume. Include deputies because the first choice may be unavailable.

Plan communications without normal systems

Keep an offline contact list and an alternative way to communicate if email, chat, or the office network is unavailable. Prepare short message templates for staff, customers, suppliers, and leadership.

Document manual workarounds

Some services can continue at a reduced level using paper forms, temporary spreadsheets, phone calls, or an alternate location. Record what is safe and practical, how information will be protected, and how temporary records will later be entered into normal systems.

Include suppliers

Record support numbers, account details, escalation routes, recovery commitments, and alternatives for important suppliers. A supplier’s recovery plan does not automatically meet your organization’s needs.

Keep a protected copy of the plan, contacts, and essential instructions outside the systems covered by the plan.

Test decisions, not only technology

Backups and failover need technical tests. The wider plan also needs exercises. Use a realistic scenario and ask the team to work through the first hour: who notices, who is called, what is stopped, what continues, and what is communicated.

Keep the plan current

Review it after significant system, supplier, staffing, or location changes. Record lessons from incidents and exercises. A short maintained plan is more valuable than a detailed document that reflects last year’s business.