The April 28 political trilogue on the EU Digital Omnibus on AI ended without agreement after approximately 12 hours of negotiations, according to independent reporting corroborated across multiple sources. No extension to the EU AI Act’s August 2, 2026 compliance deadline is in force. Under Article 85(3) of the EU AI Act, that date remains the operative legal baseline until a Digital Omnibus extension is published in the Official Journal of the European Union. That has not happened.
The dispute reportedly centers on conformity assessment architecture for AI systems embedded in products already governed by sectoral safety legislation, the category of products listed in Annex I of the EU AI Act, which includes medical devices, machinery, civil aviation systems, and motor vehicles. According to analysis attributed to Bird & Bird, negotiations stalled over how the conformity assessment obligations in the AI Act interact with the existing CE marking and third-party assessment requirements under those sectoral laws. That characterization comes from a primary source whose URL is currently broken and awaiting resolution, treat it as attributed analysis, not confirmed regulatory text.
A follow-up trilogue session is expected around May 13, 2026, though the Cypriot Council Presidency has not formally confirmed the date. A T3 source puts it at “approximately 13 May 2026, two weeks after the failed 28 April session.” Bird & Bird’s own analysis, available in cross-reference fragments, describes it as “early to mid-May” with no formal confirmation. For compliance planning purposes, May 13 should be treated as approximate.
Why this matters now: legal advisors, including DLA Piper, are recommending that organizations treat August 2, 2026 as the operative compliance deadline and resume preparation immediately. That recommendation is legal analysis, not regulatory authority, but it reflects a sound reading of the situation. There is no mechanism by which the Omnibus extension takes effect retroactively. If the May 13 session fails, the Digital Omnibus is unlikely to pass before August 2 with time for Official Journal publication. That scenario is no longer hypothetical. It’s the default trajectory.
What hasn’t changed: Annex III high-risk system obligations under the AI Act, risk management systems, data governance documentation, technical documentation, transparency requirements, and human oversight measures, apply in full on August 2 regardless of what happens in May. The Omnibus, if passed, could modify certain conformity assessment pathways for Annex I sectoral products, but it doesn’t touch the core Annex III obligations most compliance programs are building toward. Teams waiting on political resolution before acting are running out of time to wait.
What to watch: the May 13 session. If the Cypriot Council Presidency announces a confirmed date and agenda, that signals genuine intent to close. If the session produces a political agreement, the next bottleneck is Official Journal publication speed, a process that takes weeks, not days. Any compliance program that hasn’t reached a near-final state by May 13 cannot realistically complete before August 2 if the session also fails. The calendar math is unforgiving.
The non-obvious question worth considering: if the Omnibus eventually passes after August 2 with a retroactive carve-out for Annex I sectoral products, organizations that built full conformity documentation will have done work that may later prove unnecessary for some product categories, but organizations that didn’t will have no legal cover. That asymmetry favors preparation over delay regardless of the political outcome.