Skip to content

AI Act timeline: key dates 2026-2028 after the Digital Omnibus

Updated 7 October 2026: the Digital Omnibus (Regulation (EU) 2026/1744, published in the Official Journal on 24 July 2026 and in force since 27 July) postponed the Annex III high-risk obligations to 2 December 2027. 2 August 2026 is still a real date — but only for the Article 50 transparency obligations, not for the bulk of the Regulation. If you haven't yet done an inventory of your organization's AI systems, it is still the moment to start — only the deadline is no longer what it was.

Quick reference: every AI Act date on one pageSee the AI Act timeline in our glossary, and what the Digital Omnibus changed.

What exactly changes on 2 August 2026

The AI Act entered into force on 1 August 2024, but its application has been phased. Some blocks have been in force since 2025 (prohibitions, AI literacy, general-purpose AI model obligations). What changes on 2 August 2026, after the Digital Omnibus, is the transparency obligations of Article 50 (except the technical marking in Art. 50(2) for systems already on the market, deferred to 2 December 2026), and full enforcement powers (national regulatory sandboxes were pushed back to 2 August 2027 by the Digital Omnibus). The full Annex III high-risk regime, which was due to apply that same day, has been postponed to 2 December 2027.

That was the official reading until the Digital Omnibus was adopted. With Annex III postponed to December 2027, 2026 stops being the year of the "big leap" for high-risk — but Article 50 keeps its original calendar, so August 2026 is not a date to ignore, only one to understand properly.

Definitive AI Act timeline

These are the key dates you need to know and communicate internally:

DateWhat comes into force
2 Feb 2025 Prohibitions under Art. 5 (unacceptable risk AI systems) + AI literacy obligations under Art. 4.
2 Aug 2025 Obligations for GPAI model providers (Chapter V), institutional governance (AI Office operational), and enforcement regime at Member State level.
2 Aug 2026 Art. 50 transparency (except Art. 50(2), deferred to Dec 2026 for systems already on the market), and full enforcement powers (national regulatory sandboxes were pushed back to 2 August 2027 by the Digital Omnibus). Annex III high-risk, which was due here, was postponed to Dec 2027 (Digital Omnibus).
2 Dec 2026 Two new Article 5 prohibited practices (AI that generates non-consensual intimate imagery or child sexual abuse material), added by the Digital Omnibus, and end of the transition for marking synthetic content from generative systems already on the market (Art. 50(2)).
2 Aug 2027 Deadline for GPAI models placed on the market before 2 August 2025 to comply, and for each Member State to have its regulatory sandbox in place (postponed by the Digital Omnibus).
2 Dec 2027 (previously 2 Aug 2026) Full high-risk regime for Annex III systems (Arts. 8–15): risk management, technical documentation, human oversight. Postponed by the Digital Omnibus.
2 Aug 2028 (previously 2 Aug 2027) Application to high-risk systems embedded in products regulated by EU harmonized legislation (Annex I). Postponed by the Digital Omnibus.

The four risk categories, in one phrase each

The Regulation organizes AI systems into four risk levels, and everything else hangs off them:

  • Unacceptable risk: directly prohibited. Subliminal manipulation, government social scoring, real-time biometric identification in public spaces (with limited exceptions), among others. Applicable since February 2025.
  • High risk: systems that may affect fundamental rights or safety. Education, employment, essential services, justice, border control, critical infrastructure. This is where the bulk of compliance sits: Arts. 8 to 15 and the full system lifecycle (risk management, data governance, technical documentation, automatic logging, transparency, human oversight, robustness and accuracy).
  • Limited risk: transparency obligations under Art. 50. Chatbots and deepfakes must inform users that they are interacting with AI or that content has been generated/manipulated.
  • Minimal risk: no specific obligations, though voluntary adoption of codes of conduct is encouraged.

GPAI: the special case

