A data center can have a construction plan, an equipment schedule and a target opening date while still lacking a sufficiently supported date for the power its workload requires. When that happens, the utility timeline belongs at the center of the project plan.
The practical challenge is knowing what a power date actually means. Does it describe a planning target, completion of a transmission project, initial service to the property, or capacity ready to support the intended operating load? Those milestones should not be treated as interchangeable.
A public schedule is the beginning of diligence
Georgia Power provides a useful example. Its Hills Bridge-Speedway project in Henry and Clayton counties supports a data-center customer requiring new transmission infrastructure. The published scope includes three transmission lines and two substations. The utility lists Q4 2028 for project completion and explicitly identifies the schedule as tentative and subject to change. [1]
That is evidence of a substantial delivery dependency. It does not establish the customer's compute start date, the amount of earlier service available, or whether an alternative first phase is feasible. Those questions require project-specific evidence.
The broader lesson is to preserve the boundary between what a utility has published and what a developer has inferred. A target for one infrastructure scope cannot, by itself, establish readiness across the entire data center.
For the underlying case, see What Happens When Transmission Becomes the Critical Path for Your Data Center? The next question is how to turn that kind of market signal into a decision.
Read the milestone before relying on the date
Georgia Power describes transmission development as a phased process involving planning, permitting, construction and completion. It notes that planning can last several years and that schedules may change with permitting requirements or community considerations. [2]
For a project team, the useful response is to ask what has become more certain at each milestone. A route study, an equipment order and permission to energize answer different questions. Visible construction activity is progress; it is not sufficient evidence that every condition for the intended load has been satisfied.
Record each material milestone with its scope, responsible party, evidence date, unresolved dependencies and next confirmation point. This makes uncertainty explicit enough to manage. It also gives leadership a way to distinguish a changed delivery assumption from an unchanged headline date.
Define the load that must become productive
A power discussion becomes more useful when the required operating state is defined. Specify the workload, the initial IT load, supporting cooling and electrical demand, reliability requirements and acceptable operating restrictions. Keep the facility demand boundary separate from the power consumed by IT equipment.
Then ask the utility what service is available for that state, when, and under what conditions. An earlier service option may be valuable, but restrictions on interruption or load growth can change which workloads it can support. The project must evaluate those conditions against actual customer and operating requirements.
Power delivery also has to align with cooling, communications, controls, cybersecurity and commissioning. Advancing an electrical milestone creates useful value only when the remaining systems can support the same operating state.
Five questions that turn a signal into a decision
| Question | Evidence to request |
|---|---|
| What does the date cover? | The named infrastructure scope and the milestone being promised or targeted. |
| What load can operate at that point? | Site-specific service capacity, facility-versus-IT boundary, restrictions and reliability conditions. |
| What must happen first? | Outstanding studies, approvals, equipment, land access, construction and energization dependencies. |
| What changes if a dependency slips? | A revised compute start, procurement exposure and feasible alternatives, with accountable owners. |
| When must the plan be reconsidered? | A decision point before the next material commitment, with evidence required to proceed. |
This is a planning framework, not a utility approval sequence. Its purpose is to connect each external signal to the decision it can actually support.
Compare credible operating states
If the required power will arrive after the desired compute start, compare a full-service opening with a smaller initial phase and, where feasible, an alternative power configuration. Evaluate each against the same workload and reliability requirements.
A smaller initial phase may reduce the power requirement, but it can also limit the workloads or customer commitments the facility can serve. Supplementary generation can introduce fuel, equipment and operating dependencies. Storage can help manage power over a defined duration, but it requires an energy source and a credible recharge strategy.
Each option also needs a workable transition into the long-term configuration. An earlier start loses appeal if it introduces disproportionate cost, operational complexity or equipment that must soon be replaced. The existing article You Need 6 MW Next Summer. The Utility Can Deliver 2 MW. What Now? explores this comparison in more detail.
Include the people who live with the infrastructure
An alternative power plan should be assessed for its effects on neighbors as well as on the project schedule. Noise, emissions, water use, traffic and land impacts can change its acceptability and execution path. The specific obligations depend on the site and design.
Utilities also have responsibilities beyond a single customer. A credible project plan recognizes the wider system and community context rather than assuming every infrastructure decision can be optimized around one opening date.
Make the next commitment match the evidence
The key management decision is when to release the next material commitment. Before doing so, connect the required operating state to documented power milestones, identify the remaining dependencies and decide what evidence would justify continuing, phasing, changing the plan or waiting.
For example, a team approaching an equipment commitment should be able to explain which service milestone supports that commitment and what it will do if the milestone changes. This is a proposed planning practice, not a description of the Hills Bridge-Speedway customer.
Waiting for full utility service can be the sound choice. Phasing can also be sound when its complete operating state, obligations and transition are supportable. The comparison should be grounded in those conditions, not in a general preference for speed.
Executive conclusion
A power date becomes useful when it is tied to a defined load, a defined milestone and a documented set of dependencies. Until then, it remains an assumption in the data-center schedule.
Treat the grid timeline as part of the project architecture. Then use the evidence to decide which commitments the project is ready to make.
Where the evidence leads
[1] Georgia Power describes a customer-specific transmission project and a tentative completion target. It does not establish the customer's operating plan or the feasibility of an earlier phase.
Georgia Power Hills Bridge-Speedway project
[2] Georgia Power explains the phases and dependencies of transmission development. The decision framework above is Blueflux editorial analysis of how project teams can evaluate such evidence.
Georgia Power Transmission Expansions and Upgrades
Connected Decision Areas
Continue with Market Intelligence to evaluate external signals, Power for AI to examine usable site power, and Deployment Strategy to consider infrastructure sequencing.
Continue Your Infrastructure Decision
Explore Deployment Strategy for the broader decision context, then use the Technical Library to investigate the technical questions behind it.
