What the Renters' Rights Act does to your mid-tenancy communication workflow

A lettings agent in Bristol told me recently that her team's renewal reminder sequence was still firing. Twelve-week emails, six-week calls, four-week decision deadlines. Going out to tenants on periodic tenancies that had no end date to renew from. Nobody had turned it off. Nobody had noticed.

That is the problem I want to talk about.

The Renters' Rights Act didn't just remove Section 21. It removed the fixed end date that every downstream workflow in your business was quietly depending on. Renewal reminders, inspection triggers, rent review windows, notice calculations: all of it was calibrated to a clock that no longer exists. What replaces it isn't a new clock. It's a different model entirely.

This post discusses workflow design in the context of the Renters' Rights Act 2025. It does not constitute legal advice. For guidance on specific notices or grounds, consult a qualified solicitor or your professional association.

What actually changed on day one

Under the old model, a tenancy had a shape. It started, it ran for six or twelve months, it either renewed or it didn't. That shape gave lettings agents a natural calendar. You knew when to contact tenants, when to serve notices, when to prepare for a void.

From the Act's commencement, all new tenancies are periodic from the start. There is no fixed term. There is no renewal. There is no expiry date to anchor anything to.

The practical consequence is that your mid-tenancy workflow, the one that runs between move-in and move-out, now has to operate without a known end point. That sounds obvious when you say it plainly. It was not obvious to the dozens of property management platforms and CRMs that spent years building date-triggered automations around six-month and twelve-month intervals.

Fixflo, for instance, is excellent at maintenance logging and contractor coordination. But if your Fixflo-adjacent CRM is sending inspection prompts based on a calculated tenancy anniversary that assumes a fixed-term rhythm, those prompts are now firing on an assumption the law no longer supports. The tool isn't broken. The workflow design underneath it is.

The fixed-term safety net is gone

Section 21 was many things, but operationally it functioned as a backstop. If a tenancy became difficult, if rent was persistently late, if a landlord simply wanted possession, the fixed-term end date gave you a procedural route that required no stated reason. Agents built their risk tolerance around it.

That's gone. What remains is Section 8, and Section 8 requires you to evidence grounds. Ground 8 (mandatory, two months' rent arrears), Ground 10, Ground 11, Ground 14: these are the tools now. Each one requires documentation. Each one requires a paper trail that starts well before you ever file a claim.

This changes the communication workflow in a specific way. Under the old model, you could afford to be reactive in the middle of a tenancy because you had a procedural exit. Under the new model, every mid-tenancy interaction is potentially evidential. A rent arrears conversation in month three matters. A maintenance complaint that went unresolved matters. An inspection report that was never written up matters.

The workflow can't treat mid-tenancy comms as routine admin anymore. It has to treat them as a continuous record.

This connects to something I wrote about in the context of AML verification gates: the moment compliance depends on a paper trail, the workflow that creates that trail becomes the compliance function. The communication log is the evidence. If the log is patchy, the evidence is patchy.

Event-driven, not date-driven

The replacement model is event-driven. Instead of a calendar that counts down to a fixed end, you build a workflow that responds to things that happen.

Here is what that looks like in practice:

mid_tenancy_workflow:
  trigger_model: event_driven
 
  triggers:
    - event: rent_payment_missed
      day_0: flag_in_crm
      day_3: automated_sms_reminder_to_tenant
      day_7: agent_call_logged_with_outcome_note
      day_14: formal_written_notice_of_arrears_sent
      day_28: review_for_Section_8_Ground_8_eligibility
 
    - event: maintenance_request_raised
      day_0: log_in_fixflo_or_equivalent
      day_3: contractor_assigned_or_escalation_note
      day_14: resolution_confirmed_or_landlord_notified
      day_21: tenant_satisfaction_logged
 
    - event: periodic_inspection_due
      cadence: every_6_months_from_move_in
      output: written_report_stored_in_tenancy_file
      note: cadence_is_internal_policy_not_legally_mandated
 
    - event: rent_review_required
      trigger: landlord_instruction_or_market_review
      notice_required: Section_13_notice_minimum_2_months
      output: written_notice_served_and_logged
 
    - event: landlord_seeks_possession
      route: Section_8_only
      required: evidence_file_current_and_complete
      grounds_to_review: [Ground_8, Ground_10, Ground_11, Ground_14]
 
  removed_triggers:
    - fixed_term_expiry_reminder
    - renewal_offer_sequence
    - Section_21_notice_window_calculation
    - break_clause_calendar_alert

The removed triggers at the bottom of that block are the ones most likely still running in your system right now. They need to be found and switched off. Not because they cause legal problems in themselves, but because they create noise that distracts your team from the triggers that actually matter.

What your CRM is probably still doing wrong

Most property management CRMs were designed around the fixed-term model. That's not a criticism. It's a description of when they were built and what the law required at the time.

The problem is that many of them haven't been reconfigured for the new reality, and the vendors aren't always flagging it loudly. If your CRM has a field called "tenancy end date" that is auto-populating, that's a sign. If it's generating "renewal due" tasks on periodic tenancies, that's a sign. If your inspection schedule is triggered by a calculated date rather than a logged event, that's a sign.

Go into your system and look for any automation that references a tenancy end date, a renewal window, or a Section 21 notice period. Each one of those automations was built for a world that no longer exists. Some of them will be harmless. Some of them will be quietly misfiling your comms in a way that matters when you eventually need to evidence a Section 8 claim.

I've written before about how AI pilots fail when they accelerate a broken process. The same principle applies here without any AI involved. Automating the wrong workflow faster doesn't fix the workflow. It produces more of the wrong output with less human review.

Where to start this week

You don't need to rebuild everything at once. Two things matter before anything else.

First, audit your active automations. Pull a list of every scheduled task, email sequence, and CRM trigger that fires based on a tenancy date. Flag anything that references end dates, renewal windows, or Section 21. That list is your change backlog.

Second, build your Section 8 evidence habit now, not when you need it. For every tenancy where rent is late or a maintenance complaint takes more than two weeks to resolve: log it, date it, store it in the tenancy file. The habit costs almost nothing when things are going well. It costs a lot when you need it and it isn't there.

Once those two are done, review your rent review process. Section 13 notices require a minimum of two months' written notice to increase rent on a periodic tenancy. If your rent review workflow was built around a fixed-term renewal conversation, replace it with a notice-based process that starts earlier and creates a paper record.

None of this requires new software. It requires looking at what your existing software is doing and correcting the assumptions baked into it.

If you want a structured review of where your current workflow breaks, the AI Workflow Audit at Web Project Studios covers exactly this: mapping what your automations are actually doing against what the legal and operational model now requires, and designing the event-driven replacement. The audit works whether you're running a single-branch operation or coordinating across multiple offices with different CRM configurations.

The Act didn't make lettings more complicated. It made the old shortcuts unavailable. Agents who move quickly on their workflow design will find the new model is perfectly manageable. Those who leave the old automations running will find out the hard way.

Sources and references

Renters' Rights Act 2025 (full text). Sections on abolition of fixed-term assured tenancies, periodic tenancy structure, Section 8 grounds for possession, and Section 13 rent increase procedure cited.

Housing Act 1988 (c. 50) (full text). Sections 8, 13, and 21 cited in the context of the pre-Act workflow model and the Section 8 grounds (Ground 8, Ground 10, Ground 11, Ground 14) that remain operative post-Act.

Sources verified on 2026-06-15. This post does not constitute legal advice.