Grid interconnection: test queue milestones and upgrade costs
A generation project in an interconnection queue is a request being evaluated, not an operating power plant. Its network-upgrade exposure can also depend on other projects in the study group. Research should preserve cluster membership and cost-study versions before treating an early estimate as a fixed development budget.
The deliverable is a project-by-upgrade matrix with a dated milestone ledger. This article concerns generation-side research involving US FERC-related interconnection processes, using official explainers read on October 25, 2026. It does not establish a particular transmission provider’s current tariff obligations or supply a legally required allocation formula.
Locate studies, restudies and allocation separately
FERC’s Order 2023-A explainer, updated January 30, 2025, describes readiness, site control, shared upgrades and compliance variations. It expressly presents an overview rather than a legal document. An actual project’s governing tariff, effective date and relevant approvals must be obtained separately.
FERC’s Order 2023 explainer, updated January 23, 2025, discusses cluster studies, restudies when a major project leaves, and allocation of network upgrades through a proportional-impact method. Those passages explain why membership and engineering results matter. They do not turn the simple capacity-proportional teaching example below into the FERC rule.
Keep study costs, network-upgrade costs, deposits and other development expenses separate. A study payment is not proof that construction is funded, and a deposit is not automatically an additional final upgrade cost. Identify the applicable line and treatment before combining amounts.
Rebuild the original cluster case
Assume three fictional generation requests: A at one hundred MW, B at two hundred and C at three hundred. Their initial study identifies a shared upgrade with an estimated cost of $60 million. For this example only, the parties allocate cost in proportion to those capacities.
Total request capacity is six hundred MW. A’s share is one-sixth, B’s one-third and C’s one-half. Allocated upgrade estimates are respectively $10 million, $20 million and $30 million. These are assumed analytical shares, not a claim about an actual tariff, substation allocation or electrical impact.
| Original member | Request MW | Assumed share | Upgrade estimate |
|---|---|---|---|
| A | 100 | 1/6 | $10 million |
| B | 200 | 1/3 | $20 million |
| C | 300 | 1/2 | $30 million |
| Total | 600 | 100% | $60 million |
The requests are not six hundred MW already available to the grid. The table contains no evidence of completed construction or commercial operation. Retain project IDs and study dates so later revisions are connected to the same request population.
Replay the cost matrix after a withdrawal
Assume C withdraws and a new engineering study, explicitly hypothetical, revises the needed shared upgrade to $45 million. A and B remain at one hundred and two hundred MW. Under the same invented capacity-based allocation, A receives one-third of the new cost, or $15 million, and B two-thirds, or $30 million.
Each remaining project’s estimate increases 50%, although total upgrade cost falls from sixty to forty-five million. The remaining projects’ old combined allocation was thirty million, not sixty. Comparing that thirty with the new forty-five exposes the reallocation that a simple deletion of C would miss.
| Remaining member | Old estimate | Revised estimate | Change |
|---|---|---|---|
| A | $10 million | $15 million | +$5 million |
| B | $20 million | $30 million | +$10 million |
| Combined | $30 million | $45 million | +$15 million |
Removing C’s thirty-million row from the original sixty would leave only thirty and understate the assumed new requirement by fifteen. Conversely, keeping the original sixty and reallocating it would ignore the new engineering estimate. Update both the cost to be allocated and the allocation basis.
Test a different engineering result
Suppose a separate restudy instead finds a $24 million shared upgrade necessary. The same illustrative capacity shares give A eight million and B sixteen million, each lower than its original estimate. A withdrawal therefore does not mechanically increase every remaining project’s cost.
The direction depends on the actual revised upgrade scope and applicable allocation. Read the new study rather than infer a fixed outcome from a withdrawal headline. Where the restudy is pending, show conditional costs and retain the old version as superseded or provisional, not as a guaranteed final amount.
Some upgrades may serve only a subset of the cluster or affect another system. Use an upgrade-by-project matrix, with a source for every applicable share. Do not spread every cost over every MW simply because the projects appeared in one queue export. The source explainers themselves distinguish allocation mechanisms and relevant systems.
Trace the evidence milestones
For each project, record request validation, applicable site-control and financial-readiness evidence, cluster and facilities studies, agreements, identified upgrades, construction and commercial operation. These are document categories to verify, not a universal schedule in which every project advances on the same dates.
Site control concerns the right to develop the project location; it does not prove network upgrades are complete. A signed interconnection agreement likewise is not proof that all required facilities are built or that the project is selling power. Obtain dated completion and operation evidence for that later claim.
Use the relevant transmission provider’s current documents and tariff to establish the actual process. The explainers’ publication dates and the research cutoff should remain visible. Do not assume every US project uses identical transition provisions or that a national reform announcement proves a particular queue record has already changed.
Reconcile deposits and project economics
If A’s revised upgrade estimate is fifteen million, a previously posted deposit cannot simply be added again or subtracted automatically. Determine whether it is security, a study payment or an amount credited to that upgrade under the applicable arrangement. With no matching treatment record, remaining cash requirements are unknown.
A cost estimate is also not proof of an unconditional invoice or a funded commitment. Keep estimate, assigned responsibility, security posted, amount paid and remaining contractual exposure separate. Any withdrawal penalty, refund or cost recovery needs the actual governing terms; this worksheet does not calculate legal consequences from the fictional allocation.
Map a project company to the issuer’s ownership and development role before forming a portfolio total. Gross request MW, equity interest and a developer’s marketed pipeline are different quantities. Multiple technologies or requests sharing a connection can also create overlap that must be resolved before adding MW or costs.
Apply the project verification sheet
| Field | Obtain | Check |
|---|---|---|
| Request | Provider ID, resource and MW basis | Proposed injection distinct from operating capacity |
| Cluster | Membership and study version | Withdrawals and additions preserved |
| Upgrade | Engineering scope and cost version | New total not inferred by deleting one member |
| Allocation | Applicable tariff and study schedules | Toy capacity shares not imposed as law |
| Funding | Deposits, security, invoices and payments | No double counting or unsupported credit |
| Milestone | Agreements, completion and operation records | Queue progress not relabelled commercial output |
When company slides and provider data conflict, compare IDs, dates, capacity definitions, study version and whether a field is requested, approved or achieved. Keep unresolved matching separate rather than select the larger MW total. A public queue with stale status does not justify inventing either completion or cancellation.
If a new allocation or upgrade schedule is unavailable, show the missing line and conditional sensitivity instead of a precise final budget. Update after membership changes, restudies, revised tariff applicability, agreements, cost notices or actual construction and operation. The conclusion should identify the current supported milestone and cost version, the dependencies that could change them and the evidence still needed before counting operating generation.
Reconcile upgrade scope before summing a portfolio
For a separate extension to the revised shared-cost case, assume the actual study also identifies a six-million-dollar upgrade assigned only to A and a four-million-dollar upgrade assigned only to B. If these are expressly additional to the shared forty-five, A’s total is twenty-one and B’s thirty-four, summing to fifty-five million.
If those dedicated items were already included in the forty-five-million scope, adding them again would be wrong. Preserve upgrade identifiers, total cost and assigned shares so a reader can distinguish an additional requirement from a differently presented component. A project-level headline with no scope reconciliation cannot settle that question.
Also retain withdrawal date, restudy issue date and company disclosure date. A later disclosure may still quote an older study. The latest publication is not necessarily the latest engineering version; match the underlying document before replacing the cost matrix.
FAQ
Does a withdrawal always reduce the remaining projects’ cost?
No. The revised engineering scope and allocation determine the effect; both directions are illustrated.
Is capacity-proportional allocation the legal rule demonstrated here?
No. It is an explicit teaching assumption and must not replace the applicable tariff and study.