Resources · Agent Operations

Bulk Section 13 Notices: Running a Portfolio Rent Review at Volume (2026)

By the Noticr Editorial Team · Updated 22 June 2026 · England only · General information, not legal advice

Since the Renters' Rights Act 2025, a Section 13 notice is the only lawful way to raise the rent on a periodic assured tenancy, and rent-review clauses are void. For a letting agency that turns the annual rent review into a volume operation: every managed tenancy needs its own statutory notice, every year. The instinct is to run it like a mail merge — one date, one batch, send. That instinct is exactly what voids notices at scale.

Bulk Section 13 is real, and it is worth automating. But it is a generate-and-track problem, not a single-date shortcut. This page explains the trap, then the compliant way to run a portfolio rent review fast.

The Portfolio-Sweep Trap

The single biggest source of void notices at an agency is applying one rent-review date to a whole book. Here is why it fails:

Each tenancy's earliest lawful effective date is 52 weeks after its own last effective increase — not once per calendar year. 52 weeks is 364 days, so the window sits on a different day for every tenancy and drifts one or two days earlier each year against the calendar. On long-running tenancies the 53-week rule pushes the window out by a further week. Pick a single date — say a tidy 1 April for the whole portfolio — and you will land inside the 52-week window on every tenancy whose last increase was less than 52 weeks before it. Those notices are void on their face.

The same sweep usually also forces a uniform effective date that ignores each tenancy's rent period, breaking the Mooney v Whiteland alignment rule (the new rent date must be the first day of a rent period). One careless batch can therefore void notices two different ways at once. The broader list is in the mistakes that invalidate a Section 13 notice.

The Compliant Way to Run It at Volume

Speed comes from automating the per-tenancy maths and the form — not from collapsing the dates. The operation:

1. Compute every tenancy's dates up front. For each tenancy, derive the earliest lawful effective date (52/53 weeks from its last increase, aligned to a rent period) and the latest safe serve date (two months earlier, from deemed service). Now the whole book is dated.

2. Sort the book by window, not by convenience. Order tenancies by their serve date. The review stops being one event and becomes a rolling schedule — a handful of notices due each week, every one already inside its lawful window.

3. Batch-generate the current Form 4A. Fill each notice programmatically with the correct landlord party, figures and per-tenancy dates, from a form kept current against statute. No Word templates. See the Form 4A guide.

4. Serve in rolling batches and capture evidence at source.As each week's window opens, serve that batch by an evidenced method and log service the moment it happens. See how to serve a Section 13 notice.

5. Keep a tribunal-ready trail per tenancy. Dates calculated, form version, method and date of service, deemed-service date — six years, per client. Built as you go, not reconstructed later.

Done this way, a portfolio rent review is faster and safer than a single sweep, because nothing is improvised and nothing lands in the wrong window. For the full per-tenancy standard behind this, see letting-agent rent-increase compliance.

How Noticr Does Bulk Section 13

Noticr computes the 52/53-week earliest effective date and rent-period alignment for every tenancy in a managed book, flags each one as its review window approaches on a portfolio compliance calendar, and generates the current prescribed Form 4A in batch with per-tenancy figures and dates. Every generation and service event is timestamped into a tribunal-ready audit trail per client, kept for six years. It turns the portfolio review from a risky once-a-year sweep into a rolling, evidenced operation — one agency plan for the whole book, not per notice.

Frequently Asked Questions

Can you serve Section 13 notices in bulk across a portfolio?

You can generate and serve them in a single pass, but they cannot share an effective date. Each Section 13 notice is per tenancy, and the earliest lawful effective date is 52 weeks (or 53 under the drift rule) after that specific tenancy's last increase — a different date for every tenancy. Bulk working is a generation-and-tracking problem, not a “one date for the whole book” shortcut. Applying a single review date across a portfolio is the most common way agencies void notices at scale.

Why does a portfolio-wide rent-review date void some notices?

Because each tenancy has its own 52-week clock running from its own last effective increase, and 52 weeks is 364 days, the windows sit on different days and drift earlier each year against the calendar. A single “spring review” date will fall inside the 52-week window for any tenancy whose last increase was less than 52 weeks before it — and those notices are void. Long-running tenancies that need 53 weeks make the spread wider.

What is the fastest compliant way to run a portfolio rent review?

Compute each tenancy's earliest lawful effective date and latest safe serve date from its own last increase, sort the book by those dates, and serve in rolling batches as each window opens — rather than forcing the whole portfolio onto one date. Generate the current Form 4A per tenancy with the correct figures and rent-period-aligned dates, and capture the service evidence at the moment of service. The speed comes from automating the per-tenancy maths and the form, not from collapsing the dates.

Should letting agents generate Form 4A from a Word template for bulk runs?

No. A Word template fossilises the prescribed form and statutory references on the day it was saved; when the form changes, every notice from that template is wrong until someone notices, and at volume that is a lot of void notices before anyone catches it. Generate the current prescribed Form 4A from a source kept up to date against statute, with per-tenancy figures and dates filled programmatically.

What audit trail do agents need for bulk Section 13 notices?

Per tenancy, kept for six years: what was served, the dates calculation behind it, the method and date of service, the deemed-service date, and the figures. At volume the trail has to be captured automatically at the point of service, because reconstructing it months later across hundreds of notices is impossible — and the audit trail is exactly what defends a notice when a tenant refers it to the First-tier Tribunal.