What a tenancy file audit should actually check

A tenancy file audit is worth doing on a schedule, not just when something's already gone wrong, because the whole point is catching gaps before a dispute or an inspection turns them into a live problem. A file can look complete at a glance — a signed agreement, some correspondence, a deposit reference number — and still be missing the specific evidence that would actually hold up under scrutiny.

Right to Rent evidence, for every occupier

The most common gap here isn't a missing check altogether, it's a check that only covered the named lead tenant on a joint tenancy, or one where the record doesn't clearly show which documents were seen and when — the specifics are covered in our full Right to Rent guide, and an audit should test the file against exactly that standard.

Deposit protection and prescribed information, as two separate checks

An audit needs to confirm both the certificate of protection and evidence that prescribed information reached every named tenant — checking one without the other is the single most common way a file audit gives a false sense of completeness.

The tenancy agreement itself

Beyond the standard clauses, it's worth checking the agreement actually reflects who's living at the property currently, that any right-of-access clause for safety inspections is clear (a gap that surfaces badly during an access dispute), and that any amendments made during the tenancy were properly documented rather than agreed verbally and never written down.

• –Right to Rent evidence for every named occupier, not just the lead tenant
• –Both the certificate of deposit protection and evidence prescribed information reached every tenant
• –A tenancy agreement that reflects who's actually living at the property, including any changes since it was signed
• –A clear right-of-access clause for safety inspections
• –Any mid-tenancy amendments documented in writing, not agreed only verbally

Auditing a random sample, not the tidiest files

It's tempting to check the files that come to mind easily — usually the newest, or the ones a team member happens to be proud of — but a genuinely useful audit pulls a random sample across the portfolio, including older tenancies that have been running quietly for years without anyone looking at the file since it was first opened. Those are usually where the real gaps live.

Building this into a rhythm rather than a one-off exercise

A single audit, however thorough, only tells you about that moment. The more useful version is a standing quarterly or twice-yearly check across a random sample of the portfolio, treated as routine rather than as a response to something having already gone wrong — the same logic behind renewing a tenancy against a proper checklist rather than letting a renewal just roll over unchecked.

Auditing the file against the tenancy, not a checklist

A file audit that works from a generic checklist tends to confirm that documents exist. A more useful audit works from the tenancy itself — its start date, its renewals, its changes of occupant — and asks whether the file reflects what actually happened. That catches the file which is complete for the original tenancy and silent on the two renewals since.

It is also the version that finds the awkward cases: a joint tenancy where one tenant was replaced, a property that changed landlord mid-tenancy, or a tenancy that continued past its fixed term without anyone documenting what it became.

Common mistakes

• –Auditing against a generic checklist rather than the tenancy's actual history
• –Files complete for the original tenancy and silent on renewals
• –Changes of occupant not reflected in the documentation
• –No record of which version of a document was used
• –Auditing existence without checking whether documents are still current
• –No follow-up, so the same gaps appear at the next audit