Reactive monitoring is the strategy nobody chooses on purpose. You drift into it. The flushing schedule slips, temperature checks become “when someone remembers”, and the first real signal that something is wrong arrives as a guest complaint, a hot sample, or a call from someone investigating a case. By then the evidence is describing a problem that already happened.
Proactive monitoring reverses the order. You generate routine evidence on a schedule, so control is shown continuously and a drift gets caught while it is still just a drift. That is the comparison worth making — not which approach is less hassle this week, but when each one hands you the information, and whether the information can still prevent harm. Under UK guidance the proactive posture is the default expectation, not an optional upgrade [1].
What each one actually means on site
Proactive monitoring is the planned stuff: routine temperature checks at sentinel and representative outlets, flushing low-use outlets on a set interval, periodic inspection of tanks and fittings for scale and sediment, and sampling where the risk assessment calls for it. Crucially, it records both the in-range readings and the exceptions. The exceptions are the point — they tell you whether the organisation actually responds when a result drifts out of limit.
Reactive monitoring is what happens when checks are triggered only by an event: a temperature complaint, a positive result somewhere else in the estate, a refurbishment, or an outbreak inquiry. Sampling after the fact. Reheating a calorifier once it has already cooled. Flushing a wing because someone finally noticed the rooms were empty.
Here is the part that trips people up. Every good proactive programme contains reactive elements — you react to exceptions, that is the whole mechanism. The trap is mistaking exception-response for a strategy. Fixing problems as they surface is not a monitoring plan; it is the absence of one with extra steps.
The criteria that actually matter
Convenience is the wrong axis to judge these on, because reactive almost always wins on convenience in any given week and loses on everything that counts. Judge them instead on four things: how early you learn of a problem, how good the evidence is and whether it covers the whole system or one tap at one moment, where the effort and cost fall, and what the records prove if the HSE or your insurer asks.
On that last point, HSE is explicit that the frequency and type of testing depend on the system and the risk assessment, not on a calendar of convenience [2][3]. L8 and HSG274 frame routine monitoring as the evidence that your control scheme is working, not as a substitute for the controls themselves. And a clean sample is narrow evidence: it describes the sampled outlet at the moment it was sampled, which is useful but is not a verdict on the system [4]. If your only “monitoring” is the occasional triggered sample, you are reading a single frame and calling it the film — worth understanding alongside on what CFU counts actually tell you.
Proactive and reactive, side by side
| What you’re judging | Proactive monitoring | Reactive monitoring |
|---|---|---|
| When you learn of a problem | While it is still a drift — an out-of-range temperature, a missed flush | After it has consequences — a complaint, a hot sample, an outbreak query |
| Evidence it produces | A continuous, dated record of control across the system | A snapshot taken after the event, usually of one outlet |
| Where effort and cost land | Steady and schedulable, planned around the building’s use | Lumpy and urgent — call-outs, disinfection, investigation, lost rooms |
| What it shows a regulator | That control was managed and recorded over time | That you responded once something had already gone wrong |
| What it cannot do | Eliminate every exception | Prevent the harm it is reacting to |
The bottom row is the honest one. A reactive sample taken after a suspected case cannot un-expose the person who breathed the aerosol. Proactive monitoring cannot promise zero exceptions either, but it catches them at the temperature gauge rather than at the GP surgery.
Which to lean on, and when
For almost any occupied building with stored or recirculated water, a planned scheme is the only posture that meets the duty to control the risk and keep records of having done so [1][5]. So proactive is not really “the better option” in a free choice — it is the baseline.
Reactive responses still have a real and necessary role, but inside the proactive scheme rather than instead of it. Investigating a positive result, sampling during an outbreak inquiry, escalating a temperature exception, re-checking after remedial work: these are legitimate triggered actions. They are responses to specific events, not a way to monitor a building day to day.
Take a low-use shower in a rarely-let room. Under a proactive scheme it sits on a weekly flush task, the missed flush escalates to the responsible person, and a pattern of misses prompts a review of how that room is used. Under a reactive posture you find out it was a problem when the next occupant turns the shower on. Same fitting, same bacteria, completely different moment of discovery.
So the practical decision is rarely “proactive or reactive”. It is “a proactive scheme with disciplined exception-handling” versus “no real scheme, with fire-fighting dressed up as a plan”. Frame any budget conversation that way and the cheaper-looking option stops looking cheap. If you want to push proactive further, continuous in-line sensors move some checks from periodic to live — covered in on continuous water quality monitoring.
A note on applying this
None of the above is a schedule you can lift onto your own site. Which outlets count as sentinel, how often you flush or check temperatures, what result is acceptable, and which exceptions should trigger a sample are all set by your own risk assessment and written scheme, applied by a competent person. Copying another building’s frequencies is itself a reactive habit. And no result, proactive or reactive, ever licenses you to ignore a control failure you already know about — a tepid stored temperature, a dead leg, fouled fittings or a lapsed treatment regime [2].
Do this one check this week
If you are unsure which posture you are actually running, run a quick honest test. Pick your three least-used outlets and ask: if one drifted out of temperature tomorrow, when would we know? If the truthful answer is “eventually”, you are running reactive monitoring whether you meant to or not. Put those three outlets on a written, dated task with a named escalation route, and you have started the switch from finding out late to knowing early.
FAQ
Is reactive monitoring ever acceptable on its own?
Not as a primary strategy. Triggered checks — sampling after a positive result, responding to a temperature exception, investigating during an outbreak inquiry — are necessary, but they belong inside a planned scheme. Relying on events to tell you when to look means accepting that some problems will only surface once people have already been exposed.
Does going proactive mean sampling more often?
Usually no. Proactive monitoring is mostly temperature checks, flushing of low-use outlets, and inspection — the controls and the routine evidence that they hold. Sampling is verification, used where the risk assessment calls for it, and HSE is clear that its frequency and type follow the system and the assessment rather than a fixed interval [2][3].
What is the fastest way to move from reactive to proactive?
Start with the written control scheme and a task schedule for your highest-risk, lowest-use outlets. Log every reading, including the ones that pass, and define what an out-of-limit result triggers and who owns the response. Once exceptions are caught and escalated automatically, you are proactive in practice, not just on paper.
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, “Testing and monitoring your water system for legionella”. https://www.hse.gov.uk/legionnaires/testing-monitoring-water-system.htm [4] BSI, “BS 7592:2022 - Sampling for Legionella bacteria in water systems. Code of practice”. https://knowledge.bsigroup.com/products/bs-7592-sampling-for-i-legionella-i-bacteria-in-water-systems-code-of-practice-1 [5] HSE, “Legionnaires’ disease - what you must do”. https://www.hse.gov.uk/legionnaires/what-you-must-do/index.htm