A remote audit checks your Legionella controls from a desk. Someone competent reads your digital records, temperature data, photographs and a guided video walkthrough instead of — or before — walking the building. Done well, it catches a stalled risk assessment or a fortnight of skipped flushes in minutes. Done lazily, it blesses tidy paperwork while the actual water goes unseen.
That gap between “the records look good” and “the system is safe” is the whole subject. Understand it, and a remote audit becomes a genuinely useful tool. Miss it, and you have paid for false comfort.
What a remote audit actually checks
Strip the technology away and a remote audit asks the same two questions an auditor asks on site: is this water system under control, and can you prove it? The difference is that the evidence arrives down a wire rather than under their own eyes.
In practice the reviewer wants read access to whatever holds your evidence, then works through it. The current risk assessment and the written scheme of control. The named responsible person and the arrangements behind them. Temperature trends and the exception and alarm history — not just the readings that passed, but what happened to the ones that didn’t. Task completion and anything overdue. Cleaning, descaling and inspection records. Sampling reports and, crucially, how any out-of-range result was closed out. L8 expects duty holders to keep records of precautions, monitoring and management arrangements [1], so a remote audit is largely a test of whether that record-keeping holds up under questioning.
Then there is the live part: a video walkthrough, where site staff carry a phone around the plant room, the cold water storage tank, the calorifier and a sample of outlets while the auditor directs the camera. This is where remote auditing earns its place. A competent eye steering someone else’s hands gets you a lot further than a folder of green ticks alone.
Continuous monitoring can feed the same review: sensors and alerts can flag temperature drift or a missed flush sooner than a quarterly visit would — but only if they’re calibrated and sited at points that mean something. A reading you can’t trust is worse than none, because it still looks like assurance (see Sensor calibration and maintenance).
What remote auditing is, and what it isn’t
Most of the trouble comes from a handful of assumptions that sound reasonable and aren’t:
| What people assume | What’s actually true |
|---|---|
| A remote audit is the same as a site visit | It examines evidence, not water. It cannot lift a tank lid, feel whether a cold tank is genuinely cold, or find a dead leg buried behind a wall |
| If the dashboard is all green, the system is controlled | A green tick proves a task was logged, not that the water is safe. Records can be complete and still be wrong |
| Going remote means the contractor never has to come on site | Physical inspection of tanks, calorifiers and TMVs still needs someone there. Remote working reduces visits; it doesn’t delete them |
| A digital logbook is a remote audit | The logbook is the evidence. The audit is a competent person interrogating that evidence against your risk assessment |
| Remote monitoring and remote auditing are the same thing | Monitoring is the continuous data feed. Auditing is the periodic judgement someone makes about whether control is genuinely being achieved |
Why the dashboard can lie to you
The single thing newcomers get wrong is trusting completeness over substance. A wall of green records feels like proof, and it is the easiest thing in the world to fake without anyone intending to.
Picture a low-use shower in a rarely-let room. The flushing task is logged every week, on time, signed off. But the person doing it runs the outlet for ten seconds — nowhere near long enough to draw fresh water through the dead leg behind it. The record is immaculate. The risk is untouched. Or a temperature sensor that has slipped off its sentinel point and now reads a warm airing cupboard rather than the tank it’s supposed to watch. The trend line looks reassuringly stable. It is measuring the wrong thing.
A remote audit is only as honest as the data it ingests, so the integrity of each record matters as much as its presence. Knowing who actually performed a task, when, and that the entry hasn’t been back-filled to paper over a gap is what separates an audit trail from a wish list — see Digital signatures and verification for maintenance tasks. The auditor’s job is to be politely suspicious of the green: the sample with no follow-up, the risk assessment whose review date quietly passed eighteen months ago.
What a camera can’t reach
There is a hard floor under remote auditing, and it is physical. A screen can’t tell you there is an inch of sludge in the base of a calorifier. It can’t register the smell of a stagnant tank, confirm a thermostatic mixing valve still blends to the right temperature under load, or trace a capped-off pipe that someone left full of warm water years ago. Those judgements need a person, on site, with the lid off.
So the sensible model is not remote instead of physical — it is remote plus a defined physical cadence for what a lens cannot judge. A remote audit is a way of looking at controls, not a control in itself, and nothing here decides for your building. What can be settled from a desk and what must be seen in person is a competent-person call against your own risk assessment, made by someone whose competence you can point to — the Legionella Control Association code of conduct is a reasonable benchmark [4]. Bringing in a third party to run the audit doesn’t move the duty: responsibility for control stays with the duty holder [3]. When a clean record and a physical inspection contradict each other, trust the inspection. What gets checked, remotely or otherwise, flows from the risk assessment, not from whatever the platform makes easy [2].
Where to start this week
You don’t need to overhaul anything to use remote auditing well. You need to set it up so it can’t deceive you.
- Get genuine read-only access to your records and monitoring data sorted before you book any audit, so the reviewer sees the live system, not a curated export.
- Write down, in advance, what the remote review will cover and what it explicitly won’t — then put the on-site half into the schedule as a dated task, not an aspiration.
- Check that each record captures who did it, when, against which asset, the result, whether it was in range, and what happened if it wasn’t. If it only captures a tick, fix the form first.
- Pair every remote audit with a physical inspection cadence for tanks, calorifiers and valves, and treat any disagreement between the two as the physical inspection’s call.
The concrete next step: pull up your last twelve weeks of monitoring data today and find one record you can’t fully trust — a flush that’s too short, a sensor you can’t place, a sign-off with no name. That single doubt is the most useful thing a remote audit could have told you, and you just found it for free. Why duty holders bother at all comes down to the asymmetry laid out in The cost of an outbreak: the audit is cheap, the failure is not.
FAQ
Can a remote audit replace the on-site Legionella inspection entirely?
Not for most systems. A remote audit is strong on the management side — risk assessment currency, record integrity, temperature trends, action close-out — but it can’t perform the physical checks a tank, calorifier or TMV needs. Treat it as the desk half of a complete audit, with a scheduled physical inspection for the rest. Where the line sits is a competent-person decision against your risk assessment [2].
Is a remote audit the same as remote monitoring?
No, and conflating them causes real gaps. Remote monitoring is the continuous stream of sensor readings and alerts. A remote audit is the periodic judgement a competent person makes about whether your controls and records actually demonstrate that the system is under control. Monitoring produces evidence; auditing interrogates it [1].
If our records are complete and all in range, why would an auditor still flag problems?
Because completeness isn’t the same as effectiveness. A full logbook can hide a flush that never clears a dead leg, a sensor reading the wrong location, or a sample with no recorded follow-up. A good auditor questions what the green ticks actually prove, not just whether they’re present.
Sources
[1] HSE, “Legionnaires’ disease. The control of legionella bacteria in water systems — Approved Code of Practice and guidance (L8)”. https://www.hse.gov.uk/pubns/books/l8.htm [2] HSE, “Legionnaires’ disease: Technical guidance (HSG274)”. https://www.hse.gov.uk/pubns/books/hsg274.htm [3] HSE, “Legionnaires’ disease — what you must do”. https://www.hse.gov.uk/legionnaires/what-you-must-do/index.htm [4] Legionella Control Association, “Code of Conduct for Service Providers”. https://www.legionellacontrol.org.uk/