For much of the recent discussion about artificial intelligence and electricity, the central question has been how much new power the country can produce.
That question is essential. Data centers, manufacturing, transportation, and other forms of electrification are adding pressure to the power system. More generation can help meet that demand.
But generation is only one part of the system. Electricity must also move from where it is produced to where it is needed, at the time it is needed, within the limits of the network.
That brings a second question into focus:
How efficiently can the existing grid move electricity to the places where demand is growing?
Capacity is not the same as deliverability
A grid can have electricity available somewhere in the system and still face difficulty delivering it to a particular location. Transmission congestion, constraints on individual lines, and limited transfer capability can affect how much power can move between regions.
In practical terms, this means that the amount of electricity a system can generate does not, by itself, tell us how much electricity a particular customer or facility can reliably receive. Location and delivery capability matter too.
This distinction is especially relevant to AI infrastructure. Data centers need large amounts of electricity at specific sites, often on demanding timelines. A national supply figure alone cannot tell a project developer whether power can reach a particular location, or when the necessary network upgrades will be complete.
DOE’s investments highlight the delivery side
The U.S. Department of Energy recently announced investments across 26 states. DOE says project recipients are expected to reconductor or rebuild more than 1,500 miles of transmission lines and deploy grid-enhancing technologies across nearly 21,000 miles. Together, the projects are expected to make more than 23 GW of additional electricity capacity available.
These figures describe a mix of transmission upgrades and technologies intended to improve use of the existing grid. They do not mean that all grid constraints are solved, or that new generation and new transmission will no longer be needed. They do show that improving the performance of existing infrastructure is part of the response to rising demand.
Some grid-enhancing technologies help operators understand or control the network more precisely. Dynamic line ratings, for example, use current conditions to estimate how much electricity a line can safely carry. Power-flow control devices can help redirect electricity toward lines with available capacity.
These measures can help unlock capacity in existing corridors. Their usefulness depends on the specific line, operating conditions, system needs, and the ability of grid operators to deploy and manage the technology.
The value of throughput
It may help to think of the grid as a network with both supply and movement constraints. Adding electricity is one way to increase what the system can serve. Improving the movement of electricity is another.
For executives and infrastructure planners, that suggests a more complete set of questions:
Is generation available?
Can the grid transfer it to the relevant region?
Can it be delivered to the specific site?
Will it be available at the times the load needs it?
What upgrades are needed to make that delivery reliable?
These questions are connected, but they are not interchangeable. A project may have access to a potential energy supply while still depending on transmission work, interconnection steps, or local network upgrades before that power is deliverable.
For large electricity users, this has implications for site selection, project schedules, utility coordination, and the cost of bringing infrastructure online. The grid’s ability to move power can influence whether a location is practical, how quickly a project can be served, and what additional investment may be required.
A broader view of the AI power question
The discussion should not become a contest between building new infrastructure and improving existing infrastructure. Growing demand may call for more generation, new transmission, upgrades to existing lines, and better tools for operating the system.
The strategic point is that grid size and grid performance are different parts of the same challenge.
As AI infrastructure expands, the value of the grid may increasingly be measured not only by how much electricity it can produce or connect, but by how effectively it can move that electricity to the right place at the right time.
The supply question remains important. The delivery question is becoming just as important.
AI infrastructure risk is moving from the grid connection into the contract
A data center can be announced. It can attract financing, begin construction and have a major customer waiting for capacity. Yet those facts do not, by themselves, establish that the facility will have the power it needs when it is supposed to become operational.
A recent report about Oracle’s Project Jupiter in New Mexico puts that gap into contractual terms.
Reuters reported on September 24 that Oracle issued a force-majeure notice to a Blue Owl unit connected to the project, citing potential delays in securing power. Reuters also reported that securing power for the site is Oracle’s responsibility under the contract. Oracle said the project remained on its planned schedule, and Blue Owl said the notice did not change its financial commitments. (reuters.com)
That combination deserves a measured reading. The notice does not prove that the project has failed, that power is unavailable, or that the 2028 target will be missed. It does show that uncertainty around power timing has reached the parties’ contractual relationship.
That is the larger signal.
Planned capacity and operational readiness are different claims
Infrastructure announcements often combine several stages into one story: investment committed, land secured, construction underway, customer demand identified, power planned.
Those are meaningful milestones. But they do not all answer the same question.
“Planned” capacity is not necessarily capacity that has been secured. A power arrangement is not necessarily proof that electricity will be available at the required scale and date. And a building nearing completion does not automatically mean the facility is ready to deliver computing capacity.
Each step needs its own evidence.
For an AI data center, the sequence may involve site development, permits, fuel or grid supply, generation or transmission infrastructure, electrical equipment, commissioning, and the final handoff into operations. A delay in one part can affect the schedule for the whole project.
When power timing reaches the contract
Electricity is often discussed as an operating cost: a major expense that grows as computing demand increases. But power availability can matter before a facility begins operating.
If the power timeline affects a project’s ability to meet an operational milestone, the consequences may include delayed revenue, changed payment timing, pressure on financing assumptions, or disputes about which party carries the cost of the delay.
In the Project Jupiter case, Reuters reported that Oracle’s notice could allow it to delay payments if the data center were derailed and did not come online as planned. The report also said the notice did not amount to Oracle exiting as the main tenant. Blue Owl said its financial commitments were unchanged. (reuters.com)
The precise effect depends on the contract and how the parties resolve the notice. The broader point does not: power risk can become delivery risk, and delivery risk can become contractual and financial risk.
The readiness questions executives should ask
The lesson is not that every data-center project is in trouble. It is that a headline capacity figure is only one piece of the readiness picture.
Executives, investors and customers should ask:
What does “power secured” mean in this project? Is there an executed supply agreement, a completed interconnection, fuel availability, installed generation, or some combination?
Who is responsible for each power milestone? The answer may differ across utility service, transmission upgrades, fuel supply, on-site generation, permits and equipment.
What evidence supports the schedule? A target date is a plan. Milestone records, approvals, construction status and commissioning evidence help show whether the plan is progressing.
What happens if a milestone slips? Review who carries the cost, which payments may change, how notice requirements work, and whether customer commitments depend on the same schedule.
What is the fallback plan? A backup source or phased energization may reduce exposure, but only if it is technically feasible, contractually available and supported by evidence.
The declared-versus-observed distinction applies to infrastructure
This is the same discipline that applies to other forms of risk: separate what has been stated from what has been demonstrated.
A project may declare a capacity target. Operational readiness asks whether the required power is available, tested and usable on the relevant timeline.
That distinction is especially important in AI infrastructure because the project’s value depends on more than a completed building. Compute capacity must be delivered in a form customers can use, when contracts say it will be available.
The force-majeure notice around Project Jupiter is not a final verdict on the project. It is a visible sign that the power timeline has become material enough to enter the contractual conversation.
The next phase of AI infrastructure will be judged not only by what gets announced or financed, but by what can be energized, delivered and supported by evidence.
“AI needs more power” is true as far as it goes. It is also too broad to tell an executive what to build, fund or approve.
A growing data center needs electricity at a specific site, at a specific time, with the reliability its operations require. Several different constraints can stand between that need and an energized facility. There may be too little generation available at the required hours. An existing transmission corridor may be congested. A local substation may need upgrades. An interconnection may still be years from completion.
Those are different problems. They do not all have the same solution.
The Department of Energy’s September 24 announcement offers a useful example. DOE said it intends to help fund 31 grid improvement projects across 26 states through its SPARK initiative. The selected projects are expected to reconductor or rebuild more than 1,500 miles of transmission lines and deploy grid enhancing technologies across nearly 21,000 miles. Together, DOE expects those efforts to make more than 23 GW of additional electricity capacity available.
That 23 GW is not a proposal for 23 GW of new generation. It is an expected increase in what the grid can carry and make available through transmission upgrades. The projects have been selected; the capacity gain still has to be delivered and measured.
The constraint may be the route
Think of generation as the source of electricity and transmission as part of the route it takes to customers. Adding supply at one end does little for a particular site if the route between them is constrained.
Reconductoring replaces the wire on an existing transmission line with a conductor that can carry more power. Other grid enhancing technologies help operators understand or improve how existing lines are used. Dynamic line ratings, for example, use current conditions to assess a line’s safe carrying capability. Power flow controls can help direct electricity across available paths.
These approaches are attractive because they can draw more value from infrastructure and rights of way that already exist. They may be especially useful where obtaining a new corridor would take much longer.
That does not make every existing line an easy upgrade. A project still has to satisfy engineering, reliability and operational requirements. Nor does an increase in transmission capability guarantee that electricity will be available during every hour a customer needs it.
What the announcement changes
The opportunity is wider than the familiar discussion about building new generation.
Advanced conductors, line monitoring, sensors, power flow controls and grid software all become more consequential when transfer capability is the binding constraint. So do the less visible tasks: studying where an upgrade will help, coordinating the work and proving that the promised capacity is available in operation.
For an AI infrastructure developer, the practical question is not simply, “How many megawatts are planned in this region?” It is:
How much power can reach this site, under the required conditions, by the date we need it?
For utilities and policymakers, the question is where targeted upgrades can relieve real congestion—and where new generation, substations or transmission corridors are still necessary.
From announced capacity to delivered power
DOE’s projected 23 GW is a meaningful signal about where grid investment is headed. It is not yet 23 GW of observed, site ready power.
The evidence will come as projects are completed and operators measure the resulting transfer capability, reliability and service to customers. That is where the declared figure becomes an operational result.
AI’s electricity challenge is often framed as a race to produce more power. In some places it will be. In others, a faster opportunity may be to move available electricity more effectively through the grid we already have.
The cheapest megawatt may already exist. The work is proving that it can reach the right place when it counts.
The rapid expansion of artificial intelligence is often discussed as a technical race.
Who has the most advanced chips? Who can build the largest models? Who can secure enough electricity? Who can bring new computing capacity online fastest?
But another constraint is emerging—one that cannot be solved by ordering more GPUs or signing another power-purchase agreement.
AI infrastructure is confronting the question of public legitimacy.
Across the United States, communities, regulators, utilities, and lawmakers are renegotiating the conditions under which large data centers will be permitted to consume local resources and reshape regional infrastructure.
The emerging message is not simply, “Do not build.”
It is closer to this:
You can build enormous AI infrastructure—but the right to build at that scale may increasingly come with obligations to pay attributable costs, disclose resource requirements, respond flexibly during grid stress, and prove that promised behavior occurred.
That begins to resemble a social contract.
The Debate Has Reached Spartanburg
The issue is no longer theoretical in Spartanburg County, South Carolina.
County officials approved a one-year moratorium affecting data-center applications that had not been finalized while the county evaluates appropriate locations and future development standards.
At the same time, residents and environmental groups have challenged aspects of a separate computing-center project already being developed at the former Kohler manufacturing site. The concerns surrounding that project include its proposed expansion, onsite generation, air emissions, noise, and the transparency of the approval process.
These are technically separate matters, but together they illustrate the same governance gap.
Communities are being asked to make long-term infrastructure decisions while basic questions may still be contested:
Who owns the project?
How much electricity will it ultimately require?
Will the power come from the public grid or onsite generation?
How much water will be consumed?
What emissions, noise, or land-use effects will accompany it?
Which infrastructure costs will be paid by the developer, and which could eventually reach existing customers?
What benefits will remain in the community after construction is complete?
When those answers arrive late, change during development, or remain buried inside fragmented proceedings, distrust should not be surprising.
The problem is not merely a communications failure. It is an evidence failure.
From Economic Development to Cost Attribution
For years, data centers were commonly presented through the language of investment, construction activity, tax revenue, and technological competitiveness.
Those benefits still matter.
But officials are now asking a second set of questions: What costs are being created, and who will pay them?
In September 2026, the U.S. House passed the Ratepayer Protection Act with overwhelming bipartisan support. The legislation would require state utility regulators to consider whether large electricity users, including data centers, should bear the incremental infrastructure costs required to serve them.
The measure may not settle the issue by itself, but its political significance is difficult to miss.
The national conversation is moving from whether AI infrastructure is economically valuable to whether its costs are being allocated fairly.
That is an important shift.
If a private facility requires new substations, transmission capacity, generation resources, water-system upgrades, or other dedicated infrastructure, existing residents and small businesses will increasingly question why those costs should be socialized while the project’s financial returns remain private.
“Who benefits?” is being joined by “Who pays?”
Transparency Is Becoming a Condition of Operation
Resource disclosure is also moving closer to the center of the regulatory bargain.
California recently enacted a package of laws requiring greater reporting around data-center electricity and water use, while strengthening protections intended to prevent infrastructure costs from being shifted onto ordinary ratepayers.
Virginia has proposed an accountability framework addressing project secrecy, environmental effects, and electricity costs, including restrictions on certain nondisclosure agreements.
Different states will take different approaches, but the direction is becoming visible.
Communities are losing patience with being asked to approve projects based primarily on economic projections while detailed resource requirements remain confidential, incomplete, or subject to later expansion.
For major AI infrastructure, transparency can no longer be treated as a public-relations accessory.
It is becoming part of the operating model.
Flexibility Could Change the Bargain
The industry is also developing a possible response to grid concerns: treating data centers as flexible loads rather than permanent, inflexible demand.
A flexible data center could reduce its draw from the grid during constrained periods by shifting computing workloads, using batteries, drawing from approved onsite generation, or temporarily curtailing noncritical activity.
That could make a facility more valuable to the grid and potentially reduce the need for some infrastructure expansion.
The idea has enough momentum that Google, Nvidia, Emerald AI, utilities, power producers, and other organizations have formed the AI Energy Management Alliance to advocate for grid-enhancing data centers.
But there is a major difference between claiming flexibility and delivering it.
If a data center receives faster interconnection, preferential pricing, tax incentives, or regulatory accommodation because it promises to reduce demand during grid emergencies, that commitment cannot remain a sentence in an application.
It must become an auditable operational obligation.
A credible framework would need to record:
• The grid condition or authorized curtailment event.
• The time the response was requested.
• The facility’s baseline demand.
• The amount of load reduction promised.
• The reduction actually delivered.
• The duration of the response.
• Any exception or failure to perform.
• The process used to verify and report the result.
This is the same distinction that appears throughout governance:
Declared flexibility describes what the operator says the facility can do.
Observed flexibility records what the facility actually did when the system was under stress.
Only the second one can support a defensible decision.
A Permit Is Not the Same as Legitimacy
Companies sometimes treat permitting as the final boundary: if the project meets the formal requirements and receives approval, construction should proceed.
Legally, that may be sufficient.
Operationally and politically, it may not be.
A permit provides legal authorization. A social license reflects continuing public acceptance of the conditions under which the facility operates.
That acceptance can weaken when project ownership is unclear, resource requirements expand, promised benefits fail to materialize, or community costs appear only after approval.
The result is not limited to protests.
It can produce moratoriums, litigation, delayed permits, stricter tariffs, lost incentives, and political pressure for broader regulation.
For developers, transparency and verifiable performance are therefore not simply compliance expenses. They are forms of project-risk management.
The Emerging Social Contract
The developing bargain for AI infrastructure appears to contain four core obligations.
1. Pay attributable costs
The costs created specifically to connect and serve a major facility should be identified rather than quietly distributed across existing customers.
2. Disclose resource requirements
Communities need credible information about electricity, water, land, emissions, noise, ownership, incentives, and expected local benefits before—not after—the central decisions are made.
3. Operate as a responsible grid participant
Where technically possible, large facilities should be capable of shifting or reducing demand during constrained conditions instead of treating the grid as an unlimited resource.
4. Prove performance
Flexibility, efficiency, and community-benefit commitments should produce evidence that regulators, utilities, and the public can independently review.
These expectations will not look identical in every jurisdiction. A facility in South Carolina will face different resources, grid conditions, and community priorities than one in California, Texas, or Virginia.
But the governing principle is likely to remain consistent:
The greater the infrastructure footprint, the greater the obligation to make its costs, behavior, and benefits visible.
Infrastructure Governance Is Catching Up
AI companies are not wrong to argue that data centers are strategically important. Compute capacity will influence economic competitiveness, scientific research, national security, and the development of new industries.
Communities are also not wrong to ask what they are being required to contribute—and what safeguards accompany that contribution.
Those positions do not have to be mutually exclusive.
The mature path is neither unrestricted development nor reflexive prohibition.
It is governed development: clear conditions, attributable costs, transparent resource claims, measurable operating commitments, and evidence that those commitments were fulfilled.
The next generation of AI infrastructure will not be judged only by how much computing power it produces.
It will be judged by whether it behaves like infrastructure worthy of public trust.
That is the quiet thesis underneath the current disputes:
AI infrastructure is developing its own social contract.
And the companies that understand that early may find it much easier to earn both a grid connection and a durable place in the communities expected to host them.
The AI infrastructure conversation is beginning to mature.
For much of the current buildout, attention has centered on announced investments, proposed data-center capacity, land acquisitions, power agreements, and projected electricity demand. But as projects move closer to construction and operation, the market is learning to distinguish what has been declared from what is actually available.
Announced capacity is not the same as energized capacity.
A similar distinction is now emerging around power flexibility.
Data-center developers increasingly describe their facilities as flexible loads capable of shifting computing workloads, discharging batteries, using on-site generation, or reducing electricity consumption when the grid becomes constrained.
Those capabilities could create significant value. They may allow utilities to connect large facilities faster, use existing grid infrastructure more efficiently, protect reliability during periods of stress, and defer some expensive system upgrades.
But a stated ability to curtail power is still only a claim.
The more important question is whether that flexibility can be observed, measured, and repeated during actual grid events.
From Flexible Design to Verified Performance
The AI Energy Management Alliance, launched by Emerald AI, Google, and NVIDIA, is advancing data centers that can dynamically manage their electricity use in response to grid conditions.
Its approach is notable because it is described as technology-neutral and performance-based. The focus is not limited to which batteries, generators, workload-management platforms, or cooling systems a facility installs. The focus is on the measurable service the facility can deliver.
That includes response speed, duration, predictability, and behavior during emergencies.
This is an important shift.
A data center may be technically capable of reducing its electricity demand under controlled conditions. That does not automatically prove it will deliver the promised reduction when the regional grid is under stress, temperatures are extreme, equipment availability has changed, and computing demand is high.
Technical capability must eventually become operational evidence.
What Observed Flexibility Should Show
If a facility commits to curtailing 100 megawatts during a grid emergency, verification should extend beyond confirming that a control system received the request.
Operators and regulators may need evidence showing:
The facility’s electricity demand before the event
The amount of load actually reduced
The time between the grid signal and the response
How long the reduction was maintained
Which energy resources or workloads produced the reduction
Whether essential computing services remained within agreed performance limits
Whether electricity demand rebounded sharply after the event
Whether the facility can reproduce the result across multiple events
Which exceptions, failures, or overrides occurred
Whether the supporting telemetry and records are complete and auditable
The baseline also matters.
A facility should not receive full credit for a reduction that would have occurred anyway because workloads had already declined. Without a credible baseline, flexibility measurements could become another version of inflated announced capacity: technically documented but operationally misleading.
Benefits Should Follow Evidence
The alliance argues that credible and verifiable flexibility commitments could support faster, risk-adjusted interconnection pathways.
That proposition makes sense. A data center that can reliably reduce its load during a limited number of critical hours may impose a different risk on the power system than a facility requiring maximum electricity delivery around the clock.
However, any preferential treatment should be connected to continuing performance.
Faster interconnection should not be granted solely because a developer includes flexible-load language in an application. The commitment should be defined before connection, monitored during operation, and reassessed as equipment, workloads, software, ownership, and grid conditions change.
Otherwise, flexibility becomes a one-time qualification rather than an ongoing operating obligation.
A defensible model would connect the lifecycle:
Declared capability → tested capability → observed grid-event performance → verified record → continued authorization
If performance falls outside the agreed limits, the system should identify the variance and determine whether operating conditions, interconnection terms, or incentives need to change.
Flexibility Is Becoming a Governance Question
This issue extends beyond electrical engineering.
Once data-center flexibility influences interconnection priority, infrastructure spending, electricity rates, or reliability planning, the underlying evidence becomes a governance concern.
Someone must establish:
What was promised
How performance is measured
Who can verify the result
What exceptions are permitted
How failures are recorded
When a commitment must be retested
What happens when observed performance no longer matches the declaration
That is the same pattern appearing across AI governance more broadly.
A policy is not proof of enforcement.
A control is not proof of execution.
A resolved incident is not proof of correction.
And a declared flexible load is not proof of grid-responsive performance.
The Next Infrastructure Advantage
Flexible AI data centers could become valuable grid participants rather than passive sources of rapidly growing demand. The technical potential is increasingly credible: research and demonstrations have shown that AI workloads can be shifted or curtailed while protecting priority services. (arxiv.org)
But the long-term value will depend on whether flexibility survives contact with real operating conditions.
The data centers that gain an advantage may not be those making the largest flexibility promises. They may be those capable of producing a consistent, independently reviewable record showing what happened when the grid actually needed them.
The market is moving from declarations toward evidence.
Announced capacity must become energized capacity.
Flexible design must become verified response.
And declared flexibility must become observed flexibility.
The AI infrastructure race has largely been communicated through declarations of scale.
Gigawatts of proposed data-center capacity. Billions of dollars in projected investment. Enormous forecasts for electricity demand. New campuses capable of housing hundreds of thousands of advanced processors.
These numbers reveal the direction of travel—but they do not always reveal which projects can actually arrive.
That distinction is becoming increasingly important.
Microsoft reportedly has an internal target to expand its global data-center capacity from approximately 12 gigawatts today to more than 38 gigawatts by 2032. Meanwhile, electricity requests from large power users across portions of the United States have climbed above 700 gigawatts. Reuters
The scale is extraordinary.
So is the uncertainty.
The next phase of AI infrastructure may therefore be defined less by declared capacity and more by observed readiness: verifiable evidence that a proposed project possesses the physical, financial and institutional conditions necessary to become operational.
Declared capacity is not delivered capacity
Declared capacity describes intention.
It may appear in a corporate target, utility interconnection request, investor presentation, electricity forecast or economic-development announcement.
But a proposed gigawatt can exist on paper long before the organization has secured:
Land
Permits
Financing
Customers
Electricity
Grid interconnection
Transformers and turbines
Cooling infrastructure
Construction labor
Community acceptance
Until those dependencies are resolved, the declared capacity remains conditional.
This does not make the projection fraudulent or meaningless. Infrastructure planning requires forecasts. Organizations must reserve land, capital and power years before facilities become operational.
The problem begins when every declaration is treated as equally probable.
A project with a press release and an interconnection request should not carry the same planning weight as one with site control, permits, committed financing, signed tenants, equipment reservations and a defined energization date.
Both may claim the same number of megawatts.
They do not represent the same level of readiness.
The market is beginning to demand proof
Evidence of this transition is already appearing across the infrastructure stack.
Utilities are introducing financial commitments and additional screening to separate credible large-load customers from speculative or duplicated applications. In Pennsylvania, Reuters found that only 20 of more than 100 proposed data centers had sought permits.
Lenders are also becoming more selective. Investors are charging more for risk and demanding stronger protections against permitting delays, electricity queues and supply-chain bottlenecks. In one case, construction financing could not be accessed until permits were secured and leases signed.
These are not merely administrative obstacles.
They are attempts to convert projections into evidence.
A permit demonstrates that a project has moved beyond general intention.
A signed lease establishes customer commitment.
An upfront payment gives the applicant something meaningful to lose.
A power agreement identifies a plausible energy source.
An equipment order connects the projected completion date to the physical supply chain.
Each one increases confidence that the proposed capacity can actually materialize.
Observed readiness is a chain, not a single document
No single artifact proves that an AI infrastructure project will succeed.
A signed lease is not useful if electricity cannot be delivered. A grid connection is insufficient if financing collapses. Available land does not create an operating data center without equipment, cooling, construction and customers.
Observed readiness must therefore be evaluated as a connected chain of evidence:
Commercial readiness: Are credible customers contractually committed?
Financial readiness: Is capital available under conditions the project can satisfy?
Regulatory readiness: Are permits, environmental requirements and local approvals progressing?
Energy readiness: Is generation available, and can the electricity physically reach the site?
Supply-chain readiness: Have critical transformers, turbines, switchgear, cooling equipment and chips been secured?
Operational readiness: Can the facility withstand equipment failures, grid interruptions, cyber incidents and other disruptions?
A weakness in any one of these areas can strand the rest.
A warehouse full of GPUs without dependable electricity is stranded compute. A power reservation without financing may become ghost demand. A fully financed project without permits can remain trapped in development.
Scale depends on the entire chain surviving.
Readiness may become a competitive asset
During the first phase of the AI infrastructure boom, scarcity made almost any plausible capacity valuable.
The next phase will likely be more discriminating.
Utilities cannot build generation and transmission around every speculative request. Lenders cannot treat every projected campus as equally financeable. Equipment manufacturers cannot reserve scarce production capacity indefinitely. Communities will increasingly question projects that consume land, water or grid capacity without producing credible benefits.
As that scrutiny increases, organizations capable of producing verifiable readiness evidence may receive:
Better access to financing
Greater credibility with utilities
Stronger negotiating positions for equipment
Faster regulatory decisions
Higher confidence from customers
More defensible project valuations
The advantage will not come from possessing the boldest forecast.
It will come from reducing uncertainty for everyone whose resources are needed to make the forecast real.
From projection to proof
The AI infrastructure buildout is not slowing into irrelevance. It is moving into a more demanding stage.
Announcements still matter. Forecasts still matter. Ambitious capacity targets still matter.
But the gap between a declared gigawatt and an energized gigawatt is becoming impossible to ignore.
The organizations that succeed may be those that can establish a traceable line from projected demand to committed capital, approved sites, contracted equipment, available generation and operational delivery.
That is the transition from declared capacity to observed readiness.
Gigawatts will remain the headline.
Evidence will increasingly determine which ones get built.
The power supply is becoming part of the data center.
The artificial-intelligence infrastructure race is producing an important shift in how data centers are designed.
For years, developers could treat electricity largely as an external utility service. They selected a location, applied for a grid connection and built the facility around the expectation that sufficient power would eventually arrive.
That model is becoming less dependable.
AI data centers require enormous amounts of electricity, often concentrated within a relatively small geographic area. At the same time, utilities must contend with transmission constraints, transformer shortages, lengthy interconnection studies and project requests that may be speculative or duplicated.
The result is a widening gap between having plans for a data center and having the power required to operate one.
A $2.6 Billion Signal
Vertiv has agreed to acquire UtilityInnovation Group, a company specializing in microgrids, advanced power controls and behind-the-meter power architecture for data centers.
The agreement calls for approximately $1.45 billion in cash at closing, with as much as $1.15 billion in additional payments tied to future earnings targets. That places the potential transaction value at approximately $2.6 billion.
The acquisition is expected to add microgrid controls, onsite-generation orchestration, specialized switchgear and energy-storage integration to Vertiv’s existing power and cooling portfolio.
That is more than a routine expansion of product offerings.
It is evidence that power availability is moving upstream into the earliest stages of data-center planning.
Vertiv describes the expanded architecture as extending from the utility interconnection to the chip. Its stated objective is to support grid-connected facilities, bridge-to-grid projects and sites capable of operating independently through onsite generation.
In other words, the power supply is becoming part of the data center itself.
Why Waiting for the Grid Is Becoming a Competitive Risk
A developer may control the land, secure financing and purchase computing equipment, yet remain unable to bring the facility online because the local grid cannot supply the requested load.
That delay carries serious consequences.
Equipment can sit idle. Construction schedules can slip. Customer commitments can be missed. Capital remains tied up in infrastructure that is not producing usable computing capacity.
For AI companies, this creates a direct connection between energy availability and speed to market.
The competitive metric is no longer merely how many GPUs a company owns. It is how quickly those GPUs can be converted into operational compute.
The industry increasingly describes this as “time to power” or “time to first token.”
Both phrases point to the same underlying reality: compute capacity does not exist in a commercially meaningful sense until it can be energized.
What a Microgrid Changes
A microgrid can coordinate multiple sources of electricity within a defined site or operating area. Depending on its design, it may combine utility service with onsite generation, battery storage and advanced control systems.
This creates several possible operating models.
A grid-connected data center can use onsite resources to strengthen reliability or manage peak loads.
A bridge-to-grid facility can begin operating with onsite generation while waiting for a larger utility connection.
An islanded facility can operate independently when utility power is unavailable or insufficient.
These options do not make the traditional grid irrelevant. Large data centers may still require substantial utility service over the long term.
What changes is the developer’s dependence on a single delivery timeline.
Instead of waiting passively for the grid to expand, the project can be designed around a coordinated portfolio of energy sources.
Power Architecture Is Now Data-Center Architecture
This shift has consequences beyond electrical engineering.
Site selection must account for access to natural gas, renewable resources, storage capability and future utility interconnection—not merely available land.
Financing must cover generation and energy infrastructure as well as buildings, cooling and computing hardware.
Operating plans must address fuel availability, emissions, maintenance, cybersecurity and the interaction between onsite systems and the surrounding grid.
Regulators and communities will also have questions about who absorbs the cost, risk and environmental impact of these facilities.
Bringing your own power does not eliminate infrastructure constraints. It relocates and redistributes them.
A microgrid can reduce dependence on the utility queue, but the project still needs credible equipment, fuel, permits, controls and operating capability. The bottleneck may move from grid interconnection to turbine availability, gas supply, emissions approval or energy-storage procurement.
There is no magic extension cord hiding behind the data center.
A New Test of Project Readiness
The move toward onsite power could also make the distinction between declared demand and observed readiness more visible.
A speculative developer may submit a large electricity request to preserve a position in the grid queue.
An execution-ready developer can demonstrate site control, financing, equipment commitments, a credible load schedule and an integrated power plan.
One has declared demand.
The other has evidence of deployment readiness.
That distinction will matter as utilities, investors and regulators decide which projects deserve scarce infrastructure capacity.
The Larger Signal
Vertiv’s proposed acquisition suggests that energy infrastructure is no longer an adjacent concern for the data-center industry. It is becoming part of the core technology stack.
That creates opportunities for microgrid developers, equipment manufacturers, energy-management platforms, project financiers and specialists capable of coordinating infrastructure across traditional industry boundaries.
It also changes the competitive landscape.
The next generation of AI infrastructure leaders may not be the companies that merely reserve the largest amount of electricity. They may be the companies that can prove they possess an executable path from site selection to energized compute.
The power queue is not disappearing.
But the most serious developers are beginning to engineer their way around it.
The artificial-intelligence infrastructure boom is generating extraordinary forecasts for electricity demand.
But there is a widening difference between the amount of power being requested and the amount of credible demand that may actually materialize.
Reuters reported on September 1 that electricity requests from very large power users—primarily data centers—exceed 700 gigawatts across portions of the Midwest, Mid-Atlantic and South. That is more than ten times the estimated current electricity consumption of all U.S. data centers.
Across the Texas grid alone, requests from data centers and other large users reportedly increased from approximately 48 gigawatts in 2023 to more than 474 gigawatts. Yet many proposed projects may be duplicated, speculative or unsupported by the financing and operational capabilities required to complete them.
The problem is becoming known as “ghost demand.”
It is easy to interpret these enormous figures as evidence that the United States simply needs to build more electricity infrastructure. That is partly true. Legitimate data-center demand is growing, and the generation and transmission systems supporting it are under pressure.
But the deeper problem is not merely insufficient capacity.
It is the quality of the information being used to plan that capacity.
A grid application is a claim, not a completed project
A developer requesting 500 megawatts of electricity is effectively making a claim about the future.
The claim says that a facility will be financed, permitted and constructed; that computing equipment will arrive; that an end user will occupy the facility; and that the operation will eventually consume the requested electricity.
None of those conditions is guaranteed merely because an application entered a utility’s pipeline.
A developer may submit similar requests in several locations while deciding where to build. A landowner may attempt to secure a valuable grid position before finding a tenant. A project may have a site but no committed financing. Another may have capital but no realistic equipment-delivery schedule.
Each proposal may appear as future demand even when several applications represent competing versions of the same project.
That is how declared demand can become disconnected from operational readiness.
Ghost demand distorts physical planning
This would be a manageable forecasting error if utilities could add capacity quickly and cheaply.
They cannot.
New generation, substations, transmission lines and grid interconnections can take years to plan, approve and construct. Major equipment such as transformers may have long procurement lead times. These decisions also involve substantial capital commitments whose costs can eventually reach businesses and households.
Utilities therefore face two opposing risks.
If they discount too many requests, they may underbuild. Credible data centers could arrive without sufficient electricity, slowing economic development and increasing reliability pressure.
If utilities treat every request as firm demand, they may overbuild infrastructure for projects that never become operational. Other customers could then be left supporting assets constructed around fictional or exaggerated growth.
The planning question is no longer simply, “How many megawatts have been requested?”
It is, “How much of that demand can be defended with evidence?”
Financial guardrails are already exposing the gap
Evidence from the market suggests that stricter requirements can significantly reduce apparent demand.
Reuters reported that Exelon reduced its estimate of high-probability data-center demand by approximately 40% after introducing stricter collateral requirements. AEP Ohio’s reported pipeline fell by more than half after rules introduced grid-study fees of up to $100,000.
Pennsylvania provides another indicator. Of more than 100 proposed data centers, only 20 had reportedly applied for permits needed to move forward. Many proposals had not secured a power source or customer.
These reductions do not prove that AI electricity demand is imaginary. Substantial load is still expected to materialize.
They demonstrate that the original queue totals should not automatically be treated as bankable forecasts.
Once applicants are required to commit capital or produce evidence, the difference between interest and readiness becomes visible.
Grid access is becoming an evidence-based allocation decision
As electricity becomes a strategic constraint, utilities and regulators will need more reliable methods for separating credible projects from speculative placeholders.
That may mean requiring applicants to demonstrate milestones such as:
Verified ownership and site control
Meaningful and potentially nonrefundable deposits
Committed financing or credit support
Identified tenants or end users
Permitting and construction progress
Equipment-procurement commitments
Realistic energization schedules
Contractually supported load forecasts
Responsibility for infrastructure costs if demand fails to materialize
These requirements transform the interconnection process from a basic queue into something closer to a staged assurance system.
A developer’s position would no longer depend solely on when an application was submitted or how much electricity was requested. It would increasingly depend on whether the project’s claims remain supported by verifiable evidence.
Projects could advance as evidence becomes stronger. Projects that miss milestones could lose priority, forfeit deposits or be removed.
That is not an attempt to stop AI infrastructure.
It is an attempt to prevent unverified ambition from consuming scarce physical capacity.
The new advantage is credible readiness
For several years, much of the AI conversation has centered on models, chips and capital.
Electricity has now joined that list of strategic inputs.
But even access to electricity may not be enough. Companies may have to demonstrate that they are capable of converting a grid reservation into an operating facility.
That creates a different kind of competitive advantage.
The strongest developer may not be the one announcing the largest campus or requesting the most megawatts. It may be the one with the clearest chain of evidence connecting capital, land, permits, equipment, construction and actual computing demand.
In that environment, proof of readiness becomes a valuable asset.
Declared megawatts may create headlines.
Verified megawatts may determine who gets energized.
This is an infrastructure-governance problem
Ghost demand reveals a familiar governance failure: treating a declaration as though it were an observed and verified condition.
The same mistake appears in many AI systems.
An organization declares that a control exists, but cannot produce evidence that it operates. A model is described as monitored, but no immutable record shows who reviewed its decisions. A project is labeled production-ready, but the supporting dependencies remain unresolved.
In each case, the claim moves faster than the evidence.
That gap may be tolerable while an idea remains inside a presentation. It becomes dangerous when institutions begin allocating capital, infrastructure or risk capacity around it.
Power grids cannot be planned from aspiration alone.
Every serious request will eventually have to answer a more demanding question:
What evidence proves this project is real?
The physical limits of the grid are forcing the AI economy toward a principle that should already be familiar:
Direction matters. Scale matters. But neither substitutes for verified readiness.
The power queue is beginning to ask for receipts—and that may be one of the healthiest developments in the AI infrastructure race.
The race to build artificial-intelligence infrastructure is usually described in terms of capital, chips and computing capacity.
Yet every AI data center ultimately depends on a more physical constraint: electricity.
That dependence has triggered a wave of large-load requests across the United States. Developers are reserving potential sites, exploring multiple utility territories and attempting to secure access to power years before facilities become operational.
The resulting interconnection queues appear to show extraordinary demand.
But they also create a difficult planning question:
How much of that demand is credible enough to build around?
Texas has brought that question into the open.
Why Texas paused the process
On August 3, 2026, Texas Governor Greg Abbott directed the Public Utility Commission of Texas and the Electric Reliability Council of Texas to conduct a comprehensive audit of data centers advancing through ERCOT’s interconnection process.
Projects must complete the audit before advancing, and noncompliant projects may be denied connection.
At the time of the directive, ERCOT was considering more than 474 gigawatts of electricity requests—more than five times the grid’s record peak demand. Approximately 90% of those new requests were tied to data centers. The audit seeks information about project ownership, projected power consumption, on-site generation, financial assistance, water demand and community impact. The official directive is available here.
Those figures do not mean Texas will actually add 474 gigawatts of new load.
They mean ERCOT received requests representing that amount.
The distinction is critical.
One project can appear as several electricity requests
A company planning a data center may evaluate multiple potential locations before making a final investment decision. Each proposed location can enter a utility’s planning process even if the company ultimately intends to develop only one.
Other applicants may be attempting to reserve a valuable grid position before securing financing, land, permits, customers or a complete construction plan.
These requests are not necessarily fraudulent. Some are part of reasonable site-selection and development activity.
However, when utilities aggregate them as though every project will be built, exploratory demand begins to resemble committed demand.
That makes the queue unreliable as a forecast.
A Reuters review found that large electricity requests across parts of the Midwest, Mid-Atlantic and South exceeded 700 gigawatts—more than ten times estimated current U.S. data-center electricity use. The reporting also found no common standard for how utilities count and disclose proposed demand. Some include only projects with signed agreements, while others count preliminary inquiries without firm commitments. Reuters described the resulting uncertainty as “ghost demand.”
The AI power queue therefore has both a capacity problem and a data-quality problem.
Utilities are being asked to make irreversible decisions using uncertain demand
Electric infrastructure cannot be scaled like cloud software.
Transmission lines, substations and generation facilities can require years of permitting, construction and capital deployment. Utilities must begin planning well before the associated demand appears.
If planners discount too much of the queue, legitimate projects may arrive before sufficient capacity is available. Reliability can deteriorate, interconnection delays can lengthen and regions may lose economically viable development.
If planners treat every request as certain, they may build expensive infrastructure for facilities that never materialize. Those stranded costs can eventually affect households and existing businesses.
The choice is not simply whether to build more power infrastructure.
It is whether the evidence supporting each projected load is strong enough to justify when, where and how much infrastructure should be built.
The queue is becoming a verification system
Historically, obtaining a position in an interconnection queue could be treated primarily as a procedural step.
That model becomes unstable when speculative applications overwhelm the planning signal.
A more defensible system would separate early interest from commercially executable demand. Projects seeking priority access to scarce grid capacity may therefore need to produce stronger evidence, including:
Financial readiness
A credible project should be able to demonstrate committed capital, credit support or enforceable financing milestones.
Deposits and study fees create financial consequences for occupying limited planning capacity without progressing. The Texas Batch Zero process reportedly required many projects to post security of $50,000 per megawatt, meaning some applicants committed tens of millions of dollars merely to enter the process. Reuters reported that proposed rule changes could make a larger portion of these deposits nonrefundable.
Money alone does not prove a facility will be completed, but it makes casual queue speculation more expensive.
Site control
Developers may need to demonstrate ownership, a binding lease, purchase options or another enforceable right to develop the proposed property.
Without site control, a large load request may represent little more than an attractive possibility.
Construction readiness
Permits, engineering plans, equipment orders and contractor commitments provide evidence that a project has progressed beyond an announcement.
Utilities may also evaluate whether the proposed commercial-operation date is consistent with the actual construction schedule.
Credible load schedules
A data center rarely reaches its full electricity demand on the first day of operation.
Developers should be able to present staged, time-bound load projections tied to buildings, equipment installations and customer commitments. A defensible schedule might specify when the first 100 megawatts will become operational, what triggers the next expansion and how demand changes if construction is delayed.
A single maximum-load figure is far less useful than an evidence-supported ramp.
Ownership and customer transparency
Regulators and utilities need to know who controls a project and whether the proposed facility has an identifiable end user.
Complex affiliate structures can obscure whether several applications represent separate developments or multiple versions of the same underlying project.
Operational flexibility
Projects that can provide on-site generation, storage or controlled load reduction may impose less risk on the grid than facilities requiring uninterrupted firm service at maximum capacity.
Flexibility will not eliminate the need for infrastructure, but it may affect how projects are evaluated and prioritized.
Credibility may become the next AI infrastructure moat
The immediate assumption might be that stricter screening will slow every project equally.
It probably will not.
Screening is more likely to separate credible projects from immature ones.
Developers with verified capital, controlled sites, transparent ownership and realistic construction schedules may gain an advantage because utilities can incorporate their demand into planning with greater confidence.
This creates a new form of infrastructure competition.
The scarce asset is not merely electricity. It is credible access to future electricity.
A queue position supported by verifiable evidence may become more valuable than a larger request backed only by projections.
Executives planning AI infrastructure should therefore ask:
Is the stated load associated with an approved and financed project?
Does the organization control the proposed site?
Are construction dates tied to documented milestones?
Does the load forecast distinguish initial demand from later expansion?
Can ownership, customers and counterparties be verified?
Has the organization accounted for deposits, transmission upgrades and delay risk?
Can the facility reduce its grid dependence during constrained periods?
These are no longer administrative details. They affect whether an infrastructure plan can survive regulatory, financial and operational scrutiny.
The lesson extends beyond Texas
Texas is the clearest current example, but the underlying problem is national.
Utilities throughout the country are trying to determine whether enormous AI-related electricity requests represent an approaching physical load or a collection of overlapping development scenarios.
Financial requirements are already changing the answer. Reuters reported that Exelon reduced its estimate of high-probability data-center demand by about 40% after introducing stricter collateral requirements. AEP Ohio’s pipeline fell by more than half after new rules introduced study fees and other requirements.
That does not prove the remaining demand is easy to serve. Even after weak or duplicated requests are removed, credible AI demand can still exceed available generation and transmission capacity.
Filtering the queue does not manufacture electricity.
It produces a more trustworthy basis for deciding where infrastructure should be built.
From declared demand to observed readiness
The broader lesson is familiar across AI governance:
A declaration is not evidence.
Organizations routinely declare that controls exist, projects are ready or demand is imminent. Effective governance tests those claims against observable conditions.
The same principle is now reaching the power grid.
A developer may declare a need for one gigawatt. Grid planners increasingly need evidence showing the financing, site, customers, construction milestones and operating schedule behind that request.
Texas’s pause is therefore more than a reaction to data-center growth.
It signals a shift from accepting projected demand at face value to verifying whether that demand is executable.
The next phase of the AI infrastructure race will not be won by whoever submits the largest power request.
It will be won by organizations able to prove that their projects are real, ready and financially capable of reaching energization.
Before the grid can allocate capacity, it must be able to trust the queue.
Much of the discussion surrounding AI infrastructure still concentrates on chips, capital and real estate.
Those inputs matter, but they do not guarantee that a data center can operate.
A facility can have land, permits, financing and thousands of GPUs on order. Without sufficient electricity—and a credible date for receiving it—the project remains planned capacity rather than usable compute.
That distinction is becoming strategically important as data-center developers compete for limited positions in electricity-connection queues.
When proposed demand creates real congestion
Britain provides a useful example.
According to Ofgem, demand-connection applications increased from 41 gigawatts in November 2024 to 125 gigawatts by June 2025. Data centers represented at least 80 gigawatts of that demand.
For perspective, the application queue does not mean all that capacity will be built or consumed. That is precisely the problem.
Some applications come from viable projects with secured land, committed capital, identifiable customers and realistic construction schedules. Others may represent duplicate, premature or speculative attempts to reserve capacity.
Yet each application enters a planning system that must determine where and when electricity infrastructure will be needed.
Consequently, phantom demand can produce real effects.
It can occupy positions in the connection queue, complicate load forecasts and delay projects that are genuinely prepared to proceed. A proposed data center does not have to reach construction to contribute to congestion. Its claim on future capacity may be enough.
Making developers prove readiness
Ofgem has proposed introducing commitment fees and additional project-progress milestones for data-center connections.
The principle is straightforward: reserving scarce grid capacity should require more than submitting an ambitious projection.
Developers may need to place capital at risk and demonstrate continued progress through evidence such as financing, customer commitments, planning advancement or procurement of long-lead equipment. Projects that stall or withdraw could lose their queue position and, depending on the final rules, forfeit some or all of their financial commitment.
This would convert grid access from a largely administrative reservation into a test of project credibility.
The market signal is difficult to miss.
Future electricity access is becoming valuable enough that regulators must discourage organizations from reserving it speculatively.
Land is only part of the infrastructure stack
For years, favorable data-center locations were evaluated through familiar factors:
Available land
Fiber connectivity
Tax incentives
Environmental conditions
Proximity to customers
Construction costs
Grid access can no longer sit quietly near the bottom of that list.
A parcel of land located near transmission infrastructure is not necessarily an energizable site. Physical proximity does not guarantee available capacity, a completed interconnection study, required network upgrades or an acceptable connection date.
The more useful question is no longer simply, “Where can the facility be built?”
It is, “Where can the facility be powered, at the required scale, within the required timeframe?”
That changes the meaning of a strategic site.
The true asset may be the combination of land, permits, transmission capacity and enforceable progress toward energization.
An emerging form of infrastructure optionality
A credible grid position gives a developer something close to infrastructure optionality.
It can influence site value, project financing, construction sequencing and the ability to secure customers. Hyperscalers and investors evaluating competing projects will increasingly need to distinguish between advertised capacity and capacity with a defensible path to power.
That creates a new diligence requirement.
Executives should ask:
Is the project merely in a connection queue, or does it have a firm connection agreement?
What network upgrades must occur before energization?
Who is responsible for financing those upgrades?
Which milestones must the project satisfy to retain its position?
Is the stated connection date conditional?
Does the developer control the land and possess the permits required to proceed?
Is the electricity supply firm, flexible or dependent on curtailment?
What evidence supports the announced megawatt figure?
These are not secondary engineering questions. They affect valuation, delivery risk and the credibility of the entire AI-capacity claim.
Announced megawatts are not operating megawatts
The AI infrastructure market is producing enormous numbers: billions in capital commitments, gigawatts of proposed demand and campuses containing hundreds of thousands of accelerators.
Those figures can create an illusion of inevitability.
But a proposed megawatt is not an energized megawatt.
Likewise, a grid application is not proof of a viable project. It may represent serious development activity, but it may also represent an attempt to preserve a future option.
This is why regulators are beginning to demand stronger evidence of readiness.
Grid queues cannot function effectively when an unverified claim receives the same treatment as a financeable, permitted and construction-ready project. When capacity is scarce, credibility must become part of the allocation mechanism.
The strategic implication
The AI infrastructure contest is shifting.
Companies will still compete for chips, technical talent and capital. Increasingly, however, they will also compete for substations, transmission capacity, generation agreements and credible energization dates.
That means the new moat may not be electricity ownership in the literal sense.
It may be something more practical: a defensible right to receive electricity at the necessary location, scale and time.
GPUs can be purchased. Buildings can be constructed. Capital can be raised.
But when the grid is constrained, credible access to future electricity becomes difficult to replicate.
The most valuable AI facility may not be the one with the largest announcement.
