Congestion relief and the priority queue

The fast lane exists. Nobody can tell you if it works.

There is one part of the Dutch connection process where anyone can read the rules and nobody outside the network operators can measure the outcome.

It is the priority route. Congestion relievers, in the language of the code. A project that relieves the grid does not wait its turn. It is ranked on what it offers, and it can be placed ahead of projects that applied first. For storage and flexible demand, that makes the route commercially relevant.

Every condition for entering that route is published. The five criteria you are ranked on are published. What is not published, anywhere, is what happens after you get in. Not the time it saves. Not the MW it has moved. On 13 May 2026 the Ministry told parliament, in its own words, that the specific impact of the congestion reliever categorisation is not in view, and that network operators have not disclosed how much flexibility these contracts represent in MW.

So Dutch grid policy now contains a route that can shape project design, and a payoff that no one has quantified publicly. If your connection timeline assumes this route delivers, you are holding an assumption the state has never tested.

Signal #1 Your place in the queue is an engineering decision, not a date

The Dutch connection queue is commonly described as a waiting line. Inside it, two ranking systems run at once, and only one of them responds to anything you do.

Congestion relievers are ranked on efficiency: location relative to the constraint, power offered, start date, duration, and price in euros per MWh. Everyone in every other category is ranked by order of arrival. The categories sit in a fixed order above that: relievers, then safety, then essential public needs including housing, then the rest.

Price is one of five criteria, not the deciding one. This is a multi-criteria ranking, not an auction. And entry is conditional on two things: the operator must formally determine that you qualify, and a contract must be signed.

The decision this changes. Most connection timelines are modelled as waiting time, because for most applicants that is all a timeline is. For a project that may qualify as a congestion reliever, application date is no longer the only variable shaping its position. Queue position becomes a function of what you build, where you put it, and what you commit to. A team that treats its connection date purely as an input from the operator, rather than partly as an output of its own design, is ignoring the one part of queue position it may be able to influence.

Signal #2 A project can clear its first investment screen on the wrong location entirely

This is the finding with the sharpest commercial edge in this issue, and it is invisible on every map you are currently using.

The same MW of flexibility has materially different value against a specific constraint, depending on its electrical location. On the radial networks of the regional operators, congestion management translates almost one to one: location plays a limited role, and flexibility converts relatively directly into capacity. On TenneT's meshed transmission network, effectiveness depends heavily on location, and not all flexibility contributes equally to relieving a given constraint. That is the ministry's own finding.

The code closes the loop from the legal side. A congestion reliever must increase capacity without creating congestion elsewhere in that operator's system, or in another operator's system. Relief that moves a constraint rather than removing it does not qualify.

The decision this changes. A site can pass the capacity screen and fail on the only location that matters for congestion relief. The capacity map tells you where the grid is constrained. It does not tell you where your flexibility is worth anything, and on the meshed layer those are not the same place. Every site screen that ends at grid colour is answering a question about the network and treating it as an answer about the asset. Two different maps. Only one of them exists in public.

Signal #3 The bottleneck is qualification, not competition

Almost all the commercial work on this route happens before the ranking begins, and this is where projects can fail.

The conditions published by Liander, Stedin, Enexis and their joint platform are not a formality attached to a good project. They are a specification. A new customer must make the full requested capacity flexible; offering only the waiting list volume, as an existing customer might, is not enough. Flexibility must be deliverable for at least four consecutive hours. Thresholds are 1 MW on the regional network, 10 MW for a direct transmission connection. Every network operator affected must approve, and status follows actual integration into the congestion management solution, not the application.

The decision this changes. A flexibility offer bolted onto an existing application and a project engineered around one are not variations of the same thing. The conditions know the difference, and they test for it at the point where reversal is most expensive. This is a design decision, taken at the start of development, disguised as a paperwork decision, taken at the end of it. Where more than one operator is affected, every operator becomes a separate approval gate.

Signal #4 The evidence breaks exactly where the money decisions begin

Dutch policy now assumes this route accelerates projects. Every variable an investment case needs in order to test that assumption is missing from the public record.

