Welcome to Global Data Center Hub. Join investors, operators, and innovators reading to stay ahead of the latest trends in the data center sector in developed and emerging markets globally.
This article is the 16th article in the series: Ground to Grid: A Free 21-Lesson Guide to Mastering Data Center Development
Why Sequencing Is the Real Construction Skill
Building a data center is a sequencing problem. Speed in any single-phase matters far less than the order in which dozens of connected tasks happen.
Get the order right, and a delay in one task stays contained. Get it wrong, and that delay spreads into all the others.
The discipline of the sequence is what keeps the schedule honest.
Construction is where the design and procurement plans become a building that can carry load.
Construction risk is cumulative. A two-week slip in one phase is manageable. Two-week slips in four phases are a different project, because each slip pushes the start of the next phase.
Quality control during the build stops problems from surfacing at commissioning.
Commissioning is the formal testing that proves the facility works.
It is also the most expensive place to find a defect, because by then the problem sits behind finished work.
The Phases of Construction
Four phases do most of the work. They overlap in practice. Each one still depends on the one before it.
1. Civil and Site Work
Civil work prepares the ground. Crews grade the site, build drainage, lay duct banks (buried concrete channels that carry power and fiber cables), and pour foundations.
None of this is visible once the building is up. A duct bank sized too small cannot be fixed cheaply later.
2. Shell and Structure
The shell is the building itself: the steel or concrete frame, the roof, and the walls. A data center shell is built for heavy mechanical and electrical loads.
The shell also protects everything that comes after it. The National Institute of Building Sciences notes that enclosure performance cannot be fully verified until the building is enclosed.
Equipment should not be set, and systems cannot be tested reliably, until the building is closed to weather.
3. Mechanical, Electrical, and Plumbing (MEP)
MEP is the core of the facility. It includes transformers, switchgear, uninterruptible power supplies (UPS), generators, cooling plant, and the distribution that carries power and cooling to the racks.
MEP is the phase most exposed to equipment lead times. Switchgear and large transformers are built to order in a factory.
If they arrive late, installation waits, no matter how far along the rest of the site is.
A purchase order date says little. The useful signals come from the factory: materials in hand, assembly under way, factory test passed.
4. Integration and QA/QC
Integration is where separate pieces become working systems. QA/QC is how the team proves each piece is right before the next one depends on it.
The U.S. Army Corps of Engineers uses a three-phase model. Before work starts, the team confirms drawings, approved materials, test methods, and safety. When work starts, the first section installed is inspected and becomes the standard for the rest.
After that, daily checks continue until the work is complete, and defects get fixed before the next trade covers them.
The key tool is the hold point. A hold point is a step the work cannot pass without sign-off.
It belongs in the project schedule, so a missed inspection moves every date that depends on it. A hold point that lives only in a spreadsheet can be walked past.
Installed and done are different states. A pulled cable still needs terminations, test results, labels, and inspection before it can be energized. A schedule that counts it as complete is reporting progress the next team cannot use.
Why Delays Compound
Delays stack. A slip early in the job carries into every phase that follows.
A permitting delay pushes back civil work and everything behind it. A late transformer delays MEP regardless of site progress.
Crews can finish every other room and still wait on the one piece of equipment that energizes them.
A commissioning defect traced to weak QA/QC forces rework. Finished work comes out, and tests run again.
Each slip may start on its own. On the schedule, they line up end to end.
The cost is well measured. A Construction Industry Institute (CII) study of 359 projects found direct rework often reaches about 5% of construction cost.
The Get It Right Initiative in the U.K. puts total error costs at up to 21% once delays and disputes are counted.
How the Best Builders Stay Predictable
The first practice is overlapping design and construction, carefully. Starting construction before design is finished can save months.
It works when each package of work is released with approved design behind it. It fails when crews build from drawings that are still changing and the field ends up making design decisions.
The second is standardized layouts and prefabricated components. A repeated layout means crews build the same thing many times, with less variance each time.
Prefabricated modules move work into factories, where it runs alongside site work.
The risk moves with it. It concentrates at design freeze, transport, and the field connections between modules. So, factory work needs the same inspections and test records as field work.
The third is QA/QC at the point of installation. This is the three-phase model and hold points, applied every day.
The turnover records get built while the work is done. Records assembled at the end tend to have gaps, and missing evidence is hard to recreate.
The fourth is early procurement, so on-site work never waits on equipment. Uptime Institute adds a rule for the end of the job: put all commissioning time in the schedule and reserve time for integrated testing, so construction delays cannot consume it.
A Real-World Example
The operators who outperform do not rely on speed alone. They create schedules they can actually meet.
They procure equipment early, reduce design variance, and treat quality control as a discipline. Predictable delivery is the real advantage.
Berlin Brandenburg Airport shows what the opposite looks like.
It was set to open in October 2011 on a budget of about €2 billion. It opened in late 2020 at a cost above €7 billion.
The failure centered on the fire protection and smoke extraction system.
Finishes went up while life-safety systems were incomplete and noncompliant.
Inspectors then found defects behind finished ceilings and walls. Fixing them meant tearing out completed work.
Berlin is an airport. Data centers depend on the same kind of concealed MEP and life-safety systems.
Strategic Implications
For developers: Sequence for resilience as well as speed. The schedule that survives is the one where a single slip does not cascade.
In practice, that means finishing complete systems.
A full power train in one data hall can be tested. Rough-in spread across three floors cannot.
For investors: A developer’s track record on predictable delivery is worth more than its fastest-ever build.
Ask how much reported progress is installed but not yet inspected, tested, and accepted.
For operators: The QA/QC discipline during construction decides how many defects you inherit at handover.
If the integrated test window is cut to save a date, construction risk moves into your first year of operations.
For policymakers: Predictable permitting lets developers build predictable schedules.
Unpredictable review is where construction risk starts, because it pushes civil work and every phase behind it.
Key Takeaway
The best builders are the most predictable ones. Their average project tells you more than their fastest one.
Speed on a single project can come from luck. Predictability across many projects comes from discipline: a sequence that absorbs a slip, quality checked at installation, and equipment ordered before it is needed.
That matters because people are waiting on the date. A tenant plans its deployment around handover.
A lender sizes its loan around the day revenue starts. When the date moves, both plans move with it.
In a business where a missed date loses a tenant, a schedule you can meet beats a schedule that looks fast on paper.
Would you rather work with a developer who is fastest on their best project or most consistent across all of them? Why?