A datacentre outside Chapelhall in North Lanarkshire draws around 25 megawatts from the grid today. Its backers describe something else entirely: energy parks generating more than a gigawatt, renewable infrastructure rivalling the country’s largest onshore windfarm, power on the scale of a small nuclear reactor. The planning applications on file cover a few square kilometres; the ambition described would need many times that. The government calls it a showpiece of British AI. Somewhere between the press release and the land registry, the project stopped describing what exists and started describing what its backers hope will one day be approved, financed and built. That gap is not a Scottish curiosity. It is the same gap UK organisations inherit every time they buy an AI system on the strength of a claim rather than a proof.

TL;DR

• A pattern now runs through British AI policy: the announcement has become the deliverable, and the infrastructure is left to catch up afterwards.
• The NHS is living a version of it, rolling out ambient voice tools and the Palantir-built Federated Data Platform on the premise that capacity and governance will develop alongside adoption rather than before it.
• The risk is not the technology, which may well work. It is the sequencing, letting political and vendor timetables set the pace at which readiness gets verified.
• For any buyer, the correction is the same: separate what is built from what is merely permitted or promised, and demand independent evidence before deployment, not after.

The announcement has become the deliverable

The Lanarkshire story matters because it is not really about one datacentre. It is about a habit. A site or a programme is designated nationally significant. Developers describe capability in the present tense that properly belongs in the conditional. Scrutiny, when it comes, arrives after the announcement rather than before it. Correspondence obtained from Scottish officials shows they understood the power problem privately whilst endorsing the scheme publicly. That is not fraud. It is something more familiar: a policy culture in which saying a thing has been built does most of the political work of building it.

For businesses watching UK AI unfold, this is the useful lesson hiding inside a regional planning row. The distance between announced capability and installed capacity is where risk accumulates, and it is almost never priced into the announcement. A gigawatt of demand does not conjure a gigawatt of supply, and a compelling vendor deck does not conjure the integration, compute and governance the deck assumes.

Strategic Reality: In an infrastructure project, the announced-versus-built gap shows up as delay. In an AI deployment, it shows up as a system doing real work before anyone has verified it can do that work safely. The gap is the same shape; the consequences are not.

The NHS is buying AI on the same terms

The health service should recognise this pattern, because it is currently reproducing it. Ambient voice technology, which transcribes and summarises clinical conversations, is being rolled out across trusts on the strength of pilot results and vendor assurance. The MHRA’s new National Commission is still working out how agentic AI systems should be regulated and who is accountable when they fail. The Federated Data Platform, developed with Palantir, was marketed on a comparable premise: rather than requiring proof beforehand, the infrastructure and administration would mature in tandem with adoption.

In each case the technology may well work. That is not the question. The question is whether the underlying capacity, in compute, integration and clinical governance, exists at the scale being promised, or whether it exists mainly in the same rhetorical register as an energy park that is still a set of planning documents. Adoption is being treated as the thing that produces readiness, when readiness is supposed to be the precondition for adoption.

Critical Context: A datacentre that cannot secure its power supply experiences delay, which harms investors and a government keen to prove its development zones work. An AI system deployed into maternity units or acute wards on the assumption that governance will catch up carries a different order of risk entirely.

This is where the NHS comparison earns its weight. The estate is not a greenfield site in Lanarkshire. It is a live system already operating close to failure in workforce and financial terms, with reviews from Ockenden to the Lampard Inquiry showing how thin the margins for error already are. Sir Jim Mackey’s accountability drive has concentrated on trust performance against contracts. It has said considerably less about whether the same discipline applies to the vendors and national programmes whose claims about readiness are, at this stage, no better independently verified than the Chapelhall energy parks.

The structural fault, not the technology

There is a version of this argument that overreaches, and it is worth naming the limit. NHS AI adoption is not simply Lanarkshire with stethoscopes. The comparison is structural, not literal. What connects a Scottish datacentre and a hospital transcription tool is not the technology but the sequencing: the tendency to let political and commercial timetables, rather than engineering reality, set the pace at which infrastructure gets verified. Where that tendency exists, the correction is identical in both cases. Before the rollout rather than after it, someone has to establish what is actually constructed, what is only permitted, and what is merely an artist’s rendition of a turbine.

