Field notes
The lettings inspection report that won't survive the next case
18 May 2026
On this page
A landlord I spoke to recently lost a Section 8 case on persistent arrears. Not because the arrears were disputed. Not because the tenant had a compelling defence. The judge asked when the last inspection had taken place, whether the tenant had been notified in writing beforehand, and whether there was any photographic evidence of the property condition at that visit. The agent had a PDF. It had a date typed at the top. There were no photos. There was no notification record. The judge was not satisfied.
The inspection had happened. It just could not be proved in a way that mattered.
This is where lettings compliance is heading. The Renters' Rights Act removes Section 21 as a fallback. Every possession route that remains runs through Section 8, and Section 8 cases are argued on evidence. The question is no longer whether your agency does inspections. It is whether your inspection records would survive cross-examination.
This post discusses how inspection documentation affects possession proceedings. It is not legal advice. If you are managing an active possession case, instruct a solicitor or licensed housing law specialist.
Section 21 was blunt but procedurally forgiving. If the paperwork was right at the start of the tenancy, you could recover possession without proving anything about what happened during it. Agents leaned on that. Inspection processes were often about landlord reassurance and maintenance scheduling, not evidence gathering.
Section 8 works differently. The grounds you rely on, whether that is Ground 8 for arrears, Ground 12 for breach of tenancy terms, or Ground 13 for property condition, require you to demonstrate a factual position. The court needs to believe that position is true and that you can prove it. A typed PDF with a date on it does not do that job.
If you want to understand the procedural shift in more detail, the Section 21 workflow post covers what the removal of no-fault eviction means for the sequencing of compliance tasks across a tenancy. The inspection problem sits inside a larger workflow failure.
Here is what a typical inspection report looks like in most mid-sized lettings agencies right now. A templated Word document or PDF, completed by whoever did the visit, with a date typed at the top, a condition rating for each room, maybe a few notes about maintenance items, and occasionally some photos attached as a separate folder or embedded in the document at low resolution.
That report has several problems when it reaches a courtroom.
The date is typed, not generated by a system with an audit log. It can be changed. The photos have no EXIF metadata because they were taken on a phone, resized, and dropped into a document. The GPS coordinates are gone. The timestamp is gone. There is no record that the tenant was notified of the visit in advance, which is a legal requirement under the Landlord and Tenant Act 1985 anyway. There is no signed acknowledgement from the tenant or any record of their response. And the inspector's name is there, but there is nothing linking that person to that property on that day in any system that was not controlled entirely by the agency.
Tools like Inventory Hive and No Letting Go exist specifically because this problem was visible before the Renters' Rights Act. Both platforms generate timestamped, geotagged reports with photo metadata preserved. Both produce outputs that are harder to challenge on procedural grounds. The issue is that many agencies using these tools are not using them for every inspection, or are using them but stripping the metadata when they export the report to send to a landlord.
The tool is only as good as the process it sits inside.
This is not about being bureaucratic for its own sake. It is about building a record that answers the questions a judge or opposing solicitor will ask. Those questions are predictable. The record should be designed around them.
| Field | What to capture | Why it matters in proceedings |
|---|---|---|
| Inspection date and time | System-generated, not manually typed | Establishes the record cannot be backdated |
| Inspector name and role | Full name, job title, employed or contractor | Identifies the witness if the case proceeds |
| Property address | Full address including postcode | Links the record unambiguously to the tenancy |
| Tenant notification record | Date sent, method (email/letter), content summary | Demonstrates legal access compliance |
| Tenant response or acknowledgement | Reply received, no reply noted, access refused | Relevant if access was disputed |
| Photos | Taken in-app or with EXIF metadata preserved | GPS and timestamp survive into the report |
| Condition notes per room | Structured fields, not free text | Easier to cross-reference against previous reports |
| Maintenance items raised | Linked to subsequent action or contractor instruction | Shows the agent acted on what they found |
| Inspector signature | Digital signature with timestamp | Confirms the report was completed at the time |
| Next inspection date | Scheduled in system, not ad hoc | Demonstrates a consistent inspection programme |
Every field in that table is answering a question someone will ask if the tenancy ends in dispute. The inspection programme should be designed with that endpoint in mind, not built around what is convenient for the property manager on a Tuesday afternoon.
Agencies that have poor inspection records usually do not have a documentation problem. They have a workflow design problem. The inspection is treated as a standalone task: go to the property, look around, write some notes, send a report to the landlord. There is no intake structure. There is no checklist that fires before the visit. There is no system that confirms notification was sent. There is no output that automatically archives to the tenancy file in the CRM.
This is the same pattern I see in AML compliance. The AML workflow post describes how agencies that look compliant on paper often have no process connecting the individual steps. Inspection records have the same failure mode: the inspection happens, the report exists, but the connective tissue between them is missing.
An AI-assisted workflow can help here, but only if the underlying structure is right first. You can automate the notification letter, auto-schedule the next inspection, and flag overdue visits in your CRM. None of that helps if the report itself is a Word document with no metadata.
If you manage a portfolio of any size, do this before the next inspection your team runs.
- Pull the last three inspection reports for any property. Check whether the photos have metadata. Open the file properties and look at the creation date. Ask whether that date matches the typed date on the report.
- Check whether there is a record in your CRM or email system of the tenant notification being sent before each of those visits. If the notification lives only in the inspector's memory, it does not exist as evidence.
- If you are using Inventory Hive or No Letting Go, confirm that the export format you send to landlords preserves the photo metadata. Some export templates strip it.
- If you are not using structured inspection software, decide whether your current process would produce a report you would be comfortable handing to a solicitor tomorrow.
- Design the pre-inspection trigger: what fires before the visit? Notification letter sent, confirmation logged, previous report pulled for comparison. Make that a checklist in your system, not an assumption.
The inspection programme is not a landlord service. It is an evidence programme. Design it like one.
If your inspection workflow was built around Section 21 as the safety net, it needs rebuilding now. The process underneath the paperwork is where cases are won or lost, and most agencies have not looked at that process since the legislation changed.
If you want to map the gaps in your current inspection or compliance workflows, the AI Workflow Audit is where we start. We look at what your process actually does, not what your policy document says it does.