Chapter 6.6
Construction Execution, Sequencing & Phased Turnover
An AI data center is not finished when it is built — it is finished when it is commissioned, and the only schedule that matters is the one that delivers energized, accepted, GPU-ready megawatts in turnover-sized blocks before the depreciation clock and the revenue window pass you by.
What you'll decide here
- Whether you procure the build as a hard-bid lump sum, a CM-at-risk GMP, or an integrated design-build/EPC — and therefore who carries schedule and trade-coordination risk on a project where the long poles are owner-furnished electrical gear and a labor pool that is structurally short.
- The turnover block size — whole building, hall, or pod — because it sets how early you can energize and earn, and how much commissioning you must interleave with live, occupied space next door.
- Where the critical path actually runs: it is almost never the concrete. It is the long-lead switchgear and transformers, the utility energization date, and the availability of qualified electricians and pipefitters during the MEP rough-in and equipment-set windows.
- How you weave Cx Level 1–5 into the construction schedule rather than bolting it on at the end — factory witness tests, owner-furnished equipment receipt, and a worst-case-branch liquid loop that cannot be fully proven without real GPUs.
- Your skilled-trades mitigation strategy — prefabrication, multi-shift work, travel premiums, and self-perform vs subcontract — decided at GC selection, not discovered at peak manpower.
The design is frozen, the slab basis is set, the cooling plant is specified, the fire strategy is approved. None of it earns a dollar until megawatts are energized, accepted, and handed to the cluster team. This chapter is about the eighteen-to-thirty-month interval between a signed GMP and a GPU drawing its first watt — and the brutal truth that runs through all of it: the building is the easy part. Steel, slab, and skin are a solved, schedulable problem. What kills AI-data-center schedules is the same short list every time — long-lead electrical gear that does not show up, a utility energization date the owner does not control, and a skilled-trades labor pool that is short by hundreds of thousands of workers nationally. Construction execution is the discipline of sequencing around those three constraints so that the parts you can control are never what you are waiting on.
This chapter works through the delivery-model fork (lump-sum vs CM-at-risk vs design-build/EPC) and who eats schedule risk under each. It traces the canonical sequence (civil → shell → MEP rough-in → equipment set → fit-out) and where it bottlenecks. Phased turnover is a revenue lever, not a project-management nicety: the unit of turnover you choose determines how early the first block earns against a 2–3-year accelerated GPU life. And the trades shortage is a first-order schedule risk that must be mitigated at GC selection, alongside the quality and inspection regime that carries a hall from substantial completion into commissioning readiness. The skilled-workforce program (recruiting, training, retention) lives in Chapter 14.11; here it is a construction-schedule input. The construction-safety program lives in Chapter 6.9; here it is an interface, not the subject.
The delivery-model fork: who carries schedule risk
Before a shovel moves, the owner picks how the build is contracted, and that single choice allocates the two risks that dominate an AI build: schedule and trade coordination. The fork is rarely about lowest first cost — at $10–12B of annual revenue per energized gigawatt, the value of getting 200 MW online six months early dwarfs the contractor's fee delta. It is about who is on the hook when the switchgear slips and the electricians are double-booked across three concurrent campuses.
Lump-sum / hard-bid transfers price risk to the GC but assumes a complete, frozen design at bid time — an assumption that is almost never true for a fast-tracked AI build where the rack generation is still moving under the design. Change orders become the battleground, and the owner discovers that a fixed price bought on incomplete documents is not actually fixed. Construction-management-at-risk (CMAR) with a guaranteed maximum price (GMP) is the workhorse model for hyperscale: the GC joins during design, prices a GMP against a still-developing set, and overruns above the GMP are the contractor's problem while savings are shared. It buys early constructability input and preserves the ability to start civil while the fit-out design matures. Integrated design-build / EPC collapses designer and builder into one contract and one schedule — the fastest path to a single throat to choke, favored when speed-to-power dominates and the owner will trade some price transparency for it. The consequence of choosing wrong: a hard-bid contract on a moving design generates a change-order war that costs more schedule than it ever saved on fee.
| Delivery model | Design completeness at start | Who carries schedule risk | Trade-coordination owner | Best fit |
|---|---|---|---|---|
| Lump-sum / hard-bid | Must be ~complete & frozen | GC (in theory); owner via change orders (in practice) | GC | Stable, repeatable, fully-designed shells |
| CMAR + GMP | Developing; priced at GMP set | Shared above/below GMP; owner on OFE | GC, with early owner input | Most hyperscale AI builds; fast-track with cost control |
| Design-build / EPC | Performance-spec; design proceeds in parallel | Single entity (designer+builder) | EPC integrator | Speed-to-power-dominated; single-throat accountability |
| Owner-led multi-prime | Varies by package | Owner (the integrator role) | Owner / owner's CM | Sophisticated self-perform owners; max control, max risk |
The construction sequence and where it actually bottlenecks
The canonical sequence is linear on paper and overlapped in reality. Civil and earthwork — mass grading, stormwater, deep utilities, foundations — is weather-exposed and front-loaded. Shell — structural steel or tilt-up, roof, skin — gets the building watertight so interior trades can work year-round. MEP rough-in — the electrical raceway, bus duct, mechanical piping, the liquid-cooling distribution backbone — is the labor-intensive heart of the schedule and the first place the trades shortage bites. Equipment set — landing the switchgear, UPS/BESS, CDUs, chillers, generators, and the heavy mechanical plant — is rigging-and-crane choreography gated by when the owner-furnished gear arrives. Fit-out — busway runs to the rack, manifold and quick-disconnect plumbing, containment, terminations, and the thousand small completions — is where substantial completion is won or lost.
Here is the decision that separates a 16-month delivery from a 26-month one: you overlap these phases, and the overlap is constrained by the critical path, which is almost never the concrete. The civil and shell durations are predictable and compressible with crews and money. The binding constraints sit downstream and outside the GC's direct control: the date the utility energizes the service, the date the owner-furnished switchgear and transformers land, and the headcount of qualified electricians and pipefitters available during rough-in and fit-out. Sequence to keep those three off the path of the things you control, and you protect the schedule. Let the trades become the constraint at peak manpower and the whole back end of the project slides — fit-out and commissioning are exactly where the shortage concentrates.
Deep dive: the liquid-cooling backbone changes the sequence — pipe before you can pull rack
A traditional air-cooled hall could defer most of its mechanical scope to fit-out. A direct-to-chip liquid hall cannot. The facility-water and technology-cooling-loop distribution — risers, headers, the CDU gallery, in-rack manifolds, and the ~150–200 quick-disconnects per rack — is heavy, code-governed charged piping (ASME B31.x / EN 13480) that must be installed, welded, NDE-inspected, flushed, and pressure-tested before the racks it serves can be energized. That work lands squarely in the MEP rough-in and fit-out windows and competes for the same pipefitter and welder labor that is already short. It also introduces a hard sequencing dependency the air world never had: multi-stage flushing and fluid-quality acceptance (a step measured in weeks per loop) gate the cooling acceptance that gates the GPU burn-in.
The consequence for execution: in a liquid hall, the cooling distribution is on the critical path to first-watt in a way it never was for air. Operators that prefabricate skidded CDU and manifold assemblies off-site (→ Chapter 6.4) pull this scope out of the congested on-site fit-out window and into a controlled factory environment — which is as much a labor-availability strategy as a quality one. The piping mechanical engineering itself is owned in Chapter 5.4 (DLC) and its pressure-system code basis in the facility-piping chapter; here it is a schedule dependency that reorders the sequence.
Phased turnover: the unit you energize is the unit you earn on
The biggest leverage in the whole construction phase is not waiting for the whole building. AI campuses are built as repeated, near-identical units — a baseline pod or hall design stamped out across phases — precisely so that the first block can be energized, commissioned, and producing while later blocks are still being poured. Multi-building hyperscale campuses now hit 12–18-month build times specifically through phased delivery (Data Center Knowledge / Mastt, 2026). The decision is what size the turnover block should be: whole building, data hall, or pod/row. Smaller blocks energize earlier and start the revenue clock sooner, but they multiply the number of times you must commission and partially energize next to occupied, live space — which brings concurrent-maintainability constraints, arc-flash boundaries around energized gear, and life-safety separation between a construction zone and a running hall into the schedule as hard interfaces.
The economic logic is stark and it is the reason phasing dominates. At roughly $10–12B of revenue per gigawatt per year (SemiAnalysis, 2025), bringing a 200 MW block online six months early is on the order of $1–1.2B of incremental revenue — and it runs against a GPU asset whose useful economic life is 2–3 years, not the 5–6 of the building. Every month a finished, un-energized hall sits dark is a month of that short asset life burned with zero return. Phased turnover converts a single distant finish line into a series of near revenue milestones, and it is why the schedule is measured in energized, accepted, GPU-ready megawatts per quarter, not in percent-complete.
Commissioning woven into the schedule, not bolted on at the end
The most expensive commissioning mistake is treating Cx as a phase that begins when construction ends. It does not. The Cx Level ladder (L1–L5) is interleaved through the entire build, and construction execution either creates the evidence trail as it goes or pays to reconstruct it later. Level 1 (factory witness / FAT) happens at the manufacturer before equipment ships — witnessing switchgear, UPS, and CDU testing in the factory is a construction-schedule activity, and skipping it imports defects to the critical-path fit-out window where they cost ten times as much to fix. Level 2 (component verification / installation) is the inspection-and-startup work that overlaps directly with equipment set and fit-out. Levels 3 and 4 (subsystem and integrated system functional testing) — energization, load-bank acceptance, redundancy-topology validation — begin the moment a block's gear is set and its service is energized, well before the building as a whole is done. Level 5 (integrated systems testing, IST) — the black-building pull-the-plug demonstration — is the gate to handover.
The decision that matters for the GC schedule: build the commissioning windows into the construction logic as named, duration-bearing activities, and protect them. The single hardest realism limit to plan around is that facility load banks reject heat to air, not into cold plates and CDUs — so the liquid loop, the CDU controls, and worst-case-branch thermal-hydraulics cannot be exercised at realistic transient heat flux without real GPUs. That makes mechanical commissioning and the cluster's GPU burn-in an explicitly overlapping, sequenced gate rather than a clean handoff: cooling acceptance and the first real-workload proxy run interlock. The full Cx program — levels, scripts, acceptance gates, and the load-realism problem — is owned in Chapter 13.1 and the cooling-acceptance specifics in Chapter 13.5; the construction job is to make the schedule honor them.
The skilled-trades shortage as a first-order schedule risk
Of all the constraints on an AI build, the one most likely to be underestimated at GMP signing and most painful at peak manpower is labor. The numbers are structural, not cyclical. The US data-center construction labor market is projected short by roughly half a million workers; the electrical trade alone needs hundreds of thousands more bodies while ~10,000 electricians leave the field annually against ~7,000 entering — a gap that compounds every year (iRecruit / Build.inc / Fortune, 2026). Electricians, MEP engineers, commissioning specialists, and project managers are consistently named the hardest roles to fill. And because electrical systems are 45–70% of total data-center construction cost (IBEW), the shortage hits the most cost-and-schedule-dense scope in the project precisely during the MEP rough-in and fit-out windows that already sit on the critical path.
The consequence is direct and quantifiable: a delayed 60 MW block costs on the order of $14M per month in lost revenue (industry estimates, 2026), and the trades shortage is now cited as a site-selection constraint — operators choose markets partly on the depth of the local skilled-labor pool, because a site you cannot staff is a site you cannot energize on schedule. Mitigation is not a back-office HR concern; it is a construction-execution decision made at GC selection. The strongest levers, in rough order of impact:
- Prefabrication and modularization (→ Chapter 6.4) — shifting skidded power and cooling assembly into a factory cuts on-site labor hours 30–50% and moves the work to a controlled labor pool, away from the congested site. This is the single largest labor mitigation available.
- Self-perform vs subcontract — GCs that self-perform electrical and mechanical control their own crews instead of competing for them on the spot market; the delivery-model choice and the labor strategy are coupled.
- Multi-shift and travel-crew premiums — running second shifts and importing traveling trades closes the local gap at a cost premium (data-center work already commands up to a ~30% wage premium over general construction).
- Early trade-partner lock-in and stacked starts — committing subcontractors during design and staggering trade peaks across a phased campus so the same crews flow from block to block rather than all peaking at once.
The owner-side workforce program — apprenticeships, pipeline development, retention — is the canonical subject of Chapter 14.11. The construction-execution point is narrower and sharper: if the trades strategy is not decided at GC selection, it will be discovered at peak manpower, and by then the only levers left are the expensive ones.
Quality, inspections, and the path to commissioning readiness
Between "the building is done" and "the cluster team can take it" sits a quality gauntlet that, run poorly, becomes the longest unplanned slip in the project. The path runs through inspections and authority-having-jurisdiction (AHJ) sign-offs — electrical, mechanical, fire, life-safety, occupancy — each of which can stop energization cold; through quality-control verification of the trades' work (weld NDE on charged piping, megger and torque verification on electrical terminations, fluid-quality acceptance on the cooling loops); and into substantial completion, the contractual milestone at which the owner can beneficially occupy. But substantial completion is not commissioning readiness. The gap between them is the punch list and the deficiency-tracking discipline that closes it.
The decision here is whether quality is verified continuously as the work is installed or audited at the end. Continuous in-line QA — using the digital Cx platform to capture installation verification and baseline "fingerprint" data as each subsystem is built (→ Chapter 13.2) — front-loads defect discovery into the construction window where it is cheap to fix. End-of-line auditing concentrates discovery into the handover window where every defect is on the critical path to first-watt and every fix competes with the same short trades for attention. A clean transition from substantial completion to Cx readiness is won months earlier, by the QC regime written into the GC's execution plan, not by heroics at the finish. The downstream consequence of a sloppy path: deficiencies surface during L4/L5 testing, where they read as commissioning failures, blow the IST window, and push the turnover block — and its revenue — into the next quarter.
Deep dive: substantial completion, the punch list, and why "done" is a defined term
"Done" is contractual, not intuitive. Substantial completion is the milestone at which the work is sufficiently complete that the owner can use the facility for its intended purpose — it typically triggers the start of warranty periods, the transfer of certain risk and insurance, and the release of much of the retainage. It does not mean every item is finished; it means the remaining items (the punch list) do not prevent beneficial use. Final completion comes later, when the punch list is closed.
For an AI build the seam that matters is the one between substantial completion and commissioning readiness — the point at which a block has enough verified, energized, accepted infrastructure for L3/L4/L5 testing to proceed. These are not the same milestone, and conflating them is a classic schedule trap: a hall can be "substantially complete" with a punch list that still contains items fatal to commissioning (an un-flushed cooling loop, an unproven protective-relay setting, an incomplete BMS point-list). The disciplined execution plan defines commissioning readiness as its own gate with its own checklist, sequenced after substantial completion and before the cluster team's GPU burn-in. The commissioning program that consumes that readiness is owned in Chapter 13.1; the construction job is to deliver a block that is genuinely ready, not merely substantially complete.