Last Update: 09/17/2026 at 10:34 PM EST

Morning Briefing: Data Centers

Thursday, September 3, 2026

September 3, 2026

Pennsylvania Makes GRID Compliance a Gate for Growth

Pennsylvania has made a decisive shift in how it will handle large data-center development: GRID compliance is now a binding condition for permits, fast-track treatment, and a major equipment tax exemption. For projects expecting at least 25 MW of peak demand, a PADEP consent order and local zoning and development approvals must be in place before permitting can proceed.

That does not amount to a moratorium. It does, however, turn the debate over power, water, grid upgrades, and local benefits into a commercial requirement at the front of the development process. Elsewhere, a temporary federal halt in Nevada and unresolved policy fights from California to Congress showed that the practical question is increasingly not whether data centers will be built, but on what terms and with whose costs disclosed.

Pennsylvania's Executive Order 2026-05 is the day's clearest concrete policy move. The state has converted its GRID framework from voluntary guidance into an enforceable gate for covered projects, tying certification to the Permit Fast Track Program and the computer data-center equipment sales-tax exemption. The order also restricts state-agency nondisclosure agreements, requires public mapping of permitting information, and will require existing facilities to report annual energy and water use beginning in July 2027. The consequence is significant: developers seeking state support must now show how generation, grid upgrades, water infrastructure, and community obligations will be handled rather than treating those issues as downstream negotiations.

In Nevada, the Interior Board of Land Appeals temporarily stopped progress on the proposed 80-acre Townsite Data Center near Boulder City. The board is reviewing challenges to the Bureau of Land Management's environmental review and public-participation process, including whether it improperly relied on analysis prepared for a solar project. The stay is not a rejection of the project, but it creates immediate schedule risk and demonstrates that a weak environmental record can become a material constraint after a federal approval has been issued.

The contest over who pays for resource impacts continued to move into formal policymaking. California lawmakers are still weighing seven bills on water disclosure, environmental review, electricity demand, and grid-cost allocation, with decisions expected later this month. In Washington, congressional subcommittees considered proposals that would require certain public water systems to charge data centers for connection and expansion costs and would direct EPA reporting on facilities averaging more than 200,000 gallons of daily water use. Neither effort is law, but both place developer-funded infrastructure and consumption disclosure firmly on the policy agenda.

A proposed Wyoming campus illustrated a different kind of permitting risk: the choice of review route itself. Oil City News reported that Prometheus Hyperscale asked Natrona County to consider industrial-park zoning for a proposed 940-acre, 1.5-GW campus near Casper. The designation could allow the project to avoid state industrial-siting review while remaining under county oversight. Commissioners took no action, and the project's financing, power, cooling, and construction plans remain proposals. Still, the request puts the division between local land-use control and state-scale review at the center of a very large prospective load.

Key Points

  • The move toward conditional development is becoming more operational, but it remains jurisdiction-specific. Pennsylvania has imposed binding requirements; California's package is still contested; federal water proposals have only reached the hearing stage. For developers and investors, that means the central risk is a patchwork of approval conditions rather than a single national rulebook.
  • Procedural legitimacy is becoming a critical-path issue alongside land and power. Nevada's pause arose from alleged defects in environmental analysis and public participation, while Wyoming's developer is seeking a county zoning route that could avoid a state review. Portland's committee recommendation for earlier disclosure of potential data-center deals points in the same direction, though it is nonbinding: communities are increasingly focused on when they get information and which public body retains control.
  • The available reporting was more about governance than deployment. It did not establish new construction starts, completed financings, power procurements, or interconnection awards. That distinction matters because regulatory scrutiny can reshape project economics and schedules before it produces a visible change in the physical buildout pipeline.

Implications

Site control alone is becoming less sufficient for large-load development. Pennsylvania's framework suggests that incentive eligibility, permitting sequence, local acceptance, infrastructure funding, and disclosure may need to be addressed as one integrated development plan. Projects that separate those questions too late may face longer negotiations or weaker access to state support.

For projects on federal land, the Nevada stay raises the value of project-specific environmental analysis and a defensible public-participation record. If the Interior Board of Land Appeals ultimately upholds the challengers' arguments, the immediate effect would be on Townsite; the broader consequence could be more cautious review of other federally managed-land proposals.

Water policy is beginning to follow the same cost-allocation logic already visible in grid debates. The congressional proposals would matter only if enacted, but they show growing pressure to distinguish ordinary utility customers from unusually large users whose connections or expansion needs require additional public infrastructure.

Watchpoints

Watch

