The systems a modern lettings agency runs on (and where the hours go)

The short answer

Most agencies do not have a software problem so much as a seam problem. The core lettings platform usually does its own job reasonably well. The time goes where information has to cross from one place to another, and where a date in a calendar turns into a chain of emails, phone calls and follow-ups.

That matters because it changes what you should buy. If the hours are at the seams, a newer platform with the same seams will not give them back. If the hours are in recurring admin, the fix is usually process and automation rather than a replacement. And if the numbers turn out to be small, the honest answer is to leave things as they are. The rules described below apply to England; Wales, Scotland and Northern Ireland differ.

The systems a lettings agency actually runs on

Whether it is one product or eight, every lettings operation has to do these jobs somewhere:

• Properties and applicants. Listings, portal feeds, enquiries and viewings. Usually the part of the stack people think of as "the CRM" — see sales and CRM.
• Referencing and Right to Rent. Checking the tenant can afford the rent and has the right to rent in England, before the tenancy starts.
• Tenancy agreements and signing. The contract itself, now written for periodic tenancies.
• Deposit protection. A government-approved scheme, with the deposit protected and the prescribed information given within 30 days.
• Rent and client accounting. Receipts, arrears, deductions, payments out to landlords and client money controls — see finance and invoicing.
• Maintenance and contractors. Tenant reports a fault, agent logs it, landlord approves, contractor attends, invoice arrives — see operations and scheduling.
• Compliance certificates. Gas safety, electrical inspection, alarms and the dates attached to each — see compliance and certification.
• Landlord reporting. Statements, documents and updates, increasingly through a client portal.

None of these is exotic. The difficulty is that one tenancy touches almost all of them, and each one wants the same facts: who the tenant is, which property, what rent, which dates.

The compliance calendar, in arithmetic

Compliance is where lettings admin stops being occasional and becomes constant. Two recurring duties alone set the rhythm in England:

• A gas safety check every 12 months, with a copy of the record given to the tenant within 28 days of the check, and to new tenants before they move in.
• An electrical installation inspection at least every five years (the EICR), with a copy to the tenant within 28 days, and any required remedial work done within 28 days or sooner if the report says so.

Take an illustrative portfolio of 100 managed homes, all with gas. That is 100 gas checks a year and 100 ÷ 5 = 20 electrical inspections:

100 + 20 = 120 certificate events a year — 120 ÷ 52 ≈ 2.3 every week, before a single new tenancy, alarm check or repair.

Each of those is not one task but several: book the engineer, arrange access with the tenant, chase the certificate, file it against the right property, send the copy within 28 days, and follow up any remedial work. A missed one is not an hours problem. It is a liability problem, which is why this is the part of the calendar most worth taking out of people's heads and inboxes.

New tenancies add their own deadlines: Right to Rent before the start, the deposit protected and prescribed information served within 30 days, the gas record and electrical report handed over, and working smoke alarms from day one, plus carbon monoxide alarms in any room with a fixed combustion appliance other than a gas cooker. Under the Tenant Fees Act the deposit itself is capped at five weeks' rent where annual rent is under £50,000, and a holding deposit at one week's rent.

Where the hours actually go

Four places account for most of the recurring admin in a lettings operation:

1. Re-keying when a tenancy starts

The same tenant, property, rent and dates entered into the applicant record, referencing, the agreement, the deposit scheme, the rent ledger and the compliance tracker. Each entry is quick. Each is also a chance for two systems to disagree about the rent or the start date, which surfaces weeks later as an arrears query that is not really arrears.

2. Matching rent

Monthly rent on 100 homes is 1,200 receipts a year, about 23 a week. When a payment reference is wrong, a tenant pays in two parts, or a housing payment arrives on a different cycle, someone matches it by hand. Rent that cannot be matched cannot be paid out.

3. Landlord statements

Rent in, fees and repairs out, balance paid to the landlord, and a statement explaining it. Where accounting and maintenance live in different systems, the statement is where the two have to be reconciled, every month.

4. Certificates and maintenance coordination

The 120 certificate events above, plus every repair, share the same shape: a message chain between tenant, agent, landlord and contractor. The work itself happens elsewhere; the coordination is what lands on the desk.

Notice what is not on the list: the lettings platform's own screens. Agencies rarely lose their week inside one system. They lose it carrying facts between systems and chasing dates. This is the same pattern we describe in why most colleges have a seam problem rather than an MIS problem.

Measuring it for your own agency

Do not estimate this in the abstract. Measure one ordinary month.

A worked example with illustrative inputs, for the same 100-home portfolio:

• 25 new tenancies a year × 6 systems × 5 minutes of entry = 12.5 hours
• 1,200 rent receipts × 3 minutes of matching = 60 hours
• 1,200 monthly landlord statements × 4 minutes = 80 hours
• 120 certificate events × 40 minutes of coordination = 80 hours

That totals 232.5 hours a year, about 4.5 hours a week. To express it as staff time, multiply the weekly figure by 4.33 to get a month (about 19.4 hours) and divide by 162.5, the hours in one UK full-time month (37.5 × 52 ÷ 12). The answer is roughly 0.12 of one person.

At 500 homes, the same inputs give about 22 hours a week, or roughly 0.6 of a full-time person. The work scales with the portfolio; the seams do not get easier with size.

Replace every input with your own. Count the systems a new tenancy actually touches, time a real rent-matching session, and time a real certificate from booking to filed copy. If your answer looks like the 100-home figure, a well-configured off-the-shelf platform and some discipline is probably all you need, and we would rather say that than sell you a build. The method is the same one we use for automation time savings generally.

Buy, connect or build

Buy when the portfolio is small, your processes are standard and the measured hours are modest. The market for lettings platforms is mature, and a good one used fully beats a bespoke system used halfway.

Connect when you already have systems that work but disagree with each other. Making the tenancy details flow once — from the agreement into the deposit record, the rent ledger and the certificate calendar — removes the re-keying without replacing anything. That is the job of an integration hub.

Build only when the portfolio is large enough that the measured hours are a real share of someone's week, or when how you run lettings is genuinely part of your offer to landlords. Even then, build around the parts that differ and keep standard tools for the parts that do not.

Two things are worth knowing whichever route you choose. First, the Renters' Rights Act moved private tenancies in England to periodic tenancies from 1 May 2026, so check any system you rely on has been updated for that regime. Second, out-of-hours calls from tenants and applicants are part of the same picture; we cover that in what an AI answering service can and cannot do. For how we approach whole-agency platforms, see software for real estate and lettings.