Renters Rights Act compliance for letting agents: what changed on 1 May
For most of a letting agent’s career, ending a tenancy was a document you produced. You served a Section 21 notice, you kept a copy, and if it came to it the court took the notice largely at face value. On 1 May 2026 that stopped. The Renters’ Rights Act 2025 abolished Section 21 no-fault evictions, converted every existing assured shorthold tenancy into an open-ended assured periodic tenancy, and left possession resting entirely on Section 8 grounds.
The legal summary is easy to recite. The operational consequence is the part that actually changes your week. Section 8 grounds are evidence grounds. Rent arrears, anti-social behaviour, breach of tenancy, damage caused by the tenant: each one has to be shown, not asserted. So the work moved. Renters Rights Act compliance for letting agents used to be a filing task you did once at the start of a tenancy and once at the end. Now it is a file you maintain continuously, because you never know which tenancy will need it, or when.
That is the shift worth internalising before anything else. You are no longer in the business of serving notices. You are in the business of keeping files that would survive a district judge reading them cold. The habit change lands on negotiators and property managers who were never asked to think like a case builder. A note that used to live in someone’s head, or in a reply buried three deep in a shared inbox, now has to sit in a place a court would accept months later.
The 31 July cliff for old Section 21 notices
There is a hard date three weeks out, and it catches agencies that assume the old rules lapsed quietly. A Section 21 notice served before 1 May 2026 is only still enforceable if the landlord applied to court by 31 July 2026. Miss that window and the notice is dead. Worse, serving a fresh Section 21 now, out of habit or from an old template still sitting in your case management system, risks a civil penalty of up to £7,000.
So this week, before the deadline, the job is boring and urgent. Pull an inventory of every outstanding Section 21 notice across your managed portfolio. For each one, make a decision with the landlord: apply to court now, or abandon it and move to a Section 8 route. Then minute that decision against the tenancy, with the date and the name of whoever made it. If a landlord later asks why a notice was allowed to expire, the answer needs to be on file, not in someone’s recollection of a phone call in July.
None of this is legal advice, and individual cases belong with your solicitor. But the operational reflex is simple: inventory, decide, record. An agency that cannot produce that list of outstanding notices quickly is already behind, and the fix is an afternoon of admin now rather than an argument with a landlord in August.
Section 13 is now a process, not a letter
Rent increases changed shape on the same date, and this is where the “file, not letter” idea becomes concrete. A statutory rent increase now runs on a Section 13 notice using the prescribed Form 4A, with a notice period doubled from one month to two. You can raise rent once in any twelve months, never in the first twelve months of a tenancy, and any rent-review clause written into the tenancy agreement is now void. If the tenant challenges, the First-tier Tribunal cannot set the rent higher than you proposed, cannot backdate it, and can defer an increase by up to two months where the tenant would face hardship. The tenant pays a £47 fee to bring that challenge.
Read that as a sequence, not a form. The figure you propose is now the ceiling, so proposing a hopeful number and negotiating downward is over. You propose a realistic figure, you attach the evidence that supports it, and you diarise the two-month clock so nothing is served late or backdated by accident. We wrote separately about using automation to draft the notice and pull local comparables, so I will not go over that ground again. The point for this piece is the process discipline wrapped around it: the right dates, the right form, in the right order, logged every single time.
The evidence trail, itemised
Here is the uncomfortable part. Most agencies already hold the evidence a Section 8 case needs. They just hold it in four places at once: the shared inbox, the property management system, a spreadsheet a negotiator keeps, and the memory of whoever handled the tenancy. A possession claim needs it in one place, dated and ordered. The trail, by category, looks like this.
Arrears: a clean ledger showing every charge and payment by date, plus every reminder you sent, with timestamps. A judge wants to see that the tenant knew and was chased, not simply that money is owed.
Anti-social behaviour: an incident log with dates, times, what happened, who reported it and what you did about it. Three entries written the week before a hearing read very differently from a log built as events occurred.
Disrepair responses: who reported what and when, the works order that followed, and evidence the work was completed. This matters defensively too, because a tenant’s disrepair counterclaim is answered by exactly this record.
Certificates, current and historic: an EICR every five years, the annual gas safety certificate, a valid EPC, smoke and carbon monoxide alarm checks, the deposit protected within thirty days, Right to Rent checks on file. Not just the current documents, but the history, because a possession claim can turn on whether a certificate was valid on the day a notice was served two years earlier.
Communications: every message to and from the tenant, filed against the tenancy rather than lost in an inbox thread. The tenancy file should read as one continuous story, from the first viewing to the current month.
Where automation earns it
This is the work no agency wants to give a person full time, and the work that quietly decides cases. It is also, almost exactly, what good automation is for. The aim is a file that assembles itself while people get on with the actual day.
In practice that means a handful of plain mechanisms. Every email and message tied to a tenancy is filed against it automatically, so the record builds itself rather than depending on someone remembering to save an attachment. Certificates are read on arrival, the expiry date logged, the next reminder set without anyone typing it into a diary. Reminder sequences for arrears or renewals leave their own audit trail, so the log of what was chased is a by-product of the chasing rather than a separate chore. And on demand, a possession-readiness snapshot per tenancy shows what is on file and what is missing, before a landlord asks rather than after.
The non-negotiable is the human gate. Nothing legal leaves the building unsigned. The system prepares, orders and flags the gaps; people read, decide and approve. That line matters for a second reason. This data is tenants’ personal information, and the ICO’s guidance on AI and data protection is worth reading before you route any of it through a system. Automation is not an excuse to be casual about who can open a tenancy file. This is the kind of quiet, compliance-shaped work our property management automation is built around: the record stays complete without a compliance officer spending a week rebuilding it from four systems the night before a hearing.
Phase 2 is coming, and the trail is the hedge
The Act is not finished arriving. A mandatory private-rented-sector landlord database is expected to begin its regional rollout in late 2026, and an ombudsman service is being stood up after that, with membership expected to become mandatory in time. Dates beyond that are not fixed, so it is worth planning for the direction of travel rather than pencilling in a diary entry that will move.
The agencies that started keeping the trail now will barely notice when the database and the ombudsman land, because a complete, dated file per tenancy is what both will want to see anyway. The ones still holding evidence scattered across four systems will feel every new obligation as another scramble, another late night, another landlord asking a question the file should already answer.
We spent eight years inside UK lettings before we started building software, so this is not a theory about someone else’s job. Compliance deadlines, maintenance coordination, the landlord who wants an answer today: we ran that desk. If you want the evidence trail to hold itself together before 31 July and stay that way afterwards, that is a conversation we are happy to have. Thirty minutes, and we will tell you honestly whether it is worth automating yet.
