Top 10 Computational Load Accountability Mapping Questions for Leaders
By KEIRSTEN BRAGER
NERC's August 19, 2026 posting split the single Computational Load Entity concept into two registrations, Computational Load Owner and Computational Load Operator, and raised the thresholds to 50 MW and 100 kV. Ten questions that help leaders map who is responsible for the work and who is accountable for the outcome, before registration positions harden.
Overview
NERC's August 19, 2026 posting replaced the single Computational Load Entity concept with two distinct registrations, Computational Load Owner and Computational Load Operator. It raised the applicable thresholds to 50 MW and 100 kV, and it moved the test for determining who is in scope into a new Site definition.
For the full breakdown of what changed and why it matters, see The Computational Load Entity Just Became Two. This piece picks up where that one ends, at the question of who inside your organization owns what.
These changes make accountability mapping the first step in planning. Ownership, operation, curtailment authority, telemetry, AI workload management, evidence production, budget authority, and risk acceptance may sit with different organizations, or with different business units under the same roof.
Responsibility and accountability are not interchangeable. Individual contributors are usually responsible for executing the work. Leaders are accountable for the outcome. Compliance failures tend to live in the space between the two, where the person doing the work has no authority to change it and the person with the authority does not know it needs changing.
The work in front of most affected organizations right now is not technical. It is getting the right people into one conversation while registration positions are still forming.
Who Belongs in That Conversation
In practice, that means the executive who can commit capital, the people who actually operate the electrical and computational infrastructure, whoever can execute a curtailment at 2 a.m., the team that owns and validates telemetry, the tenant or business unit that controls AI workload placement, legal and compliance, and the risk owner who will ultimately sign.
OT security belongs in that room from the first meeting, rather than being handed a decision after it is made. The control systems, network segmentation, and remote access paths sitting underneath curtailment and telemetry are what determine whether those commitments can actually be honored. An organization that maps accountability without OT security at the table will document a curtailment capability it cannot securely execute, and a telemetry feed it cannot defend.
Clear accountability boundaries prevent gaps in risk coverage, support defensible capital allocation, and keep a business unit from discovering an obligation it assumed someone else owned.
The following questions can help organizations begin that discussion and identify the areas that require formal accountability mapping. Each question has two answers, and they are frequently different people.
The Ten Questions
Below is a modified RACI table you can complete for your own organization:
| # | Question | Responsible (executes the work) | Accountable (owns the outcome) | Evidence that proves it |
|---|---|---|---|---|
| 1 | Who owns the facility, and which assets fall inside the Site as NERC now defines it? | |||
| 2 | Who is registered, or expected to register, as Computational Load Owner, and who as Computational Load Operator? | |||
| 3 | Who operates the electrical, computational, and supporting infrastructure? | |||
| 4 | Who has the authority to order load curtailment or disconnection, and who physically executes it? | |||
| 5 | Who receives, acknowledges, and responds to reliability directives at 2 a.m. on a holiday weekend? | |||
| 6 | Who owns, validates, and provides the required telemetry and operational data? | |||
| 7 | Who manages AI workloads, automated workload shifting, and other changes that could materially affect load behavior? | |||
| 8 | Who can produce and retain evidence for NERC, the Regional Entity, or another applicable authority? | |||
| 9 | Who owns the budget for compliance, cybersecurity, telemetry, and operational readiness? | |||
| 10 | Who ultimately owns the reliability, compliance, cybersecurity, operational, and financial risk? |
If the two middle columns hold different names, or if multiple organizations appear across them, the accountability boundary deserves closer examination.
A name in a contract or a registration record may not identify who can actually make the decision, execute the curtailment, access the telemetry, manage the AI workloads, or produce the evidence when it is requested. Those gaps tend to surface during an event rather than before one.
Webinar Recording Coming Soon
Keirsten Brager and NERC O&P expert Earl Shockley joined us on September 3 for a practitioner-level webinar on what FERC's computational load order settled, what remains unresolved, and what affected organizations should do during the next 90 days. A recording will be posted here once available.
The session took place the same day the ballot-pool join window closed.
Recording: Watch on our YouTube channel here.
Key Dates
| Date | What closes or opens |
|---|---|
| August 19 to September 3, 2026 | Project 2026-02 ballot-pool join window |
| September 3, 2026 | This webinar |
| September 9 to 18, 2026 | Initial ballot and non-binding poll |
| September 18, 2026 | Comment deadline on the ROP registry criteria |
Organizations that need to move from discussion to documented accountability should put these ten questions into a written RACI and test it against an actual curtailment or evidence-production scenario, before an event forces the gaps into view.
The clearest sign a boundary is unsettled is disagreement, not silence. If two people in the room give different answers to the same question, that gap is where the mapping work should start, while registration positions under Project 2026-02 are still forming rather than after the standards and enforcement follow.
This piece follows The Computational Load Entity Just Became Two, the opening piece in this series on the August registration changes. Later installments will go deeper on the standards that attach to these registrations as Project 2026-02 moves through its ballot process this fall.
Sources and Further Reading
NERC Rules of Procedure: Appendix 2, 5A, and 5B revisions, Consideration of Comments
Project 2026-02 Computational Loads: posted drafts, comment form, ballot pool
FERC order, Docket No. RD26-7-000, 196 FERC ¶ 61,031, July 16, 2026
August 13, 2026 industry CEO letter from Jim Robb
PJM July 22 load-transfer event, Operating Committee presentation, August 6, 2026, and PJM's summary of the Operating Committee review
Large Loads Action Plan: August 13, 2026 industry CEO letter, Level 3 Alert materials
Large Loads FAQs and Checklist for Computational Load Entities: dates, standard numbers, ballot enrollment
NERC Standards, Compliance, and Enforcement Bulletin, August 24, 2026: ballot-pool join window (August 19 to September 3), initial ballot and non-binding poll (September 9 to 18), and ROP registry-criteria comment deadline (September 18)
NERC Rules of Procedure, Appendix 3D: Registered Ballot Body Segment definitions, including Segment 7 (Large Electricity End Users)
