The EU AI Act Omnibus, part of the broader Digital Omnibus Package, has entered trilogue negotiations between the European Commission, Council, and Parliament, according to Europa.eu and analysis from A&O Shearman. The process is intended to consolidate and amend elements of the existing AI Act. Its most consequential feature isn’t the amendments themselves, it’s the deadline structure they’d introduce.
One date isn’t moving. The original AI Act’s full application date of August 2, 2026 remains in place per the established AI Act timeline. That’s the baseline everything else is built on.
What’s new, and what must be read carefully, are the Omnibus-specific dates now surfacing from trilogue discussions. These are negotiating positions, not enacted law. A&O Shearman’s trilogue analysis indicates the following dates are under discussion:
– December 2, 2027, reported convergence point for compliance obligations covering standalone Annex III high-risk AI systems – August 2, 2028, reported convergence point for AI embedded in regulated products (Annex I) – February 2, 2027, a proposed deadline for synthetic content labeling, pending trilogue conclusion
None of these dates should appear in a compliance roadmap as confirmed requirements. They are where negotiations are heading, not where they’ve landed.
Why the deadline structure matters more than the dates
The Omnibus’s significance isn’t the specific calendar dates, it’s what they replace. The original AI Act included conditional mechanisms that gave companies some flexibility in how they phased compliance. The Omnibus, as currently structured in trilogue, would replace that flexibility with hard dates. For legal and compliance teams that built AI Act roadmaps around phased timelines, the Omnibus represents a renegotiation of those assumptions, not just an update.
According to A&O Shearman’s analysis, negotiators are working toward political agreement at the April 28 trilogue meeting. That meeting’s outcome will determine whether the Omnibus moves toward formal adoption or requires additional rounds. Until April 28 passes, all Omnibus-specific dates remain subject to change.
What to watch
The April 28 meeting is the immediate milestone. If political agreement is reached, the Omnibus moves toward formal adoption, at which point the negotiating positions on dates begin hardening into legal requirements. The established August 2, 2026 full application deadline is the only date compliance teams should be treating as confirmed. Everything beyond that is contingent on Omnibus outcomes.
Synthetic content labeling is the wildcard. The proposed February 2027 deadline affects generative AI providers specifically, and it arrives before the more complex Annex III and Annex I obligations. If the Omnibus finalizes, this may be the first hard deadline many AI companies face under the amended framework.
TJS synthesis
The Omnibus trilogue is a signal that the EU isn’t finished designing its AI compliance architecture, it’s redesigning it while the clock runs toward August 2026. Companies that deferred detailed AI Act planning on the assumption they had until 2027 or 2028 now face a narrower window to understand what the final framework will require. The prudent approach is to build compliance infrastructure around the enacted August 2026 requirements now, while treating the Omnibus dates as planning assumptions to be confirmed after April 28.