A power delivery date moves when the work it rests on moves: when the grid's schedule for new service shifts, when an approval runs long on a public calendar, when something must be extended across land the project does not own, or when a change arrives after the construction schedule was set. The date is the sum of that work: power delivery, approvals, infrastructure and the construction that remains. A date offered without the work behind it is an assumption, not a schedule.
Energy.LLC develops sites for data center and energy operators, and a date from us names the work behind it, part by part; each part has its own reasons to move.
Power delivery moves on the grid's schedule.
Existing service is the power a property draws today, and a data center usually needs far more than that. The rest comes from the grid, through new or enlarged lines and equipment that the company operating the grid plans, orders and builds on its own schedule, and that schedule, not the project's, sets the date.
Large electrical equipment is ordered long before it is installed. The property's request waits behind other requests on the same part of the grid, and the scope of the work can grow once the facility's full power need is known. A line along the property or a substation beside it establishes none of this: neither the capacity a project needs nor the date it arrives.
Approvals move on public calendars.
A project needs the town's approval of the use and the building, and often state and federal permits for air, water, wetlands and road access. Each runs on a public calendar of filing, notice, hearing, decision and appeal, and none of those clocks belongs to the developer.
A use the rules do not allow needs the rules changed before any permit can be sought, a separate proceeding with its own calendar. Organized opposition lengthens the review, and a pause or rule change adopted while an application is pending can stop it. A town that sees a project early, while the project can still change, shapes it before it is filed, and that is how we work with the towns we work in.
Infrastructure moves on what has to be extended.
A data center draws on more than the grid: water and a way to return it, roads for construction traffic, and fiber that reaches the property and is in service. The ground is infrastructure too, from the soils that carry the structure to any contamination in its history.
Each is its own work with its own builder and often its own permit. The date moves when a service has to cross land the project does not own and an easement has to be negotiated, when a carrier will not put its fiber in service on the schedule, or when the ground needs more work than the record suggested.
Construction moves on its critical path.
What remains is the project itself: design, engineering, equipment ordered far in advance, construction and the operator's fit-out, scheduled against each other. That schedule has a critical path, the chain of tasks on which the date rests; a delay on the chain moves the date and a delay elsewhere does not.
What moves the chain is work that arrives late and changes a decision made earlier: an operator's requirement changed after design begins, an approval condition that alters the layout, equipment that misses its ship date. Some work can run side by side when planned together, the building and the grid's work for instance; some cannot start until something else has finished, and a schedule that treats dependent work as parallel carries a date that will move.
A promising parcel is not a date.
All of this is open on the day a parcel is considered. A parcel beside strong service, with an industrial history and a use the rules allow, is where the work begins; it is not a date on which it ends.
A date from Energy.LLC therefore carries the work it rests on: the service in place kept apart from the service planned, and each open piece of work tied to the decision that will settle it, so that when a decision moves you see the date move with it, not afterwards. We evaluate the path behind a site with our proprietary site intelligence before it reaches you, and the date is as firm as the work behind it and no firmer.
A credible date can show its work.
Whoever offers you a date, ask to see the work behind it: which service is in place and which is only planned; which approvals are granted and where the rest sit on their calendars; what has to be extended and across whose land; what the construction schedule assumes and what the date becomes if any of it slips; and who carries each piece, the developer, the operator, the company operating the grid, the town or someone else.
The form a site takes changes how much of that work falls to you, and our note on where to start sets out the difference across land with power, a building with power and a facility built to your plan. What we need from an operator to put a date against a site, the location, the capacity and the timing, is on our page for operators.
Questions this note answers
What does a power delivery date depend on?
It depends on the work still to do between the property and an operating facility: the service the grid has to build, the approvals the town and the agencies have to grant, the infrastructure that has to be extended, and the design and construction of the project itself. The date is as firm as the least certain of those, and a parcel tells you where that work starts, not when it ends.
Why do power delivery dates slip?
Most slips come from work whose schedule belongs to someone other than the developer: the grid's equipment and the requests ahead of the project's, a hearing calendar, an appeal, an easement, a state permit. The rest come from changes made after the schedule was set: a larger capacity request, a late design change, a condition attached to an approval. A date given with the work behind it shows which of these it is exposed to.
Does existing service on a property mean an earlier date?
Existing service is a starting point, not a date. Whether it carries what you need, and when, depends on the work between the service in place and the capacity you require, and that work is the grid's to plan and build. A standing building with service saves the time it takes to build the structure; the power date still rests on the grid's work.
What should I ask before planning on a delivery date?
Ask for the date's basis rather than the date itself: for each piece of work behind it, whether it is complete, under way or not begun, and whose decision settles it; then ask what the date becomes if the least certain piece runs long. A developer who has worked the date out can answer piece by piece. A developer who has assumed it will answer with the date again.
Can a developer promise a power delivery date?
Nobody can promise a date that rests on decisions it does not make, and much of a power delivery date does: the grid's schedule, a town's vote, an agency's permit. What a developer can do is show how far each piece of work has come, state the service in place apart from the service planned, and carry the work that is its own. A date offered that way can be planned around; a date offered as a promise cannot be checked.
Tell us your date, and we will show you what stands between a site and that date.
Send an inquiry