← Back to all briefings
AI 6 min read Published Updated Credibility 93/100

EU AI Act

The deadline for GPAI providers to submit to EU AI Act codes of practice was May 2025. If you are offering general-purpose AI models in the EU, you should already have your transparency commitments and code of practice submissions in place. The AI Office is reviewing compliance.

Kodi C.

Editor & Research Lead

Accuracy-reviewed by the editorial team

AI pillar illustration for Zeph Tech briefings
AI deployment, assurance, and governance briefings

Nine months after Regulation (EU) 2024/1689 entered into force, is the deadline for GPAI providers to submit Commission-endorsed codes of practice under Article 56(5). The teams are validating Annex XI documentation—training data summaries, compute usage, copyright safeguards, and evaluation protocols—while cross-checking systemic-risk triggers that could lead to Article 55 designations. The submission package includes downstream deployment guidance so customers can satisfy Article 52 transparency and risk duties.

Regulatory checkpoints

  • Code submission. Providers must attest to compliance with the approved code of practice or face direct application of Article 53 requirements, including expanded documentation and risk mitigation duties.
  • Annex XI completeness. Ensure transparency summaries cover training data provenance, evaluation coverage, energy usage, and policies for watermarking or content provenance.
  • Systemic-risk triggers. Providers must monitor indicators such as scale of deployment, compute intensity, and dual-use potential that could prompt systemic-risk designation and heightened oversight.

Aligning your controls

  • Configuration management. Store submitted code commitments, evaluation artifacts, and mitigation plans in controlled repositories for future audits.
  • Downstream assurance. Synchronize customer-facing documentation, service-level terms, and support processes with the commitments captured in the code of practice.
  • Monitoring handoff. Establish playbooks for updating the Commission and national authorities when model changes affect the submitted Annex XI metrics.

What teams should do

  • Host customer briefings explaining the code-of-practice scope, residual risks, and escalation paths for serious incidents.
  • Integrate code commitments into roadmap governance so future model iterations trigger re-validation before release.
  • Coordinate with legal, policy, and commercial teams on how code obligations affect licensing, indemnity, and partnership agreements.

Code development participation

GPAI providers should actively participate in industry code development through recognized bodies and associations. Document contributions to working groups, submitted comments on draft provisions, and positions on key compliance questions. Active engagement shapes favorable code interpretations and shows good-faith compliance efforts to the AI Office.

Multi-provider coordination

Foundation model providers serving multiple downstream deployers should coordinate documentation standards and support commitments. Establish common templates for model cards, risk disclosures, and update notifications that satisfy code requirements while enabling efficient scaling across customer bases.

Regulatory backdrop

This development represents a significant milestone in the broader regulatory environment affecting ai initiatives globally. Organizations must understand not only the immediate requirements but also the interconnected policy frameworks that influence implementation strategies and compliance obligations.

The regulatory environment continues to evolve as policymakers balance innovation enablement with risk mitigation and stakeholder protection. This particular development reflects ongoing efforts to establish clear governance frameworks that support responsible adoption while maintaining appropriate safeguards against potential misuse or unintended consequences.

Stakeholders across multiple sectors should consider how this development intersects with existing compliance obligations under frameworks such as GDPR, CCPA, SOC 2, ISO 27001, and industry-specific regulations. The interconnected nature of modern regulatory requirements means that addressing one area often has implications for related compliance domains.

What to consider

Organizations seeking to align with these requirements should begin with a thorough gap analysis comparing current capabilities against the specified standards. This assessment should encompass technical infrastructure, organizational processes, personnel competencies, and governance mechanisms.

A phased implementation approach typically proves most effective, beginning with foundational elements before progressing to more advanced capabilities. Priority should be given to areas presenting the greatest risk exposure or compliance urgency, while building sustainable practices that can adapt to evolving requirements.

Key implementation factors include resource allocation, timeline management, stakeholder coordination, and change management. Organizations should establish clear governance structures to oversee implementation progress and ensure accountability across relevant business units and functional areas.

Technical implementation should follow security-by-design principles, incorporating appropriate controls from the outset rather than attempting to retrofit security measures after deployment. This approach typically reduces overall implementation costs while improving security posture and compliance outcomes.

Managing risk

Effective risk management requires systematic identification, assessment, and treatment of risks associated with this development. Organizations should use established frameworks such as NIST RMF, ISO 31000, or COBIT to structure their risk management approach.

Risk identification should consider technical vulnerabilities, operational disruptions, regulatory penalties, reputational impacts, and strategic implications. Each identified risk should be assessed for likelihood and potential impact, with appropriate risk treatment strategies developed for high-priority items.

Continuous monitoring capabilities are essential for detecting emerging risks and evaluating the effectiveness of implemented controls. Organizations should establish key risk indicators and reporting mechanisms that provide timely visibility into risk exposure across relevant domains.

Risk tolerance thresholds should be established at the organizational level, with clear escalation procedures for risks that exceed acceptable levels. This governance framework ensures appropriate oversight while enabling agile responses to changing risk conditions.

