How to Review Water Risk for an AI Data Center
A site-diligence checklist for water sources, cooling design, permits, consumption, and operating limits.
Power risk is not one metric. It is a chain of dated obligations: the utility studies the request, parties fund required upgrades, equipment arrives, permits remain valid, and the site receives service under a defined tariff. A delay in any link can change the construction schedule and project cost.
A utility filing is a fact about the filing. It is not proof that the project will finish on the sponsor's stated date. Keep the three statement types visible:
| Question | Evidence | If unresolved |
|---|---|---|
| When can the utility deliver the required load? | Executed agreements, studies, and dated utility correspondence | Model a later service date |
| Who pays for upgrades and overruns? | Tariff, facilities agreement, construction contract, and guarantees | Keep the cost outside the base case |
| What happens during curtailment? | Service terms, operating limits, backup design, and tenant obligations | Test reduced availability and added operating cost |
| Can the project survive a schedule change? | Debt covenants, lease milestones, equipment orders, and delay remedies | Identify the party that must add capital |
Do not reduce the review to a regional power-price forecast. The investment depends on a specific site, utility, tariff, equipment plan, and delivery schedule. Keep each source date and unresolved condition next to the financial model.
For current source-backed AI infrastructure records, browse the greencio intelligence feed.
Disclaimer: This material is for research and discussion. It is not investment, legal, engineering, or tax advice.
A site-diligence checklist for water sources, cooling design, permits, consumption, and operating limits.
How specialist analysis, review records, approval authority, and external action stay separate.
A method for measuring tool-schema overhead and loading only the instructions a task needs.
What the public Tapestry and PJM record establishes, and what site power diligence still requires.
A review method for contract terms, liquidity, timestamps, resolution risk, and source reporting.
A correction on general-purpose model documentation, energy estimates, scope, and application dates.
How GreenCIO routes a question, records its sources, and leaves trade-offs with the human reviewer.
How LCOE normalizes project cost, which assumptions drive it, and which risks need separate review.
How to review movable workloads, grid data, deadlines, baselines, and reporting before claiming a saving.
The bounded extraction, scoring, validation, and storage path behind each submitted source URL.
Review the contracts, funding layers, and operating dependencies behind a hyperscale project.
A review checklist for workload energy, power sources, cooling, water, hardware use, and evidence.