Setting Up Escalation Rules: Who Should Get the Reminder When a Certificate Is About to Expire

The reminder that only one person sees

Most compliance reminder systems, CertMinder UK included, start with a sensible default: a certificate is coming up for renewal, so the system emails the person responsible for that property. That works right up until the moment it doesn't - the property manager is on leave, the inbox is overflowing after a busy week of move-ins, or the email quietly lands in a folder nobody checks. Three weeks later the Gas Safety record has lapsed and nobody noticed until a tenant query forced the issue.

This isn't really a reminder problem. It's an escalation problem. A single notification to a single person is a single point of failure, and property compliance is exactly the kind of thing that shouldn't depend on one person's inbox discipline on any given Tuesday.

Why "set it and forget it" doesn't hold up

Landlords and letting agents often set up their reminder lead times once (see our piece on choosing sensible lead times) and assume the job is done. Lead time answers "how early does the first warning go out." It doesn't answer the more important question: what happens if that first warning is ignored?

In a one-person portfolio, that question barely matters - you're the only recipient, and if you miss it, you miss it. The moment you're managing compliance across a team, a branch, or a block of managed properties, the gap between "a reminder was sent" and "a reminder was acted on" is where certificates actually lapse. CertMinder UK's job is to make sure the system keeps nudging until someone with the authority to act actually does.

Building an escalation chain in three tiers

A workable escalation structure for most letting agencies and portfolio landlords looks roughly like this:

Tier one - the property manager or point of contact. The person who deals with that property day to day gets the first reminder, at whatever lead time suits the certificate type (EICRs need longer runways than, say, an EPC renewal that's mostly admin).

Tier two - the branch manager or team lead. If tier one hasn't actioned the reminder - no work order raised, no contractor booked - within an agreed window, the same alert goes to whoever supervises that property manager. This tier exists to catch the ordinary stuff: holiday cover gaps, a genuinely overloaded week, an email that got buried.

Tier three - the landlord or the business owner. If the certificate reaches a set number of days from expiry with still no action logged, the notification goes to the top: the landlord themselves, or the agency principal. Nobody enjoys being tier three, which is exactly why it works as a backstop - it's rare, and it's meant to be.

The number of tiers and the gap between them is yours to set. A small portfolio might only need two tiers. A multi-branch agency managing certificates for dozens of landlords usually wants all three, with branch-level visibility built in so each office can see its own pipeline without wading through everyone else's.

What should trigger the next tier

The trigger shouldn't just be time passing - it should be the absence of a specific action. In CertMinder UK terms, that's usually one of: no work order has been raised against the upcoming renewal, or a work order exists but no contractor has confirmed a date. Escalating purely on a countdown, regardless of what's actually been done, trains people to ignore the early warnings because they know a human will eventually sort it - which defeats the point. Escalating on inaction, not on elapsed time alone, keeps tier one meaningful.

Setting this up without creating noise

The failure mode on the other side is escalation chains that fire too readily and train everyone to tune out notifications altogether. A few practical guardrails:

Keep the gap between tiers wide enough that a manager has a genuine chance to act before the reminder goes over their head - a day or two at minimum, longer for certificate types with naturally long lead times. Make sure tier two and tier three notifications say clearly what hasn't happened yet, not just that something is due, so the person receiving an escalation isn't starting from zero. And review the chain occasionally: if a particular property manager's name keeps appearing at tier two, that's a conversation worth having directly, not just a workflow to keep patching around.

A note on who stays in control

It's worth saying plainly: escalation rules decide who gets told, not who gets to decide. CertMinder UK will surface the right reminder to the right person at the right tier, but booking the contractor, choosing the supplier, and signing off the work order stays with you. We don't take referral fees or kickbacks from contractors, and we don't quietly steer which one gets picked when an escalation lands - the alert is information, not a nudge toward anyone's preferred supplier. The decision is still yours; we're just making sure it reaches someone who can make it in time.

This is general information about setting up reminder and notification workflows, not legal advice on compliance deadlines themselves - for the underlying legal requirements and timings, check current government guidance.