A registration logo on a contractor’s quote tells you they have signed up to a standard. It does not tell you whether your water system is under control this week. Those are different questions, and mistaking the first for the second is how a compliant-looking site still ends up with a positive sample and an awkward phone call.
The Legionella Control Association (LCA) registers service providers who commit to its Code of Conduct and a set of service standards [1]. That commitment is worth having. But its value is wasted if you treat the badge as the finish line. The sharper move is to take the standards the LCA expects of a provider and run them back over your own arrangements as a fault-finding exercise.
What LCA registration actually signals
Under the ACoP L8, anyone carrying out Legionella control on your behalf must be competent, and you have to be able to show how you satisfied yourself of that [2]. LCA registration is one recognised route to that assurance: it means the provider has formally committed to a published Code of Conduct and to delivering against defined service standards [1].
What it is not is a transfer of responsibility. The legal duty stays with you, registered provider or not [3]. And registration describes the provider’s general commitment, not the state of your cold tank, your calorifier or your rarely-used shower today. A registered provider can still under-deliver on one contract, and a duty holder can still fail to act on what a good provider reports. Both happen, and neither shows up in a logo.
Start with the symptom, not the certificate
Most failures arrive quietly. A monitoring round slips by a fortnight. A hot return reads a couple of degrees low and nobody flags it. A monthly contractor report ticks every box and has never once recorded an exception, which should worry you more than a report full of them. A sample comes back positive at a single outlet.
The instinct is to fix the immediate task and move on. The better habit is to ask what that symptom reveals about the system that produced it, then trace it back. The LCA service standards are useful here precisely because they give you ready-made headings to check against: clear scope, competent people, monitoring done and recorded, results interpreted, and action recommended when something is out of range.
Tracing a failure back to its cause
Work left to right. Name the symptom, reach for the most likely cause first, run the check that confirms or kills it, then act. If the same weakness turns up in more than one row, you have a system fault, not a one-off defect.
| Symptom you noticed | Most likely cause | The check that confirms it | What to do |
|---|---|---|---|
| Positive sample at one low-use outlet | Stagnation; a control that was scheduled but not actually performed | Flushing records against how the outlet is really used, and whether it was ever on the schedule | Flush and reassess; then ask why the gap wasn’t caught in routine reporting |
| Monitoring rounds repeatedly missed | Unclear split of responsibilities between you and the provider | The written allocation of duties and the agreed scope, plus who signs off each round | Confirm scope in writing and name one person who reviews the evidence |
| Reports that never record an exception | A tick-box service, or readings nobody interrogates | Whether out-of-spec results are recorded with a recommended action, the discipline a service standard exists to enforce | Ask the provider to show their last few flagged exceptions; if there are none across many sites, reassess them |
| Risk assessment actions still open months on | No owner for remedial work | The open-actions log and who is accountable for closing each item | Assign owners and dates; treat repeat slippage as a management failure, not a paperwork one |
| An inspection concern or improvement notice | A systemic gap, not a single defect | All of the above at once, plus whether management actually reviews the data | Run the whole grid; fix the conditions, not just the cited item |
The grid is deliberately blunt. Its job is to stop you closing a symptom without finding the cause, because an unfound cause rebuilds.
When the provider is the problem
If the rows keep pointing at the same place, vague scope, reports with no exceptions, recommendations that never become action, the fault may sit with the provider rather than the plant. This is where registration earns its keep a second time: it hands you a concrete standard to measure them against, and to re-tender against if it comes to that.
Ask direct questions. Can they show competence records for the people actually attending your site, not just for the company? How do they handle a result outside the action level, who do they tell, and how quickly? Will they put their scope and your retained duties in writing? A genuinely competent provider welcomes those questions. Reluctance to answer them is itself a finding, and it is the kind of finding an HSE inspector tends to surface anyway.
What registration can and cannot do for you
Treat none of this as a stand-in for your own risk assessment. LCA registration supports competence; it does not set your control limits, choose your monitoring frequency or close your remedial actions. Those come from a competent, site-specific assessment, and monitoring intervals in particular follow that assessment rather than any membership scheme [4]. The duty to manage the risk is not something you can hand to a third party along with the work [3]. Registration narrows the question of who is competent to help; it never answers the question of whether your site is safe today.
FAQ
Does hiring an LCA-registered provider make us compliant?
No. It helps you show that the people doing the work are competent, which is part of the picture. Compliance still rests on a current risk assessment, controls that are genuinely carried out, and records that prove it, and the legal duty stays with you [3].
Is LCA membership a legal requirement?
No, it is voluntary. The law requires competent help; registration is one well-recognised way to demonstrate you assured yourself of that competence [2]. A non-registered provider can be perfectly competent, but you then carry more of the burden of evidencing how you checked.
We are satisfied with our contractor, so is there any point auditing them against the LCA standards?
Yes, especially if their reports never surface a problem. Running your own arrangements against the standards costs little and tends to expose the quiet gaps, unclear scope, unreviewed data, open actions, long before a sample or an inspector does.
Sources
[1] Legionella Control Association, “Code of Conduct for Service Providers”. https://www.legionellacontrol.org.uk/ [2] 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 [3] HSE, “Legionnaires’ disease - what you must do”. https://www.hse.gov.uk/legionnaires/what-you-must-do/index.htm [4] HSE, “Legionnaires’ disease: Technical guidance (HSG274)”. https://www.hse.gov.uk/pubns/books/hsg274.htm