A data center makes money when its white space is energized, commissioned and handed to the tenant. Not when the shell is dry, not when the roof is on, and not when the general contractor reports ninety percent complete. Owners who track the building instead of the power path find out too late that the finish date was never about the building. These are the five dates we watch every week on a data center program.
1. Utility energization
Permanent power is the one date nobody on the project fully controls. It depends on the utility, the substation, the transmission work and sometimes a regulator. It belongs in the schedule as real logic with real predecessors, not as a milestone someone typed in. If permanent power slips and the schedule does not move, the schedule is not connected to it.
2. Long-lead electrical equipment on site
Switchgear, transformers, generators, UPS modules and chillers can carry lead times measured in many months. Each one needs a procurement chain in the schedule: submittal, approval, release, fabrication, factory test, shipment, set. The approval step is where owners lose the most time without noticing, because it looks like paperwork.
3. Mechanical and electrical complete by data hall
A campus is not one finish. It is a sequence of halls, each with its own path. Tracking a single overall percent complete hides the fact that Hall 1 may be on time while Hall 2 is quietly carrying the risk. We schedule and report each hall as its own critical path.
4. Integrated systems testing
Commissioning runs through levels, from factory tests to full integrated systems testing under simulated load. It is the phase most often squeezed when earlier work runs late, and the phase least able to absorb it. A credible schedule gives commissioning its real duration and protects it with logic, not with a hopeful constraint.
5. Ready for service
This is the tenant's date, and often the revenue date. Every day between the forecast and the contract date has a price, sometimes written into the lease. Know that price. Put it in front of the team. It changes how fast decisions get made.
What this looks like on a live campus
On a multi-tenant colocation data center in Texas, four data halls and 36 MW, tenants had signed for megawatts on specific dates. We scheduled and reported each hall as its own path from energization through integrated systems testing, so a slip in one hall could never hide inside a campus average. Every hall was energized and handed over on the day it was sold.
What to ask for
- The native P6 file every update, with the power path and each hall's path filtered and explained.
- A Monte Carlo run that shows the P80 ready-for-service date, refreshed each quarter.
- A long-lead log tied to schedule activities, with submittal and release dates tracked, not just delivery.
Our founder spent much of her career in data center and infrastructure construction, and this is the list she built the firm's data center practice around. See how we work in data centers, or price one late day on your own campus with the Cost of Delay calculator.
