Right to rent check automation for UK letting agents

Right to rent check automation sits at an intersection most letting agencies find uncomfortable: mandatory compliance obligations that arrive on a predictable schedule, executed by a process that depends on someone remembering to act. Every tenancy in England requires a check before the tenancy begins. For tenants with time-limited permission to remain in the UK, a follow-up check must happen before that permission expires. Across a portfolio of fifty or a hundred active lets, those deadlines accumulate. Missing one is not a paperwork oversight. It carries civil penalties and, for repeat or knowing failures, criminal liability. This is a job where AI can carry significant administrative load without replacing the human judgement the law requires.

Why right to rent tracking breaks down in practice

The initial check sounds manageable. Before an adult moves in, you verify their right to rent by examining an original document or using the Home Office online service for those with digital status. You record what you checked, when and the outcome. The check is done.

The follow-up requirement is where manual tracking breaks down.

If a tenant holds time-limited leave to remain in the UK, the initial check establishes their right to rent for a defined period. That permission has an expiry date. Under the Right to Rent scheme, the landlord or agent must conduct a follow-up check before that date passes. If the tenant's status has changed, an obligation to notify the Home Office may arise.

In a branch managing sixty active lets, expiry dates are scattered across the year. A tenant with a two-year visa might have moved in eighteen months ago. Another holds a student visa with twelve weeks left to run. A third has indefinite leave to remain and needs no follow-up. Tracking which tenants hold time-limited permission, when their leave expires and when the follow-up must take place is not complex analysis. It is the kind of work that falls to whoever has capacity, which in a busy lettings office can mean it does not surface until it is close to too late.

The consequence of a missed follow-up is not a note on the file. Civil penalties apply to landlords and agents who fail to carry out required checks. Repeat failures carry higher consequences. The Home Office conducts spot checks, and TPO complaints around missed procedure are possible where the agency had a known obligation and did not act on it.

Most letting agents understand the rules. The gap is in the tracking across a moving portfolio.

What right to rent check automation actually does

The shape of an AI agent built for right to rent check automation follows the same event-triggered loop that applies to any compliance-driven lettings workflow. Trigger, read context, reason, take action, log.

Initial check prompt. The trigger is a new application reaching the stage in the CRM where identity and right to rent verification is required. The agent reads the tenancy record, identifies the adult occupants and prompts the responsible property manager. The prompt includes each occupant's name, the property address, the expected tenancy start date and a reminder of what the check covers. Nothing is decided by the AI. The purpose is to get the right task in front of the right person at the right moment, with the relevant information already assembled.

Where an applicant uses the Home Office online service, the agent can draft the message requesting their share code. That draft lands in the property manager's review queue via the inbox copilot, ready to send or edit before anything goes out.

Expiry tracking and follow-up prompts. After the initial check is completed and the outcome is logged in the CRM, the agent reads the recorded permission expiry date. It calculates the window for the follow-up check and sets a watch on that date. Two to four weeks before the expiry, the property manager receives a clear prompt: the tenant's name, the property address, the expiry date and the recorded basis of the original check. If the first prompt is not actioned, a second arrives. No one needs to remember to check the diary.

Audit record prompts. After each check is completed, the agent prompts the property manager to log the outcome in the CRM: what was examined, the date, the expiry date of any time-limited permission and who conducted the check. This creates the record the agency needs if a Home Office inspection takes place.

All three loops are prompting and logging, not determining. The AI does not assess documents. It does not decide whether a tenant has the right to rent. It surfaces the task at the right time and records what happened. The determination and the document review remain a person's responsibility throughout.

This is the same underlying pattern Sortd applies across lettings AI automation more broadly: each compliance-driven workflow is a defined trigger, a clear action and a logged result. The agent handles the tracking. The person handles the decision.

What it looks like for a letting agency

Take a two-branch independent managing ninety active lets across a mix of students, professionals and overseas workers. Four property managers share responsibility for compliance across the portfolio.

Without a systematic tracking process, follow-up check dates are managed through CRM reminder entries that property managers set individually when the initial check is completed. In a busy quarter, the reminder gets created when there is time, which means some expiry dates sit in the system without a watch on them.

With right to rent check automation in place, the picture is different.

A new application comes in for a one-bed flat. The applicant holds a biometric residence permit. The initial right to rent check is completed on the tenancy start date and the permit expiry date is logged in the property record. The next morning, the agent reads the record and sets a follow-up watch for forty days before that expiry date.

Fourteen months later, the forty-day prompt lands in the property manager's Slack feed: a clear message that the tenant's permit expires on a specific date, that the last check was conducted on the tenancy start date and that a follow-up is required. The property manager sees it alongside their other flagged tasks that morning, not buried in a CRM reminder that requires them to actively search for it.

The same loop applies to student tenants on time-limited visas and anyone else whose permission to remain has a defined end date. The tracking runs quietly in the background. The property manager receives a timely, clear prompt. The check itself is a person examining a document or running a share code through the Home Office service. The administration around it is handled without anyone needing to monitor a spreadsheet.

Compliance and integration reality

Right to rent checks are a legal obligation, not a discretionary process. They sit alongside AML requirements, deposit protection and inspection scheduling as things the agency must do and be able to demonstrate it has done. Compliance-first design matters here, and it is worth reading how that principle applies across the full picture of AI estate agency compliance before any build goes to live data.

UK GDPR applies to the data involved in right to rent tracking. Tenant identity information is personal data. The lawful basis for processing it in this context is legal obligation: the Immigration Act 2014 requires the check, and processing data to carry it out is necessary to comply with that legal duty. The agent reads the minimum required to do the job: name, recorded expiry date and tenancy record. A data processing agreement with the AI provider is required before any live data is processed. Data must be held in UK or EU infrastructure. Sortd runs on UK and EU infrastructure by default.

The agent does not conduct the check and has no access to document verification systems or Home Office lookup services. That boundary is written into the build specification, not left to the model's discretion. On the TPO side, the expectation is accurate record-keeping and timely action. The automation delivers both: the prompt arrives in time to act, and the outcome is logged to the CRM.

Sortd builds right to rent automation on top of the CRMs UK independent agencies actually use: Reapit, Alto, Jupix, Vebra, Dezrez, agentOS. Where the CRM holds the tenancy record and the permission expiry date, the automation is straightforward to implement. Where those fields are not consistently populated, the first step is establishing the record-keeping discipline the automation depends on.

Property Industry Eye carries regular coverage of enforcement activity around the Right to Rent scheme and is a useful reference as the scheme continues to develop.

How to get started

The right starting point for any letting agency evaluating right to rent check automation is to audit the current process. How are follow-up check dates recorded in your CRM? Who monitors which tenancies have time-limited permissions outstanding? What happens to that tracking when a property manager is on leave or leaves the branch?

If the honest answer is that follow-up checks depend on individual CRM reminder entries rather than a centralised, monitored workflow, that is where the automation belongs. A well-built agent can prompt, track and log right to rent follow-ups on any CRM that holds the tenancy record and the permission expiry date. The build is not complicated. The value is in the reliability: no check date falls through because no one happened to look.

Sortd starts with a discovery call and a free working version of the agent, built against a test slice of your CRM. You see how the prompting and logging work on your own tenancy data before committing to a full build.

If right to rent compliance is a genuine operational risk for your agency, start with a conversation.