---
title: "Integrating Legionella records with facility management systems"
source_url: https://legionella.io/articles/integrating-legionella-records-with-facility-management-systems/
canonical_url: https://legionella.io/articles/integrating-legionella-records-with-facility-management-systems/
pillar: "Digital Logbooks & Record Keeping"
summary: "How to fold Legionella monitoring into your FM or CAFM system so records tie to assets, survive an audit, and never let a green dashboard hide a missed check."
primary_keyword: "FM integration"
date_published: 2025-09-16
date_reviewed: 2026-06-26
author: "Legionella.io editorial team (REMOTE TECH LTD)"
reviewed_against: "HSE L8 and HSG274 guidance"
region: "United Kingdom"
license: "(c) REMOTE TECH LTD. Quote freely with attribution and a link to source_url."
---

# Integrating Legionella records with facility management systems

Most buildings already run a facility management system that knows every asset, every planned task and every work order — except, often, the water-hygiene ones. Legionella monitoring tends to live somewhere else: a spreadsheet on a shared drive, a water treatment contractor's portal, a folder of scanned logsheets nobody opens until an auditor asks for them.

Pull the two together properly and your evidence trail tells one coherent story. Do it badly and you get a confident green dashboard sitting on top of records that fall apart the moment anyone checks underneath.

This checklist is for getting it right the first time — so the integrated records hold up at an audit, an insurance query, a handover to a new manager, or the worst case, an incident investigation.

## Why your FM system should hold the water records

The argument for integration is not tidiness. UK Legionella compliance rests on duty holders keeping records of the precautions taken, the monitoring carried out, and the management arrangements behind them, which L8 sets as a clear expectation [1]. If those records sit in a separate silo from the asset register and the work-order history, you are maintaining two versions of the truth and hoping they agree on the day you get inspected.

A facility management or CAFM platform already holds the asset register, the planned maintenance schedule and the contractor records. Folding Legionella tasks into that same spine means one place holds the asset, the task, the result and the exception. Done well, FM integration also kills the weekly chase for missing logsheets — a recurring, invisible cost that a good digital logbook removes (see [Case study: improved compliance with digital logbooks](https://legionella.io/articles/case-study-improved-compliance-with-digital-logbooks/) for how that plays out on a real estate).

## What an integrated record actually has to prove

Before the checklist, fix the target. A record is not proof of control because it exists; it is proof because it shows the right things. For each control task, an auditor or a new responsible person should be able to read off: which asset, who did the work, when, what the result was, whether that result was acceptable, and — when it was not — what happened next. HSG274 sets out the technical detail of what monitoring and inspection should capture for hot and cold water systems [2]; your integrated record needs to carry all of it, not a summarised tick.

## The integration checklist

Work through these in order. The first group is the one people skip, and it is the one that decides whether the rest is worth anything.

**Reconcile the two asset registers first**
- Map every asset and sampling point named in the current Legionella risk assessment to a unique asset or location record in the FM system, and list any that have no match.
- Reconcile the naming and IDs so a calorifier, TMV, storage tank or sentinel outlet is identified the same way in the risk assessment and in the work-order history.
- Confirm dead legs, low-use outlets and decommissioned assets are recorded deliberately, not quietly dropped because the FM system never carried a record for them.

**Turn the written scheme into scheduled tasks**
- Recreate each task from the written scheme of control as a planned maintenance task, carrying its frequency, its acceptable result or limit, and a named owner.
- Set tasks so they cannot be closed without the actual reading entered — a temperature, a description, a result — rather than a bare completion tick.

**Capture the full evidence every time**
- Record who carried out the task (named operative or user ID), the date and time, the asset, the result, and whether it fell in or out of range.
- Attach the supporting evidence where it matters: photographs, thermometer calibration records, flush confirmations, sampling and contractor reports.

**Wire up the exceptions, not just the completions**
- Configure an out-of-range or missed result to raise a corrective work order automatically and alert the responsible person.
- Require close-out evidence — what was done, by whom, and the re-check result — before any corrective action can be marked complete.

**Make it auditable and durable**
- Provide a read-only view or a clean export that ties tasks, results, exceptions and actions back to each asset, so an auditor is not handed raw database screens.
- Set a record retention period in line with L8 and your scheme, and confirm archived records stay readable through staff changes and system migrations.

## Putting it to work without fooling yourself

The danger with a slick integrated system is that the dashboard becomes the thing you trust instead of the water. Green should mean the task was done and the result was in range — not merely that the system generated the task on schedule. Spot-check the records underneath the colour now and then.

Watch the averages, too. A healthy site-wide average temperature can hide one sentinel outlet that has been running tepid for a month, and that single outlet is the one that matters. An integrated record earns its keep by surfacing the outlier, not smoothing it away.

Then there is the contractor question. Many water treatment providers keep their results in their own portal, which is fine until you realise your "integrated" evidence is actually a monthly PDF buried in an inbox. Decide explicitly how those results land against the right asset in your system, and where the master copy lives. If that pushes you toward hosting and access questions, [Cloud vs on-premise: where to host your Legionella data](https://legionella.io/articles/cloud-vs-on-premise-where-to-host-your-legionella-data/) covers the trade-offs. Whatever you choose, accountability stays with the duty holder — outsourcing the work or the software does not outsource the responsibility [3].

## Where the software stops

Integration organises evidence; it does not control water. A perfectly configured workflow proves nothing if the calorifier runs cool or a low-use shower never actually gets flushed. The retention periods, monitoring frequencies and acceptable limits you build into the system come from your own risk assessment, applied through L8 and HSG274 by a competent person — not from a software default someone clicked past during setup. And no dashboard replaces a competent person reading the exceptions and deciding what they mean. Where the risk assessment calls for sampling, treat it as verification that follows the system and the assessment, not a fixed calendar entry [4].

## FAQ

### Does putting our Legionella records in a CAFM system make us compliant?
No. The system stores and organises the evidence; compliance comes from controlling the water and being able to show it. A well-configured platform makes that proof far easier to produce and far harder to lose, but on its own it changes nothing about the underlying control [1].

### Our water treatment contractor keeps results in their own portal — is that enough?
It can be, provided those results reliably reach your record against the correct asset and you can retrieve them quickly at audit. The test is simple: if the contract ended tomorrow, would you still hold a complete, readable history? Accountability sits with the duty holder regardless of whose software the data lives in [3].

### How long should the integrated records be kept?
Set retention to match L8 and your written scheme; monitoring and inspection records are commonly held for several years. Confirm the current expectation against L8, and make sure a future system migration cannot quietly orphan the archive.

## A practical first move

Start with the reconciliation, not the software. Print the asset and sampling-point list from your current risk assessment, sit down with whoever administers the FM system, and tick off how many of those assets already exist as records you could attach a result to. The size of that gap is the real measure of the work ahead — and it tells you whether you are integrating genuine control or just switching on a module over the cracks.

## Related reading

- [Case study: improved compliance with digital logbooks](https://legionella.io/articles/case-study-improved-compliance-with-digital-logbooks/)
- [Cloud vs on-premise: where to host your Legionella data](https://legionella.io/articles/cloud-vs-on-premise-where-to-host-your-legionella-data/)
- [Building shutdowns: flushing and monitoring during low use](https://legionella.io/articles/building-shutdowns-flushing-and-monitoring-during-low-use/)

## 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, "Legionnaires' disease — what you must do". https://www.hse.gov.uk/legionnaires/what-you-must-do/index.htm
[4] HSE, "Testing and monitoring your water system for legionella". https://www.hse.gov.uk/legionnaires/testing-monitoring-water-system.htm