A structured defect report with timestamps, photographs, location references, and applicable code citations will get a faster, more serious response from a builder than an email list. The format signals that you are organised, that the defects are documented, and that the record exists independently of any conversation you might later have.
That distinction matters more than most homeowners realise. The difference between a defect that gets resolved and one that quietly disappears is often not the severity of the issue — it’s the quality of the paperwork behind it.
Why email defect lists don’t work
Most homeowners report defects by email. They write something like: “Hi, just following up on a few things we noticed — the grout in the main bathroom looks uneven in places, one of the power points in the kitchen doesn’t seem to be working, and there’s a gap above the door in the laundry.”
That email is easy to ignore. It has no timestamp embedded in the defect itself (only the email timestamp, which your builder can claim they didn’t see). It has no photos. It has no location reference more specific than “main bathroom.” It has no indication of severity, no reference to any building standard, and no clear status — was this already flagged? Is this new? Has anything been done?
More practically: it’s easy to cherry-pick. A builder who wants to avoid a costly repair can acknowledge the power point and the grout while simply not responding to the laundry gap. You have no clear record of what was said about which item. A follow-up email about the gap gets a reply: “We’ll get someone to look at it.” That’s not a commitment, and it doesn’t create any obligation.
Email is also easy to delay. Without a clear structure signalling urgency and completeness, a defect list sits in an inbox like any other email — to be dealt with when convenient.
What a formal defect report needs
A report that a builder has to take seriously contains specific elements.
Timestamp. Not just the date the email was sent, but the date and time each defect was logged. This matters for warranty purposes and for any later dispute — you need to be able to demonstrate not just that you reported the defect, but exactly when.
Location reference. “Main bathroom” is not enough. “Main bathroom — floor-to-wall junction at south wall, approximately 400mm from the shower screen” is specific enough to find without interpretation.
Photographic evidence. A photo taken at the time of logging, showing the defect clearly. Where size matters, a reference object — a coin, a ruler, a hand — in frame. Where the defect requires context, a wider shot showing where in the room it sits, as well as a close-up showing the detail.
Defect description. Specific, objective language. Not “the grout looks bad” but “grout joint on floor tiles in main bathroom is inconsistent — approximately 4mm wide in some sections, closing to 1mm in others across the same run.”
Applicable standard or code reference. This is where most informal defect lists fall down entirely. If a defect relates to a specific requirement under the NCC (National Construction Code), a relevant Australian Standard, NHBC Standards in the UK, or any other code, citing it transforms your report from a personal opinion into a documented non-compliance.
Status. Open, In Progress, or Resolved. Without status tracking, even a good report becomes a static document — a snapshot of one day, with no indication of what’s happened since.
The psychology of a builder receiving a report versus an email
There’s a well-understood dynamic in construction disputes: the less formal your complaint looks, the less formal the response tends to be.
An email with a few bullet points looks like a conversation. The response can be informal, partial, and non-committal. “We’ll get onto it” is a legitimate reply to a conversational email. It creates no obligation, establishes no timeline, and documents nothing.
A PDF report with a cover page, a numbered defect list, timestamps, photos, location references, and code citations looks like paperwork. It looks like documentation. It looks like the beginning of a paper trail that could end up before a tribunal. The response to that kind of document tends to be more specific, more timely, and more formal — because it has to be. The builder’s site supervisor can see that you know what you’re doing, and that everything you’ve sent them exists as a permanent record.
This isn’t about being adversarial. Most builders want to resolve legitimate defects. A clear, structured report makes that easier — it removes ambiguity about exactly what needs to be fixed, where, and to what standard. But it also raises the cost of inaction, which matters when a builder is deciding how to prioritise their schedule.
What to include in the covering message
The report does most of the work. The covering message should be brief and direct.
Something like: “Please find attached a defect report prepared following our [inspection date] walkthrough. The report documents [number] items across [areas]. Each item includes a photo, location reference, description, and where applicable a reference to the relevant standard. Please review and confirm your intended approach to rectification by [date — typically 14 to 21 days for minor items; sooner for anything structural or affecting waterproofing].”
That’s all. No apologetic language, no hedging, no lengthy background. The report contains the detail. The covering message communicates that you expect a response, and by when.
Keep a copy of every email you send and receive. If your builder responds verbally rather than in writing, follow up immediately: “Thanks for speaking today. To confirm what we discussed — [builder] will attend to [defect description] by [agreed date]. I’m noting this in writing for our records.”
Building a paper trail
The value of a paper trail compounds over time. If your builder addresses an item promptly and correctly, the trail shows that. If they delay, dispute, or ignore, the trail shows that too.
The key entries in a useful paper trail are: the date you first logged each defect, the date you formally notified your builder, any acknowledgement or response from the builder, any agreed remediation timeline, and whether rectification was completed satisfactorily.
Without each of those data points, a later dispute becomes a “he said, she said” situation — difficult to resolve and unlikely to favour the homeowner. With them, you have a documented sequence of events that a tribunal can follow.
For practical guidance on building this kind of record from the ground up, the defect documentation guide on this site covers the photography and logging workflow in detail.
Defects liability periods and why the date you notified matters
The date you first formally reported a defect is not just a record-keeping detail. In many cases, it determines whether you are within your rights to claim rectification at all.
Under the Australian Consumer Law (ACL), builders are required to provide services that are fit for purpose and completed with due care and skill. State-level legislation adds more specific protections: QBCC warranty provisions in Queensland, the NSW Home Building Act 1989, the Domestic Building Contracts Act 2000 in Victoria. These frameworks typically include a defects liability period (DLP) of 12 months from practical completion, during which the builder must return and rectify reported defects. For major or structural defects, extended warranty periods apply — commonly 6 years in NSW, 6 years in Victoria, 3 years through QBCC for structural and 1 year for non-structural.
In the UK, the NHBC Buildmark warranty provides 2-year builder defect coverage from legal completion and 8-year structural coverage beyond that. New homes warranty providers including NHBC, LABC Warranty, and Premier Guarantee all have notification requirements — if you don’t report within the applicable period, you may lose the right to claim.
The critical point: it’s the date of formal written notification that starts the clock for the builder’s obligation to respond, and in disputes, it’s the date of written notification that you have to be able to prove. A verbal conversation doesn’t establish that date. A text message is better but not ideal. A formal defect report, timestamped and delivered in writing, is the appropriate standard.
What to do if the builder ignores the report
A builder who doesn’t respond to a formal defect report after a reasonable period — typically 14 to 21 days for minor items, sooner for anything urgent — has given you documented evidence of non-response. That’s worth having.
Your escalation options depend on jurisdiction, but they’re broadly similar across Australia and the UK:
Queensland: File a complaint with the QBCC. They have powers to compel rectification and conduct their own inspection. You’ll need to demonstrate you’ve made reasonable attempts to resolve directly first — a paper trail showing you sent a formal report and received no adequate response satisfies that requirement.
New South Wales: Lodge a complaint with NSW Fair Trading. For disputes that don’t resolve there, NCAT (the NSW Civil and Administrative Tribunal) handles building matters. Bring your timestamped defect report, all correspondence, and any inspection records.
Victoria: The Domestic Building Dispute Resolution Victoria (DBDRV) process is the first step before VCAT. VCAT handles disputes that don’t resolve through DBDRV, and a structured, timestamped defect report is central to making your case.
UK: The NHBC has a resolution service for warranty claims. For disputes outside warranty, the New Homes Ombudsman Service (NHOS) handles complaints about new build homes and can require builders to take remedial action.
In all cases, what these bodies need is what a proper defect report provides: evidence that the defect exists, documentation of when it was first identified, proof that the builder was formally notified, and a record of what response (if any) was received. An email list rarely satisfies all of those requirements. A structured, timestamped report with photos and code references does.
Shareable reports and the dispute process
Tribunals — QCAT, NCAT, VCAT, or equivalent — are evidence-based. They don’t resolve disputes based on accounts of verbal conversations. They look at documents: what was in the contract, what the applicable standard requires, when the defect was identified, when the builder was notified, and what evidence exists of the defect itself.
A shareable defect report, prepared at the time of inspection and shared with your builder in writing, is exactly the kind of document that serves you well in that process. It’s not created retrospectively. It’s not assembled under pressure after things have gone wrong. It’s a contemporaneous record — created at the time, for the purpose of tracking and resolving defects — that happens to also function as evidence when you need it.
The alternative is trying to reconstruct events from memory, emails, and half-remembered conversations. That rarely goes well.
If you’re in the process of actioning an inspection report and trying to structure your follow-up, the guide to actioning your building inspection report covers how to prioritise defects by urgency and what your obligations are at each stage.
Key Takeaways
- An email list is easy to ignore, cherry-pick, and delay — a structured report with timestamps, photos, and code references is not
- The date of formal written notification matters for defects liability periods under ACL, QBCC, the NSW Home Building Act, the Domestic Building Contracts Act (VIC), and NHBC warranty terms
- A formal report changes the psychology of the interaction — it signals documentation, creates obligation, and raises the cost of inaction
- Your covering message should be brief and include a clear response deadline — let the report carry the detail
- If your builder ignores a formal report, you have documented evidence of non-response — the basis for a QBCC complaint, NSW Fair Trading referral, DBDRV process, VCAT or NCAT claim, or NHOS complaint in the UK
- Tribunals work on evidence — a timestamped, structured defect report is exactly what they need; a sequence of informal emails is not
Free to download
Stop losing track of defects.
Checka helps you capture issues, stay organised, and arrive at handover with a complete record of your build.