Built for UK water hygiene· a register that mirrors the estate
Water asset register software that mirrors the estate, not the paperwork
Tanks, calorifiers, TMVs, cooling towers: the estate is the thing you actually maintain. BlueWave's register is built so every job leaves its mark on the asset.
Asset and site register capabilities reviewed .
The problem it kills
Most asset registers are a spreadsheet tab created during onboarding and updated at gunpoint. Within a year it disagrees with the estate: assets decommissioned, TMVs added, a calorifier swapped — none of it recorded, because recording it was someone's extra job. Then a risk assessment cites an asset that no longer exists, and the client notices before you do.
One registry, and everything hangs off it
Sites, their assets, and the schematics that explain them sit in one navigable structure. It's the same spine the compliance records cascade from, so the register isn't a parallel document to maintain; it's the platform's backbone.
- Sites and assets in one navigable registry
- Schematics attached where they're useful: at the site and asset
- The same structure your records, jobs and history hang off
One job, every asset it touched
A monitoring round covers the tank, the calorifier and twelve TMVs, so the job records all of them in one sheet. There's no splitting reality into artificial one-asset jobs to fit the software's shape.
- Multiple assets per job, as the work actually happens
- Per-asset readings inside a single job sheet
- The day's story stays whole: one engineer, one site, one job
History stays with the asset
Every job that touched the asset, with its job sheets, readings and photos, stays on the asset's history across years, engineers and even ownership of the contract. Certificates and other documents you upload sit beside it.
- Full service history held by the asset, not an engineer's memory
- Certificates, schematics and manuals uploaded to the asset
- New engineer on site? The asset briefs them
A register nobody updates is historical fiction
The spreadsheet register fails for a structural reason: keeping it current is extra work that competes with real work. In BlueWave the asset's history updates because the work updates it: every booking records against the assets it covered. Nobody has to remember, which is the only maintenance policy that survives contact with a busy week.
Your BS 8580-1 risk assessments cite this register — how the standards fit together is mapped on the compliance hub.
Common questions
Can one job cover multiple assets?
Does asset history survive an engineer leaving or a contract changing hands?
How does the asset register stay up to date?
What kinds of water assets can it track?
See your estate the way your auditor wishes you did
Bring one real site to the demo — we'll build its register live, assets and schematics included, and show you the history view your spreadsheet can't.