What records NSW builders must keep, and how long to hold them

Most building businesses do not lose records through carelessness. They lose them because nobody decided, at the time the record was created, how long it needed to be kept and where it needed to live. Files accumulate in email inboxes, on a supervisor’s phone, in a tradie’s ute, and in a shoebox of paper invoices. When a certifier, a regulator, or a client’s solicitor asks for something, the business discovers the record either does not exist in a usable form or cannot be found.

Retention obligations are not a single rule. They come from several directions at once: the licensing regime that governs who may contract for residential building work, the tax law that governs what you must substantiate, the contract you signed with the client, and the warranties that survive practical completion. Each of those can impose a different period, and the period that matters is the longest one that applies to that record class.

This article is about retention and audit readiness across a whole business. It is not about bookkeeping method or tax reporting. The question it answers is narrower and more practical: what do you keep, for how long, and how do you prove it when asked.

Why retention periods are longer than the job

The instinct on most sites is to treat the project file as finished when the job is handed over and the final invoice is paid. That instinct is wrong, and it is wrong for a reason that has nothing to do with sentiment. The obligations that generate the need for the record often outlive the work itself.

Statutory warranties on residential building work run for a defined period after completion, and the defects that trigger them are frequently not visible at handover. Waterproofing failures, slab movement, and roof defects can take years to present. If a claim arrives in year four and your only evidence of what was installed and how is a photograph on a phone that has since been replaced, you are defending the claim from a position of weakness.

The same logic applies to licensing. A regulator investigating a complaint about your work will want to see the contract, the plans approved for construction, the variations, the inspection records, and evidence of insurance. Whether you can produce those determines whether the complaint is resolved with a conversation or escalates.

Tax law adds a further layer. The Australian Taxation Office requires businesses to keep records that substantiate the information they report, and those records need to be retained for the period the tax law sets out. That obligation is separate from your building obligations, but it applies to overlapping documents: contracts, invoices, payment records, and bank statements. You should check the current ATO requirement for the retention period that applies to your business structure, because it is not the same for every entity type.

The record classes a NSW building business actually holds

It helps to stop thinking about records as a pile of paper and start thinking about them as classes, each with its own trigger event and its own retention period. A workable set for a residential building business looks like this.

Contract and pre-contract records. The signed contract, any pre-contract disclosure, the scope of works, the plans and specifications the contract incorporates, and the evidence that the client was given the documents they were entitled to receive. The trigger is the date the contract was signed.

Approvals and certifications. Development consent, construction certificates, BASIX certificates, and any other approval that authorised the work. These need to be retrievable for the life of the building in many cases, because a subsequent owner may need them.

Variations and instructions. Every written variation, every signed instruction, and every record of an oral direction that was later confirmed in writing. Variations are the single most common source of dispute, and a variation that was never documented is effectively a free upgrade you gave away.

Inspection and compliance records. Inspection reports, test results, certificates from trades, and evidence that critical stage inspections occurred. Where a certifier or a principal certifying authority has issued a document, that document belongs in the project file.

Insurance and licensing records. Certificates of currency for home building compensation cover and any other relevant policy, plus the licence details for the entity and for any nominated supervisor. These are current-state records: you need the version that was in force at the time of the work, not just the current one.

Financial records. Invoices, receipts, payment schedules, and bank records. These overlap with your tax obligations and should be retained to whichever period is longer.

Correspondence and site records. Site diaries, photographs, emails, and messages that record what happened on a given day. These are the records that win or lose defect disputes, and they are the ones most likely to be lost.

Pool and spa projects carry their own record set

Pool and spa work is a good illustration of why a generic retention schedule is not enough. A pool project generates compliance records that a standard residential job does not, and the obligations sit with both the builder and the owner at different stages.

Under the NSW arrangements for building a pool, there are requirements that apply to the barrier and to the approvals process, and there are separate ongoing obligations that attach to the owner once the pool is in use. If you are the builder, your file needs to show that the barrier was constructed as approved, that the required inspections occurred, and that the documentation you were responsible for providing was in fact provided.

