Summary Under the proposed Cloud and AI Development Act (CADA), Article 32(2)(d) mandates that non-price award criteria evaluating a tenderer's contribution to the European cloud and AI ecosystem must be "ancillary and not decisive" in the award of the contract. This means these sovereignty-focused criteria cannot be the determining factor that wins the contract; they must remain subordinate to core technical and financial performance requirements. Contracting authorities must ensure that the weighting of these criteria does not override the primary objective of securing the most economically advantageous tender (MEAT). While these criteria can differentiate between closely matched bids, they cannot act as a veto or a protectionist barrier that displaces a technically superior or more cost-effective offer.

Detail

The proposed Cloud and AI Development Act (CADA), COM(2026) 502 final, introduces a specific mechanism to foster the EU's digital sovereignty without disrupting the single market or violating international trade obligations. Article 32, titled "Union added value," requires contracting authorities to include non-price award criteria in public procurement procedures for innovative cloud computing services and AI systems. These criteria evaluate the tenderer's contribution to strengthening the Union's digital supply chain, integrating Union technologies, and delivering services using hardware designed or manufactured in the Union.

However, to prevent these strategic objectives from distorting competition, Article 32(2) imposes strict constraints on their application. Specifically, Article 32(2)(d) states that these non-price award criteria must be "ancillary and not decisive in the award of the contract."

The Legal Meaning of "Ancillary and Not Decisive"

The phrase "ancillary and not decisive" serves as a critical legal safeguard. It ensures that the policy goal of reducing dependence on third-country providers does not supersede the fundamental principles of EU public procurement: transparency, non-discrimination, and the pursuit of the most economically advantageous tender.

  1. Ancillary (Subordinate): The criteria must be secondary or supplementary to the main subject matter of the contract. The primary purpose of the procurement remains the acquisition of a specific cloud service or AI system that meets defined technical and functional needs. The "Union added value" assessment is an additional layer of evaluation, not the core purpose of the purchase. It evaluates how the service is delivered (e.g., using EU-designed chips or software) rather than what is being delivered (e.g., compute capacity, latency, security features). As Article 32(2)(a) requires, these criteria must be "linked to the subject matter of the contract," reinforcing their supplementary nature.
  2. Not Decisive (Non-Determinative): The criteria cannot be the tie-breaker or the primary driver that determines the winner of the contract. A tenderer with superior technical performance and better pricing must not lose the contract solely because a competitor scores higher on these ancillary sovereignty criteria. If the difference in technical or financial merit is significant, the "Union added value" criterion cannot override it. The core technical and financial criteria must retain the primary weight in the decision-making process.

Interaction with MEAT Scoring and Weighting

In EU public procurement, the most economically advantageous tender (MEAT) principle requires authorities to balance quality and price. Article 32(2)(d) ensures that the "Union added value" criteria do not distort this balance. Contracting authorities must design their evaluation methodologies so that the weight assigned to these ancillary criteria is proportionate.

While CADA does not specify a maximum numerical weight in the article text itself, the requirement that the criteria be "not decisive" implies a structural limit. If a non-EU provider offers a technically superior and significantly cheaper solution, they should not be disqualified simply because an EU-based provider scores higher on supply chain localization criteria, unless the difference in technical/financial merit is negligible. The "Union added value" acts as a differentiator among otherwise comparable bids, not as a veto power for non-compliant supply chains.

Recital 67 of the proposal provides a concrete illustration of this proportionality. It suggests that contracting authorities could consider a "maximum weighting of 15 out of 120 points" to be allocated to European added value within the overall evaluation methodology. This specific example (12.5%) underscores the legislative intent that these criteria remain subordinate. A weighting that approaches or exceeds the weight of the core technical or price criteria would likely violate the "not decisive" requirement of Article 32(2)(d).

Procedural Safeguards

To comply with Article 32(2), contracting authorities must ensure that these criteria meet four cumulative conditions:

  • Linked to the subject matter: The criteria must relate directly to the cloud or AI service being procured (Article 32(2)(a)).
  • No unrestricted freedom of choice: The criteria must not give the authority arbitrary discretion (Article 32(2)(b)).
  • Expressly set out: The criteria and their weighting must be clearly defined in the procurement documents or contract notice (Article 32(2)(c)).
  • Ancillary and not decisive: The criteria cannot be the determining factor for the award (Article 32(2)(d)).

