Key takeaways
- Retention is a decision per record type: tax and employment records must be kept for the period the ATO sets, security of payment records support recovery of money, and client plans and personal information should be deleted once the job and any dispute window have passed.
- The ATO requires records that substantiate income, expenses and GST, and a builder who deletes them early loses the ability to defend an assessment or a variation claim.
- Security of payment in NSW runs on documented payment claims, schedules and notices, so those records need to survive long enough to support adjudication and recovery.
- Personal information in client files, such as contact details, identification documents and site records, carries privacy obligations that do not end at practical completion, so give the file a disposal date when you close it.
- A written retention and disposal schedule, applied consistently, is the cheapest defence: it shows a certifier, a court or a privacy complainant that you handled data deliberately rather than by accident.
Most builders think about client data as a security problem: someone gets into the system, or a laptop goes missing. That is real, but it is only half the exposure. The other half is retention. Data you are not entitled to keep, kept longer than you need it, is a liability that grows while it sits on a drive doing nothing.
Privacy obligations attach to personal information — names, addresses, phone numbers, identification documents, images of people and their property. Those obligations do not switch off at practical completion. If a complaint is made or a client asks what you hold, the question is not whether you secured the file. It is whether you should still have it at all.
This article covers the retention side: what the law expects you to keep, how long, and how to dispose of the rest without losing the records that protect your money. The companion piece on cyber security for a building business deals with locking the data down. This one deals with deciding what exists in the first place.
Two duties pulling in opposite directions
A builder runs two record regimes at once, and they are not the same regime.
The first is a keep-it duty. Tax law, employment law and security of payment law all require you to hold certain records for certain periods. The ATO’s record keeping guidance is blunt about the purpose: records must substantiate what you earned, what you spent, and how you worked out your GST. If you cannot produce them, you carry the consequence in an audit or a dispute. Security of payment works the same way. The NSW security of payment framework runs on documented payment claims, schedules and notices, and a builder with no paper trail is a builder with no leverage.
The second is a delete-it duty. Personal information that you no longer need for the purpose you collected it should not be kept indefinitely. That includes client contacts, identification documents, and images that identify a person or their property. Keeping it ‘just in case’ is not a neutral act. It expands the pool of data that can be exposed, subpoenaed or complained about.
The resolution is not to pick a side. It is to split the file. Mandatory business records go into a long-term archive. Client personal information gets a disposal date and is removed once the job and any realistic dispute window have passed.
Records you must keep versus client information you should delete
| Keep | Delete or de-identify |
|---|---|
| Tax invoices, bank statements and GST records | Superseded quote versions no longer relied on |
| Employment and subcontractor records | Personal contact details kept only for marketing |
| Payment claims, schedules and notices | Site photos showing neighbouring properties |
| Current drawings and approvals for a live job | Old drawings once the job and dispute window close |
| Insurance certificates and warranties | Client identification documents copied at signing |
What you must keep, and why the period is not arbitrary
Retention periods exist because the claims they support can be raised later. A tax assessment can be reviewed after the fact. A payment dispute can go to adjudication after the work has stopped. An employment matter can surface long after a worker has left.
You do not need to memorise every period. You do need to know which categories are governed by a rule and which are governed by your own judgement, because that determines whether deleting something is housekeeping or evidence destruction.
Governed categories include:
- Tax and financial records — income, expenses, GST calculations, bank records and the documents that support them. The period is set by the ATO and varies with your circumstances, so check the current requirement rather than relying on what you were told years ago.
- Employment and subcontractor records — wages, super, tax withheld, contracts and any records that show a worker was engaged lawfully.
- Security of payment records — payment claims, payment schedules, notices and the correspondence around them. These are the records that let you enforce a debt or defend a claim.
- Insurance and warranty records — policies, certificates, defect records and manufacturer warranties, kept for as long as a claim could be made.
Everything else in a project file is a judgement call. That is where most builders get into trouble, because the judgement is never made. The file simply never gets closed.
Client information is not the same as project records
A project file contains two kinds of things, and they behave differently.
Project records are about the building: drawings, engineering, approvals, inspection records, variations, defects. They may reference a person, but their purpose is to describe the work.
Personal information is about the client: their name, contact details, identification, financial circumstances, and often their property. It was collected to do the job. Once the job is done and the disputes have settled, the reason for holding it largely evaporates.
That distinction matters because the disposal decision is different for each. You might keep a set of as-built drawings for years to answer a defect question. You do not need the client’s driver licence copy for that period, and holding it creates risk with no offsetting benefit.
The practical move is to tag data at collection. When a client signs up, note what you are collecting and why. When the job closes, that tag tells you what can go.
Plans and drawings: the file that outlives the job
Drawings are the most commonly over-retained item on a builder’s system. They are large, they are copied between consultants, and they end up in email threads, shared drives, USB sticks and site tablets.
Three problems follow.
First, version control. If you keep every revision forever, you cannot easily prove which drawing was current at the time of construction. A dispute or a defect claim turns on that question, and a folder full of unlabelled PDFs answers it badly.
Second, scope creep. Old drawings from a completed job are sometimes reused as a starting point for a new one. That is efficient until a superseded detail or a non-compliant element carries across, and the client’s design ends up in a building it was never intended for.
Third, personal information. Drawings can show internal layouts, security features, and in some cases the names of occupants. Combined with an address, that is information worth protecting, and it should not be sitting in an archive with no owner.
A workable rule: keep the current approved set and the as-built set for the life of the retention obligation. Keep earlier revisions only where they show a change that matters, such as a variation, a defect rectification or an approval condition. Delete the rest at project close.
Site photos and the people in them
Site photos are evidence, and the article on site photo record keeping as evidence covers how to take and label them. From a privacy angle, the question is what is in the frame.
A photo of a slab or a frame is a project record. A photo that captures a neighbour’s backyard, a worker’s face, a client’s child in the yard, or the interior of an occupied home is personal information. If the photo is not needed for a claim, a defect record or an inspection, it should not be kept.
This is not about avoiding photos. It is about culling them. At project close, review the photo set, keep what supports the build record, and remove what does not.
The same logic applies to site diaries and inspection notes. They are valuable, and they should be retained for the period that supports your position. They should not carry a running commentary on a client’s personal circumstances.
A disposal routine for a closed project file
- 1Confirm the job is closedCheck that practical completion, final payment and any defects period are finished.
- 2Separate the mandatory recordsPull out tax, employment and payment records into the long-term business archive.
- 3Identify personal informationList the client names, contacts, identification and site images held in the file.
- 4Delete or de-identify the restRemove the personal information from systems, backups and shared drives.
- 5Record what you didLog the date, the categories removed, and who authorised the disposal.
Where the data actually lives
A retention policy fails if it only covers the obvious system. Client information spreads across:
- Accounting and job management software.
- Email inboxes and sent items, including attachments.
- Shared drives and cloud storage.
- Personal phones and tablets used on site.
- Paper files, site folders and the ute.
- Backup drives and archived exports.
Deleting a file from the main system while a copy sits in a backup or a personal inbox is not deletion. When you build a disposal routine, include the places people actually store things, and check that backups age out on a defined cycle.
Paper is the hardest part. A site folder that goes into a filing cabinet never comes out. If you run paper, give each project file a cover sheet with a disposal date written on it, and treat that date as a task, not a suggestion.
When a client asks what you hold
Clients increasingly ask for a copy of their file, or ask you to delete it. How you respond depends on what the record is.
You can provide records that belong to the client, such as their contract, variations, certificates and as-built drawings. You should not hand over internal costing, margin analysis, subcontractor pricing or records that belong to someone else.
On deletion requests, the same split applies. You can delete personal information that is no longer needed. You cannot delete records you are legally required to keep, such as tax and payment records, and you should say so plainly rather than promising something you cannot deliver.
Two habits make this easy. Keep a written schedule that says what you retain and for how long. And when a request arrives, check the schedule before you answer, so your response is consistent with what you have actually done.
The mistake that costs the most. Deleting a project file as a clean-up exercise before the payment and defect windows have closed. You lose the records that prove what was built, what was claimed and what was agreed, and the cost lands on you in adjudication or a defect claim with no way to reconstruct the position.
A worked example
A builder in western Sydney finishes a residential extension. Practical completion is signed off, the final payment is received, and the client moves back in. The project folder is sitting on a shared drive with the client’s signed contract, three revisions of drawings, a copy of the client’s identification, a folder of site photos, and an email thread about a variation that was agreed but never formally documented.
The builder’s office manager suggests clearing the drive because it is nearly full. That is the moment the decision gets made, and it is usually made badly.
A disciplined close-out looks like this. The tax records, invoices and payment correspondence go into the long-term business archive, because they support the income and GST position. The security of payment documents — the payment claim, the schedule, and any notices — stay with them, because they are the evidence if the final payment is disputed. The as-built drawings and the certificates stay with the project record, because a defect question can be raised later. The client’s identification copy is deleted, because there is no ongoing reason to hold it. The duplicate drawing revisions are deleted, keeping only the approved and as-built sets. Photos that show neighbouring properties or the client’s interior are culled. The variation email thread is printed or saved into the project record, because it documents a change to the contract.
Then the disposal is logged: the date, what was removed, and who approved it.
None of that is onerous. The point is that it happened deliberately, at a defined moment, by someone who knew which category each item fell into. The version of the story where the drive simply gets wiped is the one that ends in an adjudication with no documents.
Building the schedule
You do not need a complicated system. You need one page that says, for each category of record, how long you keep it and where it lives.
Start with the governed categories and get the periods right. Check the current ATO requirement for tax and employment records, and confirm the position on security of payment records against the NSW framework. Then add your own categories: current drawings, as-built drawings, defect records, warranties, client identification, site photos, site diaries.
For each one, write down the retention trigger. Some records run from the end of the financial year. Some run from practical completion. Some run from the end of a defects liability period. Being clear about the trigger is what stops the schedule from becoming a document nobody uses.
Then set a review. Once a quarter, pull the closed jobs and run the disposal routine. It takes less time than reconstructing a file under pressure.
Two related disciplines sit alongside this. Your own CPD records have their own retention expectations, covered in the article on CPD record retention for NSW builders. And the broader framework of what NSW builder CPD requires is set out in the guide to how NSW builder CPD works. If you want to build the retention and record-keeping habits into your formal training, the PointCPD course catalogue lists the options, and the PointCPD home page is the starting point for NSW builder CPD courses.
If something goes wrong
Two failure modes matter.
The first is a data breach. If client information is exposed, lost or accessed without authorisation, the response is not just internal. Report it through the ReportCyber service run by the Australian Cyber Security Centre, and assess whether the people affected need to be told. A breach of data you should have already deleted is harder to explain than a breach of data you were entitled to hold.
The second is a safety-related record gap. Some records exist because work health and safety law requires them, including records connected to silica exposure controls. Safe Work Australia sets out the WHS duties for silica, and those duties imply records you must keep. Deleting them early is not a privacy win; it is a compliance failure.
The test for any deletion is simple. Could you explain, to a certifier, a court or a client, why this record existed, why you kept it for that period, and why you removed it when you did? If the answer is yes, you have a retention practice. If the answer is that nobody thought about it, you have a risk.
Questions builders ask
How long do I have to keep client records for a completed job?
It depends on the category. Tax, employment and payment records have periods set by the ATO and by the security of payment framework, and those periods should be checked against the current requirements. Client personal information, such as contact details and identification documents, should be deleted once the job and any realistic dispute window have passed. Splitting the file into mandatory business records and client personal information is the practical way to manage both.
Can I delete a project file once the client has paid in full?
No. Payment in full does not close the risk. Defect claims, warranty obligations and payment disputes can all be raised after final payment, and the records you need to respond are the ones in the file. Keep the approved and as-built drawings, certificates, payment records and defect records for the applicable retention period, and delete only the personal information and duplicates you no longer need.
Do I need to keep copies of client identification documents?
Usually not beyond the point where they serve a purpose. Identification is collected to verify who you are contracting with, and once the contract is signed and the job is underway, the ongoing need is limited. Holding identity documents for years creates exposure with no offsetting benefit. If you must retain them for a specific legal reason, record that reason alongside the document.
What should I do if a client asks me to delete all their data?
Separate what you can delete from what you must keep. Personal information that is no longer needed can be removed. Records you are legally required to retain, such as tax and payment records, cannot be deleted on request, and you should tell the client that plainly. Check your written retention schedule before responding so your answer matches what you have actually done.
Are site photos personal information?
Some are. A photo of a slab or frame is a project record. A photo that shows a neighbour’s property, a worker’s face, or the interior of an occupied home is personal information. Review the photo set at project close, keep what supports the build record and any claim, and remove the rest.
Where should retention and disposal sit in my business?
It should sit with a named person, not with whoever notices the drive is full. Write a one-page schedule covering each record category, its retention trigger and where it lives, then run a disposal routine on closed jobs at a set interval. Log each disposal with the date, the categories removed and the person who approved it. That log is your evidence that the process is deliberate.
Sources
- Record keeping for business · Australian Taxation Office
- ReportCyber · Australian Cyber Security Centre
- WHS duties for silica · Safe Work Australia
- About Security of Payment for construction contractors · NSW Government
Published 24 July 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.
