Regulatory intelligence · case study

From change to action: the omnibus deadline shift

One real regulatory change, followed through every step of the Trusq loop — from the source document to what it means for one system on one register.

01

Source change

On 19 November 2025 the European Commission proposed the digital omnibus on AI (COM(2025) 836), targeted amendments to the AI Act's implementation timing. Parliament and Council reached a provisional agreement on 7 May, adopted the file on 16 and 29 June, and it was published on 24 July 2026 as Regulation (EU) 2026/1744. It entered into force on 27 July 2026.

Regulation (EU) 2026/1744 is in force from 27 July 2026. The amended dates are now binding (what changed, old vs new).

02

Obligation affected

The deferral touches three tracked obligations — the Article 50(2) content-marking carve-out and both high-risk tracks. The amended dates are now binding; see the full entries, source and changelogs on AI Act deadlines.

Art. 50

Article 50 transparency duties apply from 2 August 2026. Regulation (EU) 2026/1744 postpones only the Article 50(2) machine-readable content-marking duty to 2 December 2026 for systems placed on the market before 2 August 2026.

Annex III

High-risk obligations for stand-alone Annex III AI systems apply from 2 December 2027 under Regulation (EU) 2026/1744.

Annex I

High-risk obligations for AI embedded in Annex I regulated products apply from 2 August 2028 under Regulation (EU) 2026/1744.
03

Impact

Illustrative scenario

Take a deployer running a CV screening model for recruitment — automated decisioning, classified high-risk under Annex III (Art. 6). Its high-risk obligations (risk management, data governance, documentation, human oversight and conformity assessment) now apply from 2 December 2027 under Regulation (EU) 2026/1744. The general 2 August 2026 milestone still governs provisions outside the deferred high-risk track.
04

Action

What this deployer does now, factually:
  • Keep the non-high-risk parts of the AI Act programme on the 2 August 2026 date — the deferral covers the high-risk requirements, not the whole Act.
  • Confirm the CV screening model sits in the Annex III track (December 2027 under the amended regulation) rather than the embedded-product track (August 2028).
  • Check whether any generative components placed on the market before 2 August 2026 rely on the content-marking postponement to 2 December 2026.
  • Re-baseline plans and contracts against Regulation (EU) 2026/1744, while preserving the audit trail of decisions made before its entry into force.
  • Record which systems use each date and the source version that establishes it.
05

Evidence

Each of those actions leaves a dated entry against the CV screening system in a monitored AI register: the obligation tracked, its formally applicable date, the former baseline and the amended date with their sources, and the timestamp of the last verification against the primary text. That per-system record — not a screenshot of any internal tooling — is what a compliance lead hands to counsel, an auditor or a market-surveillance authority: a traceable answer to ‘what did we know, and when, about this deadline.’
Case published: 17 Aug 2026. Reflects the situation as of that date. Not legal advice: Trusq indicates likely attention points; a competent authority or court always has the final say. Regulation (EU) 2026/1744 is in force from 27 July 2026. The amended dates are now binding (what changed, old vs new).
← From EU change to action