How can a region get itself flagged as a compute capacity gap area under CADA?

Summary A region cannot unilaterally "flag" or self-declare itself as a compute capacity gap area under the proposed Cloud and AI Development Act (CADA). Instead, the identification of these gaps is a centralized, data-driven process led exclusively by the European Commission. Under Article 15 of the proposal, the Commission is mandated to monitor available compute capacity, the volume of demand, and the resulting deficit across the Union. This monitoring is conducted "in cooperation with the Member States." Once the Commission identifies specific "underserved areas" based on this data, those areas become eligible to be designated by Member States as data centre acceleration zones, unlocking streamlined permitting and strategic project status.

Detail

The proposed Cloud and AI Development Act (CADA), COM(2026) 502 final, addresses the critical shortage of computing capacity in the EU by establishing a rigorous monitoring framework. This framework is designed to move beyond fragmented national assessments and provide a unified Union-wide view of infrastructure health. The mechanism for identifying where capacity is lacking is codified in Article 15, titled "Monitoring the capacity gap."

The Commission's Exclusive Mandate Under Article 15

The core of the capacity gap identification process lies in Article 15(1), which explicitly assigns the responsibility of identification and monitoring to the European Commission. The text states:

"For the purpose of monitoring progress in the achievement of the objectives of Decision (EU) 2022/2481, the Commission shall identify and monitor: (a) the compute capacity available in the Union, including edge computing capacity; (b) the volume of demand for data centre capacity; (c) the size of the capacity gap and underserved areas that could be identified by the Commission, in cooperation with the Member States, and subsequently used as acceleration zones for the deployment of data centre capacity."

This provision establishes three distinct metrics that the Commission must track:

Available Capacity: This includes not only traditional data centre capacity but also edge computing capacity, ensuring that distributed, low-latency infrastructure is accounted for in the Union's total supply.
Volume of Demand: The Commission must assess the current and projected demand for data centre capacity across the Union.
The Capacity Gap and Underserved Areas: Crucially, the Commission must calculate the deficit (the gap) and specifically identify "underserved areas."

The phrase "in cooperation with the Member States" in Article 15(1)(c) is the only direct link for regional actors to influence this process. It implies that while the Commission holds the final authority to define and flag a region as "underserved," it relies on data, reports, and insights provided by national authorities to do so accurately. A region cannot simply submit a form to the Commission; it must ensure its national competent authority includes its specific data in the reports submitted to the Commission.

From "Underserved Area" to "Acceleration Zone"

The primary strategic value of being identified as an "underserved area" under Article 15 is the direct pathway it creates for regulatory acceleration. The text of Article 15(1)(c) explicitly notes that these identified areas "could be identified by the Commission... and subsequently used as acceleration zones for the deployment of data centre capacity."

This creates a two-step mechanism:

Identification: The Commission, using data from Member States, flags a geographic area as having a significant capacity gap (an "underserved area").
Designation: Member States are then empowered and expected to designate these specific areas as data centre acceleration zones under Article 10.

Article 10(1) requires Member States to designate at least one data centre acceleration zone "where data centre capacity is being deployed within the territory of a Member State." While the proposal does not explicitly state that only Commission-identified underserved areas can be acceleration zones, the logic of Article 15 suggests that these identified areas are the primary candidates for such designation to address the Union's capacity deficit.

Once an area is designated as an acceleration zone, it benefits from a suite of facilitation measures:

Streamlined Permitting: Under Article 13, the permit-granting procedure for data centre projects in acceleration zones shall not exceed 12 months from the submission of a comprehensive application.
Aggregated Baseline Permits: Article 13(2) allows Member States to issue an "aggregated baseline permit" for the entire zone, covering common permits required for data centre projects, excluding only installation-specific permits.
Strategic Project Status: Projects located in these areas are more likely to qualify as "data centre strategic projects" under Article 14. Specifically, Article 14(1)(e) lists as a criterion for strategic designation: "the project addresses a major shortage of compute capacity in an area identified as having such a shortage under Article 15."

The Role of Edge Computing and Regional Disparities

The inclusion of "edge computing capacity" in Article 15(1)(a) is significant for regions that may not have the grid capacity or land availability for massive hyperscale data centres but are critical for low-latency applications. The monitoring framework is designed to capture these distributed assets, ensuring that regions with high edge node potential are not overlooked in the capacity gap analysis.

Furthermore, the proposal acknowledges that capacity is geographically concentrated. The explanatory memorandum notes that the "deployment of data centres across the Union is lagging and remains concentrated in a limited number of established hubs, creating structural imbalances." Article 15 is the tool designed to expose these imbalances. By identifying "underserved areas," the Commission aims to guide investment away from saturated hubs and toward regions where capacity is scarce, thereby "ensuring balanced geographic deployment across Member States."

The Cooperative Mechanism: How Regions Influence the Process

Since the Commission cannot monitor every local grid constraint or industrial demand spike in real-time without national input, the "cooperation" mentioned in Article 15(1)(c) is the critical channel for regional influence.

