A Groundbreaking Is Not a Permit

Large data center projects increasingly reach the public domain through a groundbreaking ceremony, a capacity headline or a capital announcement. None of those events proves that construction can proceed without interruption. For investors, operators and developers, data center permit due diligence has therefore become a core development-readiness test rather than a legal box to tick after site selection.

The distinction became unusually visible in West Java this week. Reuters reported on 30 September 2026 that the provincial governor ordered BDx Data Centers to halt construction at its Jatiluhur campus until the required permits were obtained and the environmental impact assessment was completed. The order followed a 22 September groundbreaking for a campus reported at 640 MW. The public sequence is a useful reminder: an announced capacity, a ceremony and even early works do not establish the same thing as a complete, enforceable permission stack.

My view is simple. When I assess a site, I do not ask whether it has “the permit.” I ask which decision authorises which activity, which conditions remain outstanding, and which evidence would survive a lender, tenant or investment committee review.

The myth: one approval unlocks the site

Data centers sit across several regulatory systems at once. Land-use consent may establish the permitted use of a site, while separate decisions govern environmental effects, water abstraction or discharge, emergency generation, road access, building control and grid works. The exact stack changes by jurisdiction, but the commercial consequence is consistent: one positive decision cannot silently substitute for the others.

The European Commission’s guidance on environmental impact assessment states that major building or development projects in the EU must be assessed for environmental impact before consent is granted. In England, official Environment Agency guidance for developers explicitly recognises that a development may require both planning permission and an environmental permit. A current consultation for an Amazon data center environmental permit in Didcot also separates matters covered by environmental permitting from the location decision handled through land-use planning.

This is why the binary labels “permitted” and “unpermitted” are too crude for serious data center market intelligence. A useful record needs to identify the authority, application or decision reference, scope, status, dates, conditions and appeal exposure. It must also show what has not yet been evidenced.

Evidence first: build the permit stack

The practical starting point is a permit matrix tied to the project’s physical scope. The matrix should distinguish campus-level permissions from building-level approvals and temporary works from permanent operation. It should also separate reported milestones from documents that can be opened, dated and checked.

At minimum, I expect to see five evidence groups.

First comes land and planning: title or control, zoning or land-use designation, planning permission, approved site plan, height and massing limits, access rights and phasing conditions. A planning approval for a broad campus concept may still leave reserved matters or building-specific submissions outstanding.

Second is environmental approval. That includes the screening opinion, impact assessment where required, consultation record, mitigation commitments and any separate permits for emissions, backup generation, noise, water discharge or hazardous materials. The West Java authorities published technical detail on 28 September about water allocation for the BDx project, including an initial requirement of 6,000 cubic metres per day and a projected maximum flow over time. That is important public evidence, but it is not itself proof that every required environmental decision has been issued.

Third is power. A connection offer, executed agreement, substation consent, easements and energisation programme are different milestones. Our earlier note on why data center capacity is not one number applies equally here: campus electrical capacity, utility import capacity and usable IT load should never be merged.

Fourth is the construction and safety package: building permits, fire strategy acceptance, emergency-services conditions, contractor notices and the exact authorisation for enabling works. A ceremonial start does not clarify whether the activity is demolition, earthworks, piling or full structural construction.

Fifth is the operating layer: licences, environmental monitoring, water and waste agreements, generator-testing limits and completion or occupancy certificates. Those items can sit beyond financial close, but their critical path must be visible before underwriting relies on an operational date.

Data center permit due diligence needs a conditions register

The decision letter is only the beginning. Conditions can require pre-commencement submissions, third-party approvals, design revisions, monitoring plans or infrastructure works. Some are routine; others can stop a programme.

For each condition, I would record the responsible party, evidence required, submission date, approving authority, dependency and status. The most important field is often not “approved,” but “approved for what?” A discharge covering one building or phase should not be represented as a campus-wide clearance.

This discipline connects directly to development-readiness milestones. It also reduces a common investment error: treating a future administrative step as if it were already bankable. The same principle applies to grid-upgrade costs and allocation, where an apparently positive connection position may still carry construction, security or reinforcement obligations.

Turn documents into a decision gate

Good due diligence does not produce a folder of PDFs and stop. It converts evidence into a decision: proceed, proceed with conditions, reprice, redesign or pause.

I use three tests. Is the evidence current and traceable to the competent authority? Does its scope match the capacity, phasing and activity being underwritten? Are the remaining conditions compatible with the claimed schedule and budget?

The last test is where market context matters. Cushman & Wakefield’s EMEA Data Centre Update reported a large development pipeline alongside operational stock. Pipeline volume is useful, but the commercial value of any individual megawatt depends on delivery evidence. A 100 MW project with a coherent permit, power and construction path may be more relevant to a tenant than a much larger announced campus whose critical approvals remain unresolved.

The decision gate should therefore combine the permit matrix with the site-qualification evidence framework, power status, delivery programme and cost exposure. For projects relying on onsite generation, our analysis of behind-the-meter power shows why a power concept can introduce new fuel, emissions and operating approvals rather than remove permitting risk.

What investors and tenants should request

Before crediting a project’s announced delivery date, I would request the authority-issued documents and reference numbers, not only a developer presentation. I would also ask for a live conditions register, a phase-by-phase consent map, evidence of challenge or appeal periods, and a schedule that links each approval to procurement and construction.

This is not an argument for delaying investment until every minor condition is closed. It is an argument for naming the residual risk correctly. A project can be attractive while still carrying permitting risk; what matters is whether that risk is visible, bounded and owned.

The same standard improves portfolio comparison. PowerlandMap’s coverage framework and access workflow are designed to separate reported facts, dated evidence and analyst interpretation. That separation matters when different markets use different approval systems and public-record quality varies.

The conclusion: verify the right to build

The durable lesson from recent events is not that one jurisdiction is unusually difficult. It is that development announcements move faster than documentary evidence. Data center permit due diligence should verify the right to perform each critical activity, the conditions attached to that right and the path from today’s status to operation.

A groundbreaking proves that a project has entered the public narrative. It does not prove planning, environmental, power and construction readiness. Investors, tenants and developers should price the difference before the site reaches a point where the only available decision is to stop.

*Matthieu Gallego — Founder, PowerlandMap*

For a source-backed review of a market, site or development pipeline, request PowerlandMap access.