Industry News30 April 2026

The Legionella Risk Assessment Software Landscape in 2026

A practical look at the tools assessors use today — LegionellaDossier, L8MS WebRAS, PocketSurvey, Vision Pro, TEAMS, Elmhurst, Micad — what they all share, where they fragment, and what an engineer-aligned tool would actually do.

If you carry out Legionella risk assessments in the UK, you almost certainly use software for at least part of the job. The question is which part, and how many separate tools you stitch together to get from a site visit to a signed-off PDF in the duty holder's inbox.

This article walks through the main tools currently in the UK market, looks at what they share, identifies where assessors lose time switching between them, and sketches what a tool aligned to the actual on-site workflow would have to do.

What's on the market

The notable platforms used for Legionella risk assessment and water-safety record keeping in the UK include:

LegionellaDossier. A platform aimed at compliance over a whole estate. It centralises an asset register, integrates with Bluetooth thermometers and IoT sensors, supports QR codes on assets, and produces compliant L8/HSG274 risk assessments on-site through a mobile app. Strong on continuous monitoring and remedial-action tracking across multiple sites.

L8MS (WebRAS). A long-standing risk-assessment authoring tool with a survey-assistant mobile app for offline plant and asset capture. Reports incorporate ACOP L8, HSG274, BS 8580, and LCA service-standard guidance, and can be exported to Microsoft Word. Sold per assessment credit, with separate products for commercial, residential, and mobile assessment workflows.

PocketSurvey Legionella. A general-purpose surveyor app retemplated for Legionella, runs on iPad, Android, iPhone, or browser. Designer- and template-editable, automated PDF report generation with photographs and site plans, ACOP L8 template included.

Vision Pro Software. Aimed at facilities managers and compliance officers. Mobile access, automated reminders, real-time reporting, task scheduling. Strong on ongoing monitoring and asset tracking; less specialised for the actual risk-assessment authoring step.

TEAMS Software. A start-to-finish solution for Legionella service-type providers. Strong on the administrative side -- scheduling, monitoring records, contract management for water-safety providers operating across many client sites.

Elmhurst Energy Legionella Software. Desktop and mobile, with a secure lodgement system. Free to scheme members; produces a certificate of completion alongside the assessment. Used widely in the residential and small-commercial space.

Micad Software. Estate-wide compliance platform, broader than Legionella -- covers asbestos, fire, and water safety together. Strong for organisations that already use Micad for adjacent compliance domains and want to consolidate.

There are others (PocketSurvey has multiple variants, several smaller assessor consultancies maintain their own tools, and a number of cooling-tower-specific products exist for the Part 1 audience), but the list above covers the platforms an assessor in the UK is most likely to encounter.

What they all do well

Walking across these tools, the same core capabilities appear repeatedly:

Mobile capture on-site. Every serious tool now ships with a mobile app, usually offline-capable, tablet-friendly. The browser-only era is over.
ACOP L8 / HSG274 alignment. All of them claim alignment to the same guidance documents. Most do it credibly.
Asset register. Tanks, calorifiers, outlets, sentinels, dead legs -- structured, queryable, often with photos.
Risk-rated findings. Some flavour of A/B/C, satisfactory/minor/moderate/high, or numerical scoring.
PDF report output. One-click generation of a branded report ready to send to the duty holder.
Monitoring records. Temperature monitoring schedules, sentinel logs, dosing records (depending on the platform).
Some form of action plan. A list of remedial actions derived from the findings, prioritised by severity.

These are no longer differentiators. They are the floor. If a tool doesn't have all of the above, it isn't competing.

Where the friction actually is

Talk to working assessors and the complaints are remarkably consistent, and they are not about features. They are about how the work flows.

The data is rarely in one place. Photos are captured in the mobile app. Temperatures are entered into a separate monitoring app, or pasted into a spreadsheet. The risk-assessment narrative is authored in a desktop tool. The action plan lives in a fourth system. By the time the report is generated, three or four separate sources have to be reconciled, and the assessor's job is increasingly to be a data integrator rather than a domain expert.

The data model is rarely the engineer's mental model. Most platforms are built around assets and tasks because that is what the compliance manager wants to see. But on-site, the engineer is thinking in terms of the system in front of them right now: what's connected to what, where the sentinels are, where the dead legs are, what the last temperature was, what the photo on the wall actually shows. When the software demands the engineer pivot from "system mental model" to "asset-task model" and back, every assessment becomes a translation exercise.

The report is generated, not authored. Auto-generated reports are convenient but they are also generic. They say what the template says, not what the engineer noticed. Most platforms make it hard to interleave engineer judgement into the structured output without breaking the template.

Multiple tools means multiple subscriptions. Cost compounds. So does training. So does the integration debt when one tool changes its API or gets acquired.

What "inline with engineer needs" would actually look like

The phrase that keeps coming up in conversations with practising assessors is: the data needs to be in line with what the engineer is doing on site, not what the back-office is asking for. They need to be ONE.

In practice, that means:

One mobile flow that mirrors the walkthrough. Open the app, describe the system, walk the site, answer the questions that actually apply. Photos attach to questions, not to a separate gallery. Temperatures attach to outlets, not to a separate log.
Dynamic question generation. Only the questions relevant to the system in front of you appear -- no scrolling past N/A items for sources you don't have. This is what HSG274's risk-based approach has been asking for since 2014, and most tools still don't do it.
One report that's already done when the assessment is. Sign-off should be the final step of the workflow, not a second mode where you re-author what you already captured.
One action plan. Findings of severity B/C automatically populate the action plan with timeframes drawn from HSG274 and ACOP L8. No double-entry.
One source of truth. Asset register, monitoring records, photos, findings, and the final PDF all live in the same data model, not in four integrated systems.

None of this is novel as an idea. It is hard as an execution -- which is why the market remains fragmented.

What L8Pro is exploring

L8Pro is a research project, not a commercial product (we have a non-commercial use notice for the reasons). The thing it is trying to demonstrate -- and the reason for building it at all -- is whether the workflow above is actually achievable as a single integrated tool, rather than a stack of integrations:

A dynamic assessment engine that generates only the questions relevant to the system in front of the engineer
Photos, temperatures, and notes attached directly to the question they answer
Severity ratings that flow automatically into a structured action plan
A single PDF that is the output of the assessment, not a separate document
Sign-off as the natural end of the flow, not a parallel ceremony

Whether that ends up being meaningfully better than the existing tools, or just different, is the question the project is asking. The tools above all do good work in their respective domains. The hypothesis L8Pro is testing is that combining the best of each into one straightforward flow -- aligned to what the engineer is actually doing on site -- is worth the engineering effort to find out.