Even platforms built for high resilience can experience a disruption. No cloud service is immune to every incident. If your email stopped loading tomorrow, the first question wouldn’t be how quickly it will return. It would be: what can your team still do while it’s unavailable?
A few practical preparations can help your business stay organised, keep essential information within reach and make clear decisions. They won’t make an outage painless. They can make it less chaotic.
1. Set up a way to communicate outside your main suite
If email and your usual collaboration tools are unavailable, your team needs another way to get instructions. Choose a backup channel that doesn’t depend on the same cloud suite or identity service. That might be a team chat platform, a messaging app or a phone-based contact process.
Agree in advance which channel to use, who can send an official update and where staff should look for information. Don’t wait for an outage to decide.
Keep an offline contact directory outside the cloud. It should include the people needed to coordinate an incident and be stored somewhere accessible if cloud accounts cannot be reached. Review it regularly so it doesn’t become a list of old numbers and departed staff.
Bookmark the public service status dashboard, too. Your IT lead can check it alongside the business’s own network health to help distinguish a broader service incident from a local internet connection problem.
2. Configure offline access for mail and files
Offline access is useful when it’s prepared and tested before you need it. For email, check the service’s current offline access instructions. The setup needs to be completed in a standard browser window, not private or incognito mode.
Choose a sync window that suits the work your team needs to reference. A 30- or 90-day window may be appropriate, depending on your settings and storage. Also enable offline access for essential documents, so active files that matter during an interruption are available locally.
For non-Google files, consider a desktop sync client that keeps selected folders available on the device. Decide which files are genuinely needed offline rather than syncing everything by default.
There’s an important limit: offline access does not fix a server-side outage. Nothing sends or receives while the service is unavailable, and live co-authoring pauses until the servers reconnect. Offline mode keeps previously synced reference material reachable; it isn’t a replacement service.
Use offline access only on company-managed, encrypted laptops. Don’t set it up on shared or personal machines, where cached business information may be accessible to others. Test it while services are working, and make sure staff know how to open the cached material.
3. Map the dependencies you might not notice
Email is often only one part of the problem. Make a simple map of the systems and processes that depend on your primary cloud account.
Start with single sign-on. If staff use “sign in with Google” to access your CRM, accounting, payroll or ticketing system, an identity outage could lock them out of those services as well. Keep tested break-glass administrator logins for critical systems, and make sure the right people know how to use them securely.
Then look at automated workflows. An automation tool may depend on an email trigger or a spreadsheet used as a database. If either stops working, the workflow may quietly stop routing leads, approvals or support tickets. Identify the processes that matter and decide how staff will notice a failure and handle urgent work manually.
Finally, check where your procedures live. If a standard operating procedure exists only in a cloud document and hasn’t been cached or made available another way, it may be unreachable during an outage. Keep essential instructions available offline and make it clear which copy is current.
This dependency check is also a good reason to review how your cloud tools fit together. Cloud consultancy can help businesses assess their setup, while managed IT support can help plan and maintain practical continuity measures.
4. Decide who does what before an outage
A short plan is more useful than a long document nobody can find. Name the people who will lead the response, and spell out their first actions.
The incident lead declares the outage and switches the team to the backup communication channel. The technical lead compares internal network health against the public status dashboard. The communications lead sends the first staff alert, then provides a predictable update every 30 minutes, even when there is no change.
That rhythm matters. A brief “no change” update helps staff know the response is active and gives them a reliable place to check for instructions. Agree on what each update should include: what is affected, the current workaround and when the next update will arrive.
Make sure each role has a deputy. If the person who normally leads the response is unavailable, or can’t access the main suite, the plan still needs to work.
Run a 15-minute tabletop exercise
A plan only counts if people can use it. Set aside 15 minutes with the staff responsible for key business processes. Tell them to imagine the primary email and collaboration suite is unavailable, then talk through three questions:
- Which team hits a dead end first? Identify the work that stops immediately and what information or access is missing.
- What could you actually open with Wi-Fi off? Ask staff to test whether the contact directory, essential procedures and active reference files are genuinely available offline.
- How will you catch missed enquiries after service returns? Decide who will check for enquiries, approvals and tickets that may not have been seen or routed during the disruption.
Keep the exercise focused on finding gaps, not blaming people. Write down what needs to change, assign an owner and test the fix. Then run the exercise again after significant changes to your tools or processes.
A considered continuity plan doesn’t need to be complicated. It needs to make communication possible, keep the right reference material reachable, expose hidden dependencies and give people clear roles. If you’d like help reviewing your cloud setup and planning a practical next step, book a free 15-minute consult or call 1800 312 972.
About Mathew
Mathew Hoffman started his IT career in 1981 and held senior roles at State Bank of NSW, Minet Australia, Wilhelmsen Lines and Rothmans of Pall Mall. He also highlighted IT’s role in the Sydney 2000 Olympics. Since 2001, Mathew has provided IT consultancy to small and medium businesses. He became an original Google Partner in 2008, and the business re-branded as Cloud Computer Company in 2017. Based in Noosa, Mathew enjoys cricket, which he has played and coached in Sydney and the Sunshine Coast, as well as spending time with family, the beach and golf.