The practical risk is that this documentation is treated as the pool supplier’s problem or the certifier’s problem. It is not. If a question arises years later about whether the barrier complied at the time of construction, the builder’s file is the first thing that will be requested. The NSW Government publishes guidance on building a pool and on owner obligations, and it is worth reading both, because the split between builder and owner responsibility is not always obvious from the contract.

Retain pool compliance records for as long as you retain the rest of the project file, and treat them as part of the project rather than a separate folder that gets lost when the job closes.

How long is long enough

There is no single number that answers this question for every record class, and any article that gives you one is oversimplifying. What you can do is apply a rule that produces the right answer regardless of which obligation is in play.

For each record class, identify every period that could apply and keep the record for the longest of them. The candidates are: the period set out in the tax law for substantiation records, the period set out in the contract, the warranty period that applies to the work, the period your insurer requires for claims purposes, and any period set out in the licensing legislation. Where you are unsure, keep the record longer. Storage is cheap; reconstructing evidence is not.

Two practical points follow from this. First, the clock usually starts at an event, not a date on a calendar. For contract records it is signing; for defects records it is practical completion or the end of the defects liability period; for financial records it is the end of the relevant tax period. Second, the period that applies to a record can change if a dispute arises. Once a claim is notified, a litigation hold should apply to everything relevant, regardless of the normal retention period.

Audit readiness is a retrieval problem

An audit or an investigation is not a test of whether you kept records. It is a test of whether you can produce them, in a usable form, within the time you are given. Those are different things, and plenty of well-organised businesses fail the second one.

The retrieval test is straightforward. Pick a completed project at random. Ask a person who was not involved in it to assemble the full record set: contract, plans, approvals, variations, inspection records, insurance certificates, and correspondence. If that takes more than a working day, or if anything is missing, your retention system has a gap.

There are three common causes of retrieval failure. The first is fragmentation: records spread across email, a project management tool, a cloud drive, and paper, with no single index. The second is naming inconsistency, so that a search for a job returns results under three different spellings of the same address. The third is orphaned records: documents held by a subcontractor or a former employee that were never copied into the business file.

None of these are solved by buying software. They are solved by deciding, before the job starts, where each record class will be filed and who is responsible for filing it. If you want a broader look at how CPD obligations interact with business systems, the PointCPD guide to running a CPD system for a building business covers the same design thinking.

Digital records, backups, and the destruction question

Most building businesses now hold records digitally, which solves the storage problem and creates a new one. A digital record is only as good as its backup and its index. A file that exists on a laptop that failed last month is not a record; it is a memory.

Whatever system you use, the record needs to be backed up somewhere separate from the device it was created on, and it needs to be readable years later. That last point matters more than people expect. File formats change, software subscriptions lapse, and cloud accounts get closed when a business restructures. If your retention period is measured in years, your storage decision needs to survive that period.

Destruction is the other half of retention, and it is deliberately not covered in detail here because the rules differ by record class and by entity. What you can do is be deliberate about it. A record that has genuinely passed the end of every applicable retention period can be destroyed, but the decision should be documented, and the destruction should be suspended immediately if a dispute, claim, or investigation is on foot. Destroying a record after you become aware of a claim is a far more serious problem than keeping it too long.

For records that relate to your own licensing and continuing professional development, the retention question is a little different, and it is covered in the PointCPD article on CPD record retention for NSW builders. The underlying principle is the same: the record needs to exist, be findable, and be held for the period that applies.

Worked example: a builder in western Sydney

A builder in western Sydney runs a small residential business with two supervisors and a rotating group of subcontractors. Work is steady, and the business has never had a formal complaint. Records are kept, in the sense that everything exists somewhere: contracts in a filing cabinet, plans in email, variations in text messages, and inspection certificates in a folder in the ute.

