A large megawatt figure is a starting point, not a complete investment story. Understanding an AI infrastructure project means asking what workload it could serve, why its location matters, what has been authorised and what can actually be delivered.
This series approaches those questions in four steps. Read in order for the broader argument, or go directly to the planning or power piece for a specific claim.
1. Start with the competitive question
Can the UK compete for the next wave of AI infrastructure?
Different workloads place different demands on location, connectivity and electricity costs. This opening analysis considers the UK’s position against selected overseas examples and includes an electricity-cost sensitivity tool. It is not a league table of investment returns.
Read for: why the relevant question is not simply which country announces the most megawatts, but which locations can serve which workloads at what cost.
2. Separate the project claims
Why data-centre project status is harder to verify than headline MW suggests
Four examples show why planning decisions, power arrangements, customer commitments and delivery forecasts need different evidence. A source may establish one narrow fact while leaving other important questions unanswered.
Read for: how to replace a broad status label with a precise statement of what is known, who says it and what remains unverified.
3. Read planning consent within its scope
Planning is not delivery: reading data-centre consent properly
A resolution, permission, reserved-matters approval and condition approval answer different questions. The article uses two Slough applications to explain why an application’s identity, the relevant phase and the actual decision matter more than a generic portal label.
Read for: why consent is not proof of construction, why an application withdrawal is not necessarily abandonment of a site, and why procedural windows should not be mistaken for completion dates.
4. Unpack “power secured”
What does “power secured” actually mean for a data centre?
Manor Farm, Wapseys Wood and Pinewood illustrate three different evidence problems: attributed supply arrangements, alternative routes and a timetable tied to an unverified starting event. The article keeps incoming supply, generation and IT capacity separate.
Read for: the difference between an application, a reported agreement and energisation, and why a future power tranche does not establish operating IT load.
The common thread: match the claim to the evidence
Across the series, the same questions recur: which project or phase, which capacity measure, which source, which date and what exactly was verified? Planning, power and physical delivery are distinct dimensions, not interchangeable steps on one universal status ladder.
Unknown does not mean absent, zero or adverse. Equally, a forecast is not an observed outcome, and an applicant’s statement does not become independent confirmation merely because it appears in an official document.
For the wider collection, browse all Smarter BI articles.