Roadmap to compliance

Developing a structured compliance roadmap helps organizations systematically address requirements while managing resource constraints and competing priorities. The roadmap should establish clear milestones, responsible parties, and success criteria for each compliance objective.

Near-term priorities typically focus on addressing imminent compliance deadlines and high-risk gaps. Medium-term initiatives build sustainable compliance capabilities through process improvements, technology investments, and workforce development. Long-term strategic planning ensures continued alignment as requirements evolve.

Documentation requirements should be addressed throughout the compliance journey, establishing evidence trails that demonstrate due diligence and support audit activities. Organizations should implement document management practices that ensure accessibility, version control, and appropriate retention.

Regular compliance assessments help organizations verify progress against roadmap objectives and identify areas requiring additional attention. These assessments should incorporate both internal reviews and independent third-party evaluations where appropriate.

Who is affected

This development affects multiple stakeholder groups, each with distinct interests, concerns, and information needs. Effective stakeholder management requires understanding these perspectives and developing appropriate engagement strategies.

Internal stakeholders including executive leadership, board members, operational teams, and employee populations require tailored communications that address their specific concerns and responsibilities. Clear role definitions and accountability structures support effective internal coordination.

External stakeholders such as customers, partners, regulators, and industry peers also have legitimate interests in organizational responses to this development. Transparent communication and demonstrated commitment to compliance build trust and support collaborative relationships.

Investor and analyst communities focus on governance, risk management, and compliance capabilities as indicators of organizational resilience and long-term value creation. Organizations should consider how their response to this development affects external perceptions and stakeholder confidence.

Infrastructure needs

Technology plays a critical enabling role in addressing the requirements associated with this development. Organizations should evaluate current technology capabilities against anticipated needs and develop enhancement plans where gaps exist.

Core technology considerations typically include data management systems, security infrastructure, monitoring and analytics platforms, and integration capabilities. Organizations should assess whether existing technology investments can be used or whether new capabilities are required.

Automation opportunities should be identified and prioritized based on efficiency gains, error reduction, and scalability benefits. Robotic process automation, artificial intelligence, and machine learning technologies may offer valuable capabilities for specific use cases.

Technology vendor relationships should be evaluated to ensure appropriate support for compliance requirements. Contractual provisions, service level agreements, and vendor security practices all merit attention as part of technology governance.

The regulatory and policy environment continues to evolve rapidly, with several emerging trends likely to influence future developments in this area. Organizations should maintain awareness of these trends and build adaptive capabilities that support ongoing compliance.

Regulatory convergence across jurisdictions creates both challenges and opportunities for multinational organizations. While harmonization efforts reduce compliance complexity in some areas, divergent national approaches require careful planning in others.

Technology evolution continues to create new capabilities and new risks requiring regulatory attention. Organizations should anticipate that current requirements will be supplemented or modified as policymakers respond to technological changes and emerging best practices.

Industry collaboration through standards bodies, professional associations, and informal networks provides valuable opportunities for sharing implementation experiences and influencing policy development. Active engagement in these forums supports more effective compliance outcomes.

Similar analysis

Additional analysis covering similar themes.

Continue in the AI pillar

Return to the hub for curated research and deep-dive guides.

Visit pillar hub

Latest guides

  • AI Governance Implementation Guide

    Operationalise the EU AI Act, ISO/IEC 42001, and U.S. OMB M-24-10 requirements with accountable inventories, controls, and reporting workflows.

  • AI Incident Response and Resilience Guide

    Coordinate AI-specific detection, escalation, and regulatory reporting that satisfy EU AI Act serious incident rules, OMB M-24-10 Section 7, and CIRCIA preparation.

  • AI Procurement Governance Guide

    Structure AI procurement pipelines with risk-tier screening, contract controls, supplier monitoring, and EU-U.S.-UK compliance evidence.

Coverage intelligence

Published
Coverage pillar
AI
Source credibility
93/100 — high confidence
Topics
EU AI Act · General-purpose AI · Codes of practice
Sources cited
3 sources (eur-lex.europa.eu, digital-strategy.ec.europa.eu)
Reading time
6 min

Further reading

  1. Regulation (EU) 2024/1689 — Articles 52 to 57 on general-purpose AI — eur-lex.europa.eu
  2. EU AI Act timeline and next steps — digital-strategy.ec.europa.eu
  3. Commission Recommendation (EU) 2024/1792 on safety of generative AI systems — eur-lex.europa.eu
  • EU AI Act
  • General-purpose AI
  • Codes of practice
Back to curated briefings

Comments

Community

We publish only high-quality, respectful contributions. Every submission is reviewed for clarity, sourcing, and safety before it appears here.

    Share your perspective

    Submissions showing "Awaiting moderation" are in review. Spam, low-effort posts, or unverifiable claims will be rejected. We verify submissions with the email you provide, and we never publish or sell that address.

    Verification

    Complete the CAPTCHA to submit.