490 days. That’s the average time needed to secure planning consent for a disputed UK Data Center scheme, based on Hoare Lea’s analysis of 33 applications published in April 2026.
The longest ran past 5 years. 9 were refused outright.
Now hold that number against your workforce plan. Whatever mobilisation schedule you built at land acquisition is 16 months out of date by the time you break ground, and almost nobody rebuilds it while planning drags on. The Cx lead you’d earmarked has taken a role in Dublin. Your MEP design resource was absorbed into another programme 8 months ago.
Planning risk is a hiring problem. Most developers only work that out in month 14. By then, the people named in the original plan are usually working somewhere else.
Frankfurt showed that technical concessions don’t buy consent
In February, councillors in a town of 25,000 outside Frankfurt voted 18 to 14 against a 174 MW campus carrying roughly 2.5 billion euros of investment. The developer had owned the site since 2022. They’d offered to make waste heat available to the town.
Bird & Bird’s summary of the council’s reasoning lists airflow, heat exposure, the small number of permanent jobs, uncertainty over future trade-tax income, and the risk of the site attracting attack.
Only the airflow point is primarily an engineering question.
The rest are political, and the heat-reuse offer didn’t touch them. That matters because it breaks the assumption many development teams still run on: that a sufficiently responsible technical proposition wins the room. Frankfurt has already passed 1.3 GW of live capacity. If a scheme falls over there, on owned land and with heat reuse on the table, then power and fibre aren’t necessarily the constraints on your next site.
England arrives at the same place by a different route. Since January 2026, qualifying large schemes can be treated as nationally significant infrastructure projects and pursued through a central development consent order process. Ministers have also intervened directly, moving a 300 MW Buckinghamshire scheme into the DCO process in March and overturning a council refusal at Court Lane in December 2024.
Read that as permission to skip the parish and you’ll regret it. Pre-application consultation remains statutory. Consent won over the heads of a hostile community can still buy a decade of friction: noise complaints, contested minor amendments, and opposition to every subsequent phase of the campus.
The mobilisation whipsaw
Here’s what a 490-day consent timeline does to delivery.
You can’t hold a commissioning team on the bench for 16 months. Contractors move on. Then consent lands, capital is committed, the client wants capacity, and you need a full delivery team inside a window measured in weeks. The programme doesn’t get 16 months back just because planning took it.
That whipsaw produces 3 failures, and we see all of them.
Over-hiring before consent, where permanent heads are carried through a delay nobody budgeted for. Under-resourcing at mobilisation, where sites compete internally for the same Cx engineers because 3 schemes cleared committee in the same quarter. And paying the panic premium, where contractor day rates are negotiated from zero leverage, on a programme where every week costs revenue from uncommissioned capacity.
Generalist recruiters fail here, and not because they lack effort. They can’t anticipate a demand spike they don’t understand the shape of. A specialist partner who tracks live availability across the Cx and QA/QC market can tell you in March who’s finishing in July. That’s a different service from sending CVs when the call comes in.
The roles that change the odds
There are 2 tracks. Most developers focus only on consent capability.
Operators are building functions that barely existed in this sector 3 years ago: community affairs managers who own relationships with residents and parish councils from site selection onwards; public affairs leads who work with elected members and regulators; ESG leads who turn commitments on water, noise, and local employment into obligations a committee can hold the developer to; and consents leads who run the DCO process and its statutory consultation. These aren’t decorative ESG roles. They shape whether the scheme reaches committee with local credibility or local hostility.
Microsoft staffs a community affairs team within its Cloud Operations and Innovation organisation, coordinating with land development, permitting, energy, and construction. Most European developers aren’t there yet, and the objection data shows the cost. Inadequate community engagement was cited in 26 of Hoare Lea’s 33 applications, and it tracked with the longest delays.
Smaller developers won’t staff all 4 roles. Decide which capabilities you’ll own and which you’ll buy from an adviser before a refusal, not after it.
The other track matters more and gets less attention. Development managers and site-selection specialists sit closest to the planning fight, and they’re the hires that genuinely move the odds. A development lead who reads local political risk during site screening saves more than a public affairs manager brought in to defend a site you should never have optioned. That’s a workforce decision made at site selection, not after refusal.
Where these people actually come from
Almost nobody has 10 years of Data Center public affairs behind them because the function barely existed in this sector 3 years ago. Screen only for direct-sector experience and your shortlist will be empty.
Look instead at onshore wind and solar, energy from waste, nuclear new build, transmission, rail and airport expansion, and minerals and quarrying. Those candidates have spent careers running statutory consultation, sitting through hostile public meetings, and negotiating community benefit packages. Local-authority planning officers and former councillors bring something rarer still: an instinct for how a committee actually reaches a decision.
Test 4 things when you interview them. A scheme they took from opposition to approval, and what changed in the design because of consultation. How they handle a public meeting that turns against them. Whether they can read a local political map: which members swing, which groups have standing, and what the council needs. And whether they can say no internally to a development director who wants to announce before engaging.
The final question filters harder than the other 3 combined.
What this looks like by 2030
Roughly 100 GW of new capacity is anticipated between 2026 and 2030. Every gigawatt has to clear a committee somewhere, in front of people who’ve read about water consumption and rising electricity bills, and who understand that a 174 MW campus may employ fewer people than the retail park it replaces. They’ll judge the local trade-off, not the global case for compute. That changes the questions committees ask and the concessions they’ll accept.
The developers who get through will be the ones who stop treating consent as a gate to pass and start treating it as a workforce-planning input. Your hiring plan needs 2 versions from now on: a version that survives a 16-month wait, and another that mobilises a full delivery team in 6 weeks. Whichever way the committee votes, you’ll need the right version fast.
We spend most of our time on the mobilisation version: tracking live contractor availability, mapping who’s due to finish, and building a team that can move when consent lands. That is what working exclusively in this sector buys you, across project and construction management and design and commissioning alike. If you’ve got a scheme approaching committee and can’t name the people you’ll need in week 1, talk to our team.
