The cooling tower duty most operators forget is a criminal offence
Written by the BlueWave team · Published · 6 min read
General information, not legal or regulatory advice. Your duties need your own competent advice.
BlueWave is Legionella compliance software for UK water hygiene contractors. BlueWave is not affiliated with or endorsed by the Legionella Control Association.
There is a duty on cooling towers that costs nothing, takes an afternoon, and is a criminal offence to skip. You have to notify the local authority, in writing, of the device before it is used. Under the 1992 notification regulations, a person in control of non-domestic premises must tell the local authority about any notifiable wet cooling tower or evaporative condenser, and operating one that has never been notified is an offence in itself.
It gets forgotten because of when it happens. Notification is a one-off task at the very start of a system's life, done once and never again, which makes it exactly the sort of thing everyone assumes someone else did. It sits outside the weekly and quarterly routine a water treatment contractor runs, so it never comes up on a service visit. Then the plant changes hands, or the contractor changes, and nobody can produce the notification because nobody knows whether there ever was one.
What the notification duty requires
The regulations are short and specific. The device is notifiable if it is a wet cooling tower or evaporative condenser. It is exempt if the water is not exposed to air, if it contains no water, or if it is connected to a mains supply only for cleaning purposes.
The Schedule to SI 1992/2225 sets out what the notification must contain: the address of the premises, the name of a person who can be contacted about the device, the number of notifiable devices on site, and the location of each one. Two further duties are the ones people miss. Any change to the information already given has to be reported within one month. And when a device is taken out of use for good, the local authority has to be told about that too. Notification is free. There is no fee and no downside, which is what makes forgetting it so avoidable.
If you take on a site with cooling towers and cannot find evidence they were notified, treat that as an open action, not a historical curiosity. Notify. It is cheaper than explaining to an inspector why the device has been running un-notified for six years.
The monitoring that sits on top
Notification gets the device on the register. Keeping it safe is the HSG274 Part 1 routine, and cooling towers are monitored harder than almost anything else because the whole point of the tower is to throw a fine aerosol into the open air.
The core cadence is weekly dip slides for general aerobic bacteria, with a target that stays consistently below 10,000 cfu/ml, and legionella samples at least quarterly sent to a UKAS-accredited lab. That runs alongside routine biocide dosing, regular inspection, and cleaning and disinfection on the schedule the risk assessment sets.
The action tables read at a different scale from domestic water
Here is where cooling towers trip up engineers who spend most of their time on hot and cold systems. The breakpoints are much higher. A cooling tower legionella result that would be routine on a tower is an emergency on a tap. One reproduction of the HSG274 Part 1 action tables sets them out roughly like this.
Aerobic count, from weekly dip slides:
| Result | Status | Action |
|---|---|---|
| Below 10,000 cfu/ml | Under control | Continue routine |
| 10,000 to 100,000 cfu/ml | Increasing | Review the programme, resample around 24 hours later |
| Over 100,000 cfu/ml | Out of control | Corrective action, shot-dose biocide, resample |
Legionella, from quarterly sampling:
| Result | Action |
|---|---|
| Not detected up to 100 cfu/l | Maintain the programme |
| Over 100 up to 1,000 cfu/l | Reassess the programme and resample |
| Over 1,000 cfu/l | Immediate action: shot-dose, resample around 48 hours later, investigate, disinfect |
| Top of the range (commonly cited above 10,000 cfu/l) | Shut down and fully disinfect |
Two honest caveats on that. The upper aerobic tier at 100,000 cfu/ml and the exact numbering rest mainly on that single reproduction of the tables, so treat them as indicative and check against HSG274 Part 1 itself. The below-10,000 aerobic target and the over-1,000 legionella action point are corroborated across several sources and are the two figures to hold in your head.
Now put the legionella numbers next to a domestic hot and cold system. On a tap, the reference points are 100 and 1,000 cfu/l: a detectable result at all prompts a review, and 1,000 is a serious problem. On a cooling tower, 1,000 cfu/l is where immediate action starts and the top of the scale runs an order of magnitude higher. Different system, different route of exposure, different levels. An engineer who applies the domestic scale to a tower will panic over a normal result; one who applies the tower scale to a tap will wave through a genuine failure. Knowing which table you are reading against matters as much as taking the sample.
Keeping the record where an inspector can find it
The notification, the quarterly results and the action taken against each breakpoint are three separate records that tend to live in three separate places, which is how the notification goes missing in the first place. Holding them together, dated, against the specific tower, is what turns a pile of certificates into something you can stand behind.
That is the job the BlueWave compliance records side does for cooling towers. You upload the notification to the tower's record. Each lab report is a PDF your office uploads to its booking, and someone there reads the result. The response is a reactive job against the same tower rather than a note in a separate remedial file nobody cross-references. Two years later, when the site changes hands or an inspector asks, the notification, the results and the response are filed against one tower rather than across folders.
None of this is difficult work. It is remembering the free legal step at the start, reading the results against the right table, and closing the loop when a breakpoint is crossed instead of leaving it open. Open loops are what get prosecuted, and an un-notified tower with a legionella exceedance and no recorded response is about the worst version of that. If cooling towers are new to your programme, the ACoP L8 checklist and the full task frequency table are where the rest of the duties sit.
Two questions sort the compliant towers from the exposed ones. Can you produce the notification for every tower on your books? And do you know, without looking it up, which action table the last legionella result was judged against? A shrug at either is the gap to close first.