Connect-and-Manage Interconnection: What Solar EPCs Should Prepare For

Connect-and-manage interconnection could change what solar EPCs track after an interconnection application is accepted.

The basic idea is simple: instead of waiting for every network upgrade needed to guarantee unrestricted output in every grid condition, a qualifying project could connect sooner if it accepts operating limits or curtailment when the grid is constrained.

That sounds like an interconnection-policy change. Operationally, it is much bigger. A project may no longer move from application to approval to PTO with one clean final state. The EPC may need to track the exact operating conditions attached to the interconnection agreement, curtailment rights, capacity limits, later upgrades, commissioning requirements, and whether the project eventually transitions to a different service level.

The proposal is not law today. But the direction matters enough that solar EPCs should understand what a connect-and-manage model would change in the workflow before it becomes another spreadsheet problem.

What is connect-and-manage interconnection?

In July 2026, U.S. Senator Martin Heinrich introduced the Grid Connection and Congestion Management Act. The proposal would require federally regulated regional grid operators to offer a faster interconnection pathway modeled on the connect-and-manage approach used in ERCOT. A participating generator could accept curtailment or other operating limits during constrained grid conditions in exchange for a more limited study scope and a potentially faster path to interconnection.

Under the proposal, the service would focus studies on what is necessary to connect a facility reliably while allowing operational measures such as curtailment, redispatch, operating limits, or remedial action schemes to manage constraints that otherwise might trigger major network upgrades. The project would not receive an unlimited right to inject power whenever it wants. It would receive a defined interconnection service with conditions that become part of the operating model.

Why is this being proposed now?

The U.S. interconnection backlog is still large even after queue volumes fell in 2025. Lawrence Berkeley National Laboratory's Queued Up 2026 analysis reports more than 2,060 GW of generation and storage actively seeking grid connection at the end of 2025. That included about 1,312 GW of generation and 749 GW of storage across roughly 8,200 active projects.

The bigger operational warning is time. Berkeley Lab reports that the median duration from interconnection request to commercial operation exceeded five years for projects built in 2025 in regions with available data. It also found that only 13% of capacity entering queues from 2000 through 2020 had reached commercial operation by the end of 2025. A large queue does not only slow developers. It creates years of changing assumptions, studies, deposits, equipment decisions, schedule revisions, financing dependencies, and project records that have to stay accurate.

The Senate committee promoting the bill says average project interconnection costs have nearly doubled since 2017, from $225 per kW to $422 per kW. Whether this particular bill becomes law or changes during the legislative process, the policy pressure is clear: grid operators are being pushed to find ways to connect ready generation faster and use operational flexibility instead of treating every constraint as a reason to wait for a full network buildout.

What changes for an EPC if interconnection becomes conditional?

Traditional project tracking often reduces interconnection to a status field: application submitted, study in progress, agreement received, construction complete, PTO granted. That is already too simple for many C&I and utility-scale projects. Under a flexible interconnection model, it becomes even less useful because two projects can both be "approved" while carrying very different operating rights and commercial risk.

One project may have full network service after required upgrades. Another may be permitted to operate now but subject to a defined export cap. A third may connect under curtailment conditions and later transition to another service. A fourth may have specific remedial-action requirements or commissioning dependencies. If all four show the same green "interconnection approved" badge, operations, finance, asset management, and leadership can make the wrong assumptions.

What should solar EPCs track under connect and manage?

The right answer is not to create another interconnection spreadsheet. The project record should separate milestone status from operating conditions. At minimum, an EPC evaluating this kind of service should be able to answer the following questions without reopening the agreement every time.

1. What interconnection service did the project actually receive?

Record the service type, grid operator, facility identifier, requested capacity, approved capacity, effective date, and the specific pathway used. The project team should be able to distinguish a standard network service from a flexible or energy-only arrangement at a glance. This matters when leadership compares pipeline capacity, when finance models output, and when operations plans commissioning.

2. What operating limits came with approval?

Do not bury operating limits in a signed PDF. Track the allowed injection level, export limit, curtailment provisions, seasonal or contingency conditions, telemetry obligations, control requirements, and any trigger that changes what the project may deliver. The agreement remains the legal source, but the operational system should surface the parts people need to run the project correctly.

3. Who receives and acts on curtailment instructions?

A conditional service is only useful if the operating process is clear. The EPC or asset owner needs a named responsible party, notification channel, escalation path, response requirement, and evidence that a curtailment instruction was received and acted on. If the project will transfer to an owner after COD, that responsibility must survive the handoff. A contact buried in a commissioning email is not a control system.

4. Which milestones are still open after physical construction?

Connect-and-manage can make "mechanically complete" and "commercially ready" even less interchangeable. A project may finish civil and electrical construction while interconnection controls, telemetry, protection settings, witness testing, operating agreements, meter configuration, or final utility acceptance remain open. EPC schedules need those dependencies as real milestones, not notes attached to a task.

5. Is there a later upgrade or transition path?

A flexible service may be the first operating state rather than the final one. Track whether the agreement allows transition to another service, what studies or network upgrades remain, who pays, what deposits or approvals are due, and which dates matter. Otherwise a project can reach COD while a commercially important second phase disappears from the team's normal project controls.

How would this affect project status and handoffs?

