When the Answer Is No, Not Just Not Yet

Some doors are locked because the building behind them was never built. Other doors are locked because someone with a key decided not to open it today. Both can look identical from the outside. However, only one of them opens if you find the right person to ask again. I think a lot of data center diligence fails to tell these two kinds of "no" apart, and a case unfolding in California right now makes the difference impossible to miss.

What Is Actually Happening in Imperial Valley

Imperial Valley Computer Manufacturing is building what would be California's largest data center, a $10 billion, 330-megawatt facility. The project was originally designed around a specific promise: reclaimed wastewater from the cities of El Centro and Imperial, with an explicit commitment not to draw from the Colorado River at all.

Both cities ultimately declined to supply that wastewater. The developer then went to the Imperial Irrigation District, asking for roughly 287 million gallons of river water per year, about 880 acre-feet. This was a small fraction, just 0.03 percent, of the district's total annual entitlement. The district denied the request. The developer is now suing to reverse that denial, arguing there is no rational basis for allowing agricultural users to combine multiple water rights into one allocation while denying an industrial user the same mechanism.

That is not a closed case. It is an open, contested one, and the distinction matters enormously for how anyone should read it.

Two Different Kinds of No

Compare this to Virginia's groundwater report from a few weeks ago. That report ran the actual hydrology, tested nine hypothetical withdrawals, and found the water simply was not reliably there under current conditions anywhere in the Coastal Plain. No amount of legal argument fixes a groundwater table that does not have the capacity in the first place. That is a physical no, and it does not become a yes through better lawyering.

Imperial Valley is a different kind of no. The water technically exists, 880 acre-feet is a rounding error against a 3.1 million acre-foot entitlement. What is being contested is not physical scarcity but allocation policy, whether an industrial user gets access to a mechanism agricultural users already use routinely. That is a fight that can, in principle, be won, lost, negotiated, or settled, because the underlying resource constraint is not the actual barrier. The barrier is a decision, and decisions can be revisited in ways physics cannot.

Why VWPP Depends on Telling These Apart

I use VWPP to describe how thermal and water risk actually behaves, Visibility, Water narrative, Permitting friction, and Public reaction timing. A physical no and a policy no both show up, at first glance, as the same red flag under Permitting friction. Treating them identically is the mistake. A physical no tells you this specific site's water math will never work, regardless of how the project is redesigned or which lawyers get involved, and the right response is finding a different site. A policy no tells you the water math could work, if the allocation decision goes differently, and the right response might be litigation, negotiation, or finding an alternative source entirely, not abandoning the site.

Getting this distinction wrong in either direction is expensive. Treating a physical no as merely a policy fight wastes years and legal fees chasing something the hydrology already ruled out. Treating a policy no as a physical dead end means walking away from a site that might actually have been salvageable with the right approach.

What This Means for Anyone Underwriting Water Risk Right Now

Before treating any water denial as settled, or any water approval as safe, ask which kind of no or yes you are actually looking at. Is the constraint physical, tested against real hydrology the way Virginia's report tested it, or is it a policy and allocation decision that technically has room to move if the right case gets made. Imperial Valley's 0.03 percent number should make that question uncomfortable for anyone who assumed water denials are always about scarcity. Sometimes they are about precedent instead, and precedent is a fight, not a wall.

If you want a site's water math run against current standards early enough to know which of these two outcomes it's actually heading toward, physical scarcity or contestable policy, I would rather find that out with you now than after a permit application makes the distinction for you the hard way.

If that's where you are, whether you're walking through this yourself or bringing it to a board, grab 15 minutes on my calendar and let's set up time to go through it

PLUS:

Grab the guide. Before advancing a data center site, there are 12 questions I make sure I can answer. I wrote them up here: [The 12 Questions Every Real Estate Professional Should Ask Before Advancing a Data Center Site].