AI Deadline | Thursday 30April 2026
Things moving through AI regulatory pipelines that will matter in the next 3 to 6 months
đŽ Act now
The Digital Omnibus deal failed Monday night after twelve hours of negotiations in Brussels. The political agreement that would have formally delayed the EU AI Actâs Annex III high-risk deadline from August 2, 2026, to December 2027 did not happen. The next trilogue is on May 13. Nothing has changed legally, which means everything founders were hoping would change has not.
Thereâs a specific thing to understand here. The Omnibus was always about two separate issues running in parallel, and the failure hits them differently.
The first is GPAI enforcement.
The EU AI Office gains full enforcement powers over General-Purpose AI providers on August 2. That was never part of the Omnibus negotiation. The Omnibus would not have delayed it, and the failure doesnât make it worse. If you offer a model via API to EU users, youâre a GPAI provider, and your deadline is 94 days away regardless of what happens in May.
The second is Annex III high-risk systems.
hiring, credit, education, and biometrics. This is what the Omnibus was meant to delay to December 2027. The sticking point on Monday was a technical disagreement about AI embedded in regulated products like medical devices, cars, and industrial machinery. Parliament wanted exemptions. Council didnât. The political alignment that seemed solid in April had a gap underneath it.
The practical consequence: stop treating the Omnibus delay as a planning assumption. Treat August 2 as your deadline. A deal on May 13 is possible, but even a June agreement canât shift your August 2 obligations in time. After political agreement, the text still needs Parliament endorsement, Council endorsement, and publication in the Official Journal before any new date takes legal effect. Working backward from a late-June agreement, legal publication hits August or September at the earliest. December 2027 doesnât become binding just because the politicians shake hands.
This week, pull up your GPAI documentation checklist. Technical architecture summary, training data overview, and downstream use instructions. The EU AI Office has said documentation requests come first in its enforcement approach. Being the company that can say âhere it isâ when the Office asks is what the next 94 days are for.
đĄ Heads up
USA | Connecticutâs AI bill passes Senate, heads to House
The Connecticut Senate voted 32-4 on April 21 to pass a 64-page AI bill covering companion chatbots, automated hiring, frontier model safety, and synthetic content labeling. The employment provisions are the most immediately relevant: from October 1, 2026, any employer in Connecticut using AI to inform hiring, scheduling, or employment decisions must notify employees and applicants. The bill now goes to the House, which rejected last yearâs version. The legislative session closes May 6. If it passes this week, October becomes a real deadline. If you build hiring AI or run it for Connecticut employees, check whether your notification and documentation processes can absorb a six-month timeline. Donât wait for the House vote to find out.
USA | Colorado rewrite is still just a draft
The Colorado governorâs working group released a draft in March that would repeal and replace the current AI Act with a narrower automated decision-making framework and push the effective date to January 1, 2027. That draft is not law. The original Act takes effect June 30, and xAIâs federal lawsuit hasnât produced an injunction yet. The practical move: do the compliance work thatâs portable under either version. Document your systemâs purpose and intended use cases, run bias tests, and map which Colorado users your tool affects. That work is valuable whether the original law survives or the rewrite lands. Do it before you find out which way it goes.
In focus
đȘđș EU | The Omnibus failure: which deadline actually just got worse for you
Mondayâs failure clarifies something this brief probably should have separated earlier. There are two distinct August 2, 2026, deadlines under the AI Act. They apply to different types of companies. The Omnibus was only ever trying to fix one of them.
The first August 2 deadline is for GPAI providers. It was never part of the Omnibus proposal. If you make a model available via API, download, or integration to EU users for use in other applications, youâre a GPAI provider. From August 2, the EU AI Office has enforcement powers. It can request documentation, impose mitigations, order model recalls, and levy fines up to âŹ15 million or 3% of global revenue, whichever is higher. That enforcement regime was locked in at August 2 regardless of what happened on Monday.
The second August 2 deadline was for Annex III high-risk systems. The AI Act as written, makes high-risk obligations enforceable August 2. The Omnibus was designed to delay this to December 2027 for standalone systems and August 2028 for AI embedded in regulated products. Mondayâs failure means the original date is still the law.
A lot of small AI companies have been planning against the Omnibus delay as if it were done. The briefing room consensus in March was that the deal was essentially agreed in principle. It wasnât. The sticking point, whether AI embedded in products regulated under sectoral law like the Medical Device Regulation should face additional AI Act conformity assessment, is a genuinely contested legal architecture question, and neither Parliament nor Council was willing to move on it after twelve hours.
The May 13 meeting will try again. The Cypriot Presidencyâs mandate expires June 30, so there is real urgency. But urgency and resolution arenât the same thing. And even if May 13 closes the deal, founders face the same publication timeline problem: political agreement in May, formal endorsement in June, Official Journal in July, new deadlines taking effect in August at the absolute earliest. The August 2 window for GPAI is already past by then. High-risk founders might get the December 2027 date confirmed before enforcement, but itâs tight.
The sensible move for Annex III companies right now is to dual-track. Work as if August 2 is real, with the documentation and risk management work thatâs required regardless. Donât invest heavily in full third-party conformity assessment until May 13 clarifies whether a longer runway is actually coming. But donât pause on the baseline work either. If the Omnibus does pass, youâll be ahead. If it doesnât, youâll be compliant.
For GPAI providers, thereâs no dual-track. August 2 was always your date. Technical documentation, training data summary, downstream use instructions. Ninety-four days.
đą On the radar
đȘđș EU | Next Digital Omnibus trilogue: May 13. The Cypriot Presidency needs a deal before June 30 when its mandate expires. A deal is plausible. Thatâs what we said two weeks ago. Watch May 13 but donât plan around it.
đŹđ§ UK | ICO Code of Practice regulations in force May 12. SI 2026/425 was laid before Parliament on April 21. It comes into force May 12. The Regulations donât set the Codeâs content, but they create the statutory obligation for the ICO to draft and consult on a Code of Practice covering AI and automated decision-making. Expect a draft Code in late 2026.
đŹđ§ UK | ICO automated hiring consultation closes May 29. 29 days. If you build or use hiring AI in the UK, this is the last window to shape the final guidance. It becomes your compliance floor in Q3. Respond now.
đŹđ§ UK | Childrenâs online safety consultation closes May 26. 26 days. AI chatbots and generative tools accessible to under-16s are in scope. Final obligations likely land in 2027, but the consultation closes soon.
đșđž USA | Bartz v. Anthropic fairness hearing: May 14. The $1.5 billion Anthropic copyright settlement gets final approval in San Francisco. 91.3% of eligible works were claimed. If approved, roughly $2,931 per book becomes the practical benchmark for unlicensed training on copyrighted text.
The one thing to do this week
Stop treating December 2027 as a confirmed high-risk deadline until May 13 produces an actual deal. If youâre a GPAI provider, start building your documentation pack today. Ninety-four days.
Deadline tracker
EU | GPAI model enforcement (AI Office powers, documentation requirements) | 2 August 2026 | 94 days; documentation must be in progress now
EU | Annex III high-risk AI systems (employment, credit, biometrics, education) | 2 August 2026 (current law) | Omnibus delay failed April 28; August 2 remains legally binding
EU | Digital Omnibus political agreement | ~13 May 2026 | Trilogue resumes; deal needed before Cypriot Presidency mandate expires June 30
EU | AI-generated content watermarking obligation | 2 November 2026 (proposed) | Dependent on Omnibus outcome; not yet law
EU | Annex III high-risk delay (if Omnibus passes) | 2 December 2027 | Not yet law; August 2 remains binding until official publication
USA | Colorado AI Act: high-risk AI in employment, credit, housing | 30 June 2026 | Original law in force; xAI lawsuit (case 1:26-cv-01515) pending; working group rewrite (January 2027 effective date) still a draft
USA | Bartz v. Anthropic copyright settlement fairness hearing | 14 May 2026 | $1.5B settlement; 91.3% claim rate; sets training data licensing benchmark if approved
USA | Connecticut AI bill: employment notification obligations | 1 October 2026 | Passed Senate 32-4 on April 21; House vote pending before May 6 session close
USA | Texas TRAIGA high-risk AI obligations | 1 January 2026 | In force
USA | Oregon SB 1546 / Washington HB 2225 (AI companion chatbots, private liability) | 1 January 2027 | Coming
UK | SI 2026/425: ICO Code of Practice regulations | 12 May 2026 | In force from May 12; ICO must now draft statutory Code
UK | ICO automated decision-making (hiring) consultation | 29 May 2026 | 29 days remaining
UK | Childrenâs online safety consultation | 26 May 2026 | 26 days remaining
UK | FCA Mills Review report | Summer 2026 | Coming