How to read a queue position, what can still go wrong after it looks secure, and why a place in the queue is not a date on a calendar.
An operator tells you a site is secured because it holds a queue position, and the number sounds definite: a place, a study phase, sometimes even a projected date. That is not the same as a signed interconnection agreement, and the gap between a queue position and power flowing is exactly where a hosting deployment can slip. A position needs to be understood on its own terms before it gets folded into an offer.
What a queue position is
A request to connect new load or generation to the grid usually enters a queue and then moves through a sequence of technical studies rather than a single approval step. Our piece on grid connection steps and lead times walks through those stages and how they differ between grid operators. A queue position is your place in that sequence: a record that the request has been filed and accepted for study, and a marker of how far it has travelled, with each study producing findings that the next one builds on.
What a position tells you, and what it does not
A queue position tells you that a request has been filed and is somewhere in the sequence. It does not, on its own, tell you that the connection is funded, that the required upgrades have been ordered, or that a date has been fixed. Ask plainly which stage the project has cleared, since an early-stage position and a late-stage position carry very different odds of turning into energised power on a useful timeline. A project can hold a position for a meaningful stretch of time while nothing changes, and a position that looks stable on paper can still depend on later steps that have not started.
Costs that can arise during the process
Moving a project through the study stages can carry its own costs, separate from the eventual cost of building the connection itself. Some stages require a study deposit or fee to proceed. A later stage can identify network upgrades that the connecting project is expected to fund in whole or in part, and that cost allocation is sometimes only known once the relevant study is complete. That is not unusual, but it means a queue position with an unresolved cost allocation attached is a different commercial proposition from one where the costs are already settled and paid. It also helps to know whether an unresolved cost allocation is shared among several projects in the same part of the network, since a bill split several ways can change size once one of those projects withdraws. Ask whether the studies completed so far have identified any required upgrades, and whether the cost of those upgrades has been assigned and accepted.
Why positions shift
Queue positions are not static once granted. A project ahead of yours in the queue can withdraw, which can move surrounding projects up, but it can also trigger a restudy if the withdrawal changes the assumptions the later stages were built on. A change to a nearby project's size or timing can do the same. Some queues process requests in batches or clusters rather than strictly one at a time, which means the fate of your position can depend on projects you have no connection to and no visibility into. A queue can also be reordered when the operator running it changes its own rules for how projects are sequenced, which is a separate risk from anything happening on your own connection. A queue position is not meaningless for that, but a position secured at one point in time should be reconfirmed rather than treated as fixed once granted.
What to ask before you rely on a queue position
Before an offer built on a queue position gets treated as a deployment date, ask the operator to show rather than describe. Ask for the study documents or correspondence from the grid operator, not a summary. Ask which stage has been cleared, what the next stage requires, and whether there is a scheduled date for it. Ask whether any identified network upgrades have been ordered, since a queue position paired with a transformer that has not yet been purchased carries the same lead-time risk covered in our piece on switchgear and transformer lead times. And ask the more basic question underneath all of this: is the capacity you are being offered energised, or is it a position in a process that has not yet produced power? That distinction is the same one set out in our piece on energised versus available capacity, and it applies just as directly to a site still moving through interconnection as it does to one that is already built.
A queue position is a real asset, and a strong one says something true about the project. What it is not, on its own, is a date you can plan a fleet delivery against. The way to close that gap is to ask for the documents behind the position rather than the position alone, and to keep asking as the project moves through each stage rather than only once at the start. Our operations page states our total capacity and the number of active projects, with power contracted and energised before hardware arrives.
