Every compliance team tracking the EU AI Act’s Digital Omnibus deal has been watching the Annex III deadline move to December 2027. That’s the right number to know. It’s not the most urgent one.
The provisional political agreement, reached on May 7, also amended the timeline for AI-generated content transparency and watermarking obligations under Article 50 of the EU AI Act. According to Travers Smith’s analysis of the deal, the compliance window for these obligations was reduced from six months to three months, placing the deadline at December 2, 2026, roughly 200 days from today. That acceleration hasn’t received the same attention as the Annex III extension, and for GenAI providers, it should.
One critical qualifier applies to every deadline in this brief: as of May 12, 2026, the provisional political agreement has not been published in the Official Journal of the European Union. Until that publication occurs, these dates reflect the provisional text and are not enacted law. Compliance teams should monitor the Official Journal and confirm with legal counsel before restructuring timelines.
Article 50 Readiness Checklist (Before December 2, 2026)
- Map all GPAI-generated content exposed to EU users
- Assess watermarking technical approach (C2PA or equivalent)
- Identify provider-deployer disclosure chain obligations
- Monitor EU AI Office for harmonized standard publication
- Confirm OJ publication date with legal counsel
Three deadlines emerge from the provisional agreement. The December 2, 2026 date governs Article 50 transparency obligations, watermarking, AI-generated content labeling, and disclosure requirements that apply to GPAI providers and deployers of generative AI tools. The December 2, 2027 date governs Annex III high-risk systems: biometrics, employment AI, and education-sector AI that must meet conformity assessment and documentation requirements. According to reporting on the provisional agreement, Annex I sectoral systems, medical devices, aviation, and automotive AI, reportedly face a third deadline of August 2, 2028, though this hasn’t been confirmed at primary source level and should be treated as partially verified.
The catch is that December 2, 2026 is arriving without the technical infrastructure the compliance ecosystem was expecting. Harmonized standards for watermarking and content provenance aren’t finalized. Legal commentators note the absence of those standards and the limited number of operational national conformity assessment authorities as factors behind the Annex III extension, though that rationale represents editorial inference from the negotiating record rather than a stated position in the provisional agreement text. For Article 50, the practical consequence is that providers may need to comply before authoritative implementation guidance exists.
Epoch AI data from May 2026 indicates more than 30 models now exceed the EU’s systemic risk threshold, establishing the scale of the GPAI provider population that Article 50 touches. The transparency obligations don’t just apply to foundation model developers, they extend to deployers who present AI-generated content to EU users.
Warning
The December 2, 2026 deadline is provisional, not enacted law, until Official Journal publication. But technical watermarking implementation takes weeks to months. Providers who delay readiness work until OJ publication will have materially less than three months to comply.
What to watch
Official Journal publication is the trigger that converts provisional dates into enacted law. Until it publishes, no deadline is legally binding, but the window for building compliant watermarking infrastructure is running regardless. Providers who wait for OJ publication before beginning technical work will have materially less than three months to implement.
The real question is whether any provider can build a compliant watermarking implementation in 12 weeks without approved harmonized standards to build against. That’s the structural problem the acceleration creates. The December 2 date is visible now. The standard it requires may not be.