A defect report has two audiences. The first is the trade who has to fix the thing. The second, the one everyone forgets until it is too late, is the certifier or the lawyer or the tribunal member who, eighteen months from now, has to decide whether the work was done and whether it was done right.
Most reports are written for the first audience and fall apart in front of the second. This is the anatomy of one that survives both.
What compliance-ready has to mean
A report is compliance-ready when you can hand it to someone who was never on site and it answers four questions with no follow-up email:
- →What was wrong, specifically and without ambiguity?
- →Where was it, precisely enough to find it again?
- →Who identified it, fixed it, and verified the fix?
- →When did each of those happen, in an order nobody can argue with?
If any of those needs a phone call to clear up, the report has failed. Everything below exists to kill the phone call.
Section one: the defect, stated once
The most common failure in defect reporting is the vague description. "Tiling NQR." "Paint issue, level 4." Those are notes to self, not records. They mean something to the person standing in front of the defect and nothing to anyone else, ever.
A description that holds up is specific and self-contained:
Cracked floor tile, approx. 200 mm hairline crack running diagonally across a single 600×600 porcelain tile, Apartment 0407 ensuite, next to the shower hob. Photographed 14 March 2026.
You should be able to find the tile from the words alone, with the photo as confirmation rather than the only evidence.
Section two: location that resolves to a point
"Level 4" is an area. A defect lives at a point. The report needs a location that resolves to one repeatable place: building, level, room or apartment number, and where it matters a pin on the drawing.
This is where a structured location tree earns its keep. When every defect hangs off the same addressing spine, the report groups by building, rolls up by level, and never invents two names for the same room. The certifier reads one consistent vocabulary instead of six supers' personal shorthand.
Section three: the evidence chain
A photo on its own is an assertion. A photo with verifiable metadata is evidence. The difference shows up the day someone claims the defect was never there, or was shot somewhere else.
Every image in a compliant report should carry, and the report should be able to show:
The word that matters is chain. The original photo is immutable. Arrows and callouts are a separate layer over it. Challenged, you produce the untouched original and the annotated version side by side. There is more on how we handle that in photo metadata as evidence.
Section four: the audit trail
This is the section that separates a real handover pack from a PDF someone threw together on the Friday. Every status change on a defect, open to assigned to in progress to ready for inspection to closed, is logged with who did it and when, and that log is part of the report, not a separate system nobody can find.
The audit trail answers the question that decides most disputes: was this actually verified, or did someone just mark it closed? A report that can show "closed by inspector P. Nadkarni, 22 March, after re-inspection" is a different document from one that just says "closed".
Section five: the cover that frames it
The last thing you write and the first thing they read. A good cover states the scope of what was inspected, the totals of how many defects and how many closed and how many outstanding, the period, and the certifying signature. It turns a list into a statement, and it gives the reader the shape of the thing before they get into the detail.
Why a spreadsheet cannot do this
Every section above depends on the data being structured, linked, and immutable at the source. A spreadsheet is none of those. It has no audit trail, because the last edit overwrites the history. It cannot anchor a photo to a pin on a revision-controlled drawing. It cannot prove a timestamp. It produces a list, and a list is not a report.
The handover pack that survives scrutiny is not a better-formatted spreadsheet. It is a different kind of thing, one where every claim carries its own evidence, and the audit trail makes the whole document impossible to quietly rewrite. If you want to see what that produces, the reports docs walk through it.