Summary

• Most void periods are not caused by residents leaving. They are caused by nobody asking them to stay early enough, and by the weeks that vanish between a resident deciding to go and a new one moving in.

• Automated renewals outreach means every resident hears from you at a fixed point before their tenancy anniversary or end date, on the channel they actually reply on, with a sequence that stops the moment they answer.

• The average void period in England was 24 days in January 2025, the longest since 2021. Cutting that to a handover of a few days is where the return is, and it is achievable with a process rather than a hiring spree.

Why do void periods happen even when residents are happy?

Because the renewal conversation starts too late, or never starts at all. A resident who has not heard from anyone by the time they start browsing listings assumes the decision is theirs alone to make, and makes it. By the time the notice arrives, your team has two months to re-let a home they could have kept.

The numbers are not small. The Goodlord Rental Index put the average void in England at 24 days in January 2025, the longest it had recorded since April 2021. Goodlord's own analysis puts the longer-run average from 2022 to 2025 at around 19 days. On a £1,400-a-month home, a three-week void costs just under £1,000 in rent that never arrives. In a 200-home building where a third of residents move on each year, that is around £65,000 a year, before you count cleaning, re-marketing and the leasing hours spent replacing a resident you already had.

Across a Build to Rent or co-living portfolio, renewals are the cheapest occupancy you will ever secure. No portal fees, no viewings, no referencing, no void. The problem is that renewals work is repetitive, date-driven and easy to let slip when the leasing inbox is full. That is exactly the kind of work that should run itself.

How far ahead should renewal outreach start?

Ninety days before the tenancy end date or anniversary, with the first message a check-in rather than an offer. That gives you time to fix anything that would make a resident leave, price the renewal properly, and still have a full two-month re-let window if they go anyway.

A practical timeline for a Build to Rent building looks like this:

• Day 90: a personal check-in. How is the home, is anything outstanding, are their plans changing. Any maintenance issue raised here gets fixed before it becomes a reason to leave.

• Day 75: the renewal offer, with the new rent and any incentive, sent on the channel the resident already uses with you.

• Day 60: a follow-up to anyone who has not replied, and a handover to a human for anyone who has pushed back on price or raised a problem.

• Day 45: a final nudge. Anyone still silent is treated as a probable move-out and the home goes into pre-marketing, so the re-let starts before the notice does.

In England the calendar changed on 1 May 2026, when the Renters' Rights Act made all private tenancies periodic and set resident notice at two months. There is no longer a fixed term to renew, so the renewal conversation is now anchored to the annual rent review and to the tenancy anniversary rather than a contract end date. The logic above still holds; the trigger date is simply the anniversary. Student accommodation runs on its own cycle, with rebooking for the next academic year typically opening in the winter term, so the same sequence starts earlier and runs against the rebooking deadline instead.

How do you automate renewals outreach across a portfolio?

Four steps, and the first one is the one most teams skip.

1. Get the dates out of the property management system. Tenancy end dates, anniversaries and current rents live in your PMS. If your outreach tool cannot read them directly, someone is exporting a spreadsheet every month, and the month that gets missed is the month the voids appear. The integration is the automation; everything else is messaging.

2. Define the audience rules once. Who gets the sequence, who is excluded (residents already in arrears, residents who have given notice, homes earmarked for refurbishment), and when it starts. Set the rules at portfolio level so a new building inherits them on day one rather than getting its own version.

3. Write the sequence once, for every channel. Email, WhatsApp and SMS behave differently. A renewal offer that reads well as an email is far too long as a WhatsApp message. Write the message once and let the tool adapt the format, rather than maintaining three versions that drift apart.

4. Make it stop. The single most important rule in any renewals sequence is that it halts the moment a resident replies, and that reply lands with a person. Nothing damages a renewal faster than a resident who has said yes receiving a third automated reminder asking whether they have decided.

What should the renewal sequence actually say?

