Priority facilities Six-monthly sampling Log per tap point

Legionella management plan software

Priority facilities must have an up-to-date risk analysis and a management plan, carry out the resulting measures periodically, keep a log and have samples taken every six months. Appfront builds the software that fills that log at the moment the work is done, rather than someone reconstructing it afterwards from scraps of paper.

What the Drinking Water Decree requires of you

If you own or manage a priority facility, fixed obligations apply for Legionella prevention. Priority facilities include hospitals and care institutions, buildings with accommodation such as hotels, bed and breakfasts, campsites and bungalow parks, swimming pools, saunas and wellness centres, marinas, asylum seeker centres and prisons, and roadside restaurants and petrol stations with shower facilities.

The obligations themselves can be summed up briefly: an up-to-date risk analysis and a management plan, drawn up by an advisory firm certified under BRL 6010, the periodic execution of the control measures from that plan, keeping a log, and six-monthly sampling to demonstrate that the installation is in order. The Human Environment and Transport Inspectorate supervises compliance.

The bottleneck is almost never the plan and almost always the log. Flushing rounds, temperature measurements and flushing of little-used tap points are jobs done in corridors, often by changing staff, sometimes outside office hours. If this is noted on paper and typed up later, a gap opens up between what was done and what was recorded. In an inspection, that gap is exactly what gets found.

How we build your Legionella software

We start from your management plan, not from a standard list. Every building has its own installation, and the plan that a BRL 6010 firm wrote for it is the starting point.

1
Turning the management plan into tasks

We go through your risk analysis and management plan and translate the measures into specific, recurring tasks with a frequency, a person responsible and a tap point or part of the installation. What is a paragraph in the plan becomes a task that appears on a list in the software.

2
Mapping the installation

Tap points, boilers, mixer taps, dead legs and the places the management plan identifies as high-risk each get their own identity. The log is tied to that. Without this structure, the log remains a chronological list in which you cannot see what happened at a specific tap point.

3
Building in sprints

We work in sprints and start with the daily tasks: flushing and measuring temperatures. Your own technical department works with us and does an early walk-through with an interim version, because only then do you find out whether a screen works with wet hands and gloves on.

4
Sampling and handover

We link the sampling and test results to the installation, set up the follow-up for an exceedance and hand over to your administrator. That includes a trial inspection: we go through the logbook as if we were the inspectorate.

What the software actually does

Six components that come back in almost every project. What you need depends mainly on how large your installation is and how many sites you manage.

Signing off at the tap point

A sticker with a code on the tap point or the installation; scanning it opens the right task straight away. The record is created where the work happens, with the time and the person who did it, instead of being written up from memory at the end of the day.

Flushing rounds and temperature measurements

A route along the tap points that are due according to the management plan, with the measured value alongside. If a temperature deviates from what the plan prescribes, it is visible immediately rather than only at the quarterly check.

Scheduling based on your management plan

The frequencies from the plan drive the task list: weekly, monthly, quarterly or six-monthly. Tasks that haven't been carried out don't disappear; they stay open and grow in urgency.

Samples and test results

For each sampling point, the date, the laboratory, the sample number and the result. Results stay attached to the point, so you see a series over the years and not just the latest measurement.

Follow-up on an exceedance

If the standard is exceeded, a fixed route kicks in: report where required, take measures, plan a resample and close the case only once the result is back in order. That process is defined in the system rather than in the head of whoever did it last time.

A logbook that stands up to inspection

Everything in one place, per site and per part of the installation, with date, person responsible and measured value, exportable whenever asked. Later changes are visible as changes and not passed off as the original.

Who we build for

Four types of priority facilities. The difference lies in the size of the installation and in who carries out the work.

Care facilities and hospitals

Large, complex installations and a vulnerable group of users, which makes the risk weigh heaviest. Often an in-house technical department, which does this alongside regular maintenance.

Hotels, campsites and leisure

Strongly fluctuating occupancy, so tap points sit idle in the low season and need attention precisely then. Often changing staff, so the software has to be usable without training.

Swimming pools, saunas and wellness

Warm water, many tap points and showers with a high aerosol risk. Here Legionella management and daily water quality checks overlap, and a single record for both makes sense.

Managers of multiple sites

Property managers and facility service providers who manage on behalf of third parties. Their question is not just carrying out the work but also proving it to the owner, alongside their facility processes.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

