On September 30, the federal statutory framework governing minimum standards for certain federal data centers is scheduled to sunset. The requirements apply to federal facilities and covered agency arrangements rather than the privately developed data centers now reshaping electricity demand, water planning, land use, and local politics across North Carolina.
Its expiration nevertheless reflects a broader policy development. No comprehensive national framework is emerging to govern the current data center buildout. Many of the consequential decisions are instead being made through state legislation, utility proceedings, local development approvals, water policies, and economic development agreements.
That shift provides important context for Senate Bill 730, the Ratepayer Protection Act. The North Carolina House passed the substantially revised bill on June 3, and it was referred to the Senate Rules Committee on June 8 for consideration of the House changes.
Large-Load Growth Is Driving the Policy Debate
The central concern behind Senate Bill 730 is the scale and concentration of expected electricity demand.
Since 2024, Duke Energy has signed electric-service agreements representing 7.6 gigawatts of new data center demand across its multistate service territory, with most of those projects reportedly under construction. The company has also been in advanced discussions involving another 15.4 gigawatts. Those figures are not limited to North Carolina, but they illustrate the size of the development pipeline facing major utilities.
Serving a large data center may require new generation, transmission, substations, distribution infrastructure, and long-lead equipment. The financial risk becomes more complicated when a customer reserves substantial capacity but develops more slowly than projected, consumes less electricity than expected, or abandons the project after the utility has begun making investments.
The most important policy question is therefore not simply whether utilities can serve new demand. It is how project-specific costs and risks are allocated among the large customer, the utility, and its existing residential, commercial, and industrial customers.
The Bill’s Strongest Provisions Address Cost Allocation
Senate Bill 730 is most effective when it focuses directly on that question.
Section 4 would require data centers with peak monthly demand of at least 100 megawatts to enter into electric-service contracts containing minimum billing requirements, contract terms long enough to recover incremental costs, credit protections, and termination provisions. The contracts would be filed with the North Carolina Utilities Commission, while the Public Staff would retain access to confidential information needed to represent customers.
These provisions are designed to protect existing customers if a large project does not develop or consume power as originally anticipated. Rather than prescribing one rate for every facility, they allow regulators and utilities to address the costs and risks associated with individual projects while establishing clear statutory protections against cross-subsidization.
Section 8 would also commission a broader study of large-load policy, including appropriate tariff terms, customer curtailment, and whether large users should provide some of their own generation. The study would be due before the 2027 legislative session.
The regulatory process is already moving in the same direction. Duke Energy Carolinas’ July settlement with the Public Staff and other parties calls for continued expedited discussions concerning a separate tariff for large-load customers. If approved, the broader settlement would reduce Duke’s proposed cumulative residential increase from approximately 18 percent to 9.5 percent over two years.
The tariff discussion remains unfinished, but it reinforces the underlying point: contracts, rates, financial assurances, and regulatory oversight are the mechanisms most directly connected to ratepayer protection.
The Water and Incentive Provisions Raise Different Questions
Other parts of Senate Bill 730 address legitimate concerns but use broader policy tools.
Section 2 would direct the Department of Environmental Quality to establish water-use standards while prohibiting evaporative cooling systems at covered data centers. Closed-loop and reclaimed-water requirements could be appropriate where water availability is limited, but an unconditional technology prohibition does not account for differences in local water supply, climate, facility design, or the electricity required by alternative cooling systems.
A more flexible standard could allow the state to impose stricter requirements in water-stressed areas while evaluating each project’s total resource demands. That approach would preserve water protection without assuming that the same cooling configuration is optimal in every county.
Section 6 would prohibit local governments from offering economic development incentives to covered data centers. This would eliminate questionable incentive packages, but it would also prevent communities from negotiating performance-based agreements even when they include disclosure requirements, investment thresholds, infrastructure commitments, and clawbacks.
The policy question is not whether every project should receive incentives. It is whether a statewide prohibition is preferable to stricter standards governing when incentives may be offered and how their costs and benefits must be reported.
Local Concerns Extend Beyond Electricity Rates
Ratepayer protection addresses only one part of the data center debate.
Local governments must also evaluate noise, water and sewer capacity, emergency services, road access, land-use compatibility, construction impacts, and the effect of a large industrial campus on nearby properties. These concerns often determine whether a technically feasible project can survive the public approval process.
Senate Bill 730 preserves existing local zoning authority and adds procedural requirements for covered projects. Even so, a durable state framework will need to leave communities with enough authority and information to address project-specific conditions.
When residents believe a project is substantially complete before the public process begins, opposition tends to move toward moratoriums, litigation, and elections. A clearer framework should reduce that pressure by establishing minimum information requirements and allowing local concerns to be addressed before positions become fixed.
Project Rejection Does Not Resolve Every Cost Question
North Carolina can avoid project-specific infrastructure investments by declining a data center development. It would also forgo the electricity revenue, tax base, construction activity, and other economic contributions associated with the project.
That does not mean every proposed facility produces a net public benefit. It means the analysis should distinguish between costs created solely by the project and broader investments the electricity system will require for reliability, replacement generation, and transmission regardless of where a particular data center locates.
A large customer that pays the full incremental cost of its service may also contribute toward the utility’s shared fixed costs. The outcome depends on the contract, tariff, infrastructure requirements, development schedule, and longevity of the customer rather than on the project category alone.
A More Durable Framework Would Be Targeted
North Carolina does not need to choose between unrestricted development and a broadly restrictive statewide regime.
A more durable approach would retain the bill’s electric-service contract requirements, Utilities Commission oversight, and large-load policy study. It would pair those protections with water standards tied to local resource conditions, clearer treatment of phased developments, and incentive rules based on transparency, performance requirements, and enforceable clawbacks.
That framework would not guarantee approval for every project. It would provide a more consistent method for determining which projects can protect ratepayers, address local concerns, and produce sufficient public value to move forward.
The title of Senate Bill 730 accurately identifies the immediate policy priority. The remaining question is whether its final provisions stay focused on protecting ratepayers or create broader restrictions that add uncertainty without materially improving that protection.