How should a bidder respond to Union added value criteria in a CADA tender?

Under the proposed Cloud and AI Development Act (CADA), bidders responding to public tenders for innovative cloud and AI services must address specific "Un

Summary Under the proposed Cloud and AI Development Act (CADA), bidders responding to public tenders for innovative cloud and AI services must address specific "Union added value" criteria as mandated by Article 32. These non-price award criteria require bidders to demonstrate how their offer strengthens the EU digital ecosystem through four specific dimensions: strengthening the digital supply chain, integrating EU technologies, contributing to security of supply via innovation, and the origin of critical hardware. Crucially, Article 32(2) stipulates that these criteria must be linked to the subject matter, expressly set out in procurement documents, and remain ancillary and not decisive in the award of the contract. Bidders should provide concrete, subject-specific evidence of EU-based components and R&D, avoiding generic corporate claims, while ensuring their core technical and financial offers remain the primary drivers of the bid.

Detail

The proposed Cloud and AI Development Act (CADA), COM(2026) 502 final, introduces a targeted mechanism to leverage public procurement to foster a resilient European cloud and AI ecosystem. Article 32 establishes a requirement for contracting authorities to include non-price award criteria in public procurement procedures specifically for "innovative cloud computing services and AI systems." These criteria are designed to evaluate a tenderer's contribution to the development of a European cloud and AI ecosystem, moving beyond price and basic technical compliance to assess strategic alignment with Union sovereignty goals.

For bidders, the ability to effectively respond to these criteria is a critical differentiator. However, the legislative text imposes strict boundaries on how these criteria function. Article 32(2) clarifies that while these criteria allow authorities to evaluate the extent of a tenderer's contribution, they must be "ancillary and not decisive in the award of the contract." This ensures that the primacy of technical and financial criteria directly connected to performance is preserved, preventing Union added value from becoming a disguised barrier to entry or a sole determinant of the winner.

Mapping the Response to Article 32(3) Dimensions

To maximize scoring potential, a bidder's response must be structured to directly address the four cumulative dimensions explicitly listed in Article 32(3). Contracting authorities are required to evaluate the extent to which the tenderer meets these specific conditions:

Strengthening the Digital Supply Chain (Article 32(3)(a)) Bidders must demonstrate how their offer contributes to strengthening the digital technology supply chain within the Union. The text explicitly highlights the use of "software or hardware designed or manufactured in the Union." A robust response should quantify the proportion of the proposed stack that relies on EU-originated components versus third-country dependencies. Evidence might include a breakdown of software modules developed by EU entities or hardware components sourced from Union manufacturers.
Integration of EU Technologies (Article 32(3)(b)) This dimension requires evidence of the integration of technologies developed in the Union. The scope is broad, encompassing not only proprietary technology but also "research and development results stemming from Union funded research and development programmes." Bidders should identify specific tools, standards, specifications, software, models, or other technologies developed in the Union that are integral to the service. Referencing specific Horizon Europe or Digital Europe Programme projects that underpin the technology can provide strong evidentiary weight.
Innovation for Security of Supply (Article 32(3)(c)) The bid must articulate how the innovation required to deliver the service contributes to "strengthening the security of supply and the development of a European cloud and AI ecosystem." This is a qualitative assessment of strategic value. Bidders should explain how their specific innovation reduces dependency on critical third-country technologies, enhances the resilience of the public sector's digital infrastructure, or fosters the development of the European ecosystem. The focus is on the strategic impact of the innovation, not just its technical novelty.
Hardware Origin and Feasibility (Article 32(3)(d)) Bidders must demonstrate the extent to which the service is delivered through "critical computing, storage and networking hardware components designed and/or manufactured in the Union." The legislation acknowledges market realities and technical constraints. It explicitly states that where full EU manufacturing is "not feasible," bidders can still qualify by using hardware from a third country, provided it is demonstrated that such hardware "contributes to strengthening the security of supply and the development of a European cloud and AI ecosystem." This allows for a nuanced argument where non-EU hardware is justified by its role in a broader, resilient EU supply chain (e.g., through open architecture, local maintenance, or lack of vendor lock-in).

Subject-Matter-Linked Evidence and Procedural Requirements

