Deploy

Set minimum application requirements 

To keep speculative projects out of the queue, require site control, technical data, maturity evidence and a forfeitable deposit with each connection application.

About this measure

Define what an applicant must provide for a connection application to be accepted, so that queues are populated by projects that are real and sufficiently developed to be assessed. Where applications are cheap to lodge and carry no obligation, developers submit early and often, hold positions in several locations while deciding which project to build, and leave grid companies unable to distinguish firm projects from options. Minimum requirements typically combine evidence of site control such as a land agreement or option, technical data sufficient for the study to be performed, evidence of project maturity such as planning status or permit applications lodged, and a financial commitment through an application fee or deposit that is forfeited if the project does not progress. Requirements should be proportionate to the size and impact of the connection, with simplified expectations for small assets, and calibrated so that they exclude speculative applications without excluding smaller developers and community projects that are serious but less well capitalised. This is the preventive counterpart to the measure Remove non-viable projects from connection queues, which removes non-viable projects already in the queue, and it is particularly relevant for large loads, where a single developer may hold applications across several jurisdictions for one facility. 

Core recommendation for this measure

Deploy

4.2 Streamline connection management


Connection timelines are one of the main constraints on renewable deployment and electrification,…

Related recommendations

Deploy

3.1 Streamline permitting


Administrative and permitting procedures, not construction, tend to account for the majority of the…