---
title: "Managing records across multiple sites"
source_url: https://legionella.io/articles/managing-records-across-multiple-sites/
canonical_url: https://legionella.io/articles/managing-records-across-multiple-sites/
pillar: "Digital Logbooks & Record Keeping"
summary: "Keep Legionella records across a property portfolio consistent and ready to produce a complete trail for whichever single site an inspector picks."
primary_keyword: "multi-site records"
date_published: 2025-11-05
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."
---

# Managing records across multiple sites

In a single building, record-keeping is a habit. Across forty buildings it becomes a system problem, and the way it fails changes. A portfolio rarely falls over because one site is sloppy. It falls over because no two sites record the same task the same way, so when an inspector walks into the one depot that matters today, nobody can lay hands on a clean, complete trail for that building.

Multi-site records have a job that single-site records don't: they have to be comparable and pullable. Comparable, so you can tell a failing site from a safe one without driving there. Pullable, so any one site's full history reaches a desk in an hour, not after a week of chasing a contractor who left in March. Get those two properties right and the sheer number of sites stops mattering.

The duty does not dilute as you add buildings. L8 expects the duty holder to keep records of the precautions, the monitoring and the management arrangements, and to appoint competent people to run them [1]. Each site still needs its own site-specific risk assessment and its own written scheme of control [2] — a portfolio system holds all of those, it does not merge them into one.

## The check, grouped by what each part proves

Run this against the whole estate, not against a single logbook. Each group answers a different question an auditor or an incident reviewer will actually ask.

**Make records comparable (set once, across every site)**
- Standardise the task vocabulary so a "monthly TMV check" or a "weekly little-used outlet flush" means exactly the same thing at every site.
- Tag every asset to one convention — site code, asset type, location — so an outlet reference is unambiguous across the estate.
- Hold a current, site-specific risk assessment for each building and record its review date; never stretch one master assessment over the portfolio.
- Name the responsible person for each site, and record who deputises when they are away or the site changes hands.

**Hold the evidence each site must produce**
- Keep task history showing who did it, when, against which asset, the result, and whether it was in or out of range.
- Link every out-of-range reading to the remedial action and its close-out, not just to a flag on a screen.
- File cleaning, descaling and sampling reports against the specific asset, with the contractor's scope and findings — not only the invoice.
- Capture a real sign-off so a completed task is attributable to a named person, not an anonymous tick. ([Digital signatures and verification for maintenance tasks](https://legionella.io/articles/digital-signatures-and-verification-for-maintenance-tasks/) covers making that attribution stand up.)

**Give head office a real portfolio view**
- Maintain a live register of all sites: current risk-assessment date, named responsible person, and open actions.
- Surface exceptions rather than averaging them — one red site must never disappear into a green portfolio mean.
- Show overdue and missed tasks by site, so attention goes where the gap actually is.

**Be ready for audit, handover and incident**
- Be able to export one chosen site's complete trail for a date range on demand.
- Keep a handover pack template so a site changing manager keeps an unbroken record.
- Set a record retention period per record type and apply it automatically to every site.
- Back the whole digital logbook up and test the restore — across a portfolio the records become a single point of failure if they live in one place. ([Backup strategies for digital Legionella records](https://legionella.io/articles/backup-strategies-for-digital-legionella-records/) goes into this.)

## Putting it to work

The fastest way to find out whether the system actually works is to attack your own weakest point. Pick the least-visited site — the small office, the seldom-staffed store — and try to produce its last six months of Legionella evidence in under an hour: the flushing records for its little-used outlets, the temperature readings, the last sample, the open actions. If you can't, the problem is the system, not that site. One dry run tells you more than any dashboard.

Write down the decision, not only the task. "This site's reception kitchen tap is flushed weekly because the unit is staffed two days a week; missed flushes escalate to the area manager; three misses trigger a use-pattern review." Recorded that way, an audit trail explains itself months later to someone who has never set foot in the building.

## What multi-site managers skip

Three gaps account for most portfolio failures, and none of them show up on a green dashboard.

The orphaned site. A building gets acquired, a contractor is TUPE'd across, the previous manager leaves — and nobody is named as responsible for it. It runs on momentum until the day it doesn't.

The flattering average. A group rolls compliance up to a single number and reports 96%. The missing 4% is one residential site with three months of skipped flushes. Averages hide exactly the outlier you needed to see.

Inconsistent naming. When site A calls it "Shower 3" and site B calls it "GF male WC, far head", you cannot compare, trend or audit across the estate, and every handover starts from scratch.

## What this can and can't settle

A multi-site system records control decisions; it does not make them. What counts as an acceptable reading, how often each outlet is checked, and how long each record is kept all flow from each building's own risk assessment, carried out by a competent person, and from your own retention policy. Treat any single figure you carry between sites — a temperature, a flushing interval, a retention period — as something to confirm against current guidance for that building, never a portfolio default to apply blindly.

## FAQ

### Do we need a separate risk assessment for each site, or can one cover the whole portfolio?
Each building needs its own site-specific assessment, because the systems, users and risks differ from one site to the next [2]. A central system should store and track every site's assessment and its review date; it should not blend them into a single document that fits none of the buildings precisely.

### How long should we keep Legionella records across all our sites?
Long enough to cover audit, handover and any later incident review, and applied consistently to every site rather than left to each manager's discretion. L8 sets out how long records of monitoring and management arrangements should be retained [1]; fix a retention period per record type and let the system enforce it. Confirm the exact periods against current guidance before you write the policy.

### If we move to one group-wide logbook, is head office now the responsible person?
No. The legal duty sits with the duty holder, and centralising the records does not move accountability [3]. Each site still needs a named local responsible person who can explain why each control exists and what happens when a result falls outside the limit; the group system simply gives them — and head office — shared evidence.

## Related reading
- [Backup strategies for digital Legionella records](https://legionella.io/articles/backup-strategies-for-digital-legionella-records/)
- [Scaling up: Legionella in large vs small buildings](https://legionella.io/articles/scaling-up-legionella-in-large-vs-small-buildings/)
- [Digital signatures and verification for maintenance tasks](https://legionella.io/articles/digital-signatures-and-verification-for-maintenance-tasks/)
- [Continuous water quality monitoring systems](https://legionella.io/articles/continuous-water-quality-monitoring-systems/)

## 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