For a UK business, the translation is direct. Every AI procurement contains three categories that vendors are incentivised to blur together.

The vendor that cannot cleanly sort its own offer into these three columns is telling you where the readiness gap sits.

What to demand before deployment, not after

The discipline the Lanarkshire story is missing is cheap to apply and expensive to skip. It is fundamentally a sequencing decision: move verification in front of the announcement rather than behind it.

Take Action: Before signing, require the vendor to demonstrate the specific capability you are buying, at something approaching your real volume, in an environment you can inspect. A pilot proves the technology can work once. A reference deployment proves it works repeatedly under load, which is the only claim that survives contact with production.

The right questions scale with organisational maturity, but the spine is constant.

• Early-stage adopters should insist on a single principle: no capability enters a live workflow until it has been evidenced independently of the vendor selling it. That alone prevents most readiness-gap failures.
• Established programmes should build the built-permitted-promised split into procurement templates, and require named accountability for the promised column, so that when a conditional capability slips, responsibility does not evaporate into a press release.
• Regulated organisations should treat vendor readiness claims as they would any other unverified control: assume they are absent until tested, and document the test. In health, finance and law, “the supplier assured us” is not a defence a regulator accepts.

Reality Check: Independent verification is not free. It adds weeks to procurement and requires people who can interrogate a technical claim. Organisations that treat that cost as friction to be removed are precisely the ones announcing capabilities they have not yet built.

Four traps hiding in the readiness gap

The pattern is easy to describe and hard to avoid, because each part of it feels reasonable in the moment.

The pilot that masquerades as proof. A successful pilot demonstrates possibility, not reliability. The failure mode is generalising from a controlled trial with motivated users to an estate-wide rollout with none of those conditions. Mitigation: treat a pilot as the start of evidence-gathering, and define in advance what a scaled deployment must show before it earns trust.

Governance promised in the future tense. “Accountability frameworks are being developed” is an admission that they do not yet exist. Deploying into that vacuum means the system is live before the rules governing its failures are written. Mitigation: make operational governance a gate, not a workstream running in parallel with adoption.

The correlated-but-not-identical interest. A vendor’s reputational risk and yours move together, which is reassuring until they diverge. The supplier is protecting its risk surface first; your regulatory exposure is yours alone. Mitigation: map explicitly which failures the vendor is contractually liable for and which land on you.

Announcement momentum. Once a capability has been announced publicly, admitting it is not yet built becomes politically costly, so the incentive is to keep asserting readiness and hope the engineering catches up. Mitigation: decouple the internal go-live decision from any external commitment, so that operational reality, not communications, sets the date.

The question worth asking of yourself

Britain does not have a shortage of ambition in artificial intelligence. It has a shortage of institutions willing to check that ambition against the concrete, the grid connection, the integration test, before the announcement goes out. Lanarkshire will eventually reveal whether its gap can be closed with political will alone. Most organisations cannot afford to wait for that answer before asking the same question of their own AI plans.

The strategic value here is not scepticism for its own sake. It is a sequencing habit that costs a few weeks of diligence and saves the far larger cost of unwinding a capability that was deployed before it was real. Three things make it work.

• Verification precedes announcement. The readiness claim is tested before it is repeated, internally or externally.
• The three columns stay separate. Built, permitted and promised are never allowed to blur, in a vendor deck or in your own board papers.
• Accountability survives the roadmap. When a promised capability slips, a named owner carries it, rather than the responsibility dissolving into the original announcement.

The next time an AI capability is presented to your organisation in the confident present tense, the single most valuable question is the one the Chapelhall planners were not asked in time: is this built, or is it an artist’s rendition of a turbine?

Source and further reading

This analysis responds to “The NHS Cannot Build Its AI Future On Unbuilt Power”, published by the Distilled Post Editorial Team on 8 July 2026 (distilledpost.com). The original piece sets out the Lanarkshire datacentre case and the NHS parallel in detail; the strategic framework for UK organisations, including the built-permitted-promised procurement test, is Resultsense’s own.

Resultsense makes sense of AI in the UK for professionals and businesses. For more analysis of how UK organisations should read AI infrastructure and vendor claims, explore our insights and news coverage, or get in touch with a tip or a question.