Cooling-water circulation and water consumption are different quantities. Circulation describes fluid moving through a system. Consumption concerns water that is not returned to the relevant source or boundary, while withdrawals and discharges describe other parts of the water balance. Clear definitions are essential when discussing a data center.

Begin by drawing the cooling loops and identifying where water enters, leaves, or remains within the system. Ask the mechanical team to distinguish internal circulating flow from makeup demand and other site uses. A high circulation rate should not be reported as if all that water were newly consumed.

The reverse mistake also matters. A closed internal loop does not automatically establish that the entire cooling plant or site uses no water. The heat-rejection arrangement and supporting services need their own review. DOE’s cooling-water guidance addresses these broader system considerations.

For planning, request estimates tied to load, weather, operating mode, and phase. Explain whether a figure represents a peak condition, an annual forecast, or a measured period. Different quantities can all be valid while answering different questions.

Use the same definitions in utility discussions, design documents, and community communication. If the cooling strategy changes, revisit the water assumptions rather than carrying forward an earlier estimate.

A useful water statement names the boundary, quantity, time period, and evidence. That discipline helps owners compare alternatives honestly and prevents misunderstandings caused by using the word water for several very different aspects of a cooling system.