The effectiveness of a bidder's response depends heavily on adherence to the procedural constraints set out in Article 32(2). These constraints dictate not only what evidence is required but also how it must be presented.

Link to Subject Matter (Article 32(2)(a)) The non-price award criteria must be "linked to the subject matter of the contract." This is a critical compliance point. Bidders cannot rely on generic corporate ESG reports, broad statements about the company's EU presence, or historical achievements unrelated to the specific tender. The evidence must be specific to the cloud or AI service being procured. For instance, if the tender is for an AI training platform, the bid must specify which EU-designed processors will be used for that specific workload, not just the company's general server fleet.
Transparency in Documents (Article 32(2)(c)) The criteria must be "expressly set out in the procurement documents or in the contract notice." Bidders must carefully review the tender dossier to identify the exact weighting, evaluation metrics, and specific definitions of "Union added value" used by the contracting authority. The response should mirror the language and structure of the tender documents to ensure the evaluators can easily map the evidence to the criteria.
Ancillary Nature (Article 32(2)(d)) The criteria must be "ancillary and not decisive in the award of the contract." This provision serves as a safeguard for market competition. It means that while a strong Union added value response can differentiate a bid, it cannot override a significantly better technical or financial offer. Bidders should not over-invest resources in this section at the expense of core technical compliance or pricing competitiveness. The strategy should be to provide sufficient evidence to score well, but not to the point of diminishing the core value proposition.

Strategic Evidencing for Bidders

To respond effectively, cloud service providers and data centre operators should prepare a dedicated annex or section in their tender that addresses each of the four dimensions in Article 32(3) with specific, verifiable evidence.

For Software/Stack (Article 32(3)(a) & (b)): Provide a detailed software bill of materials (SBOM) or a technology stack map that highlights EU-originated components. Explicitly reference any Union-funded R&D projects (e.g., Horizon Europe, Digital Europe) that underpin the technology. Include documentation showing the integration of Union-developed standards or specifications.
For Hardware (Article 32(3)(d)): Supply documentation on the origin of servers, accelerators, and networking gear. If using non-EU hardware, provide a robust rationale explaining how it still contributes to EU security of supply. This could include evidence of local manufacturing partnerships, open-source hardware designs, or the absence of restrictive licensing that would hinder EU autonomy.
For Innovation/Security (Article 32(3)(c)): Draft a narrative explaining how the proposed solution reduces dependency on critical third-country technologies. Highlight specific features that enhance the resilience of the public sector's digital infrastructure. Connect the innovation directly to the "security of supply" objective, demonstrating how it mitigates specific risks identified in the tender.

What this means for you

For cloud service providers and data centre operators, Article 32 of the CADA proposal represents a formalized advantage for EU-centric offerings. While the criteria are ancillary, they provide a structured way to compete against non-EU hyperscalers who may offer lower prices but less strategic alignment with EU sovereignty goals.

You should audit your current supply chain and technology stack to identify EU-based elements. Prepare standardized evidence packages that can be easily adapted to different tender requirements. Ensure your technical proposals clearly distinguish between core service delivery (which remains the decisive factor) and Union added value (which serves as a tie-breaker or differentiator). Remember that the criteria must be linked to the specific contract subject matter; generic claims will likely be scored poorly or rejected as non-compliant with Article 32(2)(a).

Common misconceptions

"Union added value is the deciding factor." No. Article 32(2)(d) explicitly states that these criteria are "ancillary and not decisive." A bidder with a superior technical solution and more competitive price can still win, even with a lower Union added value score. Do not sacrifice core competitiveness to maximize this score.

"Only fully EU-made hardware qualifies." Incorrect. Article 32(3)(d) provides a fallback for hardware that is not designed or manufactured in the Union. If you use third-country hardware, you can still score points if you can demonstrate that it contributes to strengthening the security of supply and the development of a European cloud and AI ecosystem.

"General corporate responsibility statements are sufficient." No. Article 32(2)(a) requires criteria to be linked to the subject matter. Broad statements about the company's EU presence are insufficient. Evidence must be specific to the cloud or AI service being tendered.

"This applies to all cloud procurement." Not necessarily. Article 32 specifically targets "innovative cloud computing services and AI systems." Standard, non-innovative cloud procurement may not trigger these specific Union added value criteria, though other procurement rules may still apply.

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