FERC's July 2026 order moves large computational loads from a largely voluntary risk-management discussion toward formal reliability-standard development. By September, NERC reported that foundational computational-load standards had passed an initial ballot. The record is important, but the status boundary matters: development and balloting are not the same as final, FERC-approved Reliability Standards applying automatically to every data center.
What FERC ordered in July 2026
On July 16, 2026, FERC issued an order in Docket RD26-7-000 directing the North American Electric Reliability Corporation to develop and submit new or modified Reliability Standards addressing reliability risks associated with the integration of computational loads into the Bulk-Power System. The Commission also directed NERC to develop revisions to its Rules of Procedure, including registry criteria for computational-load entities.
The order sets December 31, 2026 as the deadline for both the Reliability Standards filing and the Rules of Procedure revisions. FERC's order therefore creates a formal federal deadline for work that NERC had already begun through its Large Loads Action Plan and standards-development process.
Sources for this sectionFERC order, Docket RD26-7-000 ↗FERC July 2026 meeting summary ↗
Why computational loads are being treated separately
FERC's order says NERC has documented multiple grid disturbances in which computational loads caused or contributed to instability of the Bulk-Power System. The concern is not simply that data centers consume large amounts of electricity. Computational loads can also have operating characteristics that differ from more traditional demand, including rapid changes in consumption and voltage-sensitive behavior that can affect planning and system response.
NERC's Large Loads Action Plan brings together standards development, registration work, disturbance analysis, modeling, technical guidance, and operational practices. The plan covers emerging large loads including data centers and cryptocurrency facilities. That broader program is useful context for the FERC order because the Commission did not create the engineering concern from scratch; it imposed a firm timetable on an existing NERC workstream.
- Large load size is only one part of the reliability question.
- Disturbance behavior and load response matter to grid planners and operators.
- Registration, modeling, planning and operational standards are separate pieces of the response.
Sources for this sectionNERC Large Loads Action Plan ↗
What had happened by September 2026
On September 19, 2026, NERC announced preliminary results indicating that foundational Computational Loads Reliability Standards had passed an initial ballot. NERC described the standards as addressing the distinctive operating characteristics and reliability risks of rapidly growing computational loads and said the work drew on incident reviews, a Level 3 Alert, the Large Loads Working Group, and stakeholder participation.
An initial ballot is an important standards-development milestone, but it is not the same thing as a final Reliability Standard approved by FERC. NERC's standards process can include comment periods, ballot validation, revisions, additional ballots and formal filings. FERC then has its own statutory role in reviewing Reliability Standards submitted by NERC. Public reporting should preserve those stages rather than collapsing them into a statement that a new federal data-center standard is already in force.
Sources for this sectionNERC initial-ballot announcement ↗NERC Project 2026-02 Computational Loads ↗
Registry criteria are a separate question from the technical standards
FERC also directed NERC to revise its Rules of Procedure to include registry criteria for computational-load entities. Registration matters because the ERO framework assigns reliability responsibilities to registered entities under defined criteria. The order therefore addresses not only what reliability requirements should exist, but also which computational-load entities may need to enter the formal registration structure.
The existence of a registry workstream does not mean that every data center is already a registered NERC entity or that every project will meet future registration criteria. Applicability depends on the final criteria and the facts of the facility or entity. Until the process is complete, a careful source review should describe the direction of travel without inventing a universal threshold or declaring a particular site covered.
Sources for this sectionFERC order, Docket RD26-7-000 ↗NERC FERC Orders and Rules - 2026 ↗
What this record does not establish about a named data center
The FERC and NERC records are system-level reliability documents. They do not identify every computational-load facility, prove that a particular data center caused an outage, establish a facility-specific violation, or determine how a specific project should be treated under a future registration threshold.
They also do not answer environmental permitting questions. A reliability standard can address modeling, disturbance performance, telemetry, planning or operational behavior without establishing generator emissions, air-quality impacts, water use or land-use effects. Those claims require different records from the relevant permitting, utility, monitoring or environmental authorities.
- Standards development is not a facility-specific enforcement finding.
- An initial ballot is not final FERC approval.
- Bulk-power reliability evidence does not substitute for an air permit or emissions record.
- Future registration criteria should not be applied retroactively by assumption.
How to use the 2026 record responsibly
The strongest supported conclusion is that computational loads have become a formal reliability-standard and registration issue within the federal electric-reliability framework. FERC has imposed a year-end deadline, NERC has advanced foundational standards through an initial ballot, and NERC's Large Loads Action Plan documents a broader technical program around emerging large loads.
For project-level research, the next step is to connect that system-level framework to actual utility, transmission, interconnection and facility records. If a Northern Virginia project is being studied, for example, the relevant evidence may include Dominion interconnection requirements, PJM filings, NERC disturbance records, utility tariffs and the facility's own public permitting record. The federal standards-development record provides context; it does not fill gaps in those project-specific sources.
The source controls over this summary. Corrections should identify the disputed sentence and the strongest available primary record.
Questions about framing and source selection: [email protected]. A named editor has not yet been published; no cited researcher is represented as responsible for this page.
Send the page URL, disputed claim and supporting source. Review does not require endorsement.
Request a correction →