A guest checks out of your hotel, flies home, and a fortnight later is admitted to a hospital in another country with pneumonia. You hear nothing. Then an email arrives from a UK public health team naming your building as a possible source. That email is the visible end of a surveillance machine most accommodation operators never see, and it is worth understanding before it reaches you.
The pathway that produced it crosses several countries, two public health systems and at least one European network, and it runs on a logic that is the opposite of how a duty holder usually thinks about risk. You watch your own building. This system watches dispersed strangers and works backwards to a shared address.
Why travel cases need their own network
Legionnaires’ disease has a long-ish incubation, commonly cited as up to around ten days [1], so by the time someone is diagnosed they are usually home, often hundreds of miles from where they breathed in the aerosol. A single sick traveller looks, to their local doctor, like an isolated community case. Nobody at that hospital has any reason to connect them to your shower, spa pool or cooling tower.
The pattern only appears when you pool cases across borders. Two guests from different countries, who never met, who fell ill in different cities, turn out to have stayed at the same accommodation within weeks of each other. No hotel and no single country would spot that alone. Catching it is the entire purpose of the European Legionnaires’ Disease Surveillance Network (ELDSNet), coordinated by the European Centre for Disease Prevention and Control (ECDC) [2].
ELDSNet runs two strands: the routine annual surveillance that produces Europe’s published case figures, and the faster travel-associated scheme that handles clusters in real time. It is the second one that generates the email to your inbox.
The cluster logic that triggers a query
A travel-associated case is, on its own, just logged, the traveller’s national centre reports it to ECDC with the accommodation they stayed at. The trigger is accumulation. When the network sees two or more cases who stayed at the same accommodation site within a defined window before they fell ill, commonly described as the two years preceding onset, though you should confirm the current operating definition against ECDC [2], that accommodation becomes a cluster site and a rapid notification goes to the country where the building sits.
This is why a single guest’s illness can sit silently against your address for many months and then suddenly matter when a second, unrelated case lands. The clock is long, and you are not told about the first one.
The notification chain, drawn out
Picture the flow as a line of boxes you could sketch on a whiteboard. It moves left to right, then loops back to you.
- Box 1, Exposure. A guest stays at your UK accommodation and inhales contaminated aerosol from a shower, spa pool, fountain or similar source.
- Box 2, Dispersal. The guest travels home to another European country before any symptoms appear.
- Box 3, Diagnosis. They develop pneumonia, are admitted, and a clinician confirms Legionnaires’ (often by urinary antigen, sometimes culture) and records a recent-travel history.
- Box 4, National report. The case is notified to that country’s national surveillance centre, which logs the accommodation and sends a travel-associated report to ECDC/ELDSNet.
- Box 5, Pooling. ECDC holds all travel reports from all member countries in one place and matches them by accommodation site.
- Box 6, Cluster detection. A second qualifying case at the same site within the window converts it from a logged case to a notified cluster.
- Box 7, Cross-border notification. ECDC alerts the UK collaborating centre, in practice UKHSA, that a UK accommodation is a cluster site [3].
- Box 8, UK action, looping back to you. UKHSA, usually working through the local authority’s environmental health team, contacts the building. You are asked to confirm a risk assessment and control regime are in place, carry out a satisfactory investigation, and report back, typically via a structured accommodation questionnaire, within a short deadline.
The two features that surprise operators are the direction and the delay. Detection happens downstream, abroad, and arrives weeks or months after exposure. Your only real defence sits upstream and continuous: the risk assessment, monitoring and records that already exist before any case is linked to you.
What the UK end actually requires of you
The European layer detects; it does not enforce. Enforcement is entirely domestic. Once UKHSA and the local authority are involved, you are inside the ordinary UK regime, the same ACoP L8 and HSG274 duties that apply on any normal day, now under scrutiny [4][5].
Expect, in broad terms: a request to evidence your current Legionella risk assessment and written scheme of control; questions about temperatures, monitoring and any spa pool or cooling system records; very likely a request for sampling to the relevant standard; and a tight turnaround on a reporting form back to public health. If your controls cannot be evidenced, the local authority can act under health-and-safety law, up to enforcement notices and, in serious cases, prosecution.
Separately, and often missed, there is a reporting duty running the other way. Where a case of Legionnaires’ disease can be linked to your work activity, the duty holder may have to report it under RIDDOR, a duty distinct from the surveillance flow above, with its own threshold and timeline. Treat the ELDSNet notification and any RIDDOR obligation as two separate questions, and confirm the RIDDOR trigger against the regulations rather than assuming the public health contact discharges it.
Where the system has blind spots
Two honest limitations are worth holding in mind. First, under-ascertainment: many infected travellers are never tested for Legionella, or are diagnosed without a recorded travel history, so a building can be a genuine source and never appear as a cluster. Absence of a notification is not evidence of a safe system. Second, attribution is probabilistic, being named as a cluster site means cases share your address in time, not that your building has been proven, by matched isolates, to be the source. Both facts argue for the same posture: get the controls right before anyone asks, because the surveillance signal is late, partial and outside your control.
This is general guidance on how the surveillance and reporting chain operates, not a compliance plan. What a notification specifically requires of your building, the sampling regime and the enforcement exposure all depend on your site and must be handled through a competent, site-specific risk assessment. Nothing here is legal or medical advice; clinical questions belong with the NHS or the treating clinician.
FAQ
We’ve had no UK guests reported ill, why are we getting a query from abroad?
Because the system is built for exactly that. Travel-associated surveillance pools cases across countries, so a UK accommodation can be flagged purely on the basis of overseas guests who fell ill after going home. You may never have had a single UK-reported case and still be named as a cluster site once two foreign cases line up against your address.
Will we be told who the affected guests are?
No. Patient identity and clinical detail stay within the public health and clinical systems for confidentiality reasons. You will typically be given the information needed to investigate, the period of stay and the nature of the exposure of concern, but not names. Your job is to evidence and improve the building’s controls, not to identify individuals.
Who pays for the investigation and sampling after an ELDSNet notification?
In practice the duty holder. The surveillance network and public health teams coordinate and assess, but the cost of demonstrating compliance, reviewing the risk assessment, sampling to the appropriate standard, and any remedial work, falls on the responsible person for the building, as it would in any UK Legionella investigation.
Does being named as a cluster site mean our building caused the cases?
Not on its own. A cluster notification means cases share your accommodation within a defined window, a strong signal that warrants urgent investigation, not proof of causation. Confirming a building as the actual source generally needs environmental sampling matched to a clinical isolate. Treat the notification as a serious prompt to act fast, while being precise about what it does and does not establish.
What to do before any notification arrives
Do not wait for the email. Pull your current Legionella risk assessment today and check it is in date, that your monitoring records for the last several months are complete, and, if you run spa pools, fountains or cooling systems, that those higher-risk assets are fully documented. The accommodation that handles an ELDSNet query calmly is the one that could have evidenced its controls the day before the query landed.
Sources
- UK Health Security Agency, “Legionnaires’ disease: guidance, data and analysis”. https://www.gov.uk/government/collections/legionnaires-disease-guidance-data-and-analysis
- European Centre for Disease Prevention and Control, “European Legionnaires’ Disease Surveillance Network (ELDSNet)”. https://www.ecdc.europa.eu/en/about-us/networks/disease-networks-and-laboratory-networks/eldsnet-about-us
- European Centre for Disease Prevention and Control, “Legionnaires’ disease”. https://www.ecdc.europa.eu/en/legionnaires-disease
- HSE, ACoP L8 (2013), “Carrying out a risk assessment”, p.12. https://www.hse.gov.uk/pubns/books/l8.htm
- HSE, HSG274 Part 2 (2024), “Operation and inspection of hot and cold water systems”, p.70. https://www.hse.gov.uk/pubns/books/hsg274.htm