What Multi-Region Entities Need to Know About Coordinated Oversight in 2026
By Patrick Miller
NERC's Coordinated Oversight Program lets multi-region entities consolidate compliance monitoring under one Lead Regional Entity, eliminating duplicate audits across six footprints. New for 2026: Category 2 GO/GOP eligibility opens May 15, annual asset verification becomes formal, periodic group reviews go standard. Breakdown of qualifications, modification paths, and audit prep questions.
Overview
NERC's tenth episode of Currently Compliant walks through the Multi-Region Registered Entity (MRRE) Coordinated Oversight Program. The headline points for entities operating across two or more regional footprints: the program eliminates duplicate compliance monitoring activities, IBR-driven Category 2 GO/GOP registrations become eligible May 15, 2026, and annual asset verification is now a formal expectation. Below: who the program serves, what changed recently, what's changing next year, and the audit prep questions any candidate entity should be asking.
What the Program Does
A registered entity operating as a Transmission Operator across all six regional footprints would otherwise face six separate compliance audits over a three-year cycle. Under coordinated oversight, that becomes one audit, led by a designated Lead Regional Entity (LRE) with support from Affected Regional Entities (AREs). The same logic extends to self-reports, certifications, inherent risk assessments, and internal controls evaluations.
The program does not eliminate compliance obligations. It eliminates redundant administration of those obligations.
| Role | Responsibility |
|---|---|
| Lead Regional Entity (LRE) | Coordinates all CMEP activities for the participating entity |
| Affected Regional Entity (ARE) | Supports the LRE; retains visibility into entity activities in its region |
| NERC Coordinator | Reviews applications, manages program documentation, processes changes |
| Coordinated Oversight Task Force (COTF) | Monthly review of applications and modification requests |
| Reliability Performance Monitoring Group (RPMG) | Final approval authority alongside ERO Enterprise |
Who Qualifies
The entry bar has four components:
Registered in two or more regional jurisdictions with one or more NERC compliance registry IDs.
United States operations only. No assets outside the U.S. are accepted.
Verified Primary Compliance Contact (PCC) and Primary Compliance Officer (PCO), with a single point of contact designated for the entire group.
Common compliance program: shared policies, procedures, and templates across all participating registrations.
The fourth requirement is the one most likely to cause friction. Entities with operationally distinct subsidiaries, recent acquisitions, or independent compliance teams across regions may need to align their programs before they can apply, not after.
What Changed Recently
NERC redesigned its website and consolidated coordinated oversight materials under a single search path. The application and modification forms have been formalized to reduce back-and-forth requests for information. The catalog of allowable modifications also expanded.
| Modification Type | Forms Required | Approval Path |
|---|---|---|
| Add NCR to group | Modification request and asset verification | Full COTF and RPMG review |
| Remove or terminate NCR | Modification request only | Processed without approval; affected parties notified |
| Group name change | Modification request and updated asset verification | Full COTF and RPMG review |
| Consolidate groups | Two modification requests plus updated asset verification | Full COTF and RPMG review |
| Change LRE | Modification request, justification, updated asset verification | Full COTF and RPMG review |
Open enforcement actions and pending registration changes can extend processing timelines. Plan accordingly.
What's Coming in 2026
Three changes worth tracking.
Periodic group reviews. COTF will now formally review existing coordinated oversight groups during normal compliance oversight activities. The stated goals: identify efficiency gains and confirm that current groups still meet program criteria. The process was happening informally; it is now harmonized across the ERO Enterprise.
Annual asset confirmation. Existing groups will receive an annual request to either confirm no asset changes occurred or submit an updated asset verification form. This creates a recurring administrative checkpoint and gives COTF a clearer trigger for reassessing LRE assignments when footprints shift.
Category 2 GO/GOP eligibility. With IBR registration ramping up, COTF is now accepting applications that include generator owner / generator operator Category 2 registrations. Approved applications begin coordinated oversight on May 15, 2026, with CORES processing starting May 16, 2026. NERC is encouraging early applications to manage the expected volume.
What This Means by Stakeholder
Multi-region utilities. The efficiency case has not changed, but the administrative cost of staying in the program is rising slightly with annual asset confirmation. The trade still favors participation for any entity registered in three or more regions.
IBR developers and operators. If you anticipate Category 2 GO/GOP registrations across multiple regions, applying before May 15, 2026 is a reasonable hedge against backlog. The program will not process approvals in CORES until that date, but pre-approval positions you to begin coordinated oversight immediately.
Compliance teams at recently acquired or recently merged entities. The common compliance program requirement is the gating issue. Inventory your policies, procedures, and templates across acquired registrations before drafting an application. Misalignment found during COTF review delays everything.
Consultants and advisors. The program is now better documented, the modification paths are formalized, and the application package is more predictable. That makes it easier to advise clients through entry. It also raises expectations for documentation quality.
Audit Prep Questions
Before applying, or before your next periodic review:
Are PCC and PCO contacts current in CORES, and is a single group point of contact designated?
Do your policies, procedures, and templates demonstrably apply across all registrations in the proposed or existing group?
Has your asset footprint changed since your last verification? Are control center locations, generation assets, transmission assets, and tie points current?
Are there open enforcement actions that will affect modification timing?
For Category 2 GO/GOP candidates: is your pre-application package ready to submit ahead of the May 15, 2026 effective date?
Open Questions
Three questions the program documentation does not yet fully resolve.
How will COTF weight efficiency gains against reliability concerns when IBR-heavy Category 2 entities span regions with very different operational profiles?
As annual asset verification matures, what threshold triggers an LRE reassessment? Is it a quantitative change in footprint, or does it remain a judgment call?
With expansion to Category 2 GO/GOPs, will COTF workload grow faster than its capacity to process applications and modifications? Backlog risk is real.
The program is sound. The expansion to IBRs is overdue. The annual confirmation cycle is reasonable. The remaining question is execution capacity at the coordinator and task force level as registration volumes grow.
