Data-centre power infrastructure raises land-take questions London planners should track

A new Planetizen explainer asks when a power company can take land for data-centre infrastructure. The item is not presented in the available feed as a London case, and the source-page text was not readable here, so this draft should be treated as a cautious context piece rather than a report on a specific UK planning decision.

The London relevance is the data question behind the headline: when large digital, energy or utility schemes need new substations, cable routes, easements or access land, residents and planning teams need to know where the powers come from, which land is affected, and whether the evidence is in a planning file, a statutory process, a land register entry or a separate utility procedure.

For London Urbanism Desk readers, the safest editorial angle is not to import a non-UK legal explanation. It is to set out the checks London residents, councillors, planners and built-environment professionals should make when data-centre-related electricity infrastructure appears in local records.

What the source does and does not establish

The available source information confirms only that Planetizen published an explainer titled “When can a power company take your land for data center infrastructure?” by Diana Ionescu on 21 July 2026. The feed summary repeats the title and gives no case study, jurisdiction, company name, statutory route, planning authority, map reference or affected site.

That means the article cannot be used on its own to claim that any London landowner is facing compulsory acquisition, that any London data centre requires a new power corridor, or that a UK electricity company has changed its approach. It also cannot establish the legal test for land-take in England and Wales.

What it can do is flag a wider urban-planning issue: data centres are not only buildings. They can be associated with electricity upgrades, cooling systems, vehicle access, security perimeters and construction logistics. Some of those effects may sit outside the most visible planning drawings if they are handled through utility consents, land rights or later technical approvals.

Key facts

Definitions London readers should separate

A “data centre” normally refers to a building or campus used to house servers and related equipment. In planning terms, the impacts may include building scale, energy demand, servicing, noise, heat rejection, backup power, security treatment and traffic during construction and operation.

“Power infrastructure” is a broader category. It may include substations, transformers, underground or overhead cables, grid connections, access tracks, control equipment and temporary construction compounds. A data-centre application may show some of this directly, but grid works can also appear in separate documents or through another consenting route.

“Land-take” should not be used loosely. It can mean outright acquisition, temporary occupation, rights of access, easements for cables, protective strips, wayleaves or construction-stage possession. These are materially different for residents and businesses. A permanent substation site is not the same as a temporary works area; a buried cable easement is not the same as the purchase of a whole plot.

For London coverage, the exact stage matters. A proposal, consultation, planning application, committee resolution, legal agreement, compulsory purchase process and completed transfer are separate events. A news story should not collapse them into a single claim that land “will be taken” unless the primary document says that.

Where to look in London records

The first check is the relevant borough planning register. Search by address, applicant, site boundary, neighbouring streets and keywords such as “data centre”, “substation”, “grid connection”, “transformer”, “cable route”, “energy centre”, “backup generator” and “temporary construction compound”. The planning statement, design and access statement, transport assessment, noise report, energy statement and environmental documents may each show different parts of the scheme.

The second check is the plan set. Red-line boundaries show the application site; blue-line boundaries can indicate other land owned by the applicant. Drawings may reveal whether a substation is inside the main site, on a separate plot, or expected to connect through land not included in the application boundary. If the cable route is absent, that absence is itself a reporting point, not a gap to fill with assumptions.

The third check is committee material. Officer reports often summarise objections, statutory consultee responses, recommended conditions and obligations. For a data-centre or utility-heavy scheme, look for conditions on energy infrastructure, construction traffic, noise, hours of work, servicing, landscaping, biodiversity, flood risk and public-realm reinstatement.

The fourth check is whether the issue sits outside the planning register. Some land-rights, grid-connection or statutory undertaker processes may not be fully visible in ordinary planning documents. If a source claims land can be acquired or occupied, the article should identify the exact legal process and document trail before presenting the claim as fact.

Why this belongs in Data and Maps

This is a data story because the public impact depends on boundaries, routes, definitions and document status. A map of a proposed building is not necessarily a map of all enabling infrastructure. A planning application boundary is not necessarily the same as a landownership boundary. A grid connection route may have a different geography from the development site.

For London readers, compatible comparisons require consistent definitions. Counting “data centres” by planning application is different from counting operational facilities, electricity substations, proposed grid connections or sites with backup generation. Comparing boroughs without checking those definitions can mislead readers about where infrastructure pressure actually falls.

Time period also matters. A live planning application, a lapsed permission and an operational facility should not be counted together unless the dataset clearly labels their status. The same applies to consultation-stage utility works and approved construction works. A map that mixes stages can be useful for scanning pressure points, but it should not be presented as a map of confirmed development.

The practical method is to build a source trail for each site: planning reference, decision stage, applicant, site boundary, associated utility drawings, committee date, conditions, legal agreements if available, and any separate statutory notices. Where the file is incomplete, say so.

What to watch next

If a London data-centre or grid-infrastructure proposal prompts concern about land rights, the next checks should be primary documents rather than commentary. Confirm the planning authority, the planning reference, the land parcels affected, the current decision stage and the specific power being relied upon. Ask whether the infrastructure is inside the main application, part of a separate application, or subject to another statutory process.

Residents should also check consultation deadlines and committee dates, because objections about route choice, construction impacts, public-realm reinstatement and noise usually need to be made within a defined process. Built-environment professionals should be precise about what is known: energy demand, grid connection, land rights and planning permission are related, but they are not interchangeable.

This draft should be held for further reporting if a London-specific case is identified. The current source is useful as a prompt for scrutiny, not as evidence of a confirmed London land-take dispute.

Source: Planetizen News, “When can a power company take your land for data center infrastructure?” https://www.planetizen.com/features/138029-when-can-power-company-take-your-land-data-center-infrastructure