New rules will soon change how electricity distributors manage connection queues, and developers will need to keep their projects moving to hold their place. We explain what is changing, how milestones will work, and what it means for developers and distributors.

Background

From 1 December 2026, new rules will change how electricity distributors prioritise and manage applications to connect distributed generation to their networks. These changes aim to keep viable projects moving and prevent stalled projects from tying up network capacity and distributor resources. Broadly the same rules will apply to large load connections from 1 June 2027.

Electricity Networks Aotearoa’s queueing and management policy for distributors (the Q&M Policy)[1] will take effect alongside amendments to Part 6 of the Electricity Industry Participation Code (Code). Together, they introduce a consistent framework for managing connection applications. Developers of large projects will need to meet milestone deadlines to keep their projects’ places in the distributor’s connection queue.

A new approach to prioritising projects

The Q&M Policy applies to distributed generation projects with a total maximum export power above 10 kW. Large distributed generation projects (300 kW or more) face additional milestone and information publication requirements. The policy sets a consistent approach to queue positions, application timeframes and visibility of the connection pipeline.

When a distributor receives a completed initial application, it must assign the application a place in its connection queue.

A project’s priority depends first on its stage of development. Projects progress through five stages: initial, interim, final, construction (negotiation) and construction (delivery). Projects further along in the connection process have higher priority. If projects are at the same stage, the project that reached that stage first has priority. Faster-moving projects can therefore overtake slower ones.

Priority positions affect how the distributor allocates resources and decides network access terms, making progress important where projects compete for constrained capacity. Distributors may still allocate resources to lower priority projects over higher priority projects where it is practical and efficient to do so.

The Q&M Policy says applications submitted before the changes take effect may be managed under either the new framework or the distributor's previous arrangements. However, the Code amendment does not say anything about how in-flight projects are to be treated under the new rules, including where they should sit in the connection queue versus new applications. We think this is a material omission. For an in-flight project, existing agreements between the distributor and applicant may have a bearing on if or how the project is brought into the new framework (for example, there may be a connection contract with specific timing requirements in it).

Milestones – keeping large projects moving

The new rules introduce project milestones for large distributed generation projects. Missing a milestone could lead to a project being de-prioritised, delayed or dropped from the connection queue.

After a large project receives final approval, the distributor and applicant must act reasonably to agree the project’s milestones, including the criteria and timeframe for each. They may record these details in a connection contract or a separate milestone agreement. We expect milestones will usually be recorded in the agreement under which the necessary network upgrades are delivered.

Clause 26 of the Q&M Policy sets out a list of default project milestones,[2]  including:

  • Design: finalising the design of the project;

  • Supply and construction contracts: entering into supply and construction arrangements to complete the project;

  • Property rights: securing property rights for the project;

  • Regulatory approvals: securing resource consents or Overseas Investment Office approval;

  • Financing: securing project financing; and

  • Commissioning: commissioning the project. The Code sets a default connection period of two years from the date the applicant’s final application to connect was approved.

The parties may also agree interim milestones, such as a date by which a resource consent application must be lodged. A milestone not listed in clause 26 cannot be included unless it is necessary for an efficient and equitable wider connection process.

When agreeing which milestones apply, the parties must consider the project’s nature and duration, how the milestones interact with other agreements or milestones, and the effects on other projects, especially those competing for the same resources. The distributor must also consider the applicant’s conduct earlier in the connection process and its track record in developing other projects.

What if a project falls behind?

Missing a milestone does not automatically de-prioritise a project. If a milestone is missed or likely to be missed, the parties can renegotiate its timeframe or criteria. However, the applicant may have to accept a lower priority position or changes to its network access terms.

Distributors must act reasonably when deciding whether to amend a milestone or lapse a project’s final approval. Relevant considerations include:

  • why the milestone was, or is likely to be, missed;

  • whether the applicant has satisfied its other milestones;

  • how the amendment could affect other projects’ access to distributor resources or network access terms; and

  • whether the applicant’s behaviour indicates a lack of intent to progress the project.

If negotiations over a missed milestone fail, or the applicant does not engage in them, the distributor may lapse the project’s final approval and remove the project from the connection pipeline. The applicant can submit a new initial application for the project, but will start again at the back of the queue.

What does this mean for developers and distributors?

For developers, the message is clear: entering the connection pipeline is only the first step; staying there requires continued progress.

Developers of large projects should agree milestone dates carefully, particularly where regulatory approvals or property, financing or supply arrangements depend on third parties. If delays are likely, early engagement with the distributor is key to protecting a project’s priority and network access terms.

For projects ready to progress, however, the changes should be welcome. This new regime can improve access to capacity and distributor resources tied up by stalled projects.

As well as agreeing the milestones and milestone dates, we recommend distributors reflect the consequences of missing a milestone in the connection contract or milestone agreement. Recording the consequences specifically, and the distributor’s tolerance for milestone dates being missed, will help avoid disputes later on.

Our team will continue to work with Electricity Networks Aotearoa as part of an ongoing contribution to the industry. We will work with the Future Networks Forum to update the large load and distributed generation connection contract templates released to the market earlier this year, to reflect the Q&M Policy.

Get in touch

If you would like to discuss how the new connection rules could affect an existing or proposed project, please contact one of our experts.

Special thanks to Milou Lodewijks and Liam Brennan for their assistance with this article. 


[1] 2026-7-connection-queueing-and-management-policy.pdf. The full name of the document is “queueing and management policy and clock stop/start mechanism for distributors”. The clock stop/start mechanism part relates to the timeframes within which certain actions in the connection application process must be completed under Part 6 of the Code.

[2] These are milestones for the applicant’s project, not for any associated distributor project to upgrade its network to enable the connection.

Contacts

Related Articles