10 April 2026 · 5 min read · The Implementation Layer

The EU AI Act Omnibus Delay: What Developers Actually Need to Know

The Digital Omnibus is enacted as Regulation (EU) 2026/1744. Annex III high-risk obligations apply from 2 December 2027 and Annex I product-embedded obligations from 2 August 2028. Here is what those dates mean for development planning.

What's happening

The Digital Omnibus entered into force on 27 July 2026 as Regulation (EU) 2026/1744. It defers Annex III high-risk obligations to 2 December 2027 and Annex I product-embedded obligations to 2 August 2028. The regulation also changes other provisions, so this article should not be read as a complete amendment summary.

On 19 November 2025, the European Commission published the Digital Omnibus on AI: a targeted simplification package proposing amendments to Regulation (EU) 2024/1689 (the EU AI Act). The headline change is a deferral of the application dates for high-risk AI system obligations.

Since then, two things have happened:

13 March 2026 — the Council of the EU adopted its general approach, broadly endorsing the Commission's deferral proposal with targeted amendments on Article 6(3) scope and regulatory sandbox timelines.
26 March 2026 — the European Parliament voted 569–45–23 (for–against–abstentions) in favour of its first-reading position, supporting the deferral but introducing amendments to strengthen Article 50 transparency requirements and to narrow the Article 6(3) procedural-task carve-out. Trilogue negotiations launched the same day.

The first trilogue on 28 April 2026 ended without agreement. A follow-up produced political agreement on 7 May, followed by parliamentary and Council approval and Official Journal publication on 24 July 2026. That negotiation history is now background; the enacted text is the authority.

What the deadlines look like now

Article 5 prohibitions and GPAI obligations are already applicable. Article 50 obligations generally have applied since 2 August 2026; providers of systems covered by Article 50(2) that were already on the market before then have until 2 December 2026. Regulation (EU) 2026/1744 sets 2 December 2027 for Annex III high-risk provisions and 2 August 2028 for Annex I product-embedded provisions.

The table distinguishes the original AI Act dates from the dates now enacted by Regulation (EU) 2026/1744.

Obligation	Original date	Enacted date	Status
Article 5 prohibitions (social scoring, subliminal manipulation, etc.)	2 Feb 2025	No change	In force
GPAI obligations (Articles 53–55)	2 Aug 2025	No change	In force
High-risk: standalone AI systems (Annex III)	2 Aug 2026	2 Dec 2027	Enacted
High-risk: product-embedded AI (Annex I — machinery, medical devices, etc.)	2 Aug 2026	2 Aug 2028	Enacted
Legacy high-risk systems placed on market before new application date	2 Aug 2027	Deferred proportionally	Proposed

Sources: Regulation (EU) 2024/1689 (Article 113 application dates), Commission Omnibus proposal, Morrison Foerster analysis, Cooley analysis, Sidley analysis.

Should you wait or act now?

The honest answer: it depends on your risk tier.

If your system is prohibited (Article 5)

Nothing has changed. The prohibitions on social scoring, subliminal manipulation, real-time remote biometric identification in public spaces, and emotion inference in workplaces and education have been in force since 2 February 2025. The Omnibus does not touch these. If Regula flags your code as prohibited-tier, act now.

If your system is high-risk (Annex III — standalone)

Regulation (EU) 2026/1744 moves the Annex III application date from 2 August 2026 to 2 December 2027. This is enacted law, not a forecast. Classification and exact obligations still require contextual assessment.

The practical advice: keep your compliance programme running against the deferred 2 December 2027 date for standalone high-risk systems. The extra time is now approved rather than merely likely, but it is not an excuse to do nothing.

If your system is high-risk (Annex I — product-embedded)

The enacted application date for the Annex I product-embedded path is 2 August 2028. If you are building AI into medical devices, machinery, or other products covered by the Union harmonisation legislation listed in Annex I, check the amended Article 113 and the relevant sector legislation. Standards publication and Official Journal citation are separate events: Article 40's presumption of conformity depends on the conditions in the enacted text.

If your system is minimal or limited risk

Do not infer that the amendment is irrelevant solely from a scanner tier. Article 50 obligations generally have applied since 2 August 2026, and the amendment includes a transition to 2 December 2026 for providers of Article 50(2) systems already on the market before 2 August 2026. Scope and other amended provisions still require contextual review.

What Regula does about this

Regula tracks every regulatory change in a structured delta log: a versioned, primary-sourced changelog for the EU AI Act. Each entry records the date, affected articles, source URL, and impact on Regula's detection patterns.

The delta log currently contains entries for:

Regulation adoption (12 July 2024)
Commission Omnibus proposal (19 November 2025)
Council general approach (13 March 2026)
Parliament first-reading position, 569–45–23 (26 March 2026)
Regulation (EU) 2026/1744 enacted and in force (27 July 2026)

The regula timeline command reports deadline information based on detected candidate risk paths. The delta log records the enacted Omnibus and its primary source. Contextual legal classification remains a human responsibility.

The regula regwatch command warns you when your installed ruleset is older than the latest delta-log entry, so you know when to update.

What to do this week

Run regula check . to identify candidate indicators and use regula timeline as a reference, then confirm classification and dates from intended purpose, deployment context and the enacted amendment. This article records the proposal-stage history; Regulation (EU) 2026/1744 now sets 2 December 2027 for Annex III and 2 August 2028 for Annex I high-risk rules.

Find out your risk tier
Run regula check . in your project root. It reports code-observable indicators associated with candidate categories. It does not determine a legal tier or whether an amendment affects your obligations.
Check whether the delay affects you
If regula check reports high-risk indicators, use regula timeline as a reference. Then determine from intended purpose and deployment context whether Article 6 and Annex III or the Annex I product path applies. The enacted dates are 2 December 2027 and 2 August 2028 respectively.
Follow the delta log
The delta log records confirmed regulatory changes and their primary sources. PyPI distribution is currently unavailable. Review the current source-install instructions and pin the exact public commit you evaluated.

$ pipx install git+https://github.com/kuzivaai/getregula.git@main && regula timeline copy

Shows your current EU AI Act deadlines based on your codebase.

Last reviewed: 14 August 2026 · Author: Regula maintainers · Not legal advice. Regula identifies risk indicators for developer review.

Not legal advice. Regula identifies regulatory risk indicators in code for developer review. It does not constitute legal advice, and its output should not be relied upon as a definitive compliance determination. Consult a qualified legal professional for legal questions. All regulatory dates cited in this article are sourced from primary EU institutions and named legal analyses; see inline links for each claim.