Where projects actually die: staging interconnection risk

Ask a developer what kills a project and you will hear about offtake, land, or permitting. In practice, a large share of projects die in the interconnection queue — quietly, at a study milestone, when the number finally comes back.

The queue is where an attractive site becomes either a project or a write-off. The mistake is treating interconnection as a permitting task rather than the central risk in development.

The queue is a financial process

Interconnection is not primarily an engineering problem. It is a process for allocating cost and position. The questions that matter are financial:

• What position do you actually hold? A queue number tells you how much capacity and how many studies sit ahead of you.
• What network upgrades are being assigned to you? The study result, not the site's apparent quality, determines whether the project is bankable.
• Who pays for upgrades triggered by others? Cluster studies can assign costs in ways that have little to do with the value your project creates.
• What is the cost and consequence of withdrawal? Deposits, milestones, and deadlines turn a slow queue into a cash-flow problem.

A site with excellent irradiance and a weak queue position is not a good project. It is an option that is probably out of the money.

Stage the spend against the risk

Because interconnection uncertainty resolves in stages, development spend should resolve in stages too. The disciplined approach is to attach a defined budget and a kill criterion to each phase, and to refuse to advance on optimism.

• Feasibility. Desktop siting, proximity to existing capacity, and an honest read of the queue. Cheap, fast, and often enough to say no.
• Queue entry and study. Fund the application and the studies, but tie the next dollar to study outcomes you have pre-defined.
• Upgrade resolution. When the assigned cost lands, decide against a threshold, not against sunk cost.
• Late stage. Only here — with a credible cost, a position, and a path — is it reasonable to commit to land and equipment.

The point is not to avoid risk. It is to make sure that when a project cannot be built economically, you learn it for a study fee instead of a land payment.

Design decisions move the risk

Interconnection risk is also a design variable. Hybrid and co-located configurations, storage paired with existing points of interconnection, and siting that respects available headroom can materially change what a study assigns to the project. These are worth evaluating early, because they change which queue you are standing in.

Most of the projects I see lose money not because the engineering failed, but because the interconnection outcome was never treated as the decision it is. Stage the risk, define the thresholds, and let the studies do the rejecting.