From application to energisation, with the stages that dominate the schedule and the ones that only look like they matter.
How long does a grid connection take? The answer usually comes back as a single number, as if the whole process were one step rather than a sequence of them. It is not. A connection moves through distinct stages, each with its own paperwork, its own cost trigger and its own capacity to stall, and the stage that decides your schedule is rarely the one that gets mentioned first. If you are building your own site rather than buying into one that is already energised, the order of these stages, and which of them you can influence, matters more than the headline estimate anyone gives you.
The stages in rough order
Most connection processes start with an initial application or enquiry that establishes what you want to connect and roughly where. That enquiry is usually followed by one or more technical studies: an early one that checks feasibility in broad terms, and a later one that looks in detail at what the surrounding network can absorb without upgrade, and what has to be built if it cannot. Once the studies settle on a scope of work, the next stage is usually a connection agreement or offer, which sets out the capacity, the cost allocation and a proposed timeline. After the agreement is accepted, the stage most people picture when they hear "grid connection" finally starts: physical construction of whatever the studies identified, followed by testing and, at the end, energisation. The exact names, the number of stages and what triggers each one differ by grid operator and by jurisdiction, so treat this as a rough shape to check against the specific process you are in, not a fixed universal sequence.
Which stage sets the schedule
The stage that gets the most attention is usually construction, because it is the one with visible activity: trenches, cabling, a substation taking shape. It is rarely the stage that decides your overall timeline. What usually sets the pace is what happens before construction ever starts: how long the technical studies take to complete, and whether they identify upgrades that require equipment with its own lead time, such as switchgear or a transformer. We went through that specific dependency in our piece on interconnection queue position, and the same logic applies here. A study that finishes quickly but identifies a major upgrade can leave you waiting longer than a study that takes more calendar time but finds nothing extra required. Ask which outcome you are looking at before assuming a fast study result means a fast connection.
What costs money, and when
Each stage tends to carry its own cost trigger, and your own planning should track them separately. Early-stage studies commonly require a deposit or a fee simply to be carried out, independent of whether the project ultimately proceeds. Once a later study identifies specific network upgrades, the connection agreement usually sets out how much of that upgrade cost falls to the connecting project, and that figure is often only known once the relevant study is complete, not before it starts. Construction itself is typically billed against the agreement rather than as a separate surprise, but the amount and the payment schedule should already be visible in the offer you accepted. Ask, stage by stage, what is being paid for and whether the amount is fixed or still subject to a study that has not yet concluded.
What you can accelerate, and what you cannot
Some parts of this process respond to pressure from your side, and some do not. You can generally control how quickly you supply the information a study requires, how fast you turn around a signature on an agreement once it is offered, and how promptly you pay a deposit or fee that is blocking the next stage from starting. What you typically cannot accelerate is the operator's own study queue, the manufacturing lead time on any equipment an upgrade requires, or another project's position in a shared process that yours depends on. Ask directly which category a given delay falls into, since pushing on a lead time that is genuinely fixed wastes effort that would be better spent making sure your own side of the paperwork is never the reason for a delay.
Evidence to keep, and how to judge whether a date is real
Each stage of a connection process tends to leave a document behind: a study report, a signed agreement, a construction schedule, a test or commissioning record. Ask for these as they are produced rather than relying on a verbal summary at the end. A date carries more weight when it comes attached to one of these documents than when it is offered as a general estimate, and more again if the document names the specific event the date depends on, such as delivery of a particular piece of equipment, rather than stating the date on its own. If a schedule can only be described in general terms with no document behind it, treat that as a sign the schedule itself has not been fixed yet, whatever the calendar says.
What to ask before you plan around a connection date
Before treating a projected energisation date as something you can commit a fleet delivery against, put a short set of direct questions. Which stage has been cleared, and is there a document that proves it? Have the studies identified any required upgrades, and has the cost of those upgrades been assigned and accepted rather than left open? Is any part of the remaining timeline dependent on equipment with its own lead time, and has that equipment been ordered? And finally, does the date you have been given trace back to a specific milestone in the process, or is it a general estimate offered without one behind it? A site worth building a schedule around should be able to answer each of these with a document, not a summary.
Paperwork does not replace looking at the site itself once construction is underway, since a stage that looks complete on paper is not the same as one you have confirmed in person. Our operations page sets out our standard of power contracted and energised before hardware arrives, alongside our total capacity and the number of active projects; hold any site to the same test before a connection date becomes part of your own plan.
