What a property inspection report actually needs to record

An inspection report's real audience isn't the person who wrote it — it's whoever reads it later without having been on site: a landlord deciding whether to authorise a repair, a colleague picking up the file, or the same inspector six months on trying to remember whether a particular issue is new or ongoing. Writing for that reader changes what's worth recording.

Specific, not general

"Kitchen in reasonable condition" tells a reader almost nothing useful later. "Small water mark under the kitchen sink, appears to be from a slow drip, tenant unaware" is something a reader can actually act on — it's specific enough to justify a plumber visit, and specific enough that if it's checked again in three months, it's clear whether it's improved, stayed the same, or got worse.

Photos support the record, they don't replace it

A photo is genuinely useful evidence, but a folder of undated, uncaptioned images with no accompanying written note is close to useless six months later when nobody can remember which room a particular photo was taken in or what specifically prompted it. Every photo needs a caption tying it to a specific, dated observation in the written report.

Consistency between visits is what makes a report actually useful

As covered in inspection scheduling best practice, using the same structure and checklist every visit is what makes reports comparable over time — a report that covers different things depending on who did the walkthrough makes it far harder to spot a pattern developing across several visits, which is often more useful than any single report on its own.

• –Specific, dated observations rather than general impressions
• –Photos captioned and tied to a specific written note, not left to speak for themselves
• –A consistent structure used every visit, so reports are genuinely comparable over time
• –A clear distinction between something noted for awareness and something that needs action
• –Direct linkage to a tracked repair for anything that needs following up

Distinguishing 'noted' from 'needs action'

Not every observation needs a repair raised against it — some things are simply worth noting for context, like a tenant's own furniture blocking a vent, without implying it's a defect needing a contractor. A report that treats every observation with the same weight either buries genuine issues in noise, or trains readers to skim past everything, including the parts that mattered. Anything that does need action should feed directly into a tracked repair, not sit as a note with no clear next step.

Why this record matters beyond the immediate repair

A well-kept history of inspection reports is also part of the evidence base a tenancy file audit or a deposit dispute might eventually draw on — a clear, dated record showing a property's condition was actively monitored throughout a tenancy is genuinely useful if a dispute later turns on whether damage was pre-existing or happened during the tenancy.

Recording condition, not just observations

A report noting "damp patch in bathroom" captures that something was seen. It does not capture whether it is worse than last time, which is usually the more useful question. Condition recorded consistently — with photographs from comparable positions — turns a series of inspections into a picture of a property over time rather than a set of unconnected snapshots.

The same applies to things that are fine. A report that only records problems cannot later demonstrate that something was checked and was satisfactory, which matters when a tenant raises an issue that was not present at the last visit.

Common mistakes

• –Recording problems without recording what was checked and found satisfactory
• –Photographs taken from inconsistent positions, so they cannot be compared
• –No comparison against the previous inspection
• –Free-text notes that cannot be compared across visits
• –No link between a report and the work it generated
• –Reports stored per visit rather than accumulating against the property