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's too late — is the certifier, 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 it can be handed to someone who was never on site and answer, without a follow-up email, four questions:
- →What was wrong, specifically and unambiguously?
- →Where was it, precisely enough to find it again?
- →Who identified it, fixed it, and verified the fix?
- →When did each of those things happen, in a sequence nobody can dispute?
If any of those needs a phone call to clarify, the report has failed. Everything below exists to remove the phone call.
Section one: the defect, stated once
The single most common failure in defect reporting is the vague description. "Tiling NQR." "Paint issue, level 4." These 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 compliant description 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, adjacent to the shower hob. Photographed 14 March 2026.
You should be able to find the tile from the description 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 a single, 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 can group by building, roll up by level, and never produce two different 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 matters the day someone claims the defect was never there, or was photographed somewhere else.
Every image in a compliant report should carry, and the report should be able to show:
The key word is chain. The original photo is immutable. Annotations, arrows, and callouts are a separate layer rendered over it. When challenged, you can produce the untouched original and the annotated version side by side.
Section four: the audit trail
This is the section that separates a real handover pack from a PDF someone made in a hurry. Every status change on a defect — open, assigned, in progress, ready for inspection, 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, following 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 (what was inspected), the totals (how many defects, how many closed, 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 dive into the detail.
Why spreadsheets can't do this
Every section above depends on the data being structured, linked, and immutable at the source. A spreadsheet is none of those things. It has no audit trail — the last edit overwrites the history. It can't anchor a photo to a pin on a revision-controlled drawing. It can't prove a timestamp. It produces a list, and a list is not a report.
The handover pack that survives scrutiny isn't a better-formatted spreadsheet. It's a different kind of artifact — one where every claim carries its own evidence, and the audit trail makes the whole thing impossible to quietly rewrite.