Which Certificate Is the Real One? Fixing the Version-Control Problem in Property Compliance

Ask most letting agents where "the" gas safety certificate for a property lives, and you'll usually get more than one answer. There's a copy in the property file. Another in an email thread from eighteen months ago. Maybe one the engineer texted over on the day, and a fourth that a previous property manager saved to a shared drive folder that nobody else has opened since. All four are real documents. Only one of them is current.

This is the version-control problem, and it rarely gets named as its own issue because it hides inside other problems. It looks like "we sent the tenant the wrong EICR" or "the contractor quoted based on an old fault report" or "the landlord forwarded us a certificate we'd already renewed." Each incident gets treated as a one-off mistake. Taken together, they're a pattern: nothing in the system actively tells people which document is the live one.

How outdated certificates creep into a property file

Certificates don't expire the moment a new one is issued — the old one just becomes obsolete, but it keeps existing in every inbox and folder it was ever forwarded to. A few common ways this plays out:

A gas engineer re-does an annual check and emails the new CP12 to the office inbox. The old one is still attached to a message three scrolls up, and it is what a new starter finds when they search "gas certificate" for that address, because it has more replies underneath it and shows up first.

An EICR comes back with C3 observations, gets remedied, and a satisfactory retest certificate is issued a fortnight later. Both documents reference the same property and the same rough date range. Someone scanning quickly grabs the first one they see.

A property changes hands between agents, or a portfolio gets absorbed into a bigger management company, and years of historic paperwork get bulk-uploaded into a new system with no clear marker for which records are current and which are archived history.

None of this is carelessness. It's what happens by default when compliance documents are stored as files rather than as records with a status.

Why this matters more than it looks like it should

A certificate isn't just proof something happened — it's what people act on. A contractor pricing a repair off an old EICR might quote for faults that have already been fixed, or miss ones that haven't. A tenant handed a superseded gas certificate at check-in has, technically, not been given evidence of a valid current check, even though everyone involved believed they had. And if a dispute or an inspection ever asks "what was the compliance status of this property on this date," pulling the wrong document from a folder full of plausible-looking candidates is an easy, human mistake to make — and a hard one to explain afterwards.

This is the gap between having compliance paperwork and being able to prove compliance. Storage isn't the same as record-keeping. A folder full of PDFs answers "do we have a certificate for this property" — it doesn't answer "which one is current, and what happened to the ones before it."

What version control actually looks like for property compliance

You don't need anything exotic. The underlying idea is the one any record-keeping system relies on: every certificate for a given property and check type is uniquely and permanently tied to that property, dated, and marked with a status — current, superseded, or archived — the moment a newer one is added. When a new CP12 comes in, the system should know it replaces the previous one for that address, not just that it's another file in the same folder. The old certificate doesn't get deleted; it stays as part of the property's history, but nobody has to guess which one to act on, because only one is ever flagged live.

The second piece is that whoever needs a certificate — a tenant, a contractor, a landlord — should only ever be able to pull the current one. If the system that generates a certificate link or a download always points at "the live record for this property and this check type" rather than a specific file someone saved once, the stale-copy problem mostly disappears on its own.

Building this without creating more admin

The point isn't to add a review step where someone manually decides which certificate is "the real one" every time paperwork comes in — that just adds friction and still depends on someone remembering to do it. The point is to have the upload itself carry that logic: a new gas safety certificate for 14 Elm Court should automatically supersede whatever gas certificate was previously live for 14 Elm Court, without anyone flagging it by hand.

This is one of the quieter reasons CertMinder UK ties every certificate to a specific property and check type rather than treating uploads as generic attachments. When a new EICR, CP12, or EPC comes in for a property, it becomes the current record for that check automatically, and the previous version drops into history rather than sitting in a folder pretending to be current. Nobody has to remember to archive the old one, and nobody downstream has to guess which PDF to trust.

Compliance is the floor, not the ceiling — and a certificate that's hard to trust because it might be an old one isn't really doing its job, even if the check itself was done properly. Getting the paperwork right the first time only counts if the right version of it is still findable a year later.

This article is for general information and doesn't constitute legal advice. For your specific obligations, check current UK government guidance or speak to a qualified adviser.