Properly label and prevent cross-contamination between potable and non-potable water hauling operations
domain: tceq.texas.gov · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Dedicate separate tanks, hoses, and fittings for potable vs. non-potable water if a fleet handles both — state hauler rules (e.g., Texas 30 TAC 290.44(i)(2)(A)) require potable tanks to be used only for drinking water and labeled accordingly
Never convert a tank previously used for non-potable liquids (dust control, irrigation, oilfield, chemicals) into potable service — this conversion is explicitly disallowed under state drinking-water hauler rules
Label non-potable tanks clearly as 'Non-Potable Water — Not for Drinking' to prevent field confusion, mirroring the same labeling discipline required on the potable side
Keep filling connections, caps, and keeper chains dedicated per tank/hose so a non-potable fitting never gets attached to potable equipment even temporarily
Where a hydrant or bulk-fill station is used for non-potable loads, maintain the same backflow-prevention discipline (RPZ) as a potable fill, since the risk to the public water system is the same regardless of the water's intended end use
Known gotchas
Regulators focus enforcement on the potable side (tank/hose labeling, source restrictions), but the underlying cross-contamination risk runs both ways — a hose swapped between an oilfield job and a drinking-water job is the classic failure mode
Labeling requirements are typically written into the potable-water hauler rule (e.g., Texas's 30 TAC 290.44), not a standalone 'non-potable labeling' regulation — so the non-potable side is often governed by general best practice and liability concerns rather than a specific labeling statute
Backflow prevention rules at the fill source (hydrant or bulk station) apply regardless of what the water will be used for downstream — utilities protect their system the same way for a dust-control fill as for a drinking-water fill
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?