Decide what can continue when the internet or a core cloud service is unavailable

Business risk and continuity: prepare, keep working and recoverFor business ownersDecision guide

When an online service is unavailable, use only an approved, dated reference for work that can continue without live confirmation. Record changes in one temporary log and pause tasks whose instructions cannot be verified. After service returns, reconcile the log against the restored system before treating appointments or work orders as current.

When an online service is unavailable, use only an approved, dated reference for work that can continue without live confirmation. Record changes in one temporary log and pause tasks whose instructions cannot be verified. After service returns, reconcile the log against the restored system before treating appointments or work orders as current.

Decide which information must be current

This guide covers non-payment operational information. Use it to prepare a service business whose appointments, instructions or work orders normally live online. Payment acceptance and duplicate card processing need a separate payment-outage procedure.

Before an incident, choose the smallest approved offline reference that would help the team. Date it, decide who can access it and set a refresh routine that fits the work. Avoid copying entire customer databases onto personal devices just because a smaller working list is inconvenient.

Service dependencies during a fictional cloud outage. Fictional example.
WorkApproved fallbackDecision ownerAfter restoration
AppointmentsDated schedule plus one controlled change logBooking coordinator confirms any new promiseCompare every changed appointment and notify affected customers
Work ordersPreviously approved scope and current job statusSupervisor pauses unclear revisionsMatch completed work and outstanding changes to the live order
Operating instructionsApproved current instruction in the agreed locationProcess owner pauses tasks with an unverified versionCheck the instruction version before releasing paused work
Read the example as a list
  • Work: Appointments. Approved fallback: Dated schedule plus one controlled change log. Decision owner: Booking coordinator confirms any new promise. After restoration: Compare every changed appointment and notify affected customers
  • Work: Work orders. Approved fallback: Previously approved scope and current job status. Decision owner: Supervisor pauses unclear revisions. After restoration: Match completed work and outstanding changes to the live order
  • Work: Operating instructions. Approved fallback: Approved current instruction in the agreed location. Decision owner: Process owner pauses tasks with an unverified version. After restoration: Check the instruction version before releasing paused work

Original ASBG example, checked 27 September 2026. Adapt the decisions to your business; this is not a certified safety plan.

Keep one temporary change record

Record the time, job reference, confirmed instruction, change made and person responsible. If several people maintain separate lists, appoint one coordinator to consolidate them before anyone makes a new promise. Do not treat an old schedule as evidence that a time slot is still available.

In a fictional maintenance office, the 08:00 approved schedule is available but the cloud service fails at 08:20. The coordinator can contact the scheduled customers. A customer requesting a different time goes into the temporary log until the coordinator confirms capacity. The original appointment is not silently overwritten on several pieces of paper.

Business Queensland: business continuity planning suggests rehearsing an IT outage and checking whether staff can reach the plan. The version-control exercise here is an original way to test that dependency.

Check whether this is an outage or a security incident

Use the provider's established status and support channels. If there is reason to suspect compromised information or accounts, follow the incident process and ask the technical provider what information is safe to use. Do not move suspect files into an unapproved new service.

ASD: Business Continuity in a Box provides an interim communications and applications framework for cyber incidents. It is aimed at organisations with appropriate technical support and does not replace a full continuity plan. This article does not instruct you to deploy that framework during an ordinary internet outage.

Reconcile before returning to normal

The coordinator compares the temporary log with the restored records, resolves conflicting changes and confirms the final instructions with the affected people. Record who completed that check. Retire duplicate working copies under your existing record-handling arrangements after the approved record has been updated.

Test this with fictional jobs while the service works. Put the approved fallback location and its owner in your one-page plan, and connect it to your existing privacy arrangements.

Decide what can continue when the internet or a core cloud service is unavailable: response card

Copy the template, save a text file for offline use, or print this page with its examples and sources. Fill in your own copy and check it before relying on it.

Decide what can continue when the internet or a core cloud service is unavailable
ASBG source check: 27 September 2026
Guide: https://australiansmallbusiness.com.au/legal/internet-outage-business-fallback
Planning example. Follow your assessed emergency procedures and current official directions.

When an online service is unavailable, use only an approved, dated reference for work that can continue without live confirmation. Record changes in one temporary log and pause tasks whose instructions cannot be verified. After service returns, reconcile the log against the restored system before treating appointments or work orders as current.

Business: [name]
Plan owner: [name and contact]
Backup: [name and contact]
Local emergency/technical advice: [verified contact]
Last local test: [date]
Next review: [date]

Confirm affected service and incident reference: [details].
Approved offline reference: [location, version, time].
Appointments: verify current status before making a new promise.
Work orders: proceed only within confirmed scope.
Instructions: pause if the approved version is unavailable.
Temporary change log: [one owner and location].
Restore: compare each change, resolve conflicts, notify affected people, retire duplicate copies.

Sources checked 27 September 2026:
Business Queensland: business continuity planning: https://www.business.qld.gov.au/running-business/risk/continuity-plan
ASD: Business Continuity in a Box: https://www.cyber.gov.au/business-government/small-business-cyber-security/small-business-hub/business-continuity-in-a-box

Check current warnings separately. Store completed cards securely and replace outdated copies.

Did this guide help you finish your task?

Optional feedback helps us see which guides need more work.

Feedback is off while site analytics is unavailable or disabled.

We report your choice and this guide’s page through site analytics. Your analytics preference applies. About feedback and privacy.

General information only. This guide doesn't take your personal or business circumstances into account and isn't financial, legal or tax advice. Rates and thresholds change — check the official sources linked in this guide and get qualified advice where your circumstances require it.