---
title: "Case study: improved compliance with digital logbooks"
source_url: https://legionella.io/articles/case-study-improved-compliance-with-digital-logbooks/
canonical_url: https://legionella.io/articles/case-study-improved-compliance-with-digital-logbooks/
pillar: "Digital Logbooks & Record Keeping"
summary: "How a UK facilities team turned scattered paper logbooks into an audit-proof Legionella record, and the one habit that made digital compliance actually stick."
primary_keyword: "digital logbook case study"
date_published: 2025-09-06
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."
---

# Case study: improved compliance with digital logbooks

Switching to a digital logbook does not, on its own, make a building any safer. The water is exactly as hot, as cold, or as stagnant as it was the day before. What changes is how clearly you can see what is happening, and how hard it becomes to let a gap quietly slide. That distinction is the whole reason digital record keeping tends to lift compliance, and it is also where people draw the wrong lesson.

The account below is illustrative: a composite built from patterns that recur across UK facilities teams, not a real named organisation. The decisions in it, though, are real ones, and most responsible persons will recognise at least one.

## The team before the switch

Picture a small in-house team looking after a dozen mixed sites: a couple of offices, a leisure centre, a handful of community buildings. An LCA-registered contractor handled the monthly temperature monitoring; the responsible person reviewed the folders each quarter. Every plant room held a paper logbook, and on paper everything looked fine. Readings were written down. Boxes were ticked. The annual sample came back clean.

The work was genuinely being done. The problem was that the records could not prove it. Out-of-range readings were noted, but nothing in the folder showed what happened next, whether a tepid outlet was re-checked, flushed, reported, or simply written down and forgotten. A few pages were missing where a logbook had been left out in a damp plant room. One site's folder had walked off with a contractor who had moved on. Ask "show me that this control worked all year", and the honest answer was a shrug.

## What the audit could not prove

The trigger was not an outbreak. It was a routine insurance-led audit that asked an awkward question: for a sample of out-of-range readings, demonstrate the corrective action. The team could not. The readings existed; the response did not.

This is the gap auditors and the HSE care about. L8 expects duty holders to keep records of the precautions taken, the monitoring results, and the management arrangements that show the system is under control [1]. A reading on its own is just data. The record that matters is the chain: the reading, the judgement against the limit, the action taken, and the sign-off that it was resolved. An audit trail that stops at the reading is not really an audit trail at all. Paper had captured the first link and dropped the rest.

## What changed when the records went digital

The fix was not "buy software". It was deciding what a record had to prove, then choosing a system that enforced it. The decisions that mattered:

- Every task was tied to a specific asset, this calorifier, that shower, not just "hot water, Site 3".
- Each entry carried a timestamp, the operator, the reading, and an automatic in-range or out-of-range flag, so nobody had to remember the limit while standing at the sink.
- An out-of-range reading could not be closed without an escalation note and a recorded action. The system would not let it disappear.
- Photos and contractor reports attached to the asset, so the evidence lived in one place rather than split between a folder, an inbox, and someone's memory.

None of that is exotic. It is simply the difference between recording that a task happened and recording whether the control worked. Monitoring frequency still came from the risk assessment, not from the app's defaults [2]; the software changed the proof, not the regime.

## The pattern hiding in the data

The most useful thing the new system did was let the responsible person read three months at a glance, and that is where a quiet pattern surfaced. One low-use wing was flushed late after every school holiday. No single miss looked serious; each was a day or two adrift. Together they were a predictable management gap that paper, scattered across separate folders, had hidden completely.

The fix was not another reminder. It was a holiday-mode task list, with named cover and a restart check before the wing reopened. That is the real payoff of better records: not the dashboard, but the decision it finally makes obvious.

## Where digital nearly made it worse

Here is the part the sales demo skips. A dashboard that shows almost everything green is reassuring, and reassurance is dangerous. Averages bury the exceptions, and the exceptions are the entire point. One repeatedly tepid outlet matters more than a hundred outlets that are fine. For the first month the team watched the headline figure and missed the holiday pattern entirely. Compliance improved only when they started reading the exceptions report instead of the summary tile.

A logbook that hides poor performance behind a green average is worse than a messy paper one that forces you to turn the pages. The duty holder still carries accountability for what the system is reporting, and for what it is not. Using a contractor, or a polished platform, does not move that responsibility anywhere [3].

## Lessons you can carry to your own records

You do not need this team's software to get most of the benefit. You need its habits.

- Record the decision, not just the task. "This outlet is flushed weekly because use is intermittent; a missed flush escalates to the responsible person; repeated misses trigger a use-pattern review" is worth far more than a tick.
- Make out-of-range entries impossible to close without an action. If your current method lets a failed reading sit unanswered, that is the first thing to change.
- Read the exceptions, not the average. Put a monthly look at everything that fell outside its limit in the diary.
- Test the handover. Could a new responsible person reconstruct the last quarter from the records alone? If a folder leaving the building would take the evidence with it, you have found your weak point.

## Before you trust your own logbook

Treat this as general guidance, not legal or design advice. A logbook, paper or digital, is a record of control and never a control in itself; changing the format will not cool a system that is running warm or move water that is sitting still. The limits, frequencies, and acceptable results that belong in it come from your site's risk assessment and written scheme, set by a competent person, not from a template or a default setting. Keep monitoring and inspection records for the retention period your scheme specifies; the duty to retain them does not depend on whether they live on paper or on a screen [1].

## FAQ

### Does moving to a digital logbook count as a control measure?
No. It is an evidence and management tool, not a control. The controls are temperature, water movement, cleanliness, and treatment; the logbook proves you ran them. A digital system improves the proof and the oversight, which is why it tends to improve compliance, but a perfect record of an uncontrolled system is still an uncontrolled system.

### Can we keep our old paper records after switching?
Yes, and you should keep them for as long as your scheme's retention period requires. The duty to retain monitoring and inspection records applies to historic paper logs exactly as it does to new digital ones [1]. A clean cut-over date, with the old folders archived and findable, avoids an awkward gap if an incident review later needs the earlier history.

### Our contractor uses their own app: does that cover us?
It helps, but the records still have to be yours to produce on demand. A contractor performing tasks under their own system does not take on your accountability as duty holder [3], and a reputable service provider should be giving you records you can audit and keep [4]. Make sure you can export or access the full history, not only a monthly summary.

## Related reading

- [Training staff on digital logbook systems](https://legionella.io/articles/training-staff-on-digital-logbook-systems/)
- [UK guidance on Legionella sampling frequency](https://legionella.io/articles/uk-guidance-on-legionella-sampling-frequency/)
- [Integrating Legionella records with facility management systems](https://legionella.io/articles/integrating-legionella-records-with-facility-management-systems/)
- [Legionella in retail stores and shopping centres](https://legionella.io/articles/legionella-in-retail-stores-and-shopping-centres/)

## 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] Legionella Control Association, "Code of Conduct for Service Providers". https://www.legionellacontrol.org.uk/