Member States are required to report on their national strategies and capacity deployment under Article 7. These strategies must include "measures to support the deployment of data centre capacity" and "measures to invest in high-intensity computing infrastructure." When Member States compile the data required for the Commission's monitoring under Article 15, they must aggregate regional data.

Therefore, for a region to be flagged as a capacity gap area:

Data Collection: The region must document its specific capacity deficits, unmet demand from local industries, and latency issues.
National Reporting: This data must be formally reported to the national competent authority responsible for digital infrastructure or energy planning.
Inclusion in National Strategy: The data should be reflected in the Member State's national cloud and AI strategy under Article 7, which is monitored by the Commission.
Commission Synthesis: The Commission synthesizes this national data with Union-wide metrics to formally identify the gap and flag the region as "underserved" in its monitoring reports.

What this means for you

For regional authorities, public-sector bodies, and local economic development agencies, the CADA proposal fundamentally changes how infrastructure gaps are addressed. You cannot apply for a "capacity gap" label; you must prove the gap exists through data to your national government.

1. Data is Your Leverage

Your primary task is to ensure your region's data is visible at the national level. If your region is suffering from a lack of compute capacity, you must document:

Current Capacity: The exact amount of available IT load (MW) and edge nodes.
Demand: Specific requests from local industries, research institutions, or public bodies that cannot be met locally.
Barriers: Grid constraints, permitting delays, or land shortages that prevent new deployment.

Without this granular data, the national authority cannot accurately report to the Commission, and your region risks being overlooked in the Article 15 monitoring process.

2. Prepare for Acceleration Zone Obligations

If your region is identified as an underserved area and subsequently designated as an acceleration zone, you will face new obligations. Under Article 10, you must:

Designate the Zone: Ensure the area is formally designated as an acceleration zone within six months of the regulation's entry into force.
Establish Single Information Points: Under Article 12, you must designate a single information point to assist data centre operators with permits, spatial planning, and grid connections.
Conduct Energy Analysis: Under Article 10(2), you must conduct a comprehensive analysis of current and future energy needs and their impact on greenhouse gas emissions for the zone.

3. Leverage Strategic Project Status

Once your region is flagged as having a capacity gap, any data centre project proposed there gains a significant advantage. Under Article 14(1)(e), a project that "addresses a major shortage of compute capacity in an area identified as having such a shortage under Article 15" meets a key criterion for strategic project designation.

Strategic projects benefit from:

Enhanced Support: Potential access to Union funding and support measures.
Streamlined Oversight: A dedicated framework for monitoring and support.
Permitting Priority: While the 12-month limit applies to all acceleration zones, strategic projects may receive additional prioritization in grid connection and permitting queues.

4. Align with National Strategies

Ensure your regional development plans are fully coherent with the Member State's national cloud and AI strategy under Article 7. Inconsistencies between regional needs and national strategy can lead to data being filtered out during the reporting process. Your region's capacity gap must be explicitly mentioned in the national strategy's measures for "deployment of data centre capacity" to ensure it is captured in the Commission's Article 15 monitoring.

Common misconceptions

Misconception 1: Regions can self-declare as capacity gap areas. Reality: The power to identify capacity gaps lies exclusively with the European Commission under Article 15. While regions provide the data, the formal identification and classification of an area as "underserved" is a Commission-led activity conducted in cooperation with Member States. There is no application form for a region to submit directly to the Commission.

Misconception 2: Being a capacity gap area automatically grants funding. Reality: Identification as a capacity gap area primarily triggers regulatory facilitation, such as the ability to be designated as an acceleration zone (Article 15(1)(c)) and the potential for strategic project status (Article 14). While this makes deployment faster and more attractive to investors, it does not automatically provide financial grants. Funding depends on separate Union programmes and the specific criteria of the strategic project designation.

Misconception 3: The Commission monitors only total EU capacity, not regional disparities. Reality: Article 15(1)(c) explicitly requires the Commission to identify "underserved areas." The proposal recognizes that capacity is geographically concentrated, creating structural imbalances. The monitoring framework is specifically designed to detect these regional disparities to ensure a balanced deployment of compute capacity across the Union.

Misconception 4: Edge computing is excluded from capacity gap assessments. Reality: Article 15(1)(a) explicitly includes "edge computing capacity" in the metrics the Commission must monitor. This is significant for regions that may not have the grid capacity for large hyperscale data centres but can support distributed, low-latency edge nodes. These areas are fully part of the capacity gap analysis.

Misconception 5: Only large hyperscale data centres count toward the capacity gap. Reality: The definition of "compute capacity" in the proposal is broad, encompassing "edge computing capacity" and "data centre capacity." The monitoring under Article 15 is designed to capture the full spectrum of infrastructure, ensuring that regions with high demand for edge nodes are not ignored in favor of only hyperscale hubs.

Official sources

Digital Decade Policy Programme (Decision (EU) 2022/2481)

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