Three years after completing a two-storey addition, the business receives a letter from a solicitor acting for the homeowner. The claim concerns waterproofing in a bathroom that was part of the addition. The builder is confident the work was done correctly and that a licensed subcontractor did it, and that the subcontractor’s certificate was received at the time.

What follows is the part that matters. The builder can find the contract and the approved plans. The variation for the bathroom upgrade is in a text message thread on a supervisor’s phone; the supervisor left the business eighteen months ago and the phone was wiped. The waterproofing certificate was emailed by the subcontractor, but the email account it was sent to was closed when the business changed providers. The inspection record exists in a paper folder, but the folder is for a different project with a similar street name.

The builder is almost certainly right on the merits. It does not matter, because the business cannot prove what was installed, by whom, under what instruction, or that it was inspected. The claim is settled on terms that reflect that, and the cost of the settlement is borne by the business. The insurance position is also weakened, because the insurer will ask the same questions the solicitor asked.

None of this required bad faith. It required only that nobody decided, three years earlier, that the variation would be filed in the project record rather than left in a message thread, and that subcontractor certificates would be copied into the business file rather than left in an inbox.

Building the schedule into how the business runs

A retention schedule that lives in a document nobody reads is not a control. It becomes one when it is tied to the events that already happen in the business: contract signing, variation approval, inspection, handover, and end of defects liability.

The simplest way to do this is to attach the schedule to the handover process. Before a job is closed off, someone reconciles the project file against the schedule and confirms that every required record class is present and filed. That single step catches most of the problems described in this article, because it happens while the people involved still remember where things are.

If you want to go further, the PointCPD article on CPD evidence that survives an audit sets out the same principle applied to your own compliance records, and the guide to how NSW builder CPD works explains the licensing context those records sit inside. Both are relevant because a regulator looking at your business will not draw a clean line between your project records and your compliance records. It will ask for both.

The commercial reality is that record keeping is invisible when it works and expensive when it does not. A business that can produce a complete project file within a day resolves most complaints early and cheaply. A business that cannot will spend the same day, and considerably more money, reconstructing a defence from fragments.

Frequently asked questions

How long do I need to keep records for a completed residential job?

Longer than most builders assume, because statutory warranties and insurance obligations outlive the job. The correct approach is to identify every period that could apply — tax, contract, warranty, insurance, and licensing — and keep the record for the longest of them. Where you are unsure, keep it longer rather than shorter.

Do I need to keep records for subcontractors as well as my own work?

Yes, for anything that supports what you built. Subcontractor certificates, inspection results, and test reports should be copied into the project file at the time they are received, not left in an email account. If a subcontractor later leaves the industry or cannot be contacted, your file is the only evidence that the work was done to standard.

What is the risk of destroying records after the defects liability period ends?

The defects liability period in the contract is not the same as the statutory warranty period or your insurance obligations, and it is usually shorter. Destroying records at the end of the contract period can leave you without evidence for a claim that arrives later. Destruction should only happen after every applicable retention period has genuinely expired, and never once a dispute is on foot.

Do pool and spa projects need extra records?

Yes. Pool and spa work generates barrier compliance and inspection documentation that a standard residential job does not, and the obligations are split between the builder and the owner at different stages. The NSW Government publishes guidance on building a pool and on owner obligations, and both are worth reading so you know which documents are yours to retain.

Can I keep everything in email instead of a formal filing system?

You can, but it usually fails the retrieval test. An audit or an investigation is a test of whether you can produce the full record set for a given project within the time allowed, and email makes that hard because records are scattered across threads and accounts. A single indexed project folder, backed up separately, is a more reliable structure.

Does the Australian Taxation Office require the same retention period as my building obligations?

No, and the periods are not aligned. The ATO requires records that substantiate what you report, retained for the period the tax law sets out, which varies with your business structure and circumstances. Because the two regimes overlap on documents like contracts and invoices, you should apply whichever period is longer to each record class. Check the current ATO guidance for your situation.

Questions builders ask

• Bookkeeping
• Compliance
• Licensing
• Records

Published 19 August 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.