General-purpose AI models (GPAI) have their own calendar. Their obligations (Chapter V) came into force in August 2025, but the Commission's enforcement powers over GPAI providers do not activate until 2 August 2026. That is: during this first year, providers of models like GPT, Claude, Gemini or Llama have been obligated, but the Commission could not fine them; from August, it can.

For GPAI models placed on the market before 2 August 2025, the deadline extends to 2 August 2027. This is the clause giving leeway to adapt pre-existing models.

Fines are deterrent: up to €35 million or 7% of global annual turnover (whichever is higher) for serious breaches of the prohibitions regime. For breaches of provider or deployer obligations, up to €15 million or 3% of global annual turnover.

Who enforces the Regulation in each country

Enforcement is two-tiered. At European level, the Commission acts through the AI Office, fully operational since August 2025, with exclusive competences over GPAI. At national level, each Member State designates one or more market authorities. Spain was a pioneer: in 2024 it created the Spanish Agency for the Supervision of Artificial Intelligence (AESIA), based in A Coruña.

The AEPD retains its role as data protection authority and, by extension, over any AI system that processes personal data. In July 2025 it published guidance clarifying that it can already act against prohibited AI systems that process personal data, even before full AI Act application. In practice, in many countries you will not have one authority but two (in Spain, AESIA and the AEPD), and both must be coordinated in your compliance plan.

What to do now if you haven't prepared yet

2 August 2026 has already passed and Annex III high-risk obligations do not apply until 2 December 2027: you have room, but not room to wait. There is no need to design a compliance program from scratch, but you should start the four tasks any auditor will want to see on day one:

1. Complete inventory of AI systems

Exhaustive list of all systems with an AI component that your organization develops, deploys or uses. Include not just in-house models: also count SaaS platforms with embedded AI (CRM, HR, marketing, customer service). A typical company discovers twice as many systems as it thought when doing this inventory.

2. Risk classification

Each system in the inventory is mapped against the four categories. Annex III of the Regulation is the reference: eight areas that automatically classify a system as high-risk (biometrics, critical infrastructure, education, employment, essential private/public services, law enforcement, borders, justice and democratic processes).

3. AI literacy program

Mandatory since February 2025 (Art. 4). Since 27 July 2026 the Digital Omnibus has reworded it: you no longer have to "ensure a sufficient level", but take measures that support the development of AI literacy among employees and third parties using AI systems, without guaranteeing a specific level for each person. It remains an obligation that can be supervised: the prudent approach is documented, role-adapted and registrable training, not simply sending a PDF.

4. Internal governance

Designate clear responsibilities. In small organizations, this often falls to the DPO expanding their role or an ad hoc committee. In medium and large organizations, a reasonable approach is an AI Governance Officer or a multidisciplinary committee (legal + IT + business + security). If you are pursuing ISO 42001 certification, this governance is the foundation on which the entire AIMS is built.

What comes next

With Art. 50 already applicable and high-risk on the horizon of December 2027, expect three market moves: (a) the first national enforcement proceedings, likely on Art. 50 transparency before high-risk —because they are easier to detect—; (b) a cascade of contractual updates in the AI supply chain (each client will demand formal compliance guarantees from their providers); and (c) the consolidation of ISO/IEC 42001 as the "ISO 27001 for AI", with audits already available under BS ISO/IEC 42006:2025.

The AI Act is not perfect and there will still be clarifications in its practical application during 2026 and 2027. But the direction is clear: in Europe, doing AI without thinking about governance is no longer an option.

Common mistakes when preparing for the AI Act

