March 8, 2026
|
September 14, 2026
By Jim David, Partner and Head of Washington
The next constraint on AI infrastructure may not be land or power, but stakeholder support. Developers should treat communications as critical infrastructure.
Major infrastructure follows a recognizable political cycle: it begins as an abstract public good – energy independence, connectivity, national security – and becomes controversial once its costs become tangible and local. Nuclear power plants, transmission lines, pipelines, highways and other large projects have all encountered versions of this dynamic. The political question shifts from “Do we need this infrastructure?” to “Why does it need to be here, what does it cost us and what do we get in return?”
For data centers, this has been an unusually swift and bruising transition. During the rise of cloud computing, data centers multiplied without significant public interest. The AI boom accelerated the development of larger, more resource-intensive facilities, while simultaneously bringing unprecedented national attention to the physical infrastructure underpinning AI. What began as scattered local zoning disputes has evolved into organized, multi-state opposition influencing policymakers at every level of government.
Communications planning can no longer begin when a project is ready to be announced – or when opposition emerges. It needs to be integrated upstream, beginning with site planning and real estate acquisition and continuing throughout development. Every new project must be ready to address three questions: 1) What resources does it use? 2) Who pays? and 3) Who benefits? Developing strategies for each will help developers anticipate risk, engage communities transparently and build the support necessary to move projects forward.
What Resources Does It Use?
The scale of today’s data center development has made resource consumption a key concern. Power is at the center of the debate, but depending on the market, water, land use, transmission infrastructure and other resource requirements can all attract scrutiny. These are no longer solely technical questions for engineers, utilities and sustainability teams. They are local community and national political issues.
The technical complexity involved can create fertile ground for misinformation. Claims about water consumption, emissions or grid impacts spread quickly when project-specific information is incomplete or difficult to find. And addressing one concern rarely ends the debate. As developers explain closed-loop cooling systems, for example, scrutiny is expanding to indirect water use associated with power generation. The conversation can quickly move beyond the boundaries of the site itself.
That puts a premium on anticipating issues rather than simply responding to them. Developers need to understand which resource issues matter locally, anticipate how they could be mischaracterized and ensure credible, accessible facts are in place before a narrative takes hold.
Who Pays?
Resource consumption becomes even more politically potent when it connects – fairly or not – to what people pay for electricity every month.
As utilities invest in generation, transmission and other infrastructure to accommodate large-scale demand, the question has become: Who should pay for it? For residents already concerned about affordability, the idea that households could bear some of the cost is anathema.
Ratepayer protection is a bipartisan issue with populist appeal. Increasingly, it is also becoming a baseline political and regulatory expectation: data center developers should pay their own way rather than shift the costs of their growth to existing ratepayers. The White House Ratepayer Protection Pledge, which 23 governors have joined, reflects how quickly that principle is becoming table stakes for the industry. Elected officials across the political spectrum have an incentive to demonstrate that households and existing businesses will not subsidize the growth of some of the world’s largest companies. Particularly with affordability on the ballot, policymakers are looking for ways to ensure high-demand customers bear the costs associated with serving them.
While companies continue to communicate their commitment to paying their own way on energy, critics now point to the voluntary nature of such pledges. There is also no common reporting framework for companies to demonstrate publicly how they are covering the incremental system costs associated with their projects.
Developers need to understand these dynamics before a project encounters opposition. The landscape will differ by state, utility territory and community. Answers to “Who pays?” must be both technically accurate and broadly credible.
Who Benefits?
To secure a social license to operate, developers are being asked to demonstrate not simply that a project is economically beneficial, but that the host community derives tangible value from it.
Capital investment and job creation remain important, but for projects consuming significant resources and occupying substantial physical footprints, those headline numbers may not be sufficient on their own. Developers need a broader, locally relevant value proposition. In many cases, that will include long-term tax revenue, infrastructure investment, local hiring and procurement, workforce development, educational partnerships and community investment. The strongest community benefit package will rarely be identical from one community to another.
Early stakeholder engagement can help developers understand what a community actually values before commitments are made. Communities are becoming more sophisticated in evaluating data center proposals, so the answer to the question “Who benefits?” needs to be specific, measurable and accountable – not simply a generic promise of economic development. A community that feels a vested interest in a project’s success provides a much stronger foundation for long-term support.
Communications as Critical Infrastructure
The ability to answer these questions is not simply a messaging exercise. The hard work involved in developing locally resonant answers can reveal vulnerabilities, identify emerging political and community risks and influence development strategy itself.
That means public affairs and communications teams need a seat at the table before a site is announced – not simply to prepare talking points, but to identify vulnerabilities, understand the opposition landscape, test the project’s value proposition, monitor emerging narratives and help development teams make decisions with stakeholder risk in mind.
The developers best positioned for the next phase of growth will treat communications and stakeholder intelligence not as a response to development risk, but as critical infrastructure for the project itself.
If you’re interested in learning more about Prosek’s data center capabilities, email us at pro-publicaffairs@prosek.com.
September 30, 2026
September 28, 2026
September 18, 2026