Sanitisation scheduling and compliance for water cooler operators

For a water cooler distributor, sanitisation is not a maintenance task — it is the contractual promise the customer bought. It is also the part of the operation most likely to fail quietly: a machine relocated between sites, a contract transferred, an engineer who left, and suddenly there is a gap in the record that only surfaces when a customer asks for their audit trail.

The fix is structural rather than administrative. Once the schedule belongs to the asset instead of the visit, the cycle survives everything that happens around it.

1. Attach the cycle to the asset, not the customer

Sanitisation intervals set at contract level break the moment a machine moves. Held against the asset record — serial number, install date, equipment type, site — the next due date travels with the machine through relocations, swaps and contract changes, and the history stays continuous.

This also gives you the per-asset view a customer audit actually asks for: every service and sanitisation on that machine, in date order, with who carried it out.

2. Set intervals by equipment type and site risk

A single blanket interval across a mixed fleet either overservices your bottled coolers or leaves your plumbed-in estate underserviced. Set a base interval per equipment type, then tighten it for higher-risk environments — healthcare, education, food handling and any site operating its own hygiene regime.

Bottled coolers get regular human contact through deliveries, so faults surface early. POU units may go unvisited between scheduled services, which makes the sanitisation visit the only inspection point in the year. Boilers add scale management, and descaling frequency should follow local water hardness rather than a national default.

3. Make due dates visible before they expire

A compliance breach is almost always a planning failure that happened weeks earlier. A rolling 30/60/90-day due list lets a coordinator fold upcoming sanitisation into routes that already pass the postcode, instead of dispatching a dedicated visit after the date has passed.

4. Combine schedules on the visit, not in the interval

Filter changes are usually throughput-driven and sanitisation is time-driven, so forcing them onto one interval distorts both. Model them as separate schedules against the same asset and let the planner merge them into a single visit when the dates converge. You get the visit efficiency without corrupting either cycle.

5. Capture the evidence at the point of work

A defensible sanitisation record names the asset, the date, the engineer, the method or kit used, and the next due date. Captured on a mobile form on site, it is complete before the engineer leaves; captured on paper, it is a backlog and eventually a gap.

6. Protect the visit with a pre-call

The most common reason a sanitisation visit does not happen is access — a locked plant room, an absent site contact, or a customer who was never told. A confirmation call or message the day before, logged against the job, converts most would-be abortive visits into completed ones at almost no cost.

7. Close the loop on collections

When a machine comes back, stop its schedule. Assets left live after collection clog the due list with work that cannot be done, and a due list nobody trusts is a due list nobody reads.