Could your small business manage a morning without its main system?

If your booking system stopped working tomorrow morning, who would notice first? More importantly, would the team know what to do next without waiting for the owner to answer their phone?

For a small business, continuity planning can begin with that kind of ordinary question. You do not need an elaborate document to discover that a key contact list is stored in the very system you might lose access to.

This is a practical starting exercise for administrative work. It is not an emergency response plan, a cyber incident procedure or a substitute for the obligations that apply to your industry.

Start with the work that cannot wait

The Australian Government's emergency management planning guide covers preparation, response and recovery. It includes identifying critical products and services, maintaining useful contacts and planning how operations can continue. People's safety comes before keeping ordinary business activity moving.

Choose one routine process to examine first. It could be confirming appointments, receiving enquiries or tracking an order. Describe what needs to happen, rather than starting with the name of the software you use.

For example, the task may be confirming tomorrow's bookings. The software is one way to do it. Thinking about the task makes it easier to identify what information, access and authority are actually needed if the usual system is unavailable.

Do not include sensitive customer information in an open workshop document. Use fictional examples for the exercise and store any real operational records according to your organisation's requirements.

Map the dependencies in plain language

On a blank page, list the people, information and services needed for the selected task. Then ask what happens if each is missing. This is an editorial exercise you can adapt, not a prescribed government template.

A fictional office might rely on one staff member to retrieve a schedule, a cloud service to display it and an internet connection to reach that service. An outage at any one point could interrupt the same task, but the response would differ.

Keep those scenarios separate. A forgotten password, a widespread service outage and a suspected security incident should not automatically trigger the same workaround. A convenient shortcut can create another problem if it bypasses access controls or spreads confidential information.

The government's risk management guidance recommends identifying risks, considering likelihood and consequences, consulting relevant people and assigning responsibility for actions. Use that approach to prioritise the gaps you find rather than trying to fix everything at once.

Write down who decides

A continuity note is much more useful when it identifies the responsible role. Someone needs authority to decide whether a temporary process is appropriate, what can wait and when specialist help is needed.

Ask who covers that role when the usual person is away. Record how to contact the appropriate support provider through a verified channel. Keep the record in an approved place that remains accessible in the scenario you are planning for.

This does not require sharing every password. The aim is to know how authorised access works, not to defeat it. For systems holding sensitive information, involve the person responsible for security and privacy before deciding on an alternative process.

Try a discussion, not a live shutdown

Gather the people who use the process and work through a fictional interruption. Do not switch off a live service or change production settings merely to test an idea.

You could ask: it is opening time, the booking service is unavailable, and the support provider has acknowledged the issue but given no recovery time. What do we know, who checks the situation, and what do we tell customers?

Listen for assumptions. One person may expect a colleague to have a copy of the schedule. That colleague may assume the owner keeps it. The exercise has found a useful gap even if nobody has written a long report.

Record uncertain answers as actions, each with a responsible person and a review date. Avoid marking an issue resolved just because a possible solution was mentioned in the meeting.

Prepare an honest customer update

Draft a short message for a routine disruption before you need it. It should explain the service affected, what customers can do and when they can expect another update. Only include a recovery time when someone has a reasonable basis for it.

For instance, a fictional business could say that online booking is temporarily unavailable and identify an approved contact channel for enquiries. It should not promise that every booking is safe or that service will return within an hour unless those statements have been checked.

Decide who approves and sends the update. Conflicting messages across email, the website and social media can make a manageable interruption harder to explain.

Check the return to normal

When a service returns, temporary records may need to be reconciled. Ask how duplicate entries, missed requests and incomplete work will be identified. Decide who confirms that the normal process is working again.

Keep a short note of what the exercise revealed and revisit it when the system or team changes. A new provider, different responsibilities or a changed service can make an old contact list misleading.

The useful result is a clear next step, not a reassuring document nobody can find. Start with one process, identify the unknowns and close the most important gap before moving to the next.

Source check: 27 September 2026. This article covers general administrative planning, not clinical procedures or professional emergency-management advice.