Summary Under the proposed Cloud and AI Development Act (CADA), data centre projects located within designated "data centre acceleration zones" benefit from a strict maximum permit-granting timeline of 12 months. This clock starts only when a comprehensive application is submitted. To facilitate this speed, the proposal introduces an aggregated baseline permit that pre-approves common zone-level requirements, and mandates that Member States treat these projects with the highest national significance status where such a legal category exists. These measures aim to eliminate regulatory bottlenecks and accelerate the deployment of critical computing capacity across the EU.
Detail
The Cloud and AI Development Act (CADA), as proposed in COM(2026) 502 final, represents a targeted intervention to address the "limited and geographically concentrated availability of computing capacity" in the EU. A primary barrier to expansion has been the fragmented and often protracted permitting processes for data centres. Article 13 of the proposal, titled "Facilitating administrative and permit-granting processes," establishes a harmonised framework to streamline these procedures specifically for projects deployed in data centre acceleration zones (designated under Article 10).
The 12-Month Maximum Timeline
The cornerstone of the accelerated deployment strategy is the introduction of a binding temporal limit on administrative decision-making. Article 13(5) explicitly states:
"The permit-granting procedure for data centre projects deployed in data centre acceleration zones shall not exceed 12 months, from the moment a comprehensive application has been submitted."
This provision creates a legal "ceiling" on the duration of the permitting process. However, the practical application of this rule involves several critical nuances that project developers must understand:
- Triggering the Clock: The 12-month period does not begin upon initial contact, site selection, or the submission of preliminary documents. It commences strictly "from the moment a comprehensive application has been submitted." This implies that the applicant bears the responsibility of ensuring the submission is complete. If an authority deems an application incomplete, the statutory clock does not start until the file is rectified and resubmitted as comprehensive.
- Member State Discretion for Shorter Limits: The proposal respects existing national efficiencies. Article 13(5) clarifies: "The time limit shall be without prejudice to any shorter time limits set by Member States." If a Member State already operates a 6-month or 9-month permitting regime for similar infrastructure, that stricter national limit remains in force. The CADA 12-month rule acts as a maximum cap to prevent excessive delays, not as a mandatory minimum duration that would override faster national processes.
- Geographic Scope: This accelerated timeline is not universal across the EU. It applies only to data centre projects deployed within data centre acceleration zones. These zones are specific territories designated by Member States under Article 10 where conditions for rapid deployment (such as grid capacity and environmental suitability) have been pre-assessed. Projects located outside these designated zones remain subject to standard national permitting timelines unless other specific EU or national laws apply.
The Aggregated Baseline Permit
To make the 12-month timeline legally and practically achievable, CADA introduces a mechanism to shift the administrative burden from individual projects to the zone level. Article 13(2) requires Member States to prepare and issue an aggregated baseline permit for each designated acceleration zone.
"For each designated acceleration zone, Member States shall prepare and issue an aggregated baseline permit authorising the deployment of data centres in that acceleration zone. This aggregated baseline permit shall cover the permits and administrative authorisations required for the data centre projects located within the acceleration zone, excluding installation-specific permits."
This mechanism fundamentally changes the permitting workflow:
- Zone-Level Pre-Approval: Before any specific data centre operator applies, the Member State must carry out all necessary procedures and assessments at the zone level. This includes environmental assessments, spatial planning procedures, and evaluations applicable to the area as a whole.
- Exclusion of Installation-Specific Permits: The baseline permit covers generic requirements (e.g., general environmental impact, zoning compliance). It explicitly excludes "installation-specific permits." These are unique to the individual project, such as specific structural engineering approvals, unique grid connection details, or site-specific safety measures.
- Reduced Redundancy: Consequently, individual data centre operators only need to obtain additional permits for activities falling outside the aggregated baseline. This significantly reduces the administrative load and potential for delays, as the bulk of the regulatory groundwork is completed in advance by public authorities.
Highest National Significance Status
To further prioritize these strategic projects within national administrative hierarchies, Article 13(5) addresses the status of data centre projects in national legal frameworks. It mandates:
"Where such a status exists in national law, data centre projects shall be allocated the status of highest national significance possible and be treated as such in permit-granting processes."
This provision aims to ensure that data centre projects in acceleration zones are fast-tracked within existing national prioritization schemes. If a Member State has a legal category for projects of "national importance," "strategic significance," or similar designations that grant priority in planning queues, judicial reviews, or resource allocation, CADA requires that data centre projects in acceleration zones be assigned this top-tier status.
However, the proposal includes a crucial safeguard for national legal sovereignty: "This paragraph shall apply only where such status exists in national law and shall not create an obligation for Member States to introduce such status." Therefore, if a Member State's legal system does not currently have a concept of "highest national significance," they are not required to create a new legal category solely for the purpose of CADA.
Role of Single Information Points
While not a direct component of the timeline itself, the efficiency of the application process is supported by Article 12, which requires Member States to designate single information points for data centre operators. These points assist operators throughout the entire lifecycle of the project. Their role is critical in ensuring that the "comprehensive application" submitted to trigger the 12-month clock is actually complete and correctly formatted, thereby avoiding unnecessary delays caused by administrative errors or missing documentation.
What this means for you
For CTOs, infrastructure architects, real estate developers, and SMEs evaluating the practical impact of CADA, the permit timeline changes represent a significant shift in risk management and project planning.
1. Predictable Scheduling for Investors The 12-month maximum provides a degree of certainty that has been historically lacking in EU infrastructure projects. For investors and developers, this cap reduces the risk of indefinite regulatory limbo. When modeling financial returns, cash flow, and ROI, you can now factor in a worst-case 12-month permitting period for projects in acceleration zones, rather than the open-ended timelines often seen in traditional planning processes. This predictability is a key enabler for capital deployment.
2. Strategic Location Selection is Critical The benefits of the accelerated timeline are geographically restricted. To access the 12-month cap and the aggregated baseline permit, your data centre must be located in a designated data centre acceleration zone. As an architect or site selector, you must verify whether your preferred location is within a zone designated by the Member State under Article 10. Building outside these zones means you may not benefit from the streamlined processes, potentially extending your time-to-market significantly and increasing regulatory risk.
3. Preparation for "Comprehensive" Applications The clock starts only upon submission of a "comprehensive application." This places the onus on you to ensure your submission is flawless. Incomplete applications will not trigger the 12-month deadline, effectively pausing the process until rectification. You should leverage the single information points (Article 12) early in your planning phase to validate your documentation. For SMEs, which may have fewer dedicated legal and regulatory resources, engaging with these single points is crucial to avoid costly delays and ensure the statutory clock starts on day one.
4. Leverage the Aggregated Baseline When planning your technical and environmental impact assessments, review the aggregated baseline permit for your target zone. Since many generic permits are already covered, you can focus your resources on the specific, installation-related permits that remain. This can reduce both the cost and complexity of your compliance strategy, allowing for a more efficient allocation of engineering and legal resources.
5. Monitor National Implementation While CADA sets the EU-wide framework, the actual implementation depends on Member States. You must monitor whether your target Member State has existing shorter time limits (which would benefit you further) and whether it has a legal concept of "highest national significance." If it does, ensure your project is formally classified under this status to maximize your priority in the permit queue. If it does not, you cannot rely on this specific prioritization mechanism.
Common misconceptions
Misconception 1: The 12-month limit applies to all data centres in the EU. This is incorrect. The 12-month maximum permit-granting period under Article 13(5) applies only to data centre projects deployed within designated data centre acceleration zones. Projects located outside these zones are not automatically subject to this timeline and may face longer, traditional permitting processes.
Misconception 2: The 12 months starts from the first inquiry or expression of interest. No. The timeline begins "from the moment a comprehensive application has been submitted." Preliminary discussions, site visits, or incomplete submissions do not start the clock. The application must be deemed comprehensive by the relevant authority to trigger the statutory deadline.
Misconception 3: Member States must create a "highest national significance" status. This is a common misunderstanding. Article 13(5) states that projects should be allocated this status "Where such a status exists in national law." It explicitly clarifies that it "shall not create an obligation for Member States to introduce such status." If a country's legal framework lacks this category, the requirement does not force them to invent it.
Misconception 4: The aggregated baseline permit covers all permits for a data centre. The aggregated baseline permit covers permits and administrative authorisations required for the zone, but it explicitly excludes "installation-specific permits." You will still need to obtain individual permits for aspects of your specific data centre design or operation that fall outside the pre-approved baseline.
Misconception 5: CADA is already in force. CADA is a proposal (COM(2026) 502 final). It has not yet been adopted by the European Parliament and Council. The timelines and mechanisms described here are "as proposed" and may change during the legislative procedure. Current national laws apply until CADA is formally enacted and its application date arrives.
Related
- How to apply for a data centre permit in a CADA acceleration zone: Article 12 & 13 guide
- How does a public body share cloud or data centre services in the EuroCloud Federation?
- How does a Member State designate a data centre acceleration zone under CADA?
- How a data centre project becomes a CADA strategic project
- How does a data centre project become a CADA strategic project, and what does it gain?
This is general information about a draft EU regulation, not legal advice.