A simpler way to run your business continuity program.

Start with what must keep running

List the products and services that customers rely on, then identify how long each can be unavailable before the consequences become serious. This creates a practical order for recovery rather than treating every process as equally urgent.

• Name the activity in plain business language.
• Set a realistic maximum interruption time.
• Record the people, premises, suppliers, systems and equipment it needs.

Plan around consequences, not every possible event

A small business does not need a separate plan for every storm, equipment fault or supplier failure. Plans built around the loss of power, premises, people, internet, communications or another critical resource remain useful across many different events.

Add specific plans where the response is materially different, such as a cyber incident or planned outage.

Use one manageable operating rhythm

• Monthly: update changed contacts, suppliers and critical resources.
• Quarterly: review the highest risks and incomplete actions.
• Twice a year: walk through one disruption scenario with the people involved.
• After any incident: record what worked, what failed and who owns each improvement.

Keep the plan ready for the person who needs it

A useful plan is available on a phone, gives a clear first action, identifies who can make decisions and includes working contact details. If the plan depends on the unavailable system or office, it is not ready.

gecko continuity brings the program into one workspace: critical activities, dependencies, risks, contacts, guided response plans, exercises and evidence. The aim is less administration and a plan that can actually be followed.