Power and cooling get the headlines. Headcount is the real bottleneck.

Every data-centre trends report published this year leads with power: grid connection queues, gigawatt campuses, liquid cooling for AI racks. All real, all worth the coverage. But ask operators what's actually most likely to slow their programme down in the next twelve months, and the honest answer sitting underneath the power story is people.

The number that isn't getting the coverage

Our cabling delivery partner ONNEC surveyed 250 senior data-centre decision-makers across the UK, Ireland, and the Nordics in May 2025. 92% had seen AI-driven capacity demand rise over the previous year, by an average of 42%. That's the statistic that makes headlines. The one that doesn't travel as far: 79% named skills shortages as a factor that will push their project timelines out.

Nobody delays a data-centre programme because they ran out of concrete. They delay it because they ran out of people certified to pull cable, terminate it, and test it to spec.

Where the people are supposed to come from

The construction workforce data-centre programmes draw from isn't data-centre-specific, and that's the actual problem. Research from the University of Cambridge's Construction and Building Trades project, cited by Places for People, puts current UK construction vacancies above 140,000, with 35% of the existing workforce over 50 against 20% under 30. On current trends the sector needs close to a million additional workers by 2032 as roughly 750,000 of today's workers retire by 2036. Data-centre builds are competing for that same shrinking pool against housebuilding, rail, energy, and every other programme with a hard hat on site.

Why this is a sourcing problem, not a training problem

Training pipelines take years to widen. Programme timelines don't wait for them. The gap that actually stalls a job isn't "we need to train more electricians" — it's the distance between "we need forty certified engineers on site in three weeks" and a standard six-to-twelve-week recruitment cycle. That's a sourcing and mobilisation problem, and it doesn't get smaller by waiting.

It's also the specific gap GO2 Workforce is built around: right-to-work and certification status tracked centrally before an engineer is ever put forward, coverage across the UK, Europe, and Asia so a local shortage doesn't stall a programme that could pull from another region, and a 48-hour mobilisation window instead of a recruitment-cycle promise.

What to actually ask a workforce partner

• How fast can you put a certified engineer on site — a number, not "we'll start looking."
• Is right-to-work and certification status tracked centrally, or scattered across individual files?
• Can you flex across regions if local supply runs short mid-programme?

The skills shortage isn't a 2030 problem to plan around later — operators are already naming it as a live risk to this year's programmes. Talk to us before headcount is the reason a milestone slips.