Utility capacity goes to whoever is ready first
Available capacity is not held for the project with the best case. It is taken by the project that can execute the agreement, post the security, and accept the terms on the day.
In constrained networks, capacity becomes available in discrete events. A project ahead in the queue withdraws. A reinforcement completes. A cluster study is restructured and releases headroom. A utility opens an allocation window.
When that happens, the capacity is not awarded to the most deserving project. It goes to the party that can execute an agreement, provide the required security, and accept the offered terms within the window the utility allows — which is frequently short, and rarely negotiable.
What readiness actually consists of
The requirement is administrative, which is why it is underestimated. Four things have to exist before the window opens.
A contracting entity. A legal entity, with the site interest or an enforceable option, capable of entering a connection agreement. Projects held in a development vehicle that has not yet been substituted, or where site control rests on an unexercised option, cannot sign.
Internal authority to commit. A connection agreement carries liabilities — capacity charges, cancellation exposure, milestone obligations — that usually require approval above project level. Where that approval requires a committee that meets monthly, the project has a floor on its response time that the window will not accommodate.
The security instrument. Utilities typically require a bond, letter of credit, or cash deposit at agreement. Arranging one takes time inside the project's own organization and inside its bank, and it cannot be started when the offer arrives.
Accepted terms. The connection offer will arrive on the utility's standard terms, with milestone obligations, capacity charges, and cancellation provisions the project may find uncomfortable. Reviewing them for the first time under a deadline produces either a rushed acceptance or a lost allocation.
The project that loses an allocation almost never loses it on the merits. It loses it because approving the commitment took three weeks and the window was ten days.
Why the merits do not decide it
Utilities are not choosing between projects on economic or strategic grounds. They are administering a process with defined requirements, and the requirements are procedural.
That is a reasonable way for a regulated monopoly to behave, and it is the source of the misunderstanding. Project teams tend to assume that a large, well-financed, strategically significant load has standing. It does not, beyond what the process gives it. A smaller project with a signed entity, an approved mandate, and a bond facility in place outranks it entirely on the day.
The related trap: capacity held without readiness to build
The mirror image is also common and more expensive. A project secures an allocation early, accepts the milestone obligations in the connection agreement, and then fails to meet them because the design, the permits, or the funding are not in place.
Connection agreements generally contain milestones — dates by which the project must have achieved defined progress or committed defined works — and failure typically means the capacity is released and the security is drawn. The project has then paid for an allocation it did not use and returns to the back of the queue.
Holding capacity is therefore not free, and it is not a hedge. It is a commitment with dates in it, and it should be entered only where the project can meet those dates or has priced the consequence of not doing so.
Preparing for the window
The practical work is a short list, and it can be done long before any capacity is in prospect.
Establish the contracting entity and its site interest, and confirm it is the entity the utility will contract with. Obtain the internal mandate in advance — a delegated authority to accept a connection offer within defined parameters, so that acceptance does not require a fresh approval cycle. Arrange the security facility so it can be issued in days. Review the utility's standard terms now, identify what is acceptable, and establish in advance which provisions the project would need to negotiate and which it would accept as offered.
Then maintain contact with the utility so the window is known about, rather than learned about afterward. Allocations released to the market are visible; allocations released to whoever asked last week are not.
None of that changes the queue, and none of it accelerates a study. It changes what happens on the day capacity appears — which, in a constrained network, is where projects are actually separated.
