A June Decision That Mixed Delay With Continuity
The European Parliament passed the Digital Omnibus on AI in a final vote on June 16, 2026, and the Council gave its green light on June 29, making the amendment official. The headline change is that the high-risk (Annex III) obligations originally set to apply on August 2, 2026 now move to December 2, 2027 for standalone systems and August 2, 2028 for product-embedded ones. But the same amendment newly lists nudify and child sexual abuse material (CSAM) generation AI as prohibited practices, and it grants only a grace period — until December 2, 2026 — for the Article 50 transparency and watermarking duties of systems already on the market. Compress all of that into the single word "delay" and three distinct tracks disappear at once.
Three Tracks, Three Different Dates
When you rebuild the response calendar, the axis is the deadline, not the nature of the duty. The nearest wall is transparency and watermarking for existing systems on December 2, 2026; next is the regulatory sandbox participation cutoff, pushed to August 2, 2027; and the high-risk core splits across two dates, December 2, 2027 and August 2, 2028. GPAI (general-purpose AI) model obligations, in force since August 2025, are untouched by the delay. The newly added prohibited practices carry no grace period and force an immediate review of business scope.
The Cost of Reading "Delay" as "Stop"
The most common failure is reading only the headline word "delay" and halting preparation entirely. Transparency and watermarking still land on December 2, 2026, and the prohibited practices were added regardless of any delay, so freezing the whole roadmap means missing duties that arrive within six months. Conversely, a team that had been sprinting toward an August 2 high-risk deadline now has room to redeploy people to other tracks for a year or more.
Rewinding the Compliance Roadmap to Its Deadlines: A Re-Sequencing Guide
(a) Planning and target numbers: the calendar rewrite starts by lining up every duty in one column by date rather than by track. Aim for 100% deadline-calendar coverage (all three types registered — delayed, continuing, newly added), a gap-analysis completion rate of 90% or higher, and prohibited-practice feature screening completed across 100% of product lines as the quarterly goal for June through September. Managing coverage as a percentage lets you trace, like an audit log, which duty fell off the calendar.
Without target numbers, re-sequencing collapses back into "whatever feels urgent." Fix the four deadlines — December 2, 2026; August 2, 2027; December 2, 2027; August 2, 2028 — as columns and fill in owner, deliverable, and completion rate; when the next amendment lands, you only update the dates in the same table.
(b) Three failure patterns and recovery: first, hearing only "delay" and stopping all preparation — bolting on watermarking notices only as the December 2 transparency deadline looms means retrofitting every already-shipped system within six months. Second, leaving the newly added prohibited practices off the calendar — if any feature touches nudify or CSAM generation even slightly, it is an immediate action item with no grace period. Third, confusing the grace treatment for new versus existing systems — the Article 50 grace period to December 2, 2026 is a buffer for systems already on the market, not an open-ended allowance for new deployments.
Design the recovery branches by counting backward from each deadline. Freeze the watermarking implementation and notice wording for the December 2 track by early October, at least eight weeks out; run prohibited-practice screening across every feature within July, right after the amendment is confirmed, and quarantine anything that trips it; and for the high-risk track, decide first whether to use the sandbox cutoff (August 2, 2027), then settle the path between applying to participate and self-documenting.
(c) Operations checklist and quality control: before release, classify each system with three questions. Does it fall under Annex III high-risk? Is it subject to Article 50 transparency? Does it touch a newly added prohibited practice? Record the applicable deadline and the governing article as mandatory fields on the classification result, and for outputs that require watermarking, log the content type, marking method, and verification approach to stand up to an audit. Because GPAI obligations from August 2025 remain in force, re-confirm that upstream model-provider contracts still carry the documentation-delivery duty.
Do not lose the intersection with content labeling here. The content-labeling code of practice published on June 10, 2026 interlocks with the August 2 tranche, so aligning your watermarking and label markings with the code's recommendations lets one implementation absorb both the December transparency deadline and the labeling requirement.
(d) Quarterly re-review loop: a confirmed amendment does not freeze the calendar. Each quarter, re-check three things — whether any duty has been newly added to or pulled forward in the deadline calendar, whether owners and dates for items left incomplete in the gap analysis have been updated, and whether prohibited-practice screening has been rerun against new or changed features. Schedule a December-transparency-deadline rehearsal in Q3 and the sandbox participation decision plus high-risk documentation kickoff in Q4, and you secure slack all the way to the 2027–2028 deadlines.
The Rewritten Calendar on One Page
This amendment postponed high-risk duties; it did not signal that you postpone preparation. Put December 2, 2026 transparency and watermarking, August 2, 2027 sandbox, and December 2, 2027 and August 2, 2028 high-risk — plus the grace-free new prohibited practices and the still-standing GPAI duties — into a single date-ordered table, and hang 100% coverage, 90% gap analysis, and full prohibited-practice screening on it as quarterly metrics; the roadmap stops flinching at the word "delay."
References
Council gives final green light to simplify and streamline rules — Council of the EU
EU Lawmakers Reach Provisional Agreement to Delay Key EU AI Act Obligations — Sidley