Knowledge · Risk, insurance and compliance
The defence is the record,
not the relationship.
A warranty or defect claim can arrive years after handover, about work nobody now remembers, from an owner the builder never met. This reference covers what to keep, how long to keep it, why the retention horizon is the statutory warranty period rather than a tax one, and why a record made on the day carries weight that a reconstruction never will. General information, not legal or insurance advice.
01 / Overview
The claim that arrives years later
A residential builder's warranty exposure does not end at handover. The statutory warranties implied into every domestic building contract run for years afterwards, they generally cannot be contracted out of, and they attach to the work rather than to the friendship. Which means the realistic scenario a builder should plan for is not a difficult client. It is a letter about a house finished several years ago, describing a defect in work that was covered by other work within days of being done, sent by someone with no memory of the build.
Two facts make that scenario harder than it first sounds. Warranty protection commonly transfers with the home, so the claimant may be a subsequent owner the builder has never met, who knows nothing of what was agreed, changed or deliberately excluded. And the work in question is usually invisible: reinforcement, membranes, flashings, framing, services, all sealed behind finishes long ago. Nobody can go and look. The dispute is decided on what was written down at the time, or on whose account is more persuasive when nothing was.
The principle
The defence is the record, not charm and not the relationship. That is not a comment on goodwill, which is worth having and often resolves things before they become claims. It is a comment on durability. Goodwill does not survive a sale of the house, a change of supervisor, a company restructure or five years. A written record does, if somebody decided to keep it in a form that can be found. This page is about that decision.
Everything here is general information about record-keeping practice, not legal or insurance advice. Retention periods, warranty periods and the way a claim is assessed differ by jurisdiction and change, so confirm the current position for the state you build in, and take advice on any actual claim.
02 / Where it fits
A different purpose from the site diary
This page is not about daily site record-keeping, which has its own reference in site diaries and daily records. The two are related and worth keeping distinct, because they have different purposes and different lifespans.
- The site diary is an operational record with live uses. Weather, labour, deliveries, directions, delays and progress, written on the day, mostly used while the job is running to justify an extension of time, support a variation, or settle a disruption argument. Its horizon is the build and the period immediately after it.
- The warranty file is a curated permanent record. What was approved, specified, built, inspected, certified and handed over, kept because a claim may arrive years later. Its horizon is the statutory warranty period, which outlasts the site by years and often outlasts the staff who were on it.
The diary feeds the file, particularly through its dated photographs and its record of directions and decisions, and a builder who keeps a good diary has already done a meaningful part of the work. But a diary is not a warranty defence on its own, because a diary rarely holds the approvals, the compliance certificates, the engineering details as built or the handover pack. Read the diary page for the daily discipline; read this one for what is kept, and for how long.
03 / The record set
What a warranty file has to hold
Eight categories, each answering a question a defect claim actually asks. Held against the job rather than scattered across a year, an email account and somebody’s phone.
Approvals and certificates
The development and building approvals, the stamped plans they were granted against, the mandatory inspection sign-offs, the occupancy or completion certificate, and the compliance certificates for plumbing, electrical, waterproofing, termite management and glazing. These answer the compliance question directly, and they are the hardest documents to reconstruct because they were issued by somebody else.
Engineering details as built
The structural drawings, the engineer’s details for footings, slabs, bracing, tie-downs and any site-specific design, and any written variation to a detail issued during construction. A structural claim is argued against what was designed and what was built, so a superseded drawing with no record of the change is a gap in the middle of the argument.
Inspection records
Council or private certifier inspections, engineer site inspections, and your own pre-pour, pre-line and pre-handover checks. An inspection record is a third party or a named person saying the work was in a particular state on a particular day, which is a different class of evidence from a photograph and worth keeping alongside it.
Dated photographs of covered work
Reinforcement before the pour, waterproofing before the screed, framing and services before the linings, flashings before the cladding, subfloor before the deck. Once the work is covered it cannot be inspected without destroying something, so the photograph taken that morning is the only remaining evidence of what is behind the wall.
Variation approvals
The written, signed variation with its scope, its price and its date, agreed before the work was done. Many defect claims are really scope claims in disguise, an owner asserting they were promised something the contract never included. A signed variation record decides that question in a minute.
Product and material specifications
The specified products, the data sheets, the batch and supplier details where they matter, and the manufacturer’s installation instructions. A claim about a failed product usually turns on whether it was suitable and whether it was installed as specified, and both questions are answered by documents rather than by memory.
Subcontractor details and their warranties
Who did the work, under what scope, with what licence and insurance, and what warranty they gave you. A builder is answerable to the owner for the whole job, so a subcontractor warranty is not a defence to the owner; it is the mechanism for recovering from the trade that caused it, and it is worthless if you cannot find who the trade was.
Handover documentation
The handover pack itself, the maintenance and care instructions given to the owner, the appliance manuals and their warranties, and the signed acknowledgement that it was all handed over. Some claims are maintenance failures rather than defects, and the handover record is what distinguishes them.
The categories are not arbitrary. Between them they answer the four questions a defect claim resolves into: what was agreed, what was built, whether it complied, and what the owner was given at handover. A file that answers all four is a defence. A file that answers three leaves the fourth to be argued from memory, which is where claims are lost. This is the same idea as documents as evidence, applied to a single job several years after it finished.
04 / Retention
How long to keep it, and what sets the clock
The retention horizon for building records is set by the statutory warranty exposure, not by the period a business keeps records for tax. Those two clocks are different, they are set by different bodies for different reasons, and the building one is usually the longer of the two. A builder who lets the accountant's calendar decide when a job file is destroyed has aligned their evidence with the wrong risk.
Setting the horizon is a three-part calculation, and each part has to come from the jurisdiction rather than from a national rule.
- The longest warranty period that could apply. Statutory warranty periods are set by each state and territory and commonly split a longer period for major or structural defects from a shorter one for other defects. The file has to survive the longer of them. As an illustration of the shape rather than a national figure, Tasmanian statutory warranties run six years from practical completion and transfer to a new owner if the home is sold within that period. Confirm the periods that apply where you build.
- When the clock starts. A period running from practical completion and a period running from some earlier date are not the same amount of exposure, and the difference can be months on a long job. Read the start point, not just the length.
- The time a claim takes to run. A claim made near the end of a warranty period is not resolved on the day it is made. Records destroyed the week a period expires can still be the records a live matter needs, so the sensible practice is to keep the file past the end of the period rather than to the edge of it.
One practical consequence: retention is a per-job decision, because the horizon runs from that job's completion in that job's jurisdiction. A business that archives by financial year is making a single decision for jobs whose clocks started at different times, which is how a file gets destroyed two years early without anyone deciding to destroy it.
None of the above is a legal retention rule. Record-keeping obligations under building, licensing, work health and safety, employment and tax law all run in parallel and are set elsewhere. Treat the warranty horizon as a floor for keeping building records, confirm the statutory periods for your jurisdiction, and take advice if you are deciding to destroy anything.
05 / Process workflow
How a claim is actually answered from records
Seven steps from the letter arriving to the response going out. Steps two through five are entirely documentary, which is why the outcome is largely decided before the claim is made.
- 01
The claim arrives
A letter, an email, sometimes a tribunal or scheme notification. It may name a defect precisely or describe a symptom vaguely, and it may come from an owner who was never your client. The first job is to read what is actually alleged, rather than what it feels like it is alleging.
- 02
Identify the job and pull the file
Address, contract, dates, stage. This step is trivial for a builder whose records are held against the job and painful for a builder whose records are held by year, by trade or in an email account. The time this step takes is a fair proxy for how the rest of the claim will go.
- 03
Establish what was contracted
The contract, the specification and every signed variation. Before arguing about quality, establish scope, because a meaningful share of defect claims are about work that was never in the contract or was removed by a variation the owner has forgotten.
- 04
Establish what was built
The engineering details as built, the product specifications, the dated photographs and the inspection records. This is the step that decides most genuine defect claims, and it is decided almost entirely by documents created at the time.
- 05
Establish that it complied
The approvals, the mandatory inspection sign-offs and the compliance certificates. Compliance is a documentary question by design; the certificates exist precisely so it does not have to be argued from opinion years later.
- 06
Decide the position honestly
Sometimes the record shows the claim is right. Finding that out from your own file, early, is worth a great deal, because rectifying a genuine defect on your own terms is almost always cheaper and less damaging than being directed to.
- 07
Respond with the evidence attached
A response that says the waterproofing was inspected on this date, here is the certificate, here are the photographs of the membrane and the specified product, tends to end a marginal claim. A response that asserts the work was done properly invites the next letter.
06 / The principle
Why the day it was made decides what it is worth
The central idea on this page is that a record made at the time and a record assembled afterwards are different classes of thing, even when both are honest. The record made at the time was created by someone who did not know what would later be argued about, for no purpose beyond documenting the day. That absence of motive is exactly what gives it weight. The reconstruction is made by someone who knows the allegation, and everyone assessing it knows that.
The second difference is accuracy rather than motive. Memory does not simply fade, it fills. Asked years later what happened at a pre-pour, an honest supervisor will describe what normally happens, because that is what the mind supplies when the specific day is gone. The answer will be sincere and it will be a description of practice, not of that slab. A photograph timestamped that morning is a description of that slab.
This is why the practical advice is always about the moment of creation rather than the moment of need. You cannot decide to have evidence when the claim arrives. The only decision available then is which of your existing records to send. Every meaningful choice about a warranty defence was made years earlier, on ordinary days, by someone taking a photograph before the plasterer arrived.
07 / Best practice
How experienced builders keep the file
The operator's observation is that most builders lose warranty claims to a filing decision rather than a building one. The records usually existed. The photographs were taken, the certificates arrived, the variation was discussed. What went wrong is that the photographs stayed on a phone that left with a supervisor, the certificate was an attachment in an email account nobody searches, and the variation was agreed over a bonnet. Nothing was destroyed. It simply could not be found by the person who needed it, four years later, in the fortnight they had to respond.
The second observation is the retention mismatch. Builders inherit their filing rhythm from the accounts side of the business, because that is the part with an external deadline every year, and building records quietly get treated the same way. But the accounts calendar has nothing to do with warranty exposure. Records get cleared out on a schedule set for a different purpose, and the gap between the two clocks is where a surprising number of claims are lost.
The disciplines that answer both observations are unremarkable. Variations documented and signed before anything is ordered, so the scope of record is never a matter of recollection. A written scope the client has actually agreed to. Photographs at every point where work disappears behind other work, filed against the job the same day rather than kept on a handset. Certificates and approvals filed against the job as they arrive, not at the end. Subcontractor details and their warranties held with the job so the recovery path still exists years later. And a handover pack with a signed acknowledgement, so what the owner was told about maintaining the home is a record rather than a claim.
None of that is warranty-specific work. It is how a well-run job is documented anyway, which is the useful part: the builder who runs this way is not preparing for a claim, they are simply operating in a way that happens to answer one. That also means no regulatory change makes the discipline newly necessary. Reform raises the cost of not having the record; it does not create the need for it.
Where software fits the workflow
The record only exists years later if creating and filing it was easier than skipping it, which is a workflow problem before it is a compliance one. In VIABUILD, variations are captured and approved before work starts, site photographs and daily records are filed against the job as they are taken, and the documents that arrive during a build, approvals, certificates, specifications, subcontractor paperwork, are held against the job rather than in an inbox. Oryn reads those documents so they are searchable by what is in them rather than by what somebody named the file, which is the difference between having a record and being able to produce it. The judgement about how to answer a claim stays with the builder; the contribution is that the file the answer stands on was assembled while the job was running.
08 / Failure modes
How warranty files fail
Almost none of these are failures to create a record. They are failures to keep it findable, keep it long enough, or write down the one thing that was agreed verbally.
Filed by year, not by job
Records organised the way the accounts are organised, by financial year and by supplier, are almost unusable for a defect claim, which arrives organised by address. The retrieval problem is a filing decision made years earlier.
Kept on a phone
The pre-pour photographs exist, on a supervisor’s handset, and the supervisor left in 2024. Photographs that were never filed against the job are not a record, they are a hope, and they leave with the person who took them.
The tax retention habit
Records cleared out on the rhythm the accountant set, while the statutory warranty exposure runs on a different and usually longer clock. The file is destroyed on schedule, and the claim arrives afterwards.
The verbal variation
The change was agreed on site, everybody was happy, nobody wrote it down, and the work was done. Years later the owner remembers a promise and there is no signed scope to answer with. This is a defect claim only in name.
The superseded drawing
The job was built to revision C, the file holds revision A, and nothing records why or when the detail changed. A structural claim against an undocumented change is a difficult claim to answer, however sound the change was.
The record made afterwards
Photographs taken and notes written once a claim has been received. They may be entirely truthful, and they still carry less weight than a record made at the time, because everyone can see they were made by somebody who already knew what was being alleged.
09 / Practical example
A bathroom leak, five years on
Illustrative only, not a benchmark. Water appears in a ground floor ceiling below an upstairs bathroom. The home has been sold once, so the claimant is an owner the builder has never met, and the allegation is that the waterproofing was never done properly.
The first builder pulls the job file. It holds the waterproofing compliance certificate naming the licensed applicator and the date, photographs of the membrane taken the morning before the screed showing the upturns and the penetrations, the product data sheet for the specified membrane, the subcontractor's details and warranty, and a signed variation from the build recording that the owner changed the shower layout after the set-out. The response goes back with all of it attached and a proposal to investigate the actual source, which turns out to be a failed shower screen seal, a maintenance item covered in the handover pack the original owner signed for. The matter is closed in a fortnight without anyone becoming adversarial.
The second builder is confident the waterproofing was done correctly, because it always is. The certificate is in an email account, the applicator has since closed their business, the photographs were on the phone of a supervisor who left, and the shower layout change was agreed on site and never written down. There is nothing to attach to the response, so the response is an assertion. The next step is an inspection, and because the evidence has to be found rather than produced, the inspection is invasive: tiles come off. Whatever the outcome, the cost of establishing it is now real, and the builder is arguing about a job they built well.
Same standard of work, same builder capability, opposite experiences. The difference was settled five years earlier, in the ten minutes it took to photograph a membrane and file two certificates against a job.
10 / FAQ
Common questions.
Long enough to cover the statutory warranty exposure for the state the work was in, which is a different and usually longer horizon than the record-keeping period a builder keeps for tax purposes. The statutory warranty periods are set by each state and territory and commonly split a longer period for major or structural defects from a shorter one for other defects, so the length has to be read from the legislation for the relevant jurisdiction rather than taken from a national rule of thumb. Tasmania is a useful illustration of the shape rather than a national figure: statutory warranties there run six years from practical completion and transfer to a new owner if the home is sold within that period. The practical rule is to set the retention horizon from the longest warranty period that could apply to the job, allow for the time a claim takes to be made and run, and never let the accounts calendar decide when a building record is destroyed. Confirm the current periods for your state, and take advice where a real claim is involved.
Because a record made at the time was made by someone who did not yet know what would be argued about. A photograph of a membrane taken on the morning of the screed had no purpose beyond documenting the day’s work, and that is exactly what makes it persuasive. The same photograph staged after a claim arrives is made by someone who knows the allegation and knows what a helpful image looks like, and everybody assessing it knows that too. The second reason is simpler: memory degrades and reconstruction fills the gaps with what should have happened rather than what did. A contemporaneous record is a description; a reconstruction is a reasonable belief. Only one of them is evidence in the ordinary sense.
Yes, and it is one of the reasons the record matters more than the relationship. Warranty protection commonly transfers with the home, so a subsequent owner within the cover period can make a claim about work done for the person who sold it to them. That owner has no memory of the build, no relationship with the builder, and no knowledge of what was agreed, changed or deliberately left out. Everything they know about the job comes from what they can see and what they have been told. The only counterweight is the documentary record of what was contracted, what was built and what complied, which is why a builder cannot rely on the goodwill of the original client to see them through a warranty period.
Dated photographs of work that gets covered up, taken immediately before it is covered. Everything else in the file can usually be reconstructed from somewhere, an approval from the authority, a certificate from the certifier, a specification from the supplier, but nobody can reinspect the reinforcement after the pour, the membrane after the screed or the framing after the linings without demolishing something. Those photographs are the only surviving evidence of a large share of the work a defect claim is likely to be about, and they cost seconds to take. If a builder adopts one discipline from this page, it is a photograph at every point where work disappears behind other work.
The two overlap in what they capture and differ in what they are for. A site diary is a daily operational record of weather, labour, deliveries, directions, delays and progress, and its most common uses are live: justifying an extension of time, supporting a variation, or settling a disruption argument while the job is running. The warranty file is a curated, permanent record of what was approved, specified, built, inspected, certified and handed over, and it is used long after the site has closed. The diary feeds the file, particularly through its dated photographs and its record of directions and decisions, but a diary alone is not a warranty defence and a warranty file alone will not run a job. The daily practice is covered separately in site diaries and daily records.
It does not change what to keep, only how quickly it may be needed and who may be reading it. Under a last-resort scheme the record is what wins at the tribunal. Under a first-resort scheme, the regulator can step into a dispute while the builder is still trading and direct a rectification, so the same record may be assessed by someone who was never on site, sooner, and without any relationship to draw on. The discipline is the same either way, which is the point: the builder who documents variations, keeps an agreed scope and photographs covered work is ready under either model. The models are compared in first-resort and last-resort warranty models.
Rarely. A photograph proves a state of affairs at a moment, which is close to decisive for covered work, but it does not prove what was contracted, what was specified, what a certifier accepted or what the owner was told at handover. A defence usually needs four things to line up: what was agreed, what was built, that it complied, and what the owner was given at handover. Photographs answer the second and contribute to the third. The signed variation, the approved specification, the compliance certificates and the handover acknowledgement answer the rest. Keeping only photographs leaves most of the argument unaddressed.
11 / Terms
Glossary for this topic
Contemporaneous record (evidence created at the time of the event rather than reconstructed later), covered work (work sealed behind later work and no longer inspectable without destruction), as-built documentation (the record of what was actually constructed, including changes to design details), compliance certificate (a licensed person's certification that specific work meets the applicable requirement), handover pack (the documentation and maintenance information given to the owner at completion), retention horizon (how long records are kept, set here by the statutory warranty exposure), subsequent owner (a later purchaser who may hold warranty protection transferred with the home). The wider vocabulary lives in the construction glossary.
The related reads are statutory warranties for what is actually being promised and for how long, first-resort and last-resort warranty models for who can enforce it and how early, and defects management for handling a claim once it has arrived.
12 / Keep reading
Related knowledge
13 / Further reading
Primary sources
- Your state or territory's building regulator and domestic building legislation, for the statutory warranty periods that set the retention horizon, and for any record-keeping obligations attached to your licence.
- The warranty scheme administrator in the jurisdiction where you build, for how a claim is made and assessed and what evidence is expected from a builder.
- A construction lawyer, for any live claim. General information about record-keeping cannot tell you how to respond to a specific allegation.
Build the file while the job is still open.
VIABUILD holds variations, approvals, certificates, specifications and site photographs against the job as they happen, so the warranty file exists years later without anyone having set out to build one.