By explicitly setting out these criteria in advance, authorities provide legal certainty to tenderers. The "ancillary" nature must be visible in the scoring grid. If the weighting of the "Union added value" criteria is disproportionately high (e.g., equal to or greater than the price or technical score), it may arguably become "decisive," thereby violating Article 32(2)(d) and potentially conflicting with the EU's obligations under the WTO Government Procurement Agreement (GPA).

What this means for you

For in-house counsel, procurement officers, and cloud providers, navigating Article 32 requires careful calibration of procurement strategies and tender responses.

For Contracting Authorities (Public Sector)

  • Design Your Scoring Matrix Carefully: Ensure that the weight assigned to "Union added value" criteria is clearly subordinate to technical and financial criteria. Avoid scenarios where the sum of ancillary criteria outweighs the core performance metrics. A safe approach, as hinted in Recital 67, is to cap these criteria at a modest percentage (e.g., 10–15%) of the total score.
  • Document the Rationale: Clearly articulate in your procurement documents why these criteria are ancillary. Demonstrate that the primary goal remains the efficient delivery of cloud/AI services, with supply chain resilience as a secondary, supportive objective.
  • Monitor for Disproportionality: Regularly review award decisions to ensure that the "not decisive" rule is being applied. If a tenderer with inferior technical specs wins solely due to high "Union added value" scores, you risk legal challenges for violating the MEAT principle and the ancillary requirement.
  • Transparency: Ensure the criteria are "expressly set out" in the tender documents (Article 32(2)(c)) to avoid claims of arbitrary decision-making.

For Cloud and AI Providers (Private Sector)

  • Assess Your Supply Chain: Even if these criteria are "ancillary," they can still be significant differentiators in competitive bids. Map your supply chain to identify opportunities to score points on Union-designed hardware or software integration.
  • Prepare for Scrutiny: Be ready to provide evidence of your "Union added value" claims, such as documentation of hardware origins or software development locations, as these will be part of the quality evaluation.
  • Challenge Unfair Applications: If you believe a contracting authority has treated these criteria as "decisive" (e.g., by weighting them so heavily that they override technical superiority), you may have grounds for a procurement review. The "ancillary" requirement is a legal shield against protectionist overreach.

Deadlines and Penalties

  • Timeline: Member States must monitor and report on the use of these criteria under Article 33. While CADA does not set a specific penalty for misapplying the "ancillary" weight in the text of Article 32 itself, incorrect application could lead to contract annulment under national procurement laws or infringement procedures by the European Commission.
  • Compliance: Ensure that your internal procurement policies are updated to reflect Article 32's requirements before CADA enters into force. Training procurement officers on the distinction between "ancillary" and "decisive" is crucial to avoid costly legal disputes.

Common misconceptions

Misconception 1: "Ancillary" means the criteria are irrelevant.

  • Reality: "Ancillary" does not mean negligible. These criteria can still carry significant weight (e.g., 10–15% of the total score, as suggested in Recital 67) and can influence the award, especially among closely competing bids. They are just not the primary determinant.

Misconception 2: Providers with non-EU supply chains are automatically disqualified.

  • Reality: Article 32(2)(d) ensures that these criteria are not decisive. A provider with a non-EU supply chain can still win the contract if their technical and financial offer is superior. The criteria act as a bonus for EU-aligned supply chains, not a ban on others.

Misconception 3: Contracting authorities have full discretion to weight these criteria as they see fit.

  • Reality: Article 32(2)(b) explicitly states that these criteria must not confer "unrestricted freedom of choice" on the contracting authority. The weighting must be objective, transparent, and proportionate to the contract's subject matter. Arbitrary or excessive weighting that makes the criteria "decisive" is prohibited.

Misconception 4: This applies to all public procurement.

  • Reality: Article 32 specifically applies to "public procurement procedures for innovative cloud computing services and AI systems." It does not apply to standard, non-innovative IT procurements or goods outside the scope of CADA.

Related

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