The April 28 trilogue session ended without a political agreement. That fact has been covered. What hasn’t been fully examined is the specific procedural mechanism that made failure almost predictable: Parliament and the Council arrived at the table with incompatible definitions of what “extension” means.
According to reporting from multiple legal analysts, including IAPP and Modulos, Parliament entered negotiations wanting any extension set to a fixed calendar date, a firm new deadline that organizations could plan against. The Council’s reported position was different: tie any extension to the achievement of implementation milestones, making the deadline conditional rather than fixed. These aren’t negotiating positions that split the difference easily. A fixed date gives certainty; a milestone-conditional date gives flexibility but creates a second-order compliance problem, companies can’t plan for a moving target.
The August 2, 2026 compliance date for Annex III high-risk AI systems is confirmed by the EU AI Act’s official text. No Official Journal entry extending that date exists as of May 2, 2026. That means 92 days remain, a figure derived from the reporting date to August 2, not a projection. It’s arithmetic, not optimism.
A follow-up trilogue is reported for approximately May 13, 2026, roughly two weeks after the April 28 collapse. Multiple legal analysts have characterized it as the last realistic window before the August 2 deadline arrives with insufficient runway for a meaningful extension to be implemented, ratified, and communicated to affected organizations. That characterization belongs to the analysts, not to the treaty text.
What matters practically is what the Parliament/Council disagreement tells compliance teams about the scenarios. If May 13 produces a deal, it will look like one of two things: Parliament concedes on the fixed-date requirement (a milestone-conditional extension), or the Council accepts a specific date (compliance teams get a new target). Either outcome changes the planning calculus differently. A milestone-conditional extension creates a monitoring obligation, teams must track whether the milestones are met to know when their obligations actually begin.
If May 13 fails, August 2 is binding. No extension scenario requires compliance teams to accelerate; the non-extension scenario requires the same. The practical divergence is in documentation strategy and internal governance sign-off timelines. Organizations that have built compliance programs around a potential extension will need to pressure-test their August 2 readiness.
The procedural dispute itself is worth understanding beyond its immediate outcome. The Parliament/Council split on fixed-vs-conditional reflects a structural tension in EU legislative dynamics: Parliament tends to prefer legal certainty, while the Council often represents member-state flexibility concerns. That tension doesn’t resolve cleanly in a trilogue session under time pressure. The same dynamic has slowed other EU digital legislation. The AI Act’s complexity adds additional friction, implementation milestones are harder to define for AI systems than for, say, product certification timelines.
The question compliance teams should be asking: if a milestone-conditional extension passes, what are the milestones, and who determines when they’re met? That answer shapes whether the extension provides genuine runway or creates a new compliance dependency.