You can’t maintain what you’ve never written down

Here’s an uncomfortable exercise. Without opening anything, write down every item across your estate that carries a statutory inspection: every hoist, every pressure vessel, every extract system, every fire door set, every lift, every piece of lifting equipment, every emergency lighting circuit. Now check it against reality.

Almost nobody passes. Buildings are easy to list — you pay rates on them. The equipment inside them accumulates: installed by a contractor, inherited with a lease, replaced during a refurbishment nobody documented. Some of it is inspected because the contractor knows it’s there. Some of it isn’t inspected at all, because the only person who knew about it left.

The register is the foundation, not a feature

Every other capability leans on it. Planned maintenance has to be scheduled against something. Service history has to attach to something. A report saying “unit 3 failed” has to resolve to something. Without a register you can track the visits, but you can’t track the equipment — and the equipment is what fails.

Structure it before you fill it

A flat list of four hundred items is only marginally better than no list. What makes a register usable is structure:

• Category and sub-category — so “all lifting equipment” is a question you can ask, not a search you have to do by memory.
• Groups — twelve identical units on one floor should be manageable together, and editable together, or nobody will keep them current.
• Location — down to the department where that’s meaningful. “Somewhere in the building” is not a location.
• Commissioning date where you have it, and honestly blank where you don’t. A guessed date is worse than a gap, because a gap invites a question and a guess doesn’t.

The cheap way to build it

Nobody has the appetite for an estate-wide audit before the system goes live, and they shouldn’t need one. Three routes work in combination:

Start with what you already own: the last twelve months of engineer reports name the equipment they tested. That’s a register, written by someone who physically stood in front of it. Second, let the register grow at the point of work — when a job or a service references an asset that isn’t listed, create it there and then, rather than noting it for later. Third, accept partial. A register covering the equipment that carries statutory risk is worth having on day one; the decorative lighting can wait.

What you get back

The payoff arrives the first time something fails. Instead of “when was that last serviced?” turning into an afternoon of email archaeology, the answer is on the record — with the report attached, the remedials from that visit, and whether they were ever closed out. That single moment tends to be when a register stops being paperwork and starts being infrastructure.