Construction backup and recovery means keeping separate copies of the files your jobs depend on, storing at least one copy away from the office, and testing that you can restore those files. It also means deciding how much work you can afford to lose and how long the business can be without it. For builders, a useful construction IT support plan Manny Rahat covers the office, active sites and the cloud services your team relies on.
What a builder actually needs to get back.
Start with the records that keep work moving and help you show what happened on a job:
- Contracts, tender submissions, insurance documents and certifications.
- Drawings, specifications, revisions, variations and project correspondence.
- Xero data and finance records.
- Microsoft 365 mailboxes, SharePoint files and Teams information.
- Estimating and job files, including Buildxact data.
- Site photos, diaries, delivery records, inspection results and signed forms.
Make an inventory before choosing a backup plan. List where each type of information lives, who uses it, and how the team would access it if the office or a device were unavailable.
Some of your files may already be held in cloud services. That can help if a laptop fails, but it does not automatically mean you have an independent backup. A deleted or changed file may sync across devices. And a cloud service’s own recovery features are not necessarily designed to restore your whole business to a particular point in time.
Ask what protection is included with each service, what it can restore, and who is responsible for it. Check the same for software such as Buildxact and Procore. A vendor’s platform may have its own recovery options, but you should understand what they cover and how your team would get data back.
Why “we have a backup” is not the same as “we can recover”.
A backup is a saved copy. A restore is the process of getting usable information back where your team needs it. The copy might exist but be incomplete, out of date, or difficult to access. Until you test a restore, you don’t know whether the process works for your files and systems.
For a builder, the test should go beyond seeing a green “successful” status. Restore a sample job to a separate location. Open key drawings and documents. Check that site photos and records are present. If your team uses specialist software, confirm that the restored files work in the version you run.
Ask your provider three plain questions:
- What is backed up? Include laptops, servers, Microsoft 365 and any job or estimating data that matters.
- How fast can it be restored? Ask for a realistic estimate based on a recent test, not a best-case promise.
- Who handles the restore? Confirm who makes the decisions, contacts the backup provider and keeps the team informed.
The three things that actually happen to builders.
These aren’t predictions. They’re practical scenarios to plan for.
A laptop is lost or fails. An estimator has the only current copy of a tender submission on a laptop. If the files are backed up elsewhere, the team can restore them to a replacement device. If they were only stored locally, the deadline may become the bigger problem.
Ransomware affects the file server. Ransomware is malicious software that can lock or damage files. If the backup is reachable from the same systems and accounts, it may also be exposed. A separate, protected copy gives you another recovery option. The restore should happen only after the affected systems are dealt with and the recovered data is checked. Most of these events start with a fake invoice or a stolen mailbox.
A break-in or fire affects the office. Computers, network equipment and any backup drives kept in the same room may be lost together. A copy stored away from the premises can help the business recover its files, even if the office itself is unavailable.
Recovery time and recovery point, in plain English.
Two terms help turn “we need a backup” into a practical plan.
Recovery point objective (RPO) is how much recent work you can afford to lose. If a job’s records are backed up once a day, the latest changes might not be in the backup yet. Ask whether that gap is acceptable for active jobs, especially where teams add photos, instructions or inspection records throughout the day.
Recovery time objective (RTO) is how long you can manage without a system or set of files. The office might be able to continue some work while email is unavailable. A site crew waiting for the current drawing may not.
Your answers may differ by project and by system. A completed job archive may not need the same recovery speed as files for a live project. Agree priorities with the people who run the jobs, then ask your provider to explain how the backup and restore process fits them.
What good backup looks like in practice.
A useful starting point is the 3-2-1 principle: keep three copies of important data, use at least two types of storage, and keep one copy off-site. For a builder, the main point is simple: don’t let one failed device, compromised account or damaged office take out every copy.
Keep at least one backup separate from everyday accounts and systems. An immutable copy is designed so it cannot be changed or deleted during a defined period, even if an account with broad access is compromised. Ask how that protection is enforced and who can change it.
Keep earlier versions of important files where practical. Versioning can help recover a drawing or document that was overwritten or changed by mistake. It is not a substitute for a separate backup, but it can make smaller recovery jobs easier.
Treat Microsoft 365 as something to assess, not something to assume is fully backed up. Ask what happens if a mailbox, SharePoint file or Teams item is deleted or changed, what recovery options apply to your setup, and whether a separate Microsoft 365 backup is in place. Don’t assume a specific recovery period: it can depend on the service, settings and backup arrangement.
Finally, schedule test restores. Pick a sample job and restore real files to a separate location. Record what was tested, when it happened, how long it took and what needs fixing. Repeat the test when your systems or backup arrangements change.
Questions to ask before you trust a backup.
Take these questions to your IT provider or whoever manages your systems:
- Which devices, servers, cloud services and job files are included?
- Are Microsoft 365 mailboxes and files backed up separately? What can be restored?
- Is at least one copy off-site and protected from changes or deletion?
- How often do backups run, and how will we know if one fails?
- When was the last successful test restore? What files were opened and checked?
- How long did that restore take, and what would take longer in a real incident?
- Who is authorised to start a restore, and who coordinates with the project team?
- Where are the backup copies stored, and who can access them?
- What happens if the office is unavailable and staff need to work from another location?
- When will we review the plan again?
You don’t need a complicated plan to start. You do need clear answers about what’s protected, where the copies are, and whether your team can get its working files back.
MTR IT builds and tests backup and recovery for builders across Melbourne, with remote support Australia wide. Call 03 9087 4390. If you’re weighing up what protection is worth paying for, read our free guide on what good IT support should cost.
