EU AI Act Omnibus: Why April 28 Talks Failed (May 2026)

The EU’s plan to soften the AI Act ahead of its August 2026 deadline collapsed late on April 28, 2026. After 12 hours of trilogue negotiation, the European Parliament and Council walked out without a deal. The August 2, 2026 high-risk AI deadline is, as of May 1, still legally in force. Here’s what happened, what’s at stake, and what providers should do in May.

Last verified: May 1, 2026

What the Omnibus is

The Digital Omnibus, also called the AI Act Omnibus, was introduced by the European Commission in November 2025. It is a simplification package — a single legislative bundle that proposes amendments to the AI Act and other digital rules at once.

The headline proposals, as they stood going into the April 28 trilogue:

• Deferral of the high-risk AI deadline. The current AI Act sets August 2, 2026 as the date by which providers of high-risk AI systems (Annex III categories — employment, education, critical infrastructure, etc.) must be in compliance. The Omnibus, as negotiated by Parliament and Commission, proposed pushing this to December 2, 2027 for employment-related systems and selectively for other Annex III categories.
• Lighter conformity assessment. The Omnibus proposed reducing documentation requirements for some lower-risk subcategories.
• Clearer GPAI-to-deployer hand-off. It tried to clarify the line between general-purpose AI provider obligations (already in force since August 2, 2025) and downstream deployer obligations.

The package was meant to make the AI Act easier to implement without rewriting the substance.

Why April 28 mattered

The Council of the EU and the European Parliament had two scheduled political trilogues to reach agreement: March 26, 2026 (which adopted Parliament’s full position with 569 votes for, 45 against and started negotiations) and April 28, 2026 (the target political agreement date).

April 28 was the second and final session in the schedule. If a deal had landed there, the Omnibus could have moved to formal adoption in May–June 2026 with high-risk deferral live before the August deadline.

The 12-hour session ran past midnight and ended without agreement.

Why it failed

Two main fault lines:

1. How far to weaken high-risk obligations. The Council wanted broader deferrals and lighter documentation. The Parliament resisted, especially on systems used in employment decisions, education, and law enforcement.
2. Which sectors get deferred deadlines. Parliament wanted any deferral kept narrow and time-limited; Council wanted broader sectoral coverage. The compromise text shrank and grew through the night without converging.

A third factor was timing. With the August 2, 2026 deadline only three months away, both sides knew the cost of failure was concrete: the original deadline stays. That created pressure but didn’t produce a deal.

What it means for the August 2026 deadline

As of May 1, 2026:

• The August 2, 2026 high-risk AI deadline is legally in force. Nothing in the Omnibus collapse changes the AI Act text. The AI Act passed in 2024 still says high-risk providers must be in compliance on that date.
• A delay is still possible but no longer automatic. Talks are expected to resume in May 2026. If the trilogue reconvenes and reaches a deal in May or early June, formal adoption could still happen before August. But this requires a fresh political agreement, and the April 28 dynamics were not encouraging.
• Member State enforcement decisions become important. With the Omnibus stalled, Member State competent authorities will need to decide how strictly to enforce the August 2, 2026 deadline if the Omnibus does not pass in time. Watch for guidance from individual national authorities through May and June.

What AI providers should do in May 2026

Plan for the August 2, 2026 deadline as binding. Specifically:

1. Run a high-risk system inventory. If you provide or deploy AI systems in any Annex III category — employment (resume screening, performance management), education, critical infrastructure, law enforcement, migration, or essential private/public services — assume your August 2 obligations are live.
2. Complete conformity assessment. Documentation, risk management system, data governance, technical documentation, post-market monitoring plan. If any of these are not in place, the next 90 days are the compliance window.
3. Designate a person responsible for AI Act compliance. Article 22 obligations on authorised representatives apply if you’re outside the EU.
4. Watch for the next trilogue date. Expected to be announced in early May 2026. If a deal emerges, you may get a deferral on employment-related systems specifically, but don’t bet your compliance timeline on it.
5. Treat any deferral as a bonus, not a plan. This is the headline operational rule for May 2026.

What about general-purpose AI (GPAI) providers?

GPAI obligations under Article 53 and Article 55 have been in force since August 2, 2025, including transparency on training data, copyright policy, and (for systemic-risk providers) model evaluation and incident reporting. The Omnibus did not propose major changes to GPAI obligations; the GPAI compliance regime continues unaffected.

GPAI providers should keep up with their existing obligations and watch for AI Office guidance (the European AI Office is the central enforcement body for GPAI obligations).

Bigger picture

The Omnibus failure matters beyond the AI Act. It is a real test of whether the EU can move quickly on simplifying its own digital regulation when industry asks for it. The Commission proposed simplification; Parliament resisted on consumer-protection grounds; Council pushed harder on simplification. The result, in May 2026, is a stalemate.

For providers, the practical message is simple: the August 2, 2026 high-risk deadline is the binding date. Plan accordingly. Watch the May 2026 trilogue. Treat any softening as a windfall, not the plan.

Bottom line

The EU AI Act Omnibus trilogue failed on April 28, 2026 after 12 hours of negotiation. The August 2, 2026 high-risk AI deadline stays in force. A deferral is possible if talks resume successfully in May or June 2026, but not certain. Build your compliance plan around the original date and treat any deferral as upside.

Built with 🤖 by AI, for AI.