The political window closed last Monday. After approximately 12 hours of negotiations, the European Parliament, the Council, and the Commission ended trilogue talks on April 28 without agreement on the proposed Omnibus amendments to the EU AI Act. Per Reuters reporting, EU countries and Parliament lawmakers could not bridge the gap on proposed simplifications to the high-risk classification framework.
The result matters more than the drama. The EU Commission’s own digital strategy site states the Act entered into force on August 1, 2024, and becomes fully applicable exactly two years later on August 2, 2026. No Omnibus adoption, no deadline movement. That date is binding law.
Annex III of the Act lists the use cases that qualify AI systems as high-risk. Providers of those systems face Article 11 technical documentation requirements, mandatory conformity assessments, EU database registration, and post-market monitoring obligations, all due before a system can be placed or put into service in the EU market. Per the authoritative EU AI Act reference site, deployers of certain Annex III systems used in specific public-sector or essential-services contexts face additional obligations under Article 27, including fundamental rights impact assessments. That last obligation isn’t universal, it applies to specific deployer contexts, not every Annex III provider.
According to TNW reporting, more than 40 civil society organizations had lobbied against what they characterized as a rollback of fundamental rights protections in the Omnibus proposals. One more trilogue session is possible in May. Whether a deal reached in May could realistically be published in the Official Journal and take effect before August 2 is a question legal analysts have not yet resolved with certainty.
That ambiguity is the key variable now. Two scenarios exist. In Scenario A, a May agreement is reached and moves through the legislative process fast enough to shift some obligations before August. In Scenario B, the baseline until proven otherwise, August 2 stands in full. Compliance teams that structured their programs around an expected extension now face a harder question: how much runway did they lose waiting?
The practical answer is that it doesn’t matter which scenario plays out if your gap analysis isn’t complete. Article 11 documentation work, risk classification audits, and conformity assessment preparation take months. Any organization with Annex III systems that hasn’t started those workstreams is already behind schedule regardless of what happens in May.
The one forward-looking question worth sitting with: if your legal team has been treating the Omnibus as a near-certain delay, have they revisited that assumption since Monday? The answer to that question determines whether your compliance posture is 94 days behind reality or 94 days ahead of it.