Pennsylvania's implementing guidance, the terms of PADEP consent orders, and the first covered projects seeking permits or tax exemptions under the mandatory GRID framework.

Watch

The Interior Board of Land Appeals' final ruling on the Townsite Data Center, including whether BLM must revisit its environmental analysis or public-participation process.

Watch

California's legislative decisions later this month, particularly whether measures shifting transmission and grid-expansion costs toward data-center operators advance.

Watch

Whether Natrona County moves forward with industrial-park zoning for the Prometheus proposal and what review, generation, emissions, water, and community conditions accompany any action.

Watch

Whether the federal water-infrastructure proposals gain committee support or remain an agenda-setting response to large data-center demand.

Fallout

The day reinforced a developing shift from broad concern about data-center impacts toward specific conditions on permits, incentives, review processes, and infrastructure costs. Pennsylvania's action is binding; Nevada's pause is project-specific; California and federal water measures remain unresolved. The common pressure point is who must demonstrate, disclose, and fund the consequences of large new loads.

Pennsylvania's GRID Development Gate

Pennsylvania is using permitting and tax-incentive access to require large data-center developers to address power, grid, water, transparency, and local-approval obligations.

Fresh developments

Executive Order 2026-05 makes GRID compliance mandatory for covered projects. Facilities anticipating at least 25 MW of peak demand need a PADEP consent order and local zoning and development approvals before permits proceed; GRID certification is also required for fast-track participation and the equipment sales-tax exemption.

Why we noticed

This is a binding state-level change, not a proposed bill or voluntary corporate pledge. It places infrastructure responsibility and public disclosure near the beginning of the project-development sequence.

Watch for:

  • PADEP guidance defining consent-order requirements and enforcement.
  • Whether developers alter project designs, power plans, or schedules to qualify for incentives and permits.
  • The first annual energy and water reports required from existing facilities in July 2027.

Federal-Land Review Risk in Nevada

The Townsite Data Center near Boulder City has become a test of whether federal agencies can rely on earlier environmental analyses when approving new AI infrastructure projects.

Fresh developments

The Interior Board of Land Appeals issued a temporary stay on the proposed 80-acre facility while reviewing challenges to BLM's environmental review and public-participation process.

Why we noticed

The project is not cancelled, but the stay converts opposition into a concrete schedule constraint. It underscores that environmental review quality can determine whether a federal approval remains usable.

Watch for:

  • The board's final decision and any required supplemental review.
  • Whether BLM changes its approach to environmental analysis for comparable proposals.
  • Any effect on other data-center applications involving federally managed land.

Water and Grid Cost Allocation

State and federal policymakers are weighing whether data-center operators, rather than general ratepayers or utility customers, should bear a greater share of the infrastructure costs associated with their demand.

Fresh developments

California's seven pending bills remain under active lobbying, including measures affecting water disclosure and grid-expansion costs. Congressional subcommittees also considered a proposal requiring certain public water systems to charge data centers for connection and expansion costs, alongside EPA reporting on high-volume water use. Portland's committee separately recommended greater disclosure of prospective local deals.

Why we noticed

The measures are at different stages and none establishes a universal rule. Together, they show that water, transmission, and transparency are increasingly being treated as development-cost questions rather than solely as local political concerns.

Watch for:

  • California legislative votes and any final treatment of transmission-cost allocation.
  • Whether the federal water proposal receives committee action or broader support.
  • Portland City Council's response to the committee's nonbinding transparency recommendation.

Wyoming's Local Versus State Siting Choice

Prometheus Hyperscale's proposed Casper-area campus raises the question of whether a very large data-center load can proceed through county industrial-park zoning rather than state industrial-siting review.

Fresh developments

The developer asked Natrona County commissioners to consider industrial-park zoning for a proposed $500 million, 940-acre campus with a stated 1.5-GW load. Commissioners did not act at the workshop.

Why we noticed

The request is only an early procedural step, but the proposed scale makes the eventual review path consequential for power generation, emissions, water, noise, traffic, and local oversight.

Watch for:

  • Whether county commissioners advance the zoning designation.
  • Whether state review remains applicable and what county conditions could be imposed.
  • More concrete evidence of financing, generation plans, cooling arrangements, and utility commitments.

Final Thought

The important change is not that large data centers face more debate; they do. It is that the debate is increasingly being translated into the mechanisms that determine whether projects proceed: consent orders, tax treatment, environmental records, zoning routes, and utility-cost rules. Pennsylvania has made that translation concrete, while Nevada shows how quickly a contested process can become a real schedule risk.