What Most Procurement Strategies Get Wrong in Data Centre Projects And Why It Delays Everything

What happens: Procurement is engaged after design is largely fixed, often dependent on late inputs from engineering and stakeholders. Contractors are brought in too late, and packaging decisions are rushed. Impact: Long-lead items are not secured Poor buildability and rework Delays embedded from day one Key insight: Procurement must start at RIBA Stage 2–3, not Stage 4. Early contractor involvement is critical. If procurement starts after design or waits on inputs the project is already late.

What happens: Procurement is treated as a linear process: RFP → compare → select. Impact: Misaligned suppliers Endless clarifications Lack of strategic alignment Key insight: Procurement is strategy, not just tendering. Tendering is a tool. It is not a strategy.

What happens: Critical equipment and supplier capacity are not secured early. Impact: Extended lead times Loss of control over delivery timelines Increased exposure to market volatility Key insight: Secure capacity early through OFCI models and framework agreements. If you don’t control long-lead equipment, you don’t control your schedule.

What happens: Projects default to a single contracting model without challenge, while packaging is treated as an afterthought. Impact: Inflated pricing due to poor risk allocation Limited bidder pool Interface risks during construction Key insight: The right contracting model whether GC, Construction Management, or hybrid must be defined early. Packaging must align with market capacity, programme, and risk. How you package the work determines who you attract and how they price it.

What happens: Decisions are driven by lowest upfront cost, with limited focus on delivery capability or lifecycle impact. Impact: Underpriced bids leading to claims Programme delays Higher operational costs and reduced reliability Key insight: Evaluate delivery capability and total cost of ownership, not just CAPEX. Saving 5% upfront can cost 20% over the lifecycle. The cheapest contractor is often the most expensive mistake.

What happens: Procurement timelines are disconnected from construction milestones, with late awards on critical packages. Impact: Site delays Acceleration costs Out-of-sequence works Key insight: Procurement must actively drive the programme, not follow it. If procurement is not driving the programme, it is delaying it.

What happens: Scopes are unclear, contracts are inconsistent, and risk allocation is poorly defined. Impact: Disputes and claims Cost overruns Lack of accountability Key insight: Strong frameworks MSAs, capacity agreements, and clear SOWs are essential. Ambiguity in contracts becomes cost on site.

What happens: Procurement, design, and construction teams operate in silos, with limited coordination. Impact: Misaligned priorities Slow decision-making Missed risks Key insight: Procurement must sit at the centre of delivery, connecting design intent with construction reality. Procurement is the connector between design intent and construction delivery.

Delays in data centre projects are rarely created on site they are designed in early, through procurement decisions made too late or without the right strategy. Procurement is not a support function. It is the foundation of successful delivery.