Offshore installations run on systems that rarely make headlines until something goes wrong. Potable water is one of them. It sits quietly behind the more obvious risks of process safety, drilling, and lifting operations, yet a failure in water quality can put an entire workforce at risk within days.
OEUK's guidelines on environmental health for offshore installations address exactly this gap, setting out expectations for potable water system design, construction, routine treatment, and ongoing risk management, including the control of legionella. The guidance is detailed and technically sound. The harder question for operators is not what good practice looks like, but how to prove, week after week, that it is actually being followed on every installation, on every shift, by every contractor involved.
Water safety is a verification problem, not just an engineering one
A well-designed potable water system can still fail if the routine tasks around it slip: a disinfection check missed, a storage tank inspection delayed, a sampling result filed but never actioned. None of these failures look dramatic in isolation. Together, over time, they are how legionella risk and water quality incidents actually happen offshore.
This is the same pattern seen across other offshore assurance disciplines. Joint integrity, scaffold inspections, and control of work systems all share the same underlying challenge: the standard is clear, but the evidence that it was followed consistently is often scattered across logs, paper records, and individual memory. Our earlier piece on why joint integrity management matters offshore makes the same point about bolted connections that applies just as well to a water storage tank or a dosing system: the risk isn't usually a lack of standards, it's a lack of consistent verification against them.
What good potable water assurance looks like in practice
OEUK's guidance points to a handful of practical measures that recur across most environmental health frameworks: correct sourcing and storage of water, disinfection and dosing at the right frequency, routine sampling and testing, and clear escalation when results fall outside acceptable ranges. On paper, this is a straightforward checklist. In practice, it depends on:
- Knowing which tasks are due, on which asset, and by when
- Recording who actually carried out each check, not just that it was scheduled
- Making test results visible to the people who need to act on them, quickly
- Keeping an auditable trail that shows the system was followed over time, not just on the day of an inspection
These are the same requirements that sit behind any operational assurance framework, whether the subject is water hygiene, electrical isolation, or scaffold integrity. Our post on what operational assurance means sets out why treating verification as a structured process, rather than a collection of individual tasks, is what actually closes the gap between having a good standard and demonstrating you have followed it.
Where this connects to control of work
Potable water tasks don't happen in isolation. Tank entries, dosing system maintenance, and pipework alterations typically need to be planned and permitted alongside other offshore work, which means they sit inside the same control of work environment as everything else on the installation. If that environment is fragmented, water hygiene tasks are easy to lose track of amid higher-profile permits. Guidance covered in our piece on what the OIM security guidelines mean for control of work offshore is relevant here too: strong oversight from the OIM depends on visibility across all planned work, not just the activities that carry the most obvious hazard.
Building assurance into everyday operations
The technical content of OEUK's potable water guidance is thorough and well established. The operational challenge for most duty holders is turning that guidance into a repeatable, verifiable routine across every installation they operate, without relying on manual tracking or after-the-fact paper trails.
That is the gap operational assurance software is built to close: turning scheduled checks, test results, and sign-offs into a single verifiable record, so that when a regulator, auditor, or your own management team asks whether the water system has been managed to standard, the answer is a matter of pulling up the record rather than chasing down the paperwork.
If your current approach to potable water management, or any other routine verification task offshore, still depends on spreadsheets and physical logs, it may be worth reviewing how that evidence is captured and where the gaps are likely to be. Getting ahead of that review is considerably easier than explaining a gap after an incident.
Source: Guidelines for Environmental Health for Offshore Installations: Potable Water Management