Field notes
The Renters' Rights Act does not care how good your template is
25 May 2026
On this page
I have sat in lettings offices where the new AST template was printed, laminated, and placed on the branch manager's desk before the ink on the government guidance was dry. The document was immaculate. When I asked how they were going to evidence a Section 8 Ground 8 claim if rent arrears built across a periodic tenancy, the room went quiet.
The Renters' Rights Act is coming. Most agents know that. What fewer have worked out is that the Act does not primarily test what your tenancy agreement says. It tests what you did, in what order, and whether you can prove it.
This post discusses workflow design for lettings compliance. It does not constitute legal advice. Consult a qualified solicitor for advice specific to your circumstances and portfolio.
The abolition of Section 21 removes the no-fault route. That is the headline. But the practical consequence is not that possession becomes impossible. It is that possession now depends entirely on evidenced grounds under Section 8, and the evidence burden sits with you, the agent, from the first day of the tenancy.
Under the old regime, a well-drafted AST bought you options. If a tenancy became difficult, Section 21 was the exit that did not require you to have documented anything in particular. You served the notice, waited out the period, applied to court if needed. The document was the process.
That exit is gone. What replaces it is a set of grounds that each carry their own evidentiary requirements. Ground 8 (mandatory rent arrears) requires you to show the arrears existed at the time of service and at the date of the hearing. Ground 10 and Ground 11 require a pattern. Ground 14 (antisocial behaviour) requires a record of complaints, responses, and escalations. None of that evidence lives in a tenancy agreement. It lives in your workflow, your CRM, and your rent account.
The agent who updates the template but not the process has a beautiful document and nothing to take to court.
Under the Act, all assured tenancies become periodic from the outset. There is no fixed term that expires into a new agreement. There is one tenancy, running continuously, with rent due on a rolling basis.
This sounds administrative. It is actually a workflow design problem.
Most lettings management systems were built around the fixed-term model. Renewal triggers, template generation, and re-signing events were the process milestones. They gave agents natural checkpoints: review the rent, update the terms, get fresh signatures. The periodic model removes those checkpoints unless you build them deliberately.
What needs to exist instead is a proactive review cycle that does not depend on a renewal event. That means a scheduled rent review process with documented rationale, a record of how any proposed increase was communicated (the Act requires use of a prescribed form for rent increases), and a log of the tenant's response or acceptance. If you skip the prescribed form and simply issue a new rent figure, you lose the ability to rely on the rent account as accurate evidence in a possession claim.
I have written before about how sequence failures in lettings workflows tend to surface at the worst possible moment. The periodic tenancy problem is a cleaner version of the same issue: the process gap is invisible until you need the evidence, and by then it is too late to go back and create it.
A Section 8 claim is not a document you file. It is the end point of a sequence that should have started months or years earlier.
Consider a Ground 8 claim. You need to show arrears of at least two months at the time of serving the notice, and still present at the hearing. County court judges are not sympathetic to agents who cannot produce a clean rent ledger. They are actively hostile to agents whose rent ledger shows unexplained gaps, credits applied without notes, or payment records that do not reconcile with the bank statements the tenant produces.
That ledger quality is a workflow output. It is the result of how rent is recorded when received, how arrears are flagged, and how every communication about the arrears is logged against the tenancy record. If your property management software does not automatically timestamp correspondence and link it to the tenancy, someone has to do that manually. Most agencies do not have a process for that. They have a habit, and habits are inconsistent.
Ground 14 is harder still. Antisocial behaviour claims require you to show what was reported, when, what action you took, what response you received, and what escalation occurred. If your process for handling complaints is an email to a shared inbox that may or may not get filed, you do not have a process. You have a prayer.
Here is what a judge sees when a Section 8 possession claim arrives. Not the tenancy agreement. The following:
section_8_evidence_bundle:
tenancy_record:
- tenancy_start_date: confirmed
- periodic_commencement: confirmed
- rent_review_history:
- each_review_date: required
- prescribed_form_served: required
- tenant_response_logged: required
rent_account:
- payment_history: complete and reconciled
- arrears_flags: timestamped
- correspondence_on_arrears:
- initial_contact: dated and logged
- payment_plan_offered: yes/no, documented
- further_escalation: dated and logged
ground_specific_evidence:
ground_8:
- arrears_at_notice_service: calculated and evidenced
- arrears_at_hearing_date: calculated and evidenced
ground_14:
- complaint_log: dated, source identified
- agent_response: dated, action recorded
- escalation_record: dated, outcome noted
notice:
- correct_form_used: confirmed
- correct_notice_period: confirmed
- service_method_evidenced: confirmedEvery item in that bundle is a workflow output. The tenancy agreement contributes one line: confirming the start date. Everything else is process.
If you cannot produce a clean version of that bundle for every tenancy in your portfolio, your template quality is irrelevant.
The Act's commencement date has moved before and may move again, but the direction is fixed. Here is how I would approach the next ninety days.
First two weeks: audit your current state. Pull five active tenancies at random. For each one, ask: could I produce the evidence bundle above right now? Where are the gaps? This is not a compliance exercise. It is a process diagnostic.
Weeks three and four: fix the rent account workflow. Every payment should be logged with a timestamp, a source, and a reference. Every arrears flag should trigger a documented contact attempt within a defined window. If your property management software does not enforce this, build a checklist that does.
Month two: build the periodic review cycle. Define a review cadence (annually is standard, quarterly for higher-risk tenancies). For each review, the workflow should include: rent assessment, prescribed form generation if an increase is proposed, a log entry regardless of outcome, and a calendar trigger for the next review.
Month three: create the complaint and escalation log. This does not need to be sophisticated. A shared document with columns for date, tenancy reference, complaint source, action taken, and outcome is sufficient. The requirement is that it exists, that it is used consistently, and that it is linked to the tenancy record.
The agents who will struggle when the Act is fully in force are not the ones with bad templates. They are the ones who confused document quality with process readiness, and found out the difference in a county court hearing.
If you want a clearer picture of where your workflow actually stands, the AI Workflow Audit is designed to map what exists against what a post-Section 21 compliance posture actually requires. It is not a legal review. It is a process review, which is the thing most agencies have not done and most need.
For a broader look at how process gaps compound over time in lettings compliance, the piece on AML workflow failures in estate agency covers the same pattern in a different context. The gap between the policy document and the actual log is always where the exposure lives.
- Renters' Rights Act 2025 (c. 26) (full text). Abolition of Section 21, periodic tenancy provisions, and prescribed rent increase forms cited.
- Housing Act 1988 (c. 50) (full text). Section 8 possession grounds cited: Ground 8 (mandatory rent arrears), Ground 10 (discretionary rent arrears), Ground 11 (persistent delay), Ground 14 (antisocial behaviour).
Sources verified on 2026-05-24. This post does not constitute legal advice.