Week 4 · Friday
When your internet or cloud provider goes down
Make a practical outage plan that distinguishes a connection problem from a cloud service failure and explains how work resumes afterward.
Imagine a busy morning at a small appointment business. The booking screen stops loading, a customer is waiting, and the next employee is due to arrive.
The immediate question is what the team can do while the problem is being resolved.
A short plan helps staff respond consistently. It should explain how to check what is affected, which work can continue, who communicates updates, and how temporary records get back into the normal system.
Find out which part is unavailable
Your device, office network, internet connection, account, and cloud service all contribute to the work. A problem with any one of them can look like “the system is down.”
Start with observations:
- Is the problem affecting one device or several?
- Can the affected device reach other familiar websites?
- Does the same service work on an approved phone using cellular data?
- Is the message about an unavailable service, a sign-in problem, or something else?
A cellular connection uses the mobile carrier's network. A phone still connected to the office Wi-Fi may be using the same internet connection as the computers, so it is not an independent check.
These observations are clues, not a complete diagnosis. Record the message and the approximate time the problem began. Give those details to the person supporting the service.
Check a trusted service status page
A status page is a provider's page for reporting known service problems and updates.
For example, the Google Workspace Status Dashboard lists the status of its services and directs users to support when an issue is not shown. A clear dashboard does not prove that your account or connection is working. Google Workspace Status Dashboard.
Save your provider's official status and support links while everything is working. During a disruption, reach them through those saved links or the provider's known website.
Choose one person to follow updates. That helps avoid several employees chasing the same issue while nobody keeps track of customers waiting for an answer.
Match the fallback to the failure
A fallback is the agreed way of continuing a task when the usual method is unavailable.
If your office internet connection fails but the cloud application is working, a tested alternative connection may let you reach it. A business-approved mobile hotspot is one possible option: it shares a cellular connection with another device.
If the cloud application itself is unavailable, changing to a hotspot does not repair that service. You may need an agreed temporary work process or to pause the affected task.
| What appears to be affected | What to check | Possible next step |
|---|---|---|
| One device or account | Whether another authorized device or account works | Contact support with the exact error and continue through an approved alternative if appropriate |
| Office internet connection | Whether the service works over an independent connection | Use a tested backup connection if it supports the task |
| The cloud service | Provider status and support guidance | Use the agreed work fallback or pause the task |
| Power at the location | Which devices and connections still have power | Follow the business's power-outage plan and reassess what work can continue |
A backup connection has limits. Check coverage at your location, data allowances, power needs, and whether it works with the devices and applications involved.
For a business serving customers around Jacksonville and Swansboro, test the locations that matter to your work. A connection that works well at home may behave differently at the office or a job site.
Prepare offline work before you need it
Some applications let you work with selected information without a connection. Confirm the specific task and setup before relying on that feature.
Google's instructions for offline Docs, Sheets, and Slides, for example, require preparation while online, a supported browser, and available device storage. The relevant files must be ready for offline use. Google: Work on documents offline.
A saved copy can also become outdated. An appointment list prepared at 8 a.m. may not include a booking made at 8:15. Label reference copies with the time they were prepared, and decide what staff may do with them.
In the opening example, the fallback could allow staff to record a customer's request and contact details for follow-up. That is different from confirming a new appointment when current availability cannot be checked.
Give the plan a person and a place
Write down who can activate the fallback and who contacts the provider. Include how the team will reach each other if normal business email or calling tools are affected.
Keep the plan accessible outside the service it is intended to cover. A recovery checklist stored only in the unavailable application is difficult to use when you need it.
Choose a point to reassess the situation. For example, the owner might decide that after 30 minutes the team will review waiting requests and update affected customers. That is an illustrative decision point, not a universal recovery target.
Communicate what you know and when you will update people again. A support reply time and an estimated repair time are different things. Avoid promising a restoration time the provider has not confirmed.
Check the work when service returns
Opening the application again is only the start of returning to normal.
Identify who will enter temporary records and check them against the current system. This is reconciliation: comparing what happened during the interruption with the records in the application.
Look for requests already recorded, missing details, conflicting changes, or work that is still waiting. Confirm the result before anyone repeats an action that may already have completed.
Store temporary records appropriately while they are needed, limit them to the information required, and follow your business's retention process afterward. A temporary workaround should not become a forgotten second customer database.
Finally, note what worked and what was missing from the plan. Even a brief interruption can show that a support number is out of date or that the backup connection needs attention.
A fifteen-minute exercise for your business
Choose one important task and draft a one-page outage plan:
- The task and the service it depends on.
- The person who checks the problem and contacts support.
- The official status page and support contact.
- The tested or proposed fallback for a connection failure.
- The agreed fallback if the service itself is unavailable.
- What staff record, who updates customers, and who reconciles the records.
Walk through the plan with one employee using an imaginary interruption. Keep the live service running. If a technical fallback needs testing, arrange a controlled test with whoever manages the devices and connection.
Mark untested ideas clearly. A phone in a drawer or an offline feature nobody has tried is a proposed fallback until you verify it.
Your takeaway: Plan for the task that stops. Check what failed, use the right fallback, and confirm the records when normal service returns.
Test your knowledge
You have finished Week 4 of the Small Business Learning Series. Try the eight-question check on cloud costs, security responsibilities, and outages. Each answer includes an explanation to help you learn.
The cumulative option through Week 4 includes 12 questions, one from each article across the first four released weeks.
The check becomes available once all three of this week's articles are live and verified, no earlier than Friday at 1 p.m. Eastern.
Next week, we will look at suspicious emails, texts, invoices, and other requests so your team can recognize common scams and know what to do next.
Follow the Small Business Learning Series for new articles on Monday, Wednesday, and Friday at 1 p.m. Eastern.