Section 21 is gone: your Monday morning workflow change

On 1 May 2026, Section 21 was abolished under the Renters' Rights Act. You already know that. What I want to talk about is what happens on the Monday after. Specifically, what your team is doing at 9am that they haven't changed yet.

The agents who get hurt by this change won't be the ones who missed the headlines. They'll be the ones who read everything, nodded along, and then went back to managing tenancies exactly as before.

What actually changed, in operational terms, not legal ones

Before 1 May, if a tenancy wasn't working, you had an exit route that required almost no documented justification. Serve notice, wait out the period, apply to court if needed. The evidence burden was low because the legal bar was low.

Section 8, which is now your only possession route for the vast majority of cases, works the other way around. Every ground you rely on must be supported. Rent arrears require a payment history that holds up to scrutiny. Anti-social behaviour requires contemporaneous records, not a retrospective summary written the week before you file. Property condition disputes require inspection records that are dated, signed, and evidenced.

The law hasn't changed what agents need to do day-to-day. It has changed the consequences of doing it badly.

The five workflow steps that now need a documented evidence trail

Most lettings operations already do some version of these. The problem is that "some version" and "documented and retrievable" are not the same thing.

1. Rent payment tracking. A bank statement or portal export pulled when something goes wrong is not enough. You need a continuous, timestamped log that shows every payment, every shortfall, and every communication sent in response. If you're manually updating a spreadsheet at the end of the month, you have a rent record. You don't have an evidence trail.

2. Inspection records. The inspection report your team fills in on a tablet, exports as a PDF, and stores in a folder labelled by address is not enough on its own. You need date, time, who conducted the inspection, tenant notification sent and when, and photos with metadata intact. A Word document with "inspection done" and a few bullet points will not serve you in a possession claim.

3. Maintenance requests and responses. Every request logged, every response sent, every contractor visit recorded. If a tenant later claims you ignored a damp issue for six months and you can't produce a timestamped thread, you're arguing from memory against their written records.

4. Tenancy breach communications. When you contact a tenant about arrears, a lease violation, or a noise complaint, that communication needs to be logged centrally, not sitting in someone's email outbox. When that team member leaves, the record leaves with them.

5. Right to rent and compliance check renewals. These were an admin task before. They're now a possession ground under Section 8 if they expire and you haven't chased them properly. "We sent a letter" is not documentation. A sent letter, a delivery confirmation, and a follow-up log is documentation.

Why "we'll take better notes" is not an answer

I've heard this in almost every conversation I've had with letting agents this spring. The intention is genuine. The problem is that note-taking is a habit that degrades under pressure, and possession situations are always high-pressure.

What a verifiable audit trail actually looks like is this: a record that was created at the time the event happened, by a defined process, stored in a place that doesn't depend on a specific person to retrieve it. Not a note written from memory the following week. Not a spreadsheet that one person maintains and three people depend on.

Here's a minimal schema for what an inspection record should capture as structured data rather than a narrative document:

inspection:
  property_id: "LET-0042"
  date: "2026-04-18"
  time: "10:30"
  conducted_by: "Sarah M."
  tenant_notified_date: "2026-04-11"
  tenant_notified_method: "email"
  tenant_present: false
  condition_items:
    - area: "kitchen"
      condition: "satisfactory"
      notes: "Minor limescale on tap fittings"
      photo_refs: ["img_001.jpg", "img_002.jpg"]
    - area: "bathroom"
      condition: "concern"
      notes: "Mould visible on ceiling, reported by tenant Feb 2026; contractor visit logged 2026-02-28"
      photo_refs: ["img_003.jpg"]
  signed_off: true
  signature_ref: "sig_0042_2026-04-18"

That's not a technical fantasy. It's what a properly designed inspection workflow captures automatically. The difference between that and a PDF report is that every field is queryable, every record is searchable, and when a solicitor asks for all inspection records showing the bathroom condition over a 12-month period, you can produce them in minutes rather than hours.

Where automation helps and where it doesn't

Automation is genuinely useful in three places here.

The first is communication logging. Every email, text, and portal message sent to a tenant should be captured automatically against their tenancy record. If your team is doing this manually (copying and pasting into a CRM or notes field), it will be done inconsistently. A workflow that logs outbound communications without requiring anyone to remember to do it is reliable in a way that human habits are not.

The second is payment history. If your accounting system and your tenancy management system aren't talking to each other, you're creating a manual reconciliation step that introduces gaps. Automated payment-to-tenancy matching, with alerts when a payment is missed or short, gives you a continuous record rather than a monthly snapshot.

The third is inspection scheduling and notification chains. Sending the required notice to tenants, logging the sent notification, and recording the inspection date can all be handled by a simple scheduled workflow. This isn't sophisticated. It's the kind of thing I've built in a couple of days for agencies who were managing it entirely through calendar reminders and follow-up emails.

Where automation can't help is the judgement layer. Whether a behaviour constitutes grounds for possession, whether a repair request signals something that needs legal advice, whether a tenant's circumstances warrant a different approach: those are human decisions. The workflow exists to make sure the evidence is there when a human needs to make a judgement call. It doesn't replace the judgement.

This is operational guidance, not legal advice. On edge cases and specific Section 8 grounds, check with your property solicitor.

The practical 30-day action list

If you're behind on this (and most independent agents are), here's how I'd sequence the next four weeks.

Week 1: Audit what you actually have. Pull five recent tenancies at random. Can you produce a complete rent payment log, all outbound communications, and the last two inspection reports within 20 minutes? If not, you know the gap.

Week 2: Fix the inspection process first. It's the most defensible record and the easiest to formalise. Agree on a structured report format, assign a named person to sign off each inspection, and decide where reports are stored. Not on someone's laptop. Shared, named, backed up.

Week 3: Centralise communication logging. This doesn't have to be automated immediately. Even a simple rule (every substantive tenant communication forwarded to a shared mailbox or logged in your tenancy system the same day) is better than the current state for most agencies.

Week 4: Connect your payment data. If your accounting and tenancy management systems can't produce a per-tenancy payment history on demand, that's the gap to close next. Whether that means a proper integration or a weekly automated export into a consistent format depends on what you're running.

The agents who have a reasonable process in place before their next possession issue will be the ones who spent a month getting this right before it became urgent. The ones who wait for the urgent moment will be building the evidence trail retrospectively, which is exactly the problem Section 8 was designed to expose.

This is a process design problem. It has a process design solution.

The same pattern shows up in AML compliance for estate agents: having a policy is not the same as having a workflow, and HMRC is now testing the latter. If you want help mapping your current process before you automate anything, that's what an AI Workflow Audit is for.