Keeping tenancy reviews on track without a renewal date

For years, the tenancy renewal did more than extend an agreement. It gave the team a reason to open the file.

That date forced a check. Has the landlord confirmed their plans? Is the rent right? Are the safety documents current? Did the tenant raise repairs that were never closed?

The renewal deadline prompted work that might otherwise have been postponed.

That matters because England’s lettings workflow changed on 1 May 2026. GOV.UK’s Renters’ Rights Act enforcement guidance for landlords and agents says the new restrictions apply to assured tenancies in the private rented sector from that date. The current GOV.UK renting out property guidance describes assured periodic tenancies as the most common tenancy type.

This is not legal advice. Letting agents should take advice on the rules and their own contracts. Operationally, one point is clear: if your branch used fixed-term renewal to tidy the file, chase decisions, and reset the landlord relationship, you need a replacement.

The renewal date was doing hidden work

Look at what happened around that date. Someone checked whether the tenant wanted to stay. Someone asked the landlord about rent. Someone reviewed deposit protection, certificates, right to rent status, repairs, arrears, contractor issues, and the management service.

The fixed term created pressure. Even imperfect pressure gives the branch a reason to make decisions before the file drifts.

When tenancies run periodically, the work does not disappear. It becomes less visible. The tenant may stay, the landlord may assume everything is fine, and the property manager may be dealing with urgent repairs elsewhere. The administrator may only touch the file when a document expires or a tenant complains.

A lack of complaints does not tell you whether repairs, updates, and landlord decisions are up to date. The team needs a regular way to review them.

The old renewal process often disguised weak management because it forced a catch-up once or twice yearly. Set review dates in the CRM rather than relying on an agreement’s end date to prompt the work.

Set a schedule for tenancy reviews

Use a mix of regular reviews and checks prompted by changes in the tenancy:

The key is ownership. “Review property” is too vague. A useful task says who owns the review, what must be checked, what evidence should be attached, and what decision is needed.

For example, a monthly portfolio scan might ask which tenancies have had no landlord update in 90 days, which repairs are overdue, which documents are missing, and which properties have no next review date.

Add a review date to any property that does not have one.

Keep a current tenancy summary with the documents

Keeping the signed agreement is only part of the job. Historic documents still matter, including old ASTs, deposit evidence, prescribed information, inventories, certificates, right to rent records, notices, and correspondence. The branch also needs a current-tenancy view that answers, quickly, “What is true today?”

That view should pull together the tenancy type, occupation status, landlord instruction, tenant communication state, rent position, open repairs, safety documents, deposit evidence, notices, next review date, and responsible person.

The Property Ombudsman codes of practice for residential letting agents are a useful reminder that agency work is judged partly by communication, record-keeping, and complaint handling. When something goes wrong, the team needs to show what was said, agreed, chased, and decided.

That is why folder structure alone is not enough. A folder can hold the signed document. It cannot tell the property manager that the document is now relevant to an open rent review, unresolved repair, or new landlord instruction.

In AvaroAI, files can sit against the contact, property, listing, or task they explain. A repair photo belongs with the repair task. A landlord instruction belongs with the property and the decision it triggered. The point is that the next person opening the record can understand the work without reconstructing it from email.

Periodic tenancies make weak signals more important

Fixed-term renewal made one question obvious: “Are we renewing?”

Periodic tenancy management asks several smaller questions instead. Is the landlord still committed to letting the property? Is the tenant likely to stay, leave, challenge rent, or raise a complaint? Are repairs damaging trust? Has the branch documented advice, instructions, and follow-up properly?

These are not all legal questions. Many are service questions. A landlord who has heard nothing for six months may assume the agent is passive. A tenant whose repair updates are scattered across emails may assume nobody is in control. A manager looking across 200 managed properties needs to know which files are quiet because they are healthy and which are quiet because nobody has looked.

Use your system to find the tenancies that need attention, including those with overdue reviews or unresolved repairs.

In AvaroAI, search and filtering are built around operational questions: review due, task overdue, documents missing, communication stale, repair still open, landlord decision needed. Use those results to prioritise the work.

That distinction matters more when the old renewal checkpoint fades. Without a hard date forcing everyone to look, the system has to surface the records that deserve attention.

Build the review around decisions, not paperwork

Each review should identify the decisions the landlord or team needs to make and record the outcome. Should the branch review rent now, later, or not at all? Proceed with a repair, request a quote, or inspect first? Prioritise tenant stability or test the market? Prepare for sale, refinance, refurbishment, or continued letting?

The review task should capture the decision, who made it, the evidence used, and the next date to revisit it.

That pattern also protects the team. If a landlord later asks why rent was not increased, the file should show the discussion and instruction. If a tenant says a repair was ignored, the file should show access attempts, contractor updates, approval, and follow-up. If a manager takes over a portfolio, the record should show live decisions rather than disconnected notes.

We covered the broader tenancy memory problem in UK lettings break when tenancy memory lives in too many places. Here, the focus is on scheduling the reviews that keep those records current.

A practical periodic tenancy review workflow

Keep the routine simple enough for a colleague to follow when the usual property manager is away.

Here is a simple workflow:

1. Give every managed tenancy a next review date.
2. Tag the reason: rent, repair, document, landlord plan, tenant communication, arrears, complaint risk, or general check.
3. Run a weekly exception filter for overdue reviews and high-risk open tasks.
4. Run a monthly portfolio filter for files with no recent landlord or tenant update.
5. Attach supporting documents, photos, instructions, and messages to the relevant task or property record.
6. Record the decision in plain language, including who made it.
7. Set the next review before closing the current one.

Set the next date while the file is open so the tenancy comes up for review again.

For branches that used renewals as the big clean-up moment, the first month will feel awkward. There will be properties with no clear owner, missing documents, old repair notes, and instructions trapped in inboxes. That shows where operational risk already existed.

Do not try to fix the whole portfolio at once. Start with live managed properties where rent is due for review, a major repair is open, a tenant has complained, documents are missing, or the file has had no meaningful update for 90 days.

The branch still needs judgement

No system should decide whether a rent increase is fair, whether a landlord should serve notice, or how a legal requirement applies to a case. Those are judgement calls for the agency and its advisers.

The system’s job is to make sure the right person has the right context before the judgement call is made.

That means the property manager can see the last landlord conversation. The branch manager can see which reviews are overdue. The administrator can see which evidence is missing. The principal can see whether portfolio risk is growing before complaints or disputes make it obvious.

The old renewal date was a useful prompt, but it was never a complete management process. UK letting teams now need to make the prompt explicit.

Give each tenancy a responsible person, a reason for review, supporting records, and a next date. That helps the team spot work due before a complaint or missed deadline brings it to their attention.

Related reading

• UK lettings break when tenancy memory lives in too many places
• UK estate agency software has to connect sales and lettings work
• A real estate to-do list is only useful when it knows what the task belongs to