The Critical Path to IST: Five Scheduling Mistakes That Delay Data Center Handover
6 min read. For delivery directors, project leads and planning managers.
Key takeaways
- Most data center delays are created in the programme months before they appear on site.
- The commissioning sequence, not the construction sequence, should drive MEP completion priorities.
- One logic-linked master programme, honest float and named interface owners protect the critical path to IST.
Most data center delays are not built on site. They are built into the programme months earlier: in a tender schedule that ignored MEP dependencies, a commissioning sequence bolted on at the end, or a critical path nobody was actually protecting. Having supported hyperscale and enterprise deliveries across the UK and continental Europe, we keep seeing the same five mistakes.
1. Treating commissioning as a phase, not a sequence
On paper, commissioning is the last bar on the Gantt chart. In reality, Level 1 factory witness testing, energization, pre-functional checks and integrated systems testing (IST) each depend on specific MEP completions, often in a different order than construction naturally delivers them. If the commissioning sequence is not driving the MEP completion sequence, the last bar on the chart quietly absorbs every upstream slip.
2. A tender programme that was never meant to be delivered
Tender programmes are written to win work, and everyone knows it. The mistake is not re-baselining immediately after award: agreeing realistic sequence logic, procurement lead times and interface milestones while there is still float to negotiate. Six months in, the same conversation costs prolongation money instead.
3. Interfaces without owners
The riskiest activities in a data center programme are rarely inside one trade’s scope; they sit between trades. Busbar energization before ceiling closure, chilled water flushing before floor sealing, controls point-to-point before integrated testing. Every interface needs a named owner and a date in the programme, not a line in the minutes.
4. Lookaheads disconnected from the master schedule
Weekly lookahead planning is where the schedule meets reality, but on many projects the lookahead lives in a spreadsheet that has never met the P6 master programme. When the two disagree, the master programme becomes a reporting fiction and the critical path stops being managed at all. The fix is boring and effective: one logic-linked programme, updated with real progress, driving the lookahead.
5. Reporting float that does not exist
Optimistic progress reporting is a loan against the commissioning period, and commissioning always pays it back with interest.
Honest schedule health checks that look at logic quality, realistic durations and genuinely available float are cheaper than the claim negotiation that follows the alternative.
What protecting the critical path actually looks like
A sequencing-led delivery approach connects three disciplines that usually operate separately: the programme (planning and scheduling), the model (BIM coordination and 4D sequencing), and the handover (commissioning management). When the same team owns all three, the critical path from tender to IST is one continuous, protected line, not three documents that meet for the first time in a delay review.
Want an independent view of your programme?
Our fixed-fee Schedule Health Check reviews your programme’s logic, float and commissioning sequence in one to two weeks and tells you plainly whether your dates will hold. Get in touch.