What an investment case needs	Public status
Time saved by priority	Not measured. The impact of the categorisation is not in view.
MW accelerated through the route	Not disclosed. Operators have not shared the flexibility volume behind these contracts.
Cost of the commitment you sign	Not benchmarked. Capacity steering contracts are too new to appear in the figures, and redispatch bid obligation contracts have been concluded only a handful of times nationwide.

Contracting is growing: the government's letter of 2 April 2026 reports a sharp increase in capacity under capacity limitation contracts for offtake. But that number covers those contracts in general. It does not isolate the priority route, and no public number does.

The decision this changes. A developer can read the rule, meet the specification, sign the contract, and still have no basis for telling an investment committee what priority is worth. An investor can price the assumption but cannot validate it against a public track record. The route is not speculative. Its value is. Anyone presenting congestion relief as a de-risking measure in a project timeline is presenting a number that does not exist.

Coda: the incentive is already bending behaviour

The ministry report describes a company that wants to expand its gas-fired CHP in order to qualify as a congestion reliever. In the report's own framing: against the decarbonisation trend, consuming more gas.

And where regular congestion management does not procure enough flexibility, an operator can issue a flextender. These are technology-neutral, and can, in the government's own words, result in gas-fired assets being deployed as a last resort.

Neither is the story. Both are evidence that a rule written to relieve the grid is producing incentives nobody set out to create, and that the market is moving on those incentives faster than the state is measuring them.

The lens

The Dutch connection debate asks the wrong question.

Everyone asks how long the queue is. The commercial question is whether your project can enter the one part of that queue that responds to engineering rather than to time, whether it sits on the layer where its flexibility actually relieves the constraint, and whether anyone can prove what the priority is worth once you hold it.

The first two are answerable today, from public sources, before you commit capital. The third is not answerable from the public record. And that is not a gap in this analysis. It is a gap in the public record, and it can sit directly underneath any Dutch project timeline that assigns value to this route.

Excluded from this analysis

Widely cited regional waiting list figures are omitted: their reference date and definition could not be established from a primary source. The Zeeland cases concern alternative transport rights, a different mechanism, and are not evidence for anything here. A reported tariff discount on time-bound transport rights remains excluded until it can be verified against the tariff code itself.

A number without a defined direction, grid layer, reference date and population does not appear in a Wattlas issue.

What we are watching for the next issue

Whether any network operator discloses the MW volume behind congestion relief contracts. That single disclosure would close the largest gap in this issue.
The first flextender awards, and whether they are met with flexibility or with generation.

Sources and confidence

Sources consulted

Systeemcode elektriciteit 2026 (BWBR0052336), consolidated text, valid from 8 May 2026.
“Flexibiliteit ontsluiten via congestiemanagement”, BlueTerra and Trinomics for the Ministry of Climate and Green Growth, 13 May 2026.
Parliamentary letter of 2 April 2026 on flexibility contracting.
Congestion reliever conditions published by Liander, Stedin and Enexis, and the joint operator platform partnersinenergie.nl.

Reference dates. Legal provisions: consolidated text valid from 8 May 2026. Ministry findings: 13 May 2026. Contracting trend: 2 April 2026. Operator conditions: 14 July 2026.

Confidence. High on the mechanism and the published conditions: read directly from the consolidated code and the operators' own pages. High on the measurement gap: the government states it in its own words. Medium on the transmission-layer siting implication: the report establishes that electrical location matters on the meshed network, but does not quantify by how much. TenneT's own congestion reliever page was unreachable at the time of writing, so the operator conditions rest on the three regional operators and the joint platform.

If your operational experience contradicts this reading, tell us. A documented correction is worth more to us than an unchallenged conclusion. [email protected]

Source list

Forward internally

Forward this internally if your team is asking:

Are we competing on merit or waiting by date, and do we qualify for the priority route at all?
Does our flexibility sit where it actually relieves the constraint, or only where the map is red?
What are we assuming this route saves us, and where did that number come from?

Request founding access

Grid Intelligence