The Parliament voted. That’s the part that made headlines. What most coverage buried: nothing changes yet.
On March 26, 2026, the European Parliament approved a mandate to delay application of certain EU AI Act rules, including obligations on high-risk AI systems and AI systems covered by EU sectoral safety legislation. The vote, confirmed by the European Parliament and the European Commission’s Digital Strategy framework, reflects the EU’s acknowledgment that readiness standards aren’t ready. But a Parliament vote is not a Council decision. The delay mechanism runs through the EU Digital Omnibus legislative proposal, and that proposal still requires Council of the European Union approval before any deadline shifts.
Three dates now in play, with different confidence levels.
The watermarking deadline is the clearest: MEPs approved giving providers until November 2, 2026 to comply with rules on watermarking AI-created audio, image, video, and text. That date is confirmed at primary source level.
The other two are proposals, not facts yet. Under the proposed delay, rules for high-risk AI systems would apply from December 2, 2027, shifted from the original August 2026 timeline. AI systems covered by EU sectoral safety legislation could move to August 2, 2028. Both of those dates are confirmed at trade press level, pending Council action to make them real.
What compliance teams should actually do right now.
CIO.com and compliance advisors recommend organizations continue EU AI Act preparation regardless of the pending delay. That advice is sound, and it has a specific rationale beyond general caution.
First, Council approval is not guaranteed. The Digital Omnibus mechanism is the vehicle, and Council negotiations could modify, delay, or reject the Parliament’s mandate. If Council doesn’t approve, the original deadlines apply, and any organization that stood down its compliance program will have lost months it can’t recover.
Second, even if the delay passes, the watermarking rules move only five months out from where they already stood. That’s not enough runway to build a new compliance program from scratch. Organizations already behind should treat November 2, 2026 as a hard deadline regardless of what happens with high-risk provisions.
Third, the standards preparation work, gap analyses, risk classification, documentation frameworks, doesn’t get easier with more time. Teams that use the delay window to do that work will be better positioned when the final deadlines land.
The compliance-in-uncertainty posture.
The EU AI Act story most organizations were following was the Parliament vote. The story compliance teams need to follow is the Council. Watch for Council working group activity on the Digital Omnibus proposal. A Council endorsement confirms the proposed dates. A Council rejection or modification reopens the timeline entirely.
TJS perspective: the Parliament’s vote signals political will for a delay, that’s meaningful. It doesn’t signal that compliance work is optional. The organizations that treat “proposed delay” as “confirmed delay” are the ones that will face compressed timelines when the Council acts and the clock resumes.