Less than you think, and nothing that reads as a template. Residents know what a mail-merge looks like. The first message should read like it came from the person who runs their building, because as far as they are concerned, it did.

Three things belong in a renewal sequence: the practical facts (date, rent, how to confirm), a real question that invites a reply (is anything in the home not working as it should), and a clear route to a human for anyone who wants to negotiate. Incentives can go in the offer message if you use them, but the check-in should never carry one. Leading with a discount tells the resident you expected them to leave.

The tone matters more than the offer. An 8 per cent rent increase delivered after a fixed repair and a friendly check-in lands very differently from the same increase arriving cold in a formal letter.

How does automating renewals improve retention rates?

It removes the two failure modes that lose residents who would have stayed: outreach that starts too late, and outreach that does not happen at all because someone was on leave. Every resident gets the same well-timed sequence regardless of how busy the team is that week.

It also surfaces the reasons people leave while there is still time to act on them. A resident who mentions a broken extractor fan at day 90 is a maintenance ticket. The same resident who mentions it in their notice email is a void. Automated check-ins turn the second case into the first.

The effect on the team is just as direct. When the timing, chasing and channel management are handled, the renewals work that remains is the part that needs a person: the price conversation, the difficult case, the resident who wants to move to a bigger home in the same building. That is a better use of a community manager than copying dates into a spreadsheet.

How do you measure whether it is working?

Track four numbers by building, and compare them to the same period last year. Renewal rate: the share of residents reaching their anniversary or end date who stay. Average void days per turnover: the gap between one tenancy ending and the next starting. Notice-to-relet time: how quickly a home that is leaving goes to market, which the day-45 pre-marketing step should shorten. And reply rate on the first check-in, which tells you whether the message and channel are right.

If renewal rate rises and void days fall, the process is working. If reply rates are low, the message or the channel is wrong before anything else is.

What does this look like with Vinny?

Vinny is the AI teammate for property teams, and renewals are one of the jobs it takes on. It reads tenancy dates from your property management system, enrols residents into a renewal sequence at the point you set, and runs that sequence across email, WhatsApp and SMS from a single message you write once. Sequences stop as soon as a resident replies, and the conversation lands with your team. A dry-run mode shows exactly who would be enrolled before anything is sent.

On the reporting side, Vinny's portfolio dashboard tracks occupancy and voids by building and flags residents whose messages show frustration, so a problem that would end in a notice gets picked up while it is still a repair.

If your team is spending its weeks chasing renewals by hand, or watching homes sit empty for three weeks between residents, book a demo and we will show you how the sequence runs against your own tenancy dates. For the leasing side of the same problem, start with our guide to what an AI leasing assistant does.

Frequently asked questions

What is a void period in property management?

A void period is the time a rental home sits empty between one tenancy ending and the next beginning. No rent is collected, but service charges, utilities, council tax and marketing costs continue, so every void day is a direct cost to the operator.

How long is the average void period in the UK?

The Goodlord Rental Index recorded an average void of 24 days across England in January 2025, the longest since April 2021, with a longer-run average of around 19 days between 2022 and 2025. Well-run Build to Rent buildings target a handover measured in days, not weeks.

When should you start renewal outreach with a tenant?

Around 90 days before the tenancy end date or anniversary. That leaves time to resolve any issue that might prompt a move-out, agree the renewal, and still have a full two-month re-let window if the resident decides to leave.

Does the Renters' Rights Act change how renewals work?

In England, yes. From 1 May 2026 private tenancies are periodic rather than fixed-term, so there is no contract end date to renew. Renewal outreach is instead anchored to the tenancy anniversary and the annual rent review, and residents can leave on two months' notice at any time, which makes proactive retention more important, not less.

Can renewals be automated without losing the personal touch?

Yes, if the sequence is written in a human voice, stops the moment a resident replies, and hands every reply to a named person. Automation should handle the timing and the chasing. People should handle the conversation.