Summary The obligation to designate a data centre acceleration zone is conditional. As proposed, Article 10(1) of CADA requires a Member State to designate at least one acceleration zone "[w]here data centre capacity is being deployed within the territory of [that] Member State". The duty is triggered by deployment activity rather than applying automatically to all Member States in every case. CADA is a proposal and not yet in force, so this is what would apply if adopted.

Detail

The proposed Cloud and AI Development Act (CADA) would introduce a harmonised framework to accelerate the deployment of data centre capacity across the EU. A central pillar is the "data centre acceleration zone" (the proposal's shorthand: "acceleration zone") — an area where permitting, sustainability and grid coordination would be streamlined for data centre projects.

The obligation to establish these zones is framed conditionally.

A conditional obligation under Article 10(1)

Article 10(1) of the CADA proposal states:

"Where data centre capacity is being deployed within the territory of a Member State, that Member State shall designate at least one data centre acceleration zone ('acceleration zone') within its territory by [P.O. insert the date of entry into force of this Regulation plus 6 months]."

As proposed, this creates a trigger: the duty to designate arises "where data centre capacity is being deployed." In practice:

  1. Deployment triggers the duty. Where data centre capacity is being deployed in its territory, a Member State must designate at least one acceleration zone.
  2. No deployment, no immediate duty. Where data centre capacity is not being deployed, the specific obligation under Article 10(1) would not be triggered. That said, CADA's broader purpose is to stimulate deployment across the Union to close the capacity gap, so this is best read as activity-dependent rather than a permanent exemption.

Designation criteria and deadline

For Member States subject to the obligation, Article 10(1) requires that they "consider" several aspects when designating zones, namely:

  • the location and dimension of the site or area, and the minimum and maximum size of facilities that could be built there;
  • available and future power grid capacity, and the possibility and conditions for on-site storage and clean energy generation;
  • available and future network connectivity capacity;
  • the capacity of the zone to support the phasing out of legacy copper networks;
  • available and future facilities that can reuse data centre waste heat;
  • all the measures taken to accelerate the granting of the necessary permits within the zone;
  • the preference for reusing brownfield sites over greenfield sites;
  • the ability of the site or area to function sustainably, particularly as regards preventing or minimising environmental impacts and supporting the reduction of carbon emissions and its climate resilience.

The deadline in the draft's placeholder wording is the date of entry into force plus six months — underscoring the urgency the Commission attaches to closing the compute capacity gap.

Broader context: monitoring and strategic projects

While the zone obligation is conditional, other parts of Title III apply more broadly. Article 15 would establish a mechanism for the Commission to monitor the Union's compute capacity gap, including identifying "underserved areas" in cooperation with Member States that could subsequently be used as acceleration zones. Separately, Article 14 would allow the Commission to designate certain data centre projects as "strategic projects" where they meet at least two of the listed criteria — for example supporting essential public-sector functions or contributing to grid stability. Designation as a strategic project is a distinct mechanism from the acceleration-zone duty, though data centre projects deployed in acceleration zones are themselves treated as strategic projects within the meaning of Article 14 of the proposed Regulation on speeding-up environmental assessments (Article 13(1)).

What this means for you

For in-house counsel and compliance officers in the data centre sector, the conditional nature of the obligation matters for planning.

Assessing Member State obligations

Consider whether your target Member States are deploying data centre capacity. Where a Member State is not deploying capacity, it may not yet have designated a zone, which could mean:

  • Less streamlined permitting. Projects outside acceleration zones may not benefit from the aggregated baseline permit or the 12-month permit-granting limit in Article 13.
  • Less predictability. Without a designated zone, the local framework for data centres may remain more fragmented.

Conversely, where a Member State is deploying capacity, it would be bound to designate at least one zone. Monitor national announcements to identify zones early, as they would offer advantages in permitting speed and regulatory clarity.

Strategic site selection

When selecting sites, prioritising designated acceleration zones can offer advantages, because these zones are designed to provide:

  • Faster permitting. Article 13(5) provides that the permit-granting procedure for projects in acceleration zones shall not exceed 12 months from a comprehensive application.
  • Coordinated infrastructure. Designation requires consideration of grid connectivity and waste-heat reuse (Article 10(1)).
  • Defined sustainability requirements. Under Article 11, Member States would set sustainability requirements in zones using specified key performance indicators.

Engagement with national authorities

Engage early with national competent authorities to understand how they interpret "data centre capacity being deployed" — for example whether planned, not just under-construction, projects count — and whether and where a Member State intends to designate a zone.

Common misconceptions

Misconception 1: Every Member State must designate an acceleration zone in all circumstances. Reality: Article 10(1) ties the duty to the deployment of data centre capacity. The obligation is triggered by that activity rather than applying unconditionally.

Misconception 2: Acceleration zones are the only places data centres can be built. Reality: Zones are designed to facilitate deployment, but the proposal does not prohibit data centres outside them. Such projects may, however, face longer timelines and less regulatory support.

Misconception 3: The 12-month permitting limit applies to all data centre projects. Reality: The 12-month limit in Article 13(5) applies specifically to projects deployed within data centre acceleration zones. Projects outside designated zones are subject to national timelines, which may be longer.

Related

This is general information about a draft EU regulation, not legal advice.