Can CADA procurement criteria reference EU standards and specifications?

Yes, under the proposed Cloud and AI Development Act (CADA), public procurement criteria can explicitly reference and reward EU-developed standards, specif

Summary Yes, under the proposed Cloud and AI Development Act (CADA), public procurement criteria can explicitly reference and reward EU-developed standards, specifications, software, and models. Article 32(3)(b) of the proposal empowers contracting authorities to award points for tenderers who "integrated technologies developed in the Union," specifically including the use of "standards, specifications, software, models or other technology developed in the Union." However, this is not a blanket preference for EU goods. As proposed, these "Union added value" criteria must remain ancillary and non-decisive, strictly linked to the subject matter of the contract, and cannot confer unrestricted freedom of choice. The Commission's explanatory memorandum suggests a maximum weighting of 15 out of 120 points for these criteria, ensuring that technical performance and price remain the primary drivers of the award.

Detail

The proposed Cloud and AI Development Act (CADA), COM(2026) 502 final, introduces a targeted framework for public procurement of cloud computing services and AI systems. Its objective is to reduce strategic dependencies on third-country providers and strengthen the European digital supply chain without violating the principles of the internal market. A central mechanism for achieving this is the "Union added value" criterion, established in Article 32.

The Specific Mandate of Article 32

Article 32(1) mandates that contracting authorities include non-price award criteria in public procurement procedures for innovative cloud computing services and AI systems. These criteria must evaluate the tenderer's contribution to the development of a European cloud and AI ecosystem.

Crucially, Article 32(3)(b) provides the specific legal basis for referencing EU-developed technical assets. It states that contracting authorities shall evaluate the extent to which:

"the tenderer has integrated technologies developed in the Union, including research and development results stemming from Union funded research and development programmes and makes use of tools, such as standards, specifications, software, models or other technology developed in the Union;"

This provision explicitly authorizes procurement documents to reward:

Standards: Technical standards developed within the Union (e.g., via CEN, CENELEC, or ETSI).
Specifications: Common specifications or other technical specifications originating in the Union.
Software and Models: Software components, AI models, or other technological tools developed within the Union.
R&D Results: Technologies stemming from Union-funded research and development programmes.

Strict Constraints: The "Ancillary" Rule

While Article 32(3)(b) opens the door for referencing EU assets, Article 32(2) imposes a rigorous set of constraints to ensure proportionality and compliance with EU public procurement law:

Linked to Subject Matter: Under Article 32(2)(a), the criteria must be "linked to the subject matter of the contract." A contracting authority cannot arbitrarily reference an EU standard that has no bearing on the specific cloud or AI service being procured.
No Unrestricted Freedom: Under Article 32(2)(b), the criteria must not "conferring unrestricted freedom of choice on the contracting authority." The evaluation must be objective and measurable.
Expressly Set Out: Under Article 32(2)(c), the criteria must be "expressly set out in the procurement documents or in the contract notice."
Ancillary and Non-Decisive: Under Article 32(2)(d), the criteria must be "ancillary and not decisive in the award of the contract."

The explanatory memorandum (Recital 67) provides concrete guidance on the "ancillary" nature of these criteria. It states that contracting authorities could consider a maximum weighting of 15 out of 120 points to be allocated to European added value. This ensures that the core technical and financial criteria remain the primary drivers of the award, while the Union added value acts as a secondary quality indicator or a tie-breaker.

Harmonization vs. Fragmentation

This framework addresses a specific market failure identified in the proposal. As noted in Recital 47, divergent national approaches to sovereignty criteria risk fragmenting the internal market. By establishing a harmonized Union-level framework for "Union added value" in Article 32, CADA aims to provide legal certainty for providers operating across borders while allowing public buyers to strategically support the European ecosystem. This complements, rather than replaces, the general principles of Directive 2014/24/EU.

What this means for you

For technology leaders, legal counsel, and public procurement officers, the proposed Article 32 creates a new compliance and strategic landscape.

For Cloud and AI Providers (SMEs and Large Enterprises)

Map Your "Union DNA": If you bid for public sector contracts, you must be able to prove the origin of your technology stack. This goes beyond your final product. You need to document the provenance of the standards, specifications, software, and models you integrate.
Leverage EU R&D: If your solution utilizes results from Horizon Europe, Digital Europe, or other Union-funded programmes, explicitly highlight this in your tender. Article 32(3)(b) specifically rewards "research and development results stemming from Union funded research and development programmes."
Prepare for the 15/120 Cap: Understand that even if you score maximum points on Union added value, it is capped. Your primary competitive advantage must still be technical performance, security, and cost. Do not rely solely on the "EU origin" of your standards to win a contract; it is a secondary differentiator.
Open Source as a Strategy: Since Article 32(3)(b) includes "software" and "models," and the proposal strongly encourages open source (Title IV, Chapter V), using EU-developed open-source components can be a strong way to demonstrate Union added value.

For Public Sector Procurement Officers

Draft Precise Criteria: When drafting tender documents, do not use vague language like "prefer EU standards." Instead, specify exactly which standards, specifications, software, or models are relevant to the subject matter. For example: "Preference will be given to solutions utilizing the EU-developed X specification for data interoperability."
Respect the Weighting Limit: Adhere to the guidance in Recital 67. Ensure that the "Union added value" criterion is weighted appropriately (e.g., max 15 points out of 120) so that it remains ancillary and not decisive. If a non-EU provider offers a superior technical solution, they must still be able to win.
Verify the Link: Before including a criterion, ask: "Is this standard/specification directly relevant to the performance of the cloud or AI service?" If the answer is no, it violates Article 32(2)(a) and could lead to legal challenges.
Transparency is Key: Ensure all criteria are "expressly set out" in the contract notice as required by Article 32(2)(c). Ambiguity in how points are awarded for EU integration will undermine the legitimacy of the procurement.

Common misconceptions

"Article 32 allows excluding non-EU providers." No. Article 32 establishes award criteria, not exclusion criteria. Providers from third countries remain eligible to participate. They may simply score lower on the "Union added value" criterion if they do not integrate EU-developed standards or technologies. Because the criterion is ancillary and not decisive, a third-country provider with superior technical and financial offers can still win the contract.

"Any EU standard can be referenced in a tender." No. Article 32(2)(a) requires that criteria be "linked to the subject matter of the contract." A contracting authority cannot reference an EU standard for, say, agricultural machinery in a tender for cloud storage services. The standard must be relevant to the specific performance or quality of the service being procured.

"EU added value is the primary factor in the award." No. Article 32(2)(d) explicitly states these criteria must be "ancillary and not decisive." The explanatory memorandum (Recital 67) reinforces this by suggesting a maximum weighting of 15 out of 120 points. Technical performance, security, and price must remain the dominant factors.

"Only the final software product counts." No. Article 32(3)(b) explicitly lists "standards, specifications, software, models or other technology." This means the use of EU-developed technical standards, architectural specifications, or even AI models developed in the Union can contribute to the score, even if the final proprietary software wrapper is developed elsewhere.

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