This guide is written for Irish letting agents and agencies managing tenancies on behalf of landlord clients — and it applies just as well to a portfolio landlord managing their own. It assumes you already know the rules. The question here isn't what you're obliged to do; it's what system makes sure it actually happens on the right day, every time, as the book grows.

The arithmetic nobody runs

Agencies rarely decide to run on spreadsheets. They inherit the decision. The first few tenancies fit in one tab, the tab grows a few columns, someone adds a second sheet for compliance dates, and five years later the business is running on a file that nobody designed and nobody fully trusts.

The reason it stops working isn't that the spreadsheet gets worse. It's that the workload it's tracking grows in a way that human attention can't match. Here is the arithmetic, using a mid-sized Irish book:

Three a week, spread unevenly across twelve months, on 150 different anniversaries — and that's before you add:

• Up to 150 rent-review eligibility dates a year (a rent may generally be reviewed no more than once in any 12-month period, with at least 90 days' written notice).
• A Part 4 milestone for every tenancy that passes six months of continuous occupation, plus the rolling six-year Tenancy of Minimum Duration cycle for tenancies created since 1 March 2026.
• BER, gas, electrical, fire alarm and insurance expiries across every property — several per property, each on its own cycle.
• Every notice of termination, where the ground, the notice period and the termination date all have to be right, and the RTB copied.

Realistically, a 150-tenancy agency is carrying somewhere north of 700 date-bound obligations a year. That's more than two per working day. A spreadsheet can hold all of them beautifully. What it cannot do is raise its hand.

There's a market pressure on top of the regulatory one. RTB rental-sector data for Q3 2025 showed the number of landlords linked to registered private tenancies falling 0.5% year-on-year to 103,774, while the share of tenancies held by landlords with 100+ tenancies rose for a ninth consecutive quarter. Fewer, larger clients means each landlord client you hold is worth more — and each avoidable slip costs more.

The five ways spreadsheets break

These aren't discipline problems. They're structural properties of the tool. A more careful team using spreadsheets hits exactly the same five walls, just later.

1. They store dates but never check them

This is the root cause of the other four. A cell containing 2026-11-14 is inert. It does nothing on 14 November. It does nothing on 13 November either. The only mechanism that turns it into an action is a human being deciding, unprompted, to open the file and scan a column — and doing so reliably, every week, for years, while also letting properties, taking viewings and answering landlords. That's not a workflow; it's a hope.

2. They drift the moment two people touch them

Two team members, two versions, one copy-paste into the wrong row and a rent figure is now wrong in a file that everyone treats as authoritative. Nothing flags it. The error propagates into a landlord statement, a rent review calculation, and eventually into a conversation you didn't want to have. Spreadsheets have no concept of a record — only of cells that happen to sit near each other.

3. They can't compute the rules

The national rent cap is not a number you can type into a column and reuse. The permitted increase depends on the documented date the rent was last set, the CPI series between that date and the review date, a proportionate 2% per-annum ceiling, and whether the property falls into a carve-out (for example, properties commenced and completed on or after 10 June 2025, and student-specific accommodation, which are linked to inflation only). Getting it wrong in either direction is expensive: too high and the review can be challenged and unwound; too low and you've under-served your client. A spreadsheet will happily hold a wrong answer with total confidence.

4. They produce no evidence

If a tenancy ends up in RTB mediation, adjudication or a Tribunal, the question is not "what does your sheet say today?" — it's "what did you do, and when, and can you show it?" A spreadsheet is a photograph of the present. It has no memory of when a row was edited, by whom, or what it said before. The evidence you need is generated only by a system that timestamps events as they happen, which means it has to exist before the dispute, not after.

5. They have no idea who's allowed to see what

Once you're multi-branch, or you have negotiators who should see their own properties and a principal who should see everything, a shared file becomes either too open or too locked down. There's no middle. And when a landlord client asks a perfectly reasonable question — "show me everything for my four properties" — the answer involves filtering a sheet that also contains twelve other landlords' data.

Where it breaks first: RTB compliance

Of everything an agency tracks, RTB obligations break first — for three reasons.

• Density. Every single tenancy generates a registration deadline plus a renewal on every anniversary, for as long as it continues. Nothing else in the business repeats that often.
• Derivation. The deadline isn't a fact you're told; it's a calculation from the tenancy commencement date. A tenancy must be registered with the RTB within one month of commencement. Anything derived is something a human can get wrong.
• Consequence. Late registration attracts a late fee, and non-registration exposes a landlord to considerably heavier sanctions — confirm current fees and penalties on rtb.ie. But the real cost for an agent is professional. Your landlord client engaged you so that this specific thing would never happen.

So RTB compliance is the right place to look when you're deciding whether your spreadsheet has run out of road — and it's the right place to start when you replace it. The rest of this guide walks through exactly what that replacement looks like, workflow by workflow, so you can judge it against what you do today rather than against a feature list.

What RTB automation actually does (workflow by workflow)

"Automation" is a word vendors use loosely, so here is the concrete version — the actual sequence TenantSync runs, in the order it runs it. Read it as a specification you can hold any software to, including ours.

Workflow 1 — The tenancy record creates its own clock

This is the substitution that matters most, and everything else follows from it. When you create a lease in TenantSync, an RTB registration record is created automatically alongside it. Nobody types a deadline. The system derives:

• the registration deadline, calculated from the tenancy start date;
• the annual renewal date, set one year out and re-based each cycle;
• an initial status of Not started, and an initial compliance risk rating.

The distinction with a spreadsheet is not cosmetic. In a spreadsheet the deadline is data you entered, so it's only as right as the day you typed it. Here the deadline is a consequence of the tenancy existing — so a tenancy cannot exist without its clock. Forgetting to add the deadline is no longer a possible mistake.

Each registration then moves through an explicit lifecycle, and the status is a real state on the record rather than a colour someone applied by hand:

Workflow 2 — Form 1: draft → validate → preview → finalise

The RTB's tenancy registration form is long, and most of what it asks for is data you already hold. TenantSync models the form properly rather than treating it as a PDF you fill in by hand — the property section (address, Eircode, local authority, dwelling type, bedrooms, BER, floor area), the tenancy section (start date, fixed term, rent and frequency, deposits, occupants, additional charges), the previous-tenancy section, the landlord section (multiple landlords, or a company with its CRO number), the tenant section, the authorised agent section, the management company section, and the declaration.

That structure is what makes the workflow possible:

The agent-specific detail is worth calling out: because the form models an authorised agent alongside up to several landlords and several tenants, an agency's own details flow through consistently on every client's registration rather than being re-typed 150 times.

Workflow 3 — The daily reminder engine

This is the part a spreadsheet structurally cannot replicate, because it requires something to happen when nobody is looking.

Every morning, a scheduled job sweeps the whole portfolio, reads each RTB registration's deadline and renewal date, works out how many days remain, and sends notifications to the right people. Specifically:

• It looks at registrations still sitting at Not started or In progress — the ones that can still go wrong.
• Urgency escalates: an early warning while there's comfortable time, upgrading to a critical alert inside the final week before the deadline.
• Reminders are grouped by landlord, so you get one useful message about a client rather than a drip of separate emails.
• Sending is throttled — at most one reminder per registration per day — so alerts stay meaningful instead of becoming noise you filter out.
• Reminders are configurable per user in settings, and RTB tracking can be turned off per tenancy where it genuinely doesn't apply.

RTB isn't the only clock running. Separate daily jobs handle rent reminders (rent due shortly, or overdue — drawing on Open Banking arrears data where a bank account is connected) and lease expiration reminders ahead of a lease end date. Notifications reach you by email, with mobile push on the iOS and Android apps, and SMS available as a metered add-on.

Reframe what that means operationally: the question changes from "did anyone check?" to "what did the system send this morning?" One is a hope; the other is a to-do list.

Workflow 4 — The annual renewal loop

Annual registration is where spreadsheet agencies get hurt most, because the first registration feels like an event and the renewals feel like background noise. But at 150 tenancies the renewals are the workload — roughly three a week, indefinitely.

TenantSync treats the renewal as a first-class part of the record: a renewal due date, a renewal submitted date, a renewal confirmed date. The renewal itself starts from last year's Form 1 data copied forward, so you're reviewing and adjusting what changed rather than rebuilding the form. Once confirmed, the next anniversary is already on the clock.

Workflow 5 — The portfolio compliance dashboard

Individual reminders keep you out of trouble. The dashboard is what lets you manage compliance rather than react to it. In one view:

• Summary counts — how many items are compliant, how many are upcoming in the next 30 days, how many are overdue.
• A single sorted timeline of everything due, across every landlord client, ordered by date.
• Filters by status and by item type, plus countdown indicators ("X days until deadline") and colour-coded badges — green for compliant, orange for upcoming, red for overdue.
• More than RTB. The same dashboard tracks RTB registration and renewal, rent reviews, Part 4 notices, BER certs, insurance, fire alarm servicing, gas safety, electrical certs, AML reviews, and custom items you define yourself.

Crucially it is scope-aware. What you see depends on your role: an individual agent sees their own properties, a branch manager sees the branch, an agency administrator sees every branch. That's the multi-branch problem a shared file can't solve — and it's what makes a per-landlord answer instant instead of a filtering exercise across other clients' data.

Workflow 6 — Rent reviews under the national cap

Rent is where a wrong answer is most expensive, so the calculation is done rather than remembered. TenantSync's rent-cap engine takes the lower of:

• the CPI-based increase between the date the rent was last set and the review date; and
• a 2% per-annum ceiling, applied proportionately to the actual number of days elapsed — not a flat 2% regardless of how long it's been.

It applies the carve-outs where they exist (properties commenced and completed on or after 10 June 2025, and student-specific accommodation, which are linked to inflation only), and returns the suggested maximum rent along with which factor was the binding constraint — so you can show a landlord client why the number is the number.

From there it generates the Notice of Rent Review as a PDF, enforcing the minimum 90-day notice period and flagging warnings if the proposed rent exceeds the cap or the notice period is too short. A rent review tracker holds the last review date and the next eligible date per tenancy, and rent-review eligibility appears as an item on the same compliance dashboard. If you just want the number, the rent-cap calculator is free and needs no account.

Workflow 7 — Part 4 status and terminations

Part 4 security of tenure isn't a document; it's a date passing. TenantSync derives each tenancy's Part 4 status from its occupation length — not yet eligible, eligible once six months of continuous occupation have passed, and further Part 4 at the later milestone — so the status is always current rather than as-at whenever someone last updated a column.

For terminations, notices are built as structured drafts rather than free-typed letters. Each available ground carries its own required notice period and its own supporting-detail requirements (for example, arrears details for a rent-arrears ground, or breach details for a breach ground), and the notice moves through an explicit lifecycle — in progress, finalised, served — with the delivery method recorded and a PDF generated. Validation issues are grouped by section so nothing is served half-complete.

Notice periods in Ireland scale with tenancy duration and differ for small versus large landlords under the post-March-2026 framework — our Part 4 and notice periods quick-reference has the full tables, and remains the authority to check a specific case against.

Workflow 8 — Evidence, generated as you go

Every step above leaves a timestamp: when a draft was last edited, when a registration was submitted, when it was confirmed, when proof was uploaded, when a notice was finalised and served. You can attach the RTB confirmation document to the tenancy, record the RTB registration number, and — where a tenancy was registered outside the system — record a dated self-attestation naming the user who made it.

None of that is exciting until it's the only thing standing between you and a difficult conversation with a landlord client, an RTB adjudicator, or your own professional indemnity insurer. The point of an audit trail is that it must already exist by the time you want it, which is precisely why it can't be assembled from a spreadsheet after the fact.

Spreadsheet vs automated: side by side

The same eight jobs, done both ways. The pattern to notice is that the spreadsheet column always contains a person doing something they might not do.

The breaking-point self-test

Rather than guessing at a magic portfolio size, answer these seven. They're deliberately concrete — each one is a thing you can check in the next ten minutes.

What to do about it

The reason agencies stay on spreadsheets long past the breaking point is almost never that they think spreadsheets are good. It's that moving sounds worse than staying. In practice it isn't.

If you're at the point of moving, the practical sequence is set out step by step in our guide to migrating an agency portfolio off spreadsheets without losing a tenancy. If you're still evaluating options, what to look for in property management software for Irish agents is the buyer's checklist — and it's written to be used against any vendor, not just us.

Frequently asked questions

Why do spreadsheets break for property management as an agency grows?

Because a spreadsheet stores a date but never checks one. Every obligation an Irish letting agent carries — RTB registration within one month of commencement, annual RTB renewal on each anniversary, a rent review no more than once every 12 months, Part 4 milestones, BER, gas, electrical and insurance expiries — is a date attached to a record, with a consequence if it passes. Those dates multiply with the portfolio while the number of people watching them does not. A spreadsheet only helps on the days somebody opens it, remembers what to look for, and reads the right row. Software checks every date every day whether anyone opens it or not, which is why the failure curve flattens instead of steepening.

At what portfolio size do spreadsheets stop working for a letting agency?

There is no universal number, but the practical breaking point is where the deadline count exceeds what one person can hold in their head — usually somewhere between 20 and 50 tenancies, and much earlier if tenancies are spread across several landlord clients, branches or bank accounts. A useful test is arithmetic rather than opinion: 150 tenancies means 150 annual RTB renewals a year, roughly three every week, forever, before you count rent reviews, Part 4 dates and certificate expiries. If nobody in the agency can name this week's three without opening a file, the spreadsheet has already stopped working — you just haven't been caught yet.

What does automated RTB compliance actually do that a spreadsheet cannot?

Five things. It derives the deadlines instead of storing them: creating a lease in TenantSync automatically creates an RTB registration record with the registration deadline calculated from the tenancy start date and the renewal date set a year out. It carries the Form 1 itself, as a saved draft that is validated for missing or inconsistent fields, previewed as a PDF, then finalised. It runs a daily job that checks every registration and renewal date across the portfolio and emails the responsible people, escalating from warning to critical inside the final week. It shows the whole book at once on a compliance dashboard, colour-coded compliant, upcoming or overdue and scoped to the user's branch or agency. And it timestamps everything — drafted, submitted, confirmed, attested, proof uploaded — so the evidence exists before you need it.

Can RTB registrations be submitted in bulk?

No — RTB registration is per tenancy, and each one is its own submission to the RTB. What can be run in bulk is the workflow around it: tracking every deadline in one dashboard, generating each Form 1 from data you already hold rather than rekeying it, copying last year's details into this year's renewal, filtering the whole book by status or landlord client, and receiving one grouped reminder rather than hunting through rows. That is what "bulk RTB compliance" honestly means for an agency.

What happens if you miss an RTB registration deadline in Ireland?

A tenancy must be registered with the RTB within one month of commencement, and registration renews annually. Filing late attracts a late fee, and non-registration can expose a landlord to significantly heavier sanctions — always confirm the current fees and penalties on rtb.ie. For a letting agent the sharper cost is professional: the landlord client engaged you precisely so this would not happen, and a missed date is a retention and professional-liability problem long before it is a fee.

Is it hard to move a lettings portfolio off spreadsheets?

Less than agencies expect. TenantSync imports properties, units, tenancies, leases and rent details from a CSV or spreadsheet, or directly from Letman — and if you'd rather not do it yourself, the TenantSync engineering team will migrate your whole portfolio for free in one short run, with no data cleaning needed on your side, then validate the RTB dates with you. The step that matters is validation: confirming each tenancy's start date, registration date and last rent review date, because those are what every automated deadline is then derived from.

Do landlords with a handful of properties need to stop using spreadsheets too?

For one or two tenancies a spreadsheet plus a calendar reminder is genuinely workable — the arithmetic is small enough to hold in your head. The calculation changes once you pass a few tenancies, or once the tenancies have different start dates, different rent review anniversaries and different certificate expiries, because that is the point at which the dates stop being memorable and start being missable. The same automation agencies use for a whole book works for a small portfolio; the difference is only how much it saves you.

Sources & further reading

Regulatory facts are drawn from official and primary sources. Product details describe TenantSync as built at the time of writing (August 2026) — verify on tenantsync.ie before deciding.

• Residential Tenancies Board — Register a tenancy, rental law changes from 1 March 2026 and RTB data hub & rental sector research
• Citizens Information — Registering a tenancy with the RTB
• Government of Ireland — Reforms to the rental sector, starting 1 March 2026
• Central Statistics Office — Consumer Price Index (the inflation series used in rent-cap calculations)
• TenantSync — tenantsync.ie (RTB compliance, rent automation, pricing and free tools)