Key takeaways
- A job file is the record that protects the builder in a dispute, so the backup should be planned around what cannot be rebuilt, not around what is convenient to store.
- Backup frequency should follow how quickly the work changes, which means active jobs need a routine that matches the daily pace of the site rather than a once-off copy at handover.
- A backup kept in the same synced folder as the working files is not a backup, because damage or deletion will reach every copy within minutes.
- Drawings and variations need their own version control, with revision letters, dated issues and superseded sets kept rather than deleted, so the builder can prove which document governed the work.
- A backup is only worth what it restores, so the routine should include a periodic test restore that is written down on the job file, not left as an assumption.
A small builder’s job file is more valuable than most of the equipment on the ute. It holds the signed contract, the variations and the instruction emails, the drawings with their revisions, the photographs that show the work before it was covered, the daily diary, the council approvals and the certificates that will be needed when the owner sells the house. When a laptop fails or a phone is lost, the loss is rarely a file. It is the record that stood between the builder and a dispute.
This article sets out a recovery routine for a small building business. It covers what to back up, how often, where the copies should sit, how to keep drawings under control and how to prove that a restore actually works. It is deliberately separate from the wider cyber security questions, such as protecting accounts from criminals and spotting fraudulent emails. Those matter, and a backup does not solve them, but a builder who has a sound recovery routine is better placed when something does go wrong.
The organising idea is that a backup is a recovery plan, not a storage habit. The question to ask is not how much space the copies take, but how long the job could be stopped if the working files disappeared tomorrow, and which of those records could never be rebuilt.
Decide what cannot be rebuilt
Start with the irreplaceable records. A signed contract can be reissued in some form, but the signed version is the one that matters. Photographs taken before the slab was poured, the frame was covered or the wall was lined are unique. So are the diary entries written on the day, the instruction emails that approved a variation and the hold point records that show an inspection took place. These are the records that protect the builder, and they cannot be recreated after the event.
Next, separate those from the records that can be rebuilt with some effort. A material schedule can be recalculated, a payment ledger can be reconstructed from the bank statements, and a supplier invoice can usually be requested again. Rebuilding is slow and irritating, but it is possible. The backup routine should give the unique records the most protection and the most frequent copies, while the rebuildable records can sit on a simpler arrangement.
The test is consequence, not size. A small file of signed variations may matter more to the business than a large folder of marketing images. Decide the priority list once, write it down, and review it when the business takes on a new type of work, such as a commercial fit-out or an owner-builder project with a different set of records.
Matching the frequency to the pace of the job
How often the backup runs should follow how quickly the work changes. A job in active construction generates new records every day: diaries, photographs, instructions, deliveries and inspections. A backup that runs once at handover is useless for the period when most of the risk exists, which is the middle of the build. For active jobs, the backup should run daily, and the people on the job should know that the routine exists.
Archived jobs change far less, and they can be backed up less often without loss of protection. A completed job that is still within the period the builder must keep records for needs its copy refreshed when a document is added, not every day. The point is that the frequency is a decision, made for each stage of the job, rather than an accident of whichever sync setting the laptop happened to have.
Automatic backup tools help, but they can also fail silently. Check the backup log after a change in the system, after an update and at the start of each new job. A routine that depends on someone remembering to press a button will eventually fail on the job that mattered most. Records captured on a phone with no signal need the same routine, and the article on working offline on building sites covers how to keep them safe until they sync.
Where the copies should sit
A backup is worth what its location allows it to survive. A copy on the same laptop as the working files is not a backup against theft, fire or a failed drive. A copy in a synced folder is not a backup against deletion, because the deletion will sync to the copy within minutes. The aim is to keep at least one copy that the everyday working environment cannot reach or overwrite.
In practice, that means more than one copy, kept in more than one place, with at least one copy offline or held in a separate account that the working files do not sync to. An external drive that is disconnected after the backup finishes is one example. A cloud backup in an account that uses separate sign-in details is another. The arrangement does not have to be complicated, but it has to be deliberate, and someone has to be able to say where each copy is without looking.
Keep the sign-in details for the backup accounts separate from the everyday accounts, and make sure more than one person in the business can reach them. A backup that only one person can access is a single point of failure, and the day that person is unavailable is often the day the files are needed.
Version control for drawings and variations
Recovery is one problem. Knowing which document governed the work is another, and it is where many builders lose more money than they lose to a dead laptop. Drawings change during a job, and the version on site is not always the version in the office. A builder who builds from an out-of-date set has a problem that no backup will fix, because the backup simply preserves the confusion.
Give each drawing a revision letter and a date, and use the same naming convention on every job. When a drawing is superseded, move it to an archive folder rather than deleting it. The archive is the record of what was issued and when, and it is what a builder needs to show the certifier, the engineer or the owner which set was approved. Where a change is made on site, write it up as a variation, issue the revised drawing and record the date it reached the crew.
Variations need the same discipline. A variation approved by email should be saved to the job file with the email, not left in the inbox. A verbal approval should be confirmed in writing the same day, and the confirmation saved with the drawings it relates to. The backup protects the file, but the version control makes the file meaningful.
Name the people who can approve a revision on site. A supervisor who marks up a drawing by hand should send the mark-up back to the office the same day, and the office should issue the revised set with a new letter. Without that loop, the crew works from a marked-up print that nobody else can see, and the job file tells a different story from the one on site. Keep the marked-up prints with the job as well, because they show what was asked for and when.
Keeping recovery separate from security
A backup protects against loss. It does not protect against every threat. If an attacker changes the files on the working computer and the sync copies the changes everywhere, the backups may hold the damage too. The Australian Signals Directorate’s small business guidance covers the basic account and device protections that reduce that risk, and those should be in place alongside the backup.
Fraud is a different risk, and a backup does not stop it. A fraudulent email asking the builder to change a supplier’s bank details can arrive in a perfectly protected inbox, and the backup will faithfully keep the record of the payment that followed. The control for that is a process: verify any change to bank details by a separate channel before the payment is made. The Australian Cyber Security Centre’s guidance on business email compromise describes the pattern in general terms, and it is worth reading with the people who approve payments.
Keep the recovery routine and the security routine in the same schedule so that they are reviewed together. A backup that has not been tested and an account that has not been reviewed are both gaps that only show up when something has already gone wrong.
Privacy and access to client records
A job file holds personal information about clients: names, addresses, phone numbers, email addresses and sometimes identity documents. How that information is stored, backed up and shared is a privacy question as well as a recovery question. Whether the Privacy Act applies to a particular business depends on its size and activities, and the Office of the Australian Information Commissioner’s guidance for small business sets out how to work that out. Even where the Act does not apply, the client expects their information to be handled with care.
Limit access to the job files to the people who need them. A subcontractor who needs the drawings does not need the client’s identity documents, and a bookkeeper who needs the invoices does not need the photographs of the interior. When a person leaves the business, remove their access to the working files and the backup accounts the same day. Old access is one of the most common ways client information leaks from a small business.
Store the job files on the business’s own accounts rather than on personal ones wherever possible. When the business changes hands or a person leaves, the records should stay with the business, and the people who need them should not have to ask the departing worker for their copies.
Worked example: a small builder in the Illawarra
A small builder in the Illawarra runs several jobs at once with two employees and a bookkeeper. The records are kept on the owner’s laptop, with photographs on the owner’s phone and drawings shared by email with the subcontractors. There is no backup beyond the laptop’s own sync, and the drawings have no revision system beyond the file names.
One morning the laptop will not start. The owner has a sync copy in a cloud folder, but the folder had been partly deleted the week before during a tidy-up, and the deletion had synced. The most recent complete copy of the variations predates the framing stage. The photographs from the framing stage are on the phone, but several of them are missing, and the diary for the same period was written in a notebook that was left on a job site.
The owner spends the following days reconstructing the records from emails, the bookkeeper’s invoices and a set of photographs the subcontractors had saved on their own phones. The rebuilt file is incomplete, and one variation cannot be proven without the email that approved it. The client is not pleased, and the owner pays for the time spent on the rebuild.
The routine that would have prevented most of the damage is simple. A daily backup to a separate account, a monthly test restore, a revision letter on every drawing and a rule that variations are saved to the file the same day. None of that is expensive, and all of it would have turned a lost few days into a lost morning.
Testing that the backup actually restores
A backup that has never been restored is a hope, not a recovery plan. Set a regular cycle for a test restore of a sample job to a separate location, and check that the key documents open, that the photographs are present and that the variations and hold point records are complete. Record the test on the job file or in the business’s own log, with the date and the name of the person who carried it out.
Recovering a job file on the day it is lost
- 1Stop and isolateStop the affected computer or device from syncing so that any damage or deletion does not spread to the other copies.
- 2Identify the last good copyFind the most recent backup that predates the loss, and check its date before restoring anything.
- 3Restore to a separate locationRestore to a new folder rather than over the working files, so the damaged state is kept for review.
- 4Check the restored jobOpen the key documents, check the photographs and confirm the latest variations and hold point records are present.
- 5Record what was lostNote in the job file what was lost, what was restored and what has to be recreated, with the date.
The test also shows whether the people in the business know how to restore. A routine that only one person can run will fail when that person is on leave. Show the steps to a second person, and let them carry out a test themselves.
Lead in. The mistake that costs the most is a backup kept in the same synced folder as the working files, because damage or deletion reaches every copy within minutes. A backup that nobody has ever restored is a hope, and the builder will only learn it is empty on the day the files are needed.
Your own licence records are part of the same discipline. The rules for keeping CPD evidence are set out by the NSW Government, and the guide to how NSW builder CPD works explains what a licence holder needs to keep and for how long. Put those records in the job file system too, with the same backup and access rules, rather than in a shoebox.
The minimum routine for a small builder
- Every active job has a named folder structure that holds contracts, variations, drawings, photographs, diaries and certificates.
- Working files sync to a copy that is not the only copy, and at least one backup is kept offline or in a separate account.
- Drawings carry revision letters and dates, and superseded sets are archived rather than deleted.
- Access to the job files is limited to the people who need it, and removed when a person leaves the business.
- A test restore of a sample job is carried out and recorded on a regular cycle.
- Client personal information is stored and shared only as far as the job requires.
The wider question of which tools a small builder should use to keep records is covered in the construction technology roadmap for small builders, and the article on digital measuring tools that log results shows how the site data flows into the job file. A good routine depends on choosing tools that you can back up and restore, rather than tools that trap the records inside a single device.
Questions builders ask
What should a small builder back up?
Back up the records that cannot be rebuilt first, which means the signed contract, the variations and their approving emails, the dated photographs, the diaries and the hold point records. Rebuildable records such as ledgers and supplier invoices can sit on a simpler arrangement.
Is a cloud sync folder a backup?
Not on its own. A sync folder mirrors deletions and damage, so a file deleted or corrupted on one device will be removed from every copy. A backup needs at least one copy that the everyday sync cannot reach or overwrite.
How often should job files be backed up?
Active jobs need a daily backup because the records change every working day. Completed jobs can be refreshed when a document is added, and the frequency should be a deliberate decision for each stage of the job.
How do I keep track of drawing revisions?
Give every drawing a revision letter and a date, use the same naming convention on every job, and archive superseded sets rather than deleting them. Check the site set against the office set before any work is covered.
Does a backup protect against fraudulent payment emails?
No. A backup keeps a record of the payment, but it does not stop it. Verify any change to supplier bank details through a separate channel before paying.
How do I test a backup?
Restore a sample job to a separate location on a regular cycle, check that the key documents, photographs and records are complete, and write the result on the job file with the date and the name of the person who carried it out.
Sources
- Small business cyber security · Australian Signals Directorate
- Privacy for small business · Office of the Australian Information Commissioner
- Business email compromise · Australian Signals Directorate’s Australian Cyber Security Centre
Published 8 October 2026. General information for builders, not legal, financial or engineering advice for a specific job. Check current requirements with the relevant regulator or standard before relying on them.
