In plumbing and water system contracting, the same sites produce the same problems year after year — because the job history lives in technicians' heads, not in a system every engineer can read before they arrive.
There is a pattern in plumbing and water system contracting that almost every company in the sector recognises. A particular site produces problems at a particular point every year. A pump that fails in the same way. A drain that blocks after heavy rain. A water temperature reading that drops out of compliance during summer. The symptoms are predictable. The response is still reactive.
The reason sites repeat the same problems is not that the problems are unsolvable. It's that the history of what has happened at each site — what was found, what was fixed, what was recommended — lives in the memories of the technicians who visited, not in a record that every engineer can read before they arrive.
In most plumbing and water system companies, site knowledge is held by individuals. The senior engineer who has been visiting the same hotel complex for three years knows the quirks of the building's water distribution system. He knows which TMVs are prone to drift, which outlets have had persistent Legionella risk readings, and that the third floor plantroom is inaccessible on Tuesdays because of a building management conflict.
This is institutional knowledge, and it is valuable. It is also invisible to anyone who is not that engineer. When he is unavailable, a colleague visits the site cold — with no access to that history. The first hour of the visit is spent identifying things that are already known. Recommendations made on previous visits may be repeated without knowing whether they were previously quoted, approved, or rejected.
For companies managing water hygiene compliance programmes, the regulatory obligation adds another layer of complexity to the site history problem. Legionella risk assessments, water temperature monitoring records, TMV service records, and schematic updates all need to be current, accessible, and auditable. In the event of a Legionella incident, these records are the first thing that will be examined.
Most companies hold this documentation in a combination of client-specific folders on a shared drive, paper records in lever arch files, and email chains. The documentation exists — but it is not systematically linked to the site's asset records, it is not automatically flagged when it is due for update, and it is not easily accessible to an engineer on site who needs to check the last temperature reading before proceeding.
Reactive breakdown work is an important revenue stream for plumbing contractors — but it is also where the site history problem has the most immediate commercial impact. An engineer attending a breakdown needs to diagnose quickly. If they have access to the full history of what has been done to that system — previous faults, repair records, parts replaced, current warranty status — the diagnosis is faster and more accurate. Without it, they are starting from scratch.
In the worst cases, a breakdown is attended, a repair is made, and the engineer leaves without realising that the same fault has been attended twice in six months — because the previous job was handled by a different engineer and the records aren't linked. The client notices. The company doesn't.
For plumbing and water system contractors, a useful per-site record needs to hold: a list of all assets with their current condition and service history; all previous visit reports linked to specific assets; all current compliance obligations with their due dates; all open recommendations that have not yet been quoted or approved; and all current documentation (schematic drawings, risk assessments, certificates) in a format that can be accessed from a mobile device on site.
This is not a large technical requirement. It is a data structure problem — one that most off-the-shelf job management tools do not solve well for water systems specifically, because the asset-level compliance tracking is more granular than those tools are designed for.
When site history is captured systematically and made accessible to every engineer, several things happen simultaneously. Repeated site problems are identified and addressed rather than just managed. Follow-on quotations are generated from recommendations that are tracked rather than forgotten. Compliance obligations are flagged before they lapse rather than after. And the company's risk exposure — in an industry where documented negligence carries real consequences — is significantly reduced.
The senior engineer's knowledge doesn't disappear when he leaves the company. It lives in the system. Every engineer who visits that site after him starts with everything he knew.
Lyt Brox System
The Flow system is built for exactly this.
See how Flow handles these operational challenges in practice.
Explore FlowNext step
We run a focused operational review — no sales deck, no generic demo. We look at how your workflows actually run and show you where the system would change the outcome.
Book Operational Review