What we use follows from your situation. For work on the floor, offline use matters most: technical rooms and basements rarely have coverage, and a record that doesn't work there doesn't get used.

If you also want to keep your pool water logbook digitally, take a look at our software for the pool water measurement logbook.

If it's about the water quality in the pools themselves, with chlorine and pH per pool, take a look at our software for a swimming pool's water quality logbook.

Native iOS and Android Offline-first storage QR and NFC tags Node.js / Python / .NET PostgreSQL Time series per sampling point Integration with laboratories Import of results Building management system integration Alerts by email and in-app Roles per location Audit logging of changes Export for inspections Hosting in the EU

Why Appfront

Recording where the work happens

Every step between the action and the record is a place where something gets lost. We build so that signing off at the tap is quicker than writing it on a slip of paper.

Built on your management plan

We don't invent frequencies or measures; they are set out in the plan drawn up by your BRL 6010 consultancy. Our software carries out that plan and does not replace it.

We test against an inspection

Before we hand over, we go through the logbook with the question an inspector will ask: show me that this measure was carried out over the past year. Anything you can't find there isn't finished yet.

Alongside what already runs

Your building management system, your maintenance planning and your water systems stay in place. We build the layer that fills and connects the logbook.

Security and privacy

Legionella data is not personal data in itself, but the records do show who carried out what and when, and that can be traced back to an employee. That is performance information and calls for restraint: the logbook is meant to demonstrate that the work was done, not to hold anyone to account for how fast they walk their rounds. We therefore focus the reporting on the installation rather than the person.

For healthcare organisations, the software also has to fit within your existing security framework, often with its own requirements for access and logging. Sampling results can be sensitive in relation to guests or residents; we set separate permissions on these so that access is limited to those who need it. All changes to a signed-off record are logged, because a logbook that can be altered unnoticed after the fact is worthless in an inspection. How we handle security ourselves is described in our information security policy; external reports go through our CVD policy.

Frequently asked questions about legionella management

These include hospitals and healthcare institutions, buildings with accommodation such as hotels, bed and breakfasts with more than five guests, campsites and bungalow parks, swimming pools, saunas and wellness centres, marinas, asylum seeker centres and prisons, and roadside restaurants and petrol stations with showers. What they have in common is that aerosols are formed around people who have not chosen to be there or who are particularly vulnerable. If you're unsure whether you fall under this, have it confirmed before you build any software.

No, and it can't. The risk assessment and management plan must be drawn up by a consultancy certified under BRL 6010. Our software carries out that plan: it turns the measures into tasks with a frequency, records that they have been carried out and keeps the evidence. If your installation changes, that is a reason to have the plan updated, not to modify the software.

Priority facilities are required to sample twice a year. The sampling points follow from your management plan; what matters is not that two samples were taken somewhere, but that the right points were sampled. We therefore link every result to the point, not just the date, so that over the years you can see a series per point.

Then you need to take action and, in certain cases, report it. The exact route depends on the level of the measurement and on your situation; your BRL 6010 adviser determines that. What the software does is enforce that route as soon as a result comes in that exceeds the limit: the report, the corrective action and the resampling become tasks that stay open until the result is back within limits.

Yes, and here that is no luxury. Plant rooms, basements and pipe shafts rarely have coverage, and those are exactly where the installation components that need attention are located. The app stores data locally and synchronises as soon as there is a connection, with a clear view of which records are still pending. A record that only works online gets skipped in the corridor and filled in later from memory.

Yes, and that is usually precisely the reason to build it. Each location gets its own installation structure and its own management plan, with permissions that differ per location. On top of that comes an overview showing where tasks are outstanding and where a sampling is coming up. Standard packages are often built around a single location and get stuck there.

Often yes, and it is worth it if your installation already measures temperatures. Then an engineer does not have to record those values by hand, and manual work is limited to what are truly physical actions, such as flushing. Whether it is possible depends on the interface your building management system offers; we establish that in the discovery phase before we commit to it.

That depends on the number of locations, the size of the installations and whether integrations are involved. A single location with a straightforward installation is a different project from a care organisation with dozens of buildings. We give a well-founded answer after the discovery phase; before that it would be a shot in the dark.

Building legionella software?

Tell us how many locations are involved and how the logbook is currently kept, and we will help think through the structure of the installation, the tasks from your management plan and the follow-up when a limit is exceeded. We build this as a standalone application and as part of a broader project involving custom software or an app.

Edit content