Legionella logbook software that finds the record before the auditor finishes the question

Five years of monitoring records, risk assessments and certificates — and the test isn't whether you have them, it's whether you can put your hand on the right one while someone watches.

Book a demo Get started

The problem it kills

Shared drives hold records the way a glovebox holds receipts. The folder structure made sense to whoever created it, the naming convention lasted six weeks, and now the disinfection certificate from March 2023 is somewhere in three places called "Site Docs", "SITE DOCS OLD" and "FINAL v3". Everyone's fine until the LCA audit, the insurance claim, or the HSE letter.

A library that files itself

Every record lands in a cascading structure — customer, site, asset, job type, date — because that's where the work created it. Filing isn't a job someone does afterwards; it's a property of capturing the work in the first place.

Customer → site → asset → job type → date, navigable in both directions
Records created by the work, filed by the structure
No naming conventions to enforce, because there's nothing to name

An audit trail you don't have to keep

Every change to every record is logged — who, what, when. Retention runs to the five years LCA guidance expects, by default, without anyone setting a reminder to not delete things.

Change history on every record
Five-year retention as the default, not a policy document
What the auditor sees is what happened

The paperwork lives with the work

RAMS, schematics, disinfection certificates — attached to the customer, site or asset they belong to, not to an email thread. Search finds them in seconds; export hands an auditor or a departing client a clean bundle.

RAMS and schematics against the right site and asset
Instant search across the whole library
Export a customer's history as a coherent record, not a zip of guesses

Structure beats discipline

A shared drive works exactly as well as the most junior person's worst Friday afternoon. That's not a people problem — it's what happens when filing depends on discipline. BlueWave removes the discipline requirement: the structure files the record, the trail logs the change, the retention just runs. Discipline takes holidays; structure doesn't.

What the logbook legally has to hold is its own guide — Legionella logbook requirements — and the full standards map lives on the compliance hub.

Common questions

How long does BlueWave keep water hygiene records?

Five years by default, the retention LCA guidance expects for monitoring records, with the trail kept without anyone having to remember not to delete it. Risk assessments and certificates stay filed against the site and asset they belong to.

Can I find a specific certificate quickly during an audit?

Records sit in a cascading library of customer, site, asset, job type and date, filed by the work as it's captured. Search returns a named asset's disinfection certificate in seconds rather than a morning spent across three folders called 'Site Docs'.

Is there an audit trail showing who changed what?

Every change to every record is logged with who, what and when. What the auditor sees is what actually happened, so you aren't reconstructing history from memory or an email thread.

Can I hand over a customer's full history when a contract ends?

Yes. You can export a customer's records as one coherent bundle of RAMS, schematics, certificates and monitoring history, rather than a zip of guesses from a shared drive. It's the same export that satisfies an auditor or a departing client.

Bring your scariest audit question

In the demo, ask us to find a specific record the way an LCA auditor would — site, asset, date, document. Watch how long it takes.

Book a demo Get started