Imagine this: tomorrow morning your main laptop or office PC turns on, flashes, and dies.
No files. No browser logins. No accounting, quotes, photos, menus, project files.
This isn’t a theoretical “IT best practice” article. It’s a DIY fire drill you can run in about an hour to answer one brutal question:
If this computer died tomorrow, exactly what would we lose, and how quickly could we get back to work?
No new software required. No IT provider required. Just some honest checking.
Start with business impact, not tools.
Make a quick list of things that would seriously hurt if they disappeared:
Customer data (CRM, spreadsheets, emails with quotes)
Accounting / invoicing (QuickBooks, Xero, etc.)
Documents & spreadsheets (contracts, proposals, SOPs)
Photos / media (job photos, menu photos, creative assets)
Specialized apps (job management, POS, booking system)
Shared files (staff drive, “Shared With Me”, NAS share)
Email & calendar (Gmail, Outlook, etc.)
For each one, jot down:
Where do I normally access it?
(Which device / app / browser account?)Where does it actually live?
(Laptop disk, Google Drive, OneDrive, local server, POS vendor cloud, etc.)
You’ll quickly see if “everything” quietly lives on one machine.
For each item on your list, ask:
If this computer died, could I still get to this from another device?
Helpful rules of thumb:
Desktop / Documents only, no sync:
That’s local only. If the machine dies, that data is gone.You can sign into a website from another device and everything’s there:
That’s cloud-based (better, but still worth backing up).Data sits on a server / NAS in the office:
That’s centralized, but the server/NAS now needs its own backup plan.
A simple table helps:
| What | Lives where? | Safe if laptop dies? |
| -------------------- | --------------------- | -------------------- |
| Customer spreadsheet | Local “Documents” | ❌ No |
| Invoices | Cloud (Xero) | ✅ Yes |
| Job photos | External USB drive | ⚠️ One copy only |
| Staff SOPs | Google Drive shared | ✅ Yes |
| POS data | On POS + vendor cloud | ⚠️ Depends |
Anywhere you see “local only” or “one fragile copy,” highlight it. Those are the bullets aimed at you.
Now the uncomfortable part.
Backups typically fall into three buckets:
Local backups
External USB drive, NAS, Windows Backup / File History, macOS Time Machine.
Cloud file sync / versioning
OneDrive, Google Drive, Dropbox.
These are better than nothing but are primarily sync + versioning, not full backups of entire systems.
SaaS / application backups
Accounting systems, job management tools, email providers.
Some have built-in recycle bins / version history; some need third-party backup.
For each critical item from Step 1, ask:
What is backing this up, and when was the last successful backup?
Concrete checks:
On Windows PCs
Open Settings → search for “Backup” or “File History.”
Is backup turned on?
When did it last complete?
On Macs
System Settings → Time Machine.
Is it on?
When was the last backup?
External drive / NAS
Do you see multiple backup dates / versions?
Or is it just “a folder I sometimes copy things into”?
(If it’s manual and ad-hoc, that’s not a reliable backup.)
Cloud storage (Google Drive / OneDrive / Dropbox)
Files in the synced folders are mirrored, not truly backed up, but:
You do usually get Trash and Version history as a safety net.
Cloud apps (email, accounting, job system)
Is there a recycle bin / trash / undelete option?
How long do they keep deleted data (30, 60, 90 days, etc.)?
Is there a “restore account” option for deleted users?
If the honest answer is “I don’t know if this is backed up”, assume it isn’t until proven otherwise.
A backup you’ve never restored from is a theory, not protection.
Run one small, safe test:
Pick an important file
Example: a 2025 invoice spreadsheet, a key contract, a current project document.
Note something about it
E.g. “Cell B2 says 17,500” or “The last line of the document is ‘Q4 changes approved’.”
Pretend it’s gone
Don’t delete it yet—just imagine the laptop is dead and this file is gone with it.Restore it from backup
From Time Machine / Windows Backup:
Browse older backups, restore that file to a different folder.From external drive:
Find the latest copy and copy it somewhere new.From Google Drive / OneDrive:
Use Version history or Restore to get a previous copy.
Check the restored file
Does it open?
Is it reasonably up to date?
Does it match what you expected?
Also: time yourself from “I need this file back” to “I have it open again.”
That’s your real-world restore time for a single file. Restoring a whole machine will take longer—but now you’ve at least tested the path.
After that test, answer these in plain language:
If this computer died at 4pm tomorrow, how much data would we lose?
Roughly: “We’d lose up to X hours / days of work on documents/email/projects.”
How long until we’re working normally again?
“Core operations in X hours / days, full recovery in Y.”
Who knows how to do the restore besides me?
“Only I know” = a single point of failure.
At least one other person should know where backups are and how to restore the essentials.
Write these answers down. That’s your backup reality, no jargon required.
Some predictable failure patterns show up again and again.
If any of these are true, put them on your “fix next” list:
Red flag #1 – “Everything is basically on my laptop.”
Move active work into a managed cloud storage (e.g. Google Drive / OneDrive).
Turn on OS-level backups (Time Machine / Windows Backup) for the laptop itself.
Red flag #2 – External backup drive is always plugged in next to the computer.
That drive dies with the PC (power surge, theft, fire).
Use it, but disconnect it after backups; keep at least one copy off-site or in the cloud.
Red flag #3 – Last backup is older than 30 days (or “no idea”).
Set backups to run automatically, not “when I remember.”
Daily is ideal; weekly is the bare minimum for many small businesses.
Red flag #4 – Only one person understands the backup.
Document the steps to restore a file and store them in a shared location.
Walk at least one other trusted person through a test restore.
Red flag #5 – Cloud systems with no backup plan at all.
At minimum, know:
How to recover deleted items.
How long deleted data is retained.
Whether a third-party backup is needed for long-term safety.
To make this stick, turn what you’ve just learned into a simple one-pager.
You can use this template: » DOWNLOAD
Backup Snapshot – as of [DATE]
Critical data:
Customer records: [where stored] – backed up by [what] – last test restore: [date]
Accounting: [tool] – backup/restore info: [summary]
Documents & spreadsheets: [where stored] – backed up by [what]
Photos / media: [where stored] – backed up by [what]
Other key systems: [list]
If the main computer dies:
Estimated data loss: [X hours/days]
Time to get core operations running again: [X hours/days]
People who can perform a restore: [names]
Next 3 improvements:
[e.g. Turn on Time Machine / Windows Backup on main machines]
[e.g. Move key docs into Google Drive/OneDrive instead of Desktop]
[e.g. Document restore steps and test quarterly]
Review and update that page once or twice a year.
It’s boring—right up until the day it saves you.
You don’t need to redesign your entire IT setup today.
If you run this one backup & restore test, write down what you found, and fix just one red flag, you’ll already be miles ahead of most businesses.If you run this fire drill and discover something ugly, hit reply and tell me (no details needed) what surprised you most. I read every response.
And just below that is a perfect place to add a:
No posts
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.