Servers produce heat continuously. Cooling approaches can include air cooling, evaporative systems, chilled water, direct-to-chip liquid cooling, and closed loops. Each has different energy, water, and equipment implications.
Project documents should identify the chosen system, not just use broad language such as “efficient cooling.”
What to verify locally: Learn what the cooling choice can—and cannot—tell you.
Cooling-system comparison
Use original public records whenever possible. A developer statement can explain an intent; an approval, permit, or utility filing is where enforceable details are more likely to appear.
Questions for the project team
Record the date, document title, agency, page number, and project address. That turns a claim into something another reader can check.
Evidence standard: this guide avoids treating a proposal as a completed project, and avoids treating a missing record as proof that no impact exists.