All writing

Water hygiene· · 5 min read

Manual vs automated Legionella monitoring

Monthly thermometer rounds or sensors? How manual and automated Legionella temperature monitoring compare on cost, coverage, records and risk, and when each makes sense.

By Alessio Grespi, Founder & CEO

Manual and automated Legionella monitoring take the same temperatures at the same points. The difference is who takes them and how often: a person with a thermometer once a month, or a sensor every few minutes.

Neither is right for every building. This post compares the two on cost, coverage, records and risk, and is plain about where manual checks still make more sense.

How each approach works

Manual. An engineer visits each site on a schedule, usually monthly. They run each sentinel outlet, wait, take a reading with a calibrated thermometer and write it in a logbook or an app. The same visit often covers flushing, inspections and other tasks.

Automated. A temperature probe is fixed at each monitored point. A small battery-powered unit reads it every few minutes and sends the result to a portal. Out-of-range readings raise an alert. Engineers visit when something needs attention, and for the tasks sensors cannot do.

Side by side

Manual roundsAutomated sensors
Readings per pointAbout 12 a yearOver 100,000 a year at five-minute intervals
Time to notice a problemUp to a monthMinutes to hours
Cost shapeLabour and travel, every visitHardware and install once, then a monthly fee
Cost as sites are addedRises in step with visitsRises with points, not with travel
RecordWritten by a person, after the factRecorded by the device, time-stamped
Missed checksEasy to miss, easy to backfillShown as a gap in the data
What it measuresWater at a running outletUsually pipe or supply temperature, continuously
Eyes on siteYes, every visitOnly when someone attends
Works with no connectivityYesNeeds a radio or mobile signal

What a monthly visit misses

A monthly reading is a two-minute sample of a system that runs all day, every day. Some problems never show up in it.

  • Overnight dips. A calorifier that falls below temperature at night and recovers by morning passes every daytime check.
  • Afternoon heat gain. A cold pipe running past a heat source can creep above 20°C for a few hours a day.
  • Outlets nobody uses. A sensor shows that a tap has not run for a fortnight, because pipe temperature shifts whenever water moves. A visit only shows that it ran today, because the engineer ran it.
  • Slow drift. A return temperature losing half a degree a month is invisible reading by reading, and obvious on a graph.
  • The day it broke. When something fails, continuous data shows when. A monthly log only shows it was fine last time.

This is the real case for automation. The value is less in any one reading than in how temperature changes over time.

Where manual still wins

Sensors are not the answer everywhere.

  • Small, simple sites. One building with a handful of outlets and someone on site every day can be checked by hand for very little.
  • Tasks that still need hands. Flushing, descaling showerheads, inspecting tanks and taking water samples are manual jobs today. Some of them, flushing first, can be automated, and that is where monitoring is heading.
  • Eyes on the system. An engineer notices a leaking valve, a missing tank lid or a dead leg left by a refit. A temperature probe does not see these directly. Some can be inferred from the data, such as a branch that never changes temperature because nobody uses it, but a trained eye still catches things a graph will not.
  • Sites with no signal. Deep basements and remote buildings can be made to work, but the cost of connectivity may outweigh the benefit.
  • Short tenancies. If you will be out of the building in a year, the install may not pay back. The sensors themselves can move with you to the next site, so it is the install labour that is lost, not the equipment.

Automation also brings its own upkeep. Batteries run down, probes get knocked, and someone has to act on the alerts. A system nobody watches is no better than a logbook nobody fills in.

The hybrid most sites end up with

In practice the choice is rarely one or the other. Sensors take over the routine temperature readings. People keep the work that needs judgement and hands, and visit less often but with a reason.

Four questions settle where the line sits for you.

  1. How many points across how many sites? The more travel between them, the stronger the case for sensors.
  2. Who uses the building? Hospitals, care homes and anywhere with vulnerable people gain most from catching problems early.
  3. How good are the records today? If rounds get missed or logbooks have gaps, automation fixes the weakest part first.
  4. What does a missed problem cost? Set the monthly fee against that, not only against the price of a visit.

Whatever the mix, the duties do not change. You still need a risk assessment, a written scheme and a competent person. Agree with them how sensor readings stand in for the checks in that scheme.

Frequently asked questions

Is automated Legionella monitoring better than manual? It gives far more readings and catches problems sooner. It does not replace flushing, inspection or sampling, so most sites use both.

Is automated monitoring cheaper? It depends on travel. Across many sites or many points it usually is. For one small building it may not be.

Can sensors replace the monthly temperature round? HSE's guidance says remote monitoring systems can be used to monitor hot and cold water systems, so they can take the readings. Whether they fully stand in for the manual check in your building is for your risk assessment and responsible person to decide.

Do I still need an engineer to visit? Yes, for flushing, cleaning, inspections, sampling and repairs. The visits become less frequent and more purposeful.

See what your system does between visits

Paqett builds and runs water hygiene monitoring that contractors and facilities teams use under their own brand. Talk to us about a pilot on one of your sites.

Sources

Keep reading

Compliance· · 4 min read

Chain of custody for sensor data

Compliance data only counts if you can prove nobody changed it. What chain of custody means for sensor readings, where logbooks fail, and what to ask a vendor.

Engineering· · 9 min read

Why per-device IoT pricing punishes fleets

Per-device and per-message IoT pricing scales with your success, not with what your fleet costs to host. A worked example at 1,000 and 50,000 devices, and the alternative.

Water hygiene· · 2 min read

Your rounds, plus the 29 days in between

A monthly temperature round is one reading per outlet. This is what the rest of the month looks like when a probe stays behind.

Engineering· · 5 min read

What chip for what kind of device

ESP32, Nordic nRF or RAK3172: which chip suits which kind of device, and what each one costs you.

Get new posts by email

One email when we publish. Nothing else.

Or talk to us about a deployment: water hygiene, white-label or built to spec.