AI Act enforcement is already a reality, and the mistakes seen in the market carry a cost that goes beyond fines. These are the most common:

  • Treating August 2026 as the only date that matters. The February and August 2025 obligations are already in force. Organisations without a systems inventory or documented AI literacy measures risk being unable to demonstrate compliance with their obligations (Articles 4 and 26, depending on their role).
  • Assuming company size is an exemption. The AI Act applies by type of use, not by company size. A small company using a credit-scoring or candidate-screening system has the same material obligations as a large corporation for that specific system, with some documentation simplifications and fine caps of its own for SMEs.
  • Handing all responsibility to the technology provider. If your company deploys a high-risk AI system developed by a third party, you are the deployer and have your own obligations, which do not disappear because the provider meets theirs. Both responsibilities coexist.
  • Classifying every system as low or minimal risk by default. Risk classification must follow documented criteria, cross-checking what the system does against Annex III. A classification without justification is worthless in front of the regulator.
  • Writing the technical documentation just before the inspection. Article 11 requires documentation before deployment. Documentation written after the fact, even if technically correct, is hard to defend as evidence of real compliance.
  • Ignoring the data protection authority as a second regulator. In Spain, for example, the AEPD can act on AI systems that process personal data under the GDPR, even before the AI Act fully applies. Many high-risk systems process personal data, which means two authorities with inspection powers, not one.

Conclusion: the AI Act is not a project, it is a date with consequences

AI Act compliance deadlines do not wait. The first two milestones have passed and the obligations they triggered can be audited today. Article 50 already applies and the December 2027 high-risk deadline is closer than it looks. Preparing for Article 10, the governance of training data, requires infrastructure that is not built in a few weeks.

The good news is that organisations already running real data governance (documented lineage, roles with authority, controlled access and measured quality) have a solid base to adapt from. AI Act compliance is not a parallel project: it is the natural extension of mature data governance to the AI systems that governance feeds.

Those without that base should start now, with clear priorities: first the inventory and risk classification, then data governance for high-risk systems, then technical documentation and logging. Not everything at once, but everything before the regulator calls.

Checklist: readiness for each AI Act milestone

  • A complete inventory of AI systems (your own, deployed, and SaaS with embedded AI).
  • A risk classification for each system with documented justification (Annex III).
  • Confirmation that no Article 5 prohibited systems are in production.
  • A documented, role-appropriate and verifiable AI literacy programme (Art. 4).
  • Internal governance with named owners (an AI Governance Officer or equivalent).
  • Contracts with GPAI providers reviewed and Chapter V compliance evidenced.
  • An operational AI risk management system for high-risk systems (Art. 9).
  • Governance of training datasets: origin, transformations and bias analysis (Art. 10).
  • Complete technical documentation, prepared before deployment, for high-risk systems (Art. 11).
  • Automatic event logging throughout the life cycle of high-risk systems (Art. 12).
  • Effective, verifiable human oversight mechanisms (Art. 14).
  • Registration in the EU database for the systems that require it.

Frequently asked questions

What exactly changes on 2 August 2026?

The Article 50 transparency obligations and full enforcement powers enter into application (national regulatory sandboxes were pushed back to 2 August 2027). The Annex III high-risk obligations that were due that day were postponed to 2 December 2027 by the Digital Omnibus (Regulation (EU) 2026/1744, in force since 27 July 2026).

What are the four AI Act risk categories?

Unacceptable risk (prohibited), high risk (strict obligations), limited risk (transparency), and minimal risk (no specific obligations) — every AI system is classified into one of these four categories.

What is a GPAI model and why is it a special case?

A GPAI (general-purpose AI) model is one like those powering generative AI assistants. It has its own set of obligations (Arts. 51-56), separate from high-risk AI systems, with an additional tier for models with systemic risk.

Which authority enforces the AI Act in each country?

Each EU Member State designates its own national authority. In Spain, for example, it is AESIA (the Spanish AI Supervision Agency).

What should a company do if it hasn't prepared for the AI Act yet?

At minimum: inventory the AI systems in use, run a preliminary risk classification, and designate someone responsible for AI governance — before the full application deadlines arrive.

Discover your AI Act exposure

Free assessment with your priority gaps and the risk classifier on the AI Governance path.

Take the free assessment See AI Act templates