where data centres get built and why, what planning can actually do about it, how data sovereignty shapes location decisions, and who carries the costs and who carries the benefits.
A data centre does not arrive in a community the way a new shop or a housing development does. It arrives preceded by years of private land acquisition, technical feasibility work, grid capacity assessment, and commercial negotiation, before a planning application is ever submitted. By the time the public sees a planning notice, many of the significant decisions about the facility have already been made.
This is not unique to data centres. It is how large industrial development works. But it is worth naming clearly, because it shapes the practical question of where influence can actually be exercised. The planning process offers a formal mechanism for objection and modification, but it operates on a proposal that has already been optimised for the developer's objectives. Understanding the earlier decisions makes it possible to engage at the point where they can be influenced.
Data centre location decisions are driven by a hierarchy of constraints and preferences. Understanding this hierarchy is useful for any community that wants to understand why a facility is proposed for a particular location, and what arguments might actually carry weight.
What does not appear prominently in this hierarchy: community preference, water stress of the local area, proximity to schools or residential areas, or any direct consideration of local environmental capacity. These factors may be relevant at planning, but they are not the developer's primary framework.
Planning permission in the UK is the primary point of democratic engagement with data centre development. Local planning authorities must assess applications against local development plans, national planning policy, and material planning considerations, which include economic, social, and environmental impacts.
Data sovereignty refers to the principle that data generated and collected within a given legal jurisdiction should be stored and processed within that jurisdiction, subject to its laws. It sounds like a technical compliance matter. It is increasingly a geopolitical one.
this is a condensed version of the lesson. the full version, with sources and figures, is being rewritten in this format. if you'd like an early read, the feedback form is open.