Data Center Construction Progress Tracking: Measuring a Fast-Track Build Hall by Hall
By Kush Agarwal, President and CEO, YelloSKYE. Published .
Executive Summary
- The Question: How do you keep an accurate, defensible picture of progress on a fast-track data centre, where trades overlap, services disappear behind ceilings within days and halls are handed over in phases?
- The Answer: Measure each hall against a short ladder of readiness milestones, not a single percentage. Name every space and system once, capture on a weekly rhythm plus every concealment and handover event, and keep each hall's evidence together so it can serve the owner report, the commissioning team and the operator.
- The YelloSKYE Angle: Construct IQ brings drone flights, fixed cameras and 360° walks into one dated record on DEX, with laser scanning available through BIM IQ for dense rooms. We have no dedicated data centre product; these are the methods we use on other complex buildings, applied to the way data halls are built.
Data centre construction progress tracking works best when every hall is measured against the handful of milestones that decide its ready-for-service date, and when each milestone is backed by dated, located evidence captured before the work is hidden. A single percent-complete figure for a building tells an owner very little; a forecast date for each hall, with the record behind it, tells them almost everything they need. Construct IQ, YelloSKYE's construction monitoring service, is built around that kind of shared visual record.
This guide is about measurement and records on fast-track projects. It assumes you already know how these buildings come together. If you want the stages from power and land through to commissioning, start with our guide to the data centre construction process and come back here for how to track them.
Why fast-track data centres are hard to measure
- Phases overlap by design. Procurement, design and construction run in parallel, so a hall can be partly built while its cooling layout is still changing. Status is a moving target.
- Halls repeat. Ten halls that look alike in photos are easy to mix up. A picture filed against the wrong hall is worse than no picture at all.
- The valuable work is the hidden work. Power and cooling distribution sits above ceilings, under raised floors and inside containment, and is closed in quickly so the next trade can start.
- The last step is the longest. Testing comes after installation is visibly finished, so a progress curve tends to flatten just as everyone expects it to finish.
- Part of the campus goes live early. Later phases are built beside energised halls with tighter access, which limits who can go where with a camera.
Each of these points leads to the same conclusion: progress has to be measured at the level of the hall and system, and the evidence has to be gathered on a schedule driven by when work disappears.
Start with a progress register, not a camera
Before anyone walks a hall with a 360° camera, set up the structure the evidence will be filed into. A register that every contractor shares avoids weeks of arguing about which room a photo shows.
Name every space once
Agree a single naming scheme for buildings, phases, halls, electrical rooms, mechanical rooms and corridors, and use it in the schedule, the drawings, the capture platform and every contractor's report. When the electrical contractor's "Hall 2 North" and the mechanical contractor's "DH-02A" are the same room, say so in writing on day one.
Weight by system, not by floor area
Floor area is a poor measure of effort in a data hall. A small electrical room can carry more cost, labour and risk than a large empty hall floor. Track each room by the systems inside it, so the report shows where the difficult work actually stands.
| Register level | Example | Who updates it | What the owner sees |
|---|---|---|---|
| Campus | Site, external works, substation, plant yard | Main contractor | Overall programme and phase dates |
| Building or phase | Building B, phase 2 | Main contractor | Forecast handover date per phase |
| Hall or room | Hall B3, electrical room B-E2 | Package managers | Milestone reached and next milestone date |
| System in a room | Busway, cooling pipework, fire suppression, controls | Trade contractors | Which system is holding the room back |
| Major item | Switchboard, UPS module, cooling unit, generator | Trade contractors and suppliers | Delivered, set, connected, ready for testing |
If every phase uses the same levels, a director can compare buildings in one sitting without translating each team's format.
Readiness milestones for each hall
Owners and tenants rarely ask how many metres of cable tray are installed. They ask when a hall will be ready. A short ladder of readiness milestones answers that question and gives every capture something to prove.
| Milestone | What has to be true | Evidence that shows it | Typical sign-off |
|---|---|---|---|
| 1. Dry and secure | Roof and envelope closed, room clean, access controlled | Drone flight of the roof, fixed camera on the entrance, 360° walk of the empty room | Main contractor and owner's representative |
| 2. Primary routes in | Main containment, busway and pipework mains installed | Weekly 360° walk located on the plan | Package managers |
| 3. Equipment set and connected | Major items in position, terminated, piped and wired to controls | Delivery records, walk at each connection milestone | Trade contractors |
| 4. Services closed | Ceilings, floor tiles and containment panels fitted after the concealment record is accepted | Walk before closure, linked to the closure permit | Main contractor quality lead |
| 5. Ready for system testing | Pre-functional checks done, punch items in the room cleared | Issue log for the room with closed items | Commissioning manager |
| 6. Ready for service | Integrated testing passed and the hall accepted by the owner | Test records plus the full visual history of the hall | Owner and operator |
The commissioning levels that sit behind milestones 5 and 6 are explained in our data centre construction process guide. The point here is narrower: each hall reports the highest milestone it has reached and a forecast date for the next one. Our guide to percent complete in construction explains why a blended percentage drifts away from the site; on a data hall the drift is worse because so much of the value is in the last two rungs.
Capture triggers on a fast-track programme
A calendar alone cannot keep pace with a hall being closed in. Combine a steady baseline with captures triggered by events, so the record is densest where the risk is highest.
| Trigger | Capture method | The question it answers later |
|---|---|---|
| Every week while external works are active | Drone flight on a fixed route | Is the campus, yard and substation work on programme? |
| Every week in each active hall | 360° walk on a fixed route | What changed in this hall since the last review? |
| The day before a slab pour | 360° walk of in-slab conduit and earthing | What is cast into this floor, and where? |
| Before any ceiling, floor or containment panel closes | 360° walk of the zone | How was this system routed and connected before it was hidden? |
| On arrival of major plant | Fixed camera on the delivery area, walk at setting | When did the item arrive, and in what condition? |
| When a room passes between trades | 360° walk agreed by both trades | What state was the room in at release? |
| Containment complete in dense rooms | Laser scan compared with the coordinated model | Does the installed geometry match the design? |
| Continuously | Fixed cameras on the plant yard, loading bay and roof | What happened between scheduled captures? |
Two habits make the triggers stick. First, make the concealment walk a condition of the closure permit, so a ceiling cannot be closed until its walk is linked to the permit. Second, give each hall a named capture owner, because shared responsibility tends to mean nobody walks the room on the day it matters.
Tracking beside a live hall during phased handover
Phased campuses create a problem most buildings never face: part of the site becomes a secure, operating facility while construction continues next door. Progress tracking has to adapt at each phase boundary.
Settle capture rules before mobilisation
Agree with the owner's security team which zones may be captured, which roles may carry a camera, where imagery is hosted, how long it is kept and who can view it. Write down how those rules change once a hall is energised, because that is usually when access tightens.
Record each hall's final condition before it transfers
The day before a hall is handed over is the last easy chance to walk it. Capture every room in full, close the open issues you can and file the record against that hall in the register, so the operator receives a complete history rather than a partial one.
Change methods at the secure line
Once walks inside an operating hall are restricted, shift the construction record to methods that stay outside it: fixed cameras on the active work fronts, drone flights over the next building and walks of the areas still under the contractor's control. Keep each phase's record separate, so evidence from a live hall is not mixed with evidence from the one still being built.
Turning the record into commissioning evidence
The capture record earns most of its value late in the project, when testing begins and the programme has little float left.
When a functional test fails, the commissioning team needs to see how the system was installed without lifting tiles or removing panels in a room that may already be live. A dated walk taken before closure, located on the plan, lets them check routing, labels and connections in minutes. Tagging the fault on the visual, at the exact position it refers to, then gives the responsible trade a clear location and a clear instruction.
For each hall, assemble a small evidence pack as it reaches milestone 5:
- The concealment walks for every closed ceiling, floor and containment zone
- Delivery and setting records for major plant
- Scan comparisons for the densest rooms
- The issue log for the hall, with each item's status and closing evidence
- A note of any design changes issued after primary routes were installed
The same pack then becomes part of the operator's handover record.
What a weekly owner report should contain
Owners of preleased capacity care about dates and risk, not activity, so keep the report short and link every claim to the record.
| Section | What it shows | Where it comes from |
|---|---|---|
| Hall readiness | Milestone reached, forecast for the next, contractual date | Progress register |
| Long-lead plant | Each major item: ordered, tested at factory, delivered, set | Procurement tracker and delivery captures |
| Concealment coverage | Share of closures in the week with a linked walk | Closure permits and capture platform |
| Open issues | Count and age of issues by hall and trade | Issue log tagged on the visuals |
| Phase boundary | Halls approaching transfer and outstanding records | Register and handover packs |
| Evidence | Links to the walks, flights and scans behind each claim | Capture platform |
Early warning signs that a hall will miss its date
Most late halls show symptoms weeks before the date slips. These are the ones worth watching in the record.
| Signal in the record | What it often means | Sensible response |
|---|---|---|
| Rooms released to the next trade late two weeks in a row | Congestion or under-resourcing upstream | Re-sequence the hall zone by zone with the trades involved |
| Closures scheduled with no linked walk | Concealment control is slipping | Stop closures in that hall until walks are caught up |
| Issues in one hall ageing beyond two review cycles | No owner, or a disputed scope | Assign each issue to a named trade with a date |
| Little activity on fixed cameras in a priority zone | Crews moved elsewhere | Check labour allocation across buildings |
| Plant set but not connected for several weeks | Missing terminations, controls or design input | Track the connection step as its own activity |
| Design change issued after primary routes are in | Rework and resequencing ahead | Capture the installed condition before any change is priced |
Where YelloSKYE fits
YelloSKYE has no data centre case study. Construct IQ offers the capture mix and platform described above, as we use them on other complex buildings.
Drone flights cover the campus, yard and external works. Fixed cameras keep a timestamped view of priority zones between flights, and DEX can alert the team when a priority zone goes quiet or a milestone is reached; our fixed-camera monitoring work has delivered up to 80 per cent fewer site visits across verified deployments. Inside the halls, 360° walks can be carried out by any site worker with no specialist technician, and the interior fit-out use case reports 70 per cent less coordination time and snags closed five times faster.
On DEX, Time Travel Playback steps back through each hall's history day by day, the progress versus plan view compares the site with the 4D schedule, and geo-referenced annotations pin issues to the exact spot. For campuses with several buildings, the portfolio monitoring use case shows leadership reviewing more than ten sites in 30 minutes on one standard format. Construct IQ integrates with Procore, Autodesk BIM 360 and Autodesk Construction Cloud, and a typical project goes from set-up to its first capture in 48 to 72 hours.
A 30-day setup checklist
- Register: Agree one naming scheme for every building, hall, room and system, and load it into the schedule and capture platform.
- Milestones: Define the readiness ladder for each hall with the owner, including who signs off each rung.
- Capture rules: Settle zones, roles, hosting, retention and post-energisation rules with the owner's security team.
- Baseline: Fly the campus and walk every hall that has started, so later captures have a starting point.
- Triggers: Add concealment walks to the closure permit and name a capture owner for each hall.
- Fixed cameras: Place them on the plant yard, loading bay and the busiest work fronts.
- Report: Issue the first weekly owner report in the format above, with links to the evidence.
- Review: After four weeks, check concealment coverage and close any gaps before the next hall starts closing in.
Frequently asked questions
How do you track progress on a data centre construction project?
Split the campus into buildings, halls, rooms and systems, and give every contractor the same names for them. Define a short set of readiness milestones for each hall, such as dry and secure, services complete, ready for testing and ready for service. Then feed each milestone with dated visual evidence captured on a fixed rhythm and just before work is concealed, and report a forecast date per hall rather than one overall percentage.
Why is percent complete misleading on a data centre?
The visible work, such as the shell, containment and large equipment, finishes early and pushes the percentage up quickly. The work that decides the ready-for-service date, including terminations, controls, flushing and testing, is less visible and sits at the end. A hall can report a high figure for weeks while its slowest system is still far from finished, so readiness milestones per hall tell the owner more.
How often should a data hall be captured during fit-out?
A weekly walk of every active hall is a sensible baseline, but it is not enough on its own once services are being closed in quickly. Add a walk before every ceiling, floor or containment panel is closed, on the arrival of major plant and when a room passes from one trade to the next. Fixed cameras can cover plant yards and loading areas continuously in between.
What progress evidence does a commissioning team need?
Commissioning engineers need to see how each system was installed before it was covered, located on the plan and dated. When a functional or integrated test fails, that record lets them check routing, connections and labels without opening finished work. A laser scan of dense rooms compared with the coordinated model adds confidence that equipment and containment sit where the design says.
Can you capture images inside a live data centre during phased construction?
Usually only within rules set by the owner's security team, and those rules often tighten once a hall is energised or handed to the operator. Agree which zones can be captured, by whom, where the images are stored and who can view them before mobilisation. Where capture inside a live area is not allowed, record the final condition of each hall the day before it transfers.