The biggest Solar1 lesson is that status must describe a decision-ready reality, not just the last completed task. Our guide to solar project status tracking makes the same point at the company level. A project can be technically "green" while carrying a condition that changes schedule, output, cash flow, or owner expectations.

For interconnection, a clean weekly review might show application status, study stage, agreement status, construction readiness, commissioning status, allowed operating capacity, open utility dependencies, next external action, owner, due date, and days blocked. If curtailment or operating limits are material, those should appear as permanent project attributes rather than temporary comments.

The same applies to handoffs. A project moving from development or engineering into construction cannot hand off only a drawing set and a utility approval email. The receiving team needs the current commercial and technical conditions attached to the grid connection. That is the broader problem covered in Solar Project Handoffs: Sales to Design to Permit to Install.

What changes for finance and project economics?

Faster interconnection is not automatically better economics. A project that reaches the grid earlier may earn revenue sooner, but curtailment can reduce output during constrained periods. The commercial case therefore depends on the exact operating rights, expected congestion, contract structure, financing assumptions, and whether the project later transitions to broader service.

For an EPC, this means interconnection data should not stop at the project manager. The finance and commercial teams may need the approved injection limit, forecasted curtailment assumption, network-upgrade obligations, deposit schedule, and milestone dates used in the project model. When those assumptions change, the cost and revenue view should change with them. An agreement revision should not update operations while finance continues modeling the original service.

This is especially important when milestone billing or customer payments depend on interconnection events. If a contract says a payment unlocks at interconnection approval, energization, PTO, or COD, the business system has to distinguish those events precisely. A conditional approval that still requires commissioning work may not mean the same thing as unrestricted commercial operation.

Does this matter to residential solar installers?

Directly, this federal proposal is aimed at transmission-connected generating facilities handled by regional grid operators. It is not a replacement for the distribution-level interconnection process used by a typical residential rooftop installer. A residential company should not read this bill and assume its local utility PTO process is about to change.

The broader lesson still matters. Interconnection is moving toward more differentiated service, more automation, more flexible operating limits, and more structured data. Distribution utilities are also experimenting with flexible interconnection, export controls, storage operating modes, and hosting-capacity tools. The operational pattern is similar: the project record needs to capture not only whether a utility said yes, but what exactly the utility approved.

What should EPC leaders change now?

You do not need to redesign your entire interconnection process around a bill that has not passed. But you can make one useful change now: stop treating interconnection as a single status field. Audit the records you already manage and separate milestones, obligations, technical conditions, commercial conditions, responsible parties, and documents.

Take one complex project with an executed interconnection agreement and ask five people to explain the approved capacity, remaining utility work, commissioning requirements, network-upgrade responsibility, and next external deadline. If the answers come from different spreadsheets, email threads, shared drives, and individual memory, the problem already exists without connect-and-manage.

A complete solar ERP should keep those records tied to the same project that holds design revisions, procurement, field progress, milestones, invoices, and final service history. That broader operating model is covered in our ERP for Solar EPC Companies buyer's guide. Solar1 is being built toward that connected model, but product availability varies by capability and should be confirmed during evaluation.

A practical connect-and-manage tracking model

For teams building or evaluating an interconnection workflow, think in six layers. First, the project identity: utility or grid operator, queue position, facility ID, requested capacity, and project contacts. Second, the process: application, studies, deposits, agreement, construction, commissioning, energization, and COD. Third, the operating conditions: service type, export or injection limits, curtailment provisions, telemetry, controls, and protection requirements.

Fourth, the obligations: who must do what, by when, with what evidence. Fifth, the commercial layer: network-upgrade cost, deposits, change orders, milestone billing, forecast assumptions, and exposure to delay or curtailment. Sixth, the future path: remaining upgrades, transition options, renewal or amendment dates, and post-COD ownership of compliance. Those six layers turn an interconnection file into an operating record.

What could change if the bill passes?

The Grid Connection and Congestion Management Act would still need to move through Congress and become law before its requirements take effect. The proposal also gives FERC and regional grid operators important implementation work. Timelines, tariff language, study procedures, technical requirements, and the practical economics of the service would matter as much as the headline idea.

If implemented effectively, the biggest change could be a shift from waiting for a grid that is fully upgraded before connection toward connecting sooner under explicitly managed constraints. For developers and EPCs, that creates a new tradeoff: earlier energization and potentially lower upfront network requirements versus more operational complexity and exposure to curtailment.

That tradeoff is exactly why software and operating discipline matter. The more flexible the interconnection service becomes, the less useful a binary approved/not-approved field becomes. Flexibility requires better records, clearer ownership, and a stronger connection between the interconnection team and the rest of the project business.

The Solar1 takeaway

The most interesting part of connect-and-manage is not that one queue might move faster. It is that interconnection could become a more dynamic operating agreement instead of a one-time gate before construction and COD. That makes interconnection data more valuable across project management, finance, commissioning, customer commitments, and long-term asset operations.

Solar1 is being built as a solar-specific ERP where interconnection is part of the same connected project record as the rest of the business. The goal is not to replace grid studies, engineering judgment, utility portals, or regulatory expertise. It is to make sure the facts those processes create do not disappear into disconnected tools after the team needs them.

If your EPC is already managing complex interconnection conditions across spreadsheets, shared drives, utility portals, and weekly status calls, connect-and-manage is a useful warning about where the workflow is heading: more flexibility, but also more conditions to track correctly.