EU AI Act Omnibus talks stalled — what SMEs should do now

Published: 1 May 2026.

If you read our earlier note on the Digital Omnibus — EU AI Act deadline may move (Digital Omnibus): what SMEs should do now — you’ll remember the core idea: political momentum for postponing some high‑risk timelines, but no reason to pause governance work.

What changed since then: the 28 April 2026 trilogue session ended without a political agreement. That matters because the Omnibus is not “extra time by default” — it only changes dates after it is formally adopted and published.

This article is a short signal → action update. It does not replace legal advice; it helps product and compliance leads communicate clearly internally and with customers.

What happened (plain English)

The Digital Omnibus is a big EU legislative package meant to simplify parts of the digital rulebook — including proposed amendments to the EU AI Act (Regulation (EU) 2024/1689). A key political promise in the AI portion was to move some high‑risk application dates so industry has more time while harmonised standards and notified bodies catch up.

On 28 April 2026, EU institutions negotiated for many hours and did not close a deal. Reporting from multiple outlets converges on a central sticking point: Annex I — AI built into products already regulated under EU product safety frameworks (for example medical devices, machinery, toys). The fight is about whether (and how) those systems stay within the AI Act’s conformity architecture versus leaning more heavily on sectoral rules alone — a “double regulation” debate you’ll hear about from industry and from civil society, for different reasons.

Annex III vs Annex I (why the whole package stalled): negotiators had been closer on postponing many stand‑alone Annex III high‑risk timelines than on the Annex I “embedded in regulated products” architecture — but in EU trilogues, nothing is adopted until everything is agreed, so one unresolved file can block the entire Omnibus.

Next beat: a follow‑up political trilogue is widely reported for around 13 May 2026 (treat the exact date as calendar‑dependent until the institutions publish it).

What did not change (the part that matters for your roadmap)

Until an amending regulation is adopted and published in the Official Journal, your safest internal planning baseline remains the dates already in force in the AI Act text for the obligations you’re preparing for — including treating 2 August 2026 as the usual focal date for teams preparing Annex III high‑risk workstreams, Article 50 transparency, and related governance. Your exact applicable dates depend on classification and role (provider vs deployer, Annex I vs Annex III, GPAI, etc.) — confirm against your AI systems inventory and qualified counsel where stakes are high.

Practical translation for SMEs:

• If you stopped work because you assumed delay was guaranteed, restart — the “maybe” is still a maybe.
• If you kept building inventory, documentation, logging, and vendor controls, continue — that work is portable even if timelines later shift.

For the full baseline schedule (and where we keep cross‑links updated), see: EU AI Act timeline: key dates & deadlines.

Five actions for this week (tight list)

These deliberately overlap with our earlier “seven actions” post — we’re compressing for busy teams.

1. Say the quiet part out loud in writing — add this sentence to your internal roadmap and customer FAQs:
   “We plan for 2 Aug 2026 until EUR‑Lex confirms otherwise; Omnibus negotiations are unresolved.”
2. Finish (or refresh) your AI systems inventory — include third‑party tools and “shadow AI” integrations.
3. Re‑run risk classification for anything that might be Annex III high‑risk or touch regulated products; write down assumptions and open questions.
4. Vendor gate — approved tools list, data residency / subprocessors, OAuth scopes, and a simple “no new AI tool without review” rule.
5. Ship Article 50 UX work that doesn’t depend on Omnibus politics — if users see AI output, disclosures, export footers, and evidence screenshots are always a good investment. Start here: Article 50 Disclosure Pack v1.

What not to do

• Don’t tell your board “deadlines are delayed” unless you can point to a published amending text in EUR‑Lex.
• Don’t burn the week refreshing Politico — schedule one 30‑minute monthly review and move on.

Sources (legislative news, April–May 2026)

• Modulos: EU AI Act Omnibus: the trilogue failed — what’s next
• IAPP: AI Act Omnibus: what just happened and what comes next
• The Next Web: EU and Parliament fail to agree on AI Act changes after 12 hours of talks

Related (Legalithm)

• EU AI Act deadline may move (Digital Omnibus): what SMEs should do now — updated with a late‑April / early‑May legislative note at the top
• Article 50 Disclosure Pack v1 — copy/paste UI strings, export patterns, logging fields, evidence checklist
• AI Act compliance checklist for 2026 — task‑oriented programme view alongside one‑off UX work
• Run the free AI Act assessment
• Primary law (verify): Regulation (EU) 2024/1689 — EUR‑Lex (HTML)

Legalithm materials are operational guidance only and do not constitute legal advice.