The program is the thing testing exists to serve

What a program contains

The shape is consistent across the guidance documents in use, even where the details differ.

1. A description of the water systems, usually as a flow diagram: where water enters, where it is heated, where it is stored, where it goes, and where it stagnates.
2. The control points: the places in that diagram where something is measured or maintained.
3. The control limits: the range each control point is meant to stay inside.
4. Monitoring: who checks, how often, and how it is recorded.
5. Corrective action: what happens when a control limit is not met, decided in advance rather than in the moment.
6. Verification: confirming that the program is being followed and that it works, which is where testing sits.
7. Documentation: the record that any of this happened.

The free water management plan builder walks through these seven elements one at a time and produces a draft outline that the building’s team then completes and adopts.

Why the diagram is the hard part

Most buildings do not have an accurate record of their water systems. Renovations added branches, a wing was taken out of use, a fixture was capped but not removed, a heater was replaced with a different arrangement.

Every one of those is a place water can sit. The exercise of walking the building and drawing what is actually there routinely finds dead legs in the plumbing, unused outlets and mixing arrangements nobody had documented, and that finding is often worth more than the first round of samples.

Where testing fits

In program language, testing is verification: it checks whether the controls are achieving what they are supposed to achieve. That framing has two practical consequences.

• The sampling plan is derived from the diagram and the control points, not from a standard list of taps.
• The response to a result is decided in advance, in writing, as part of the program, which is what prevents an unexpected number from producing panic or paralysis.

How that plan is built, point by point, is on sampling and analysis.

Who writes it, and who owns it

Typically a team: facilities and engineering, who know the building; a water treatment or environmental professional, who knows the controls; and management, who own the decisions and the budget. Some buildings add clinical or infection-prevention staff, and in healthcare facilities that participation is expected rather than optional.

The program belongs to the building owner. A consultant can write it; nobody can own it on your behalf, and a program kept only in a vendor's files is a program you do not have.

Frequently asked