BLOG POST

Power & Pipes

FERC, CFTC, and State Energy Law Developments

Data Centers Move Closer to NERC Oversight

The North American Electric Reliability Corporation (NERC) filed a petition in October 2026 with the Federal Energy Regulatory Commission (FERC) proposing to bring large computational loads, including certain data centers, directly within NERC’s registration framework and, consequently, subject those entities to NERC’s reliability compliance framework.

The proposal marks a step toward expanding NERC’s oversight beyond traditional electric industry participants to large computational loads—a distinct category of electricity consumers that would, for the first time, face direct federal reliability compliance obligations. Technology companies and other large load developers, owners, and operators should begin considering the potential implications for project design, development, and commercial arrangements.

NERC’s Proposal Creates Two New Registration Categories

NERC seeks to amend its Rules of Procedure to create two new registration functions: Computational Load Owner (CLO), which owns and maintains a Computational Load Site, and Computational Load Operator (CLOP), which operates a Computational Load Site. A Computational Load Site is one or more buildings, structures, or installations at a single location that primarily contain information technology infrastructure for software services, artificial intelligence, cryptocurrency mining, or other computational activities.

The proposal would require registration by CLOs and CLOPs for sites with at least 50 megawatts of total connected load supplied through equipment connected to the bulk-power system (BPS) at 100 kilovolts (kV) or higher from one or more connection points. NERC defines “total connected” to include cooling and other supporting systems, not only computing equipment. NERC’s proposal is limited to computational loads rather than all large industrial or commercial customers.

NERC’s current petition does not propose new Reliability Standards applicable to computational loads. However, NERC is separately advancing standards that would impose substantive compliance obligations on CLOs and CLOPs. On October 26, 2026, NERC’s Board of Trustees adopted foundational Reliability Standards addressing computational load interconnection and modeling, operational data and communications, and protection coordination and disturbance monitoring.

Both the proposed registration changes and the new Reliability Standards remain subject to FERC approval, and, if approved, any mandatory standards obligations would take effect according to their approved implementation schedules. If FERC approves those standards as filed, the compliance obligations would arrive on a staggered basis over approximately a calendar year after approval, with longer implementation deadlines for requirements involving the installation of new equipment.

Why Are Energy Regulators Focused on Computational Loads?

Computational loads may experience rapid and significant fluctuations in electricity demand, including sudden reductions in consumption during grid disturbances, potentially causing voltage and frequency deviations that may affect the stability of the BPS. These potential risks have raised concerns for NERC, the FERC-certified Electric Reliability Organization responsible for the reliable operation and planning of the BPS, and FERC itself. In its petition, NERC identifies several recent incidents involving large, unexpected load reductions that illustrate these potential risks. A recurring concern is that in many cases grid planners and operators lack data and coordination directly from these large loads to mitigate potential disturbances.

NERC’s petition follows initiatives through NERC’s Large Loads Action Plan and work of its Large Loads Task Force (now the Large Loads Working Group), including incident reviews, a May 2026 Level 3 alert, and a gap assessment showing limits in what existing registered entities can do. In addition, FERC directed NERC in July 2026 to submit proposed registry criteria and an initial set of Reliability Standards for computational loads by December 31, 2026, and NERC filed the petition in response to that directive.

NERC’s Legal Authority to Regulate Loads

Historically, NERC’s regulatory focus has been on entities performing specified reliability functions associated with the operation of the electric grid, rather than end-use electricity customers. NERC derives its authority from Section 215 of the Federal Power Act, which provides for mandatory Reliability Standards applicable to “users, owners, and operators” of the BPS. Although Section 215 expressly excludes facilities used in the local distribution of electric energy from the definition of the BPS, NERC relies on the statute’s reference to “users” to support registering certain computational loads whose operations may materially affect BPS reliability. Thus, NERC’s proposal would extend direct reliability oversight to qualifying electricity customers notwithstanding the traditional distinction between regulated grid infrastructure and end-use facilities.

What Companies Should Consider Now

Beyond assessing whether a facility meets NERC’s proposed registration criteria, developers, owners, and operators of large computational loads should consider the potential commercial implications of registration, particularly when negotiating new agreements or evaluating in-flight projects. Key considerations include the following:

  • Defining the Computational Load Site: NERC’s proposed definition of a “Computational Load Site” may encompass multiple buildings or installations based on shared infrastructure and coordinated use and is not limited by property boundaries, such as parcel lines. Accurate application of NERC’s definitions and the 100 kV criteria is critical for determining whether facilities are potentially in scope for NERC’s registration criteria. Developers and operators should evaluate how facility configurations and NERC’s proposed voltage and load thresholds may affect whether and how a project falls within NERC’s scope under the proposed framework.
  • Allocation of Regulatory Responsibility: Commercial arrangements for large computational load projects often involve multiple parties with distinct ownership and operational responsibilities. This could result in multiple CLOs or CLOPs at a single site under NERC’s proposed framework. Parties should consider how registration and compliance responsibilities will be allocated, including whether NERC’s alternative registration mechanisms (e.g., Joint Registration Organization or Coordinated Functional Registration) may be appropriate to manage day-to-day compliance responsibilities.
  • Future Compliance Obligations and Change in Law Risk: Registration of CLOs and CLOPs could eventually subject these entities to NERC Reliability Standards obligations, potentially including Critical Infrastructure Protection (CIP) cybersecurity and physical security requirements. Parties should consider whether existing and future agreements adequately address these potential obligations, including the allocation of compliance costs, operational impacts, and changes to contractual performance and security requirements.
  • Transaction Structuring and Future Expansion: Developers, owners, operators, and tenants should consider how phased load ramps, campus expansions, and changes in ownership or operational control could trigger NERC registration and compliance obligations. Transaction documents and commercial agreements may need to account for these potential regulatory triggers, including the allocation of compliance costs and responsibilities as projects develop or expand.

Looking Ahead

NERC’s petition represents a step toward potentially imposing direct reliability obligations on qualifying owners of Computational Load Sites, part of a broader shift toward addressing the reliability impacts of large electricity customers through direct regulatory oversight.

Large computational load developers, owners, and operators should evaluate potential registration obligations now and consider how future NERC compliance requirements could affect project development, operational arrangements, and commercial contracts. Early planning may help avoid costly adjustments once the registration framework and applicable Reliability Standards take effect.

Comments on NERC’s proposal may be filed in Docket No. RR27-1-000 by November 20, 2026.

How We Can Help

Our team counsels clients on NERC registration, compliance programs, audit preparation, and enforcement and advises on the development and commercial arrangements needed to support large load projects. In addition, the Morgan Lewis Data Center Strategic Initiative brings together lawyers across disciplines to address the interconnected issues involved in developing, financing, investing in, and operating data centers and digital infrastructure.

We stand ready to advise participants across the data center lifecycle, including on-site acquisition and development, construction and leasing, power procurement and energy infrastructure, project and structured finance, investments and joint ventures, network connectivity, equipment and technology procurement, supply chain matters, tax and economic incentives, regulatory compliance, data center operations, and compute capacity arrangements.

For additional developments and analysis, visit our data center practice and Data Center Bytes blog.