AI Deadline | Thursday 7 May 2026
Things moving through AI regulatory pipelines that will matter in the next 3 to 6 months
đ´ Act now
Connecticutâs AI bill passed the House 131-17 on May 1. Governor Lamont has said heâll sign it. That changes the status of October 1, 2026, employment notification obligations from âmight happenâ to âwill happen.â
From October 1, any employer using AI to make or inform decisions about hiring, firing, promotions, or scheduling in Connecticut must notify employees and job applicants that AI is in use. The notice has to be given before the decision and has to be specific enough that the person understands which decisions are being influenced by automated systems. If you build hiring AI or HR automation that Connecticut employers use, you have 147 days.
The bill is broader than employment. Companion chatbot operators face obligations from January 1, 2027, including age verification, access controls for under-16s, and a prohibition on manipulative engagement patterns designed to foster emotional dependence. Frontier model providers face new safety requirements. Synthetic content labeling obligations cover anyone generating images, audio, or video for distribution.
The employment piece is the one with the most immediate clock. If youâre selling hiring automation to US customers, Connecticut is probably in your customer base. Your enterprise customers there will be looking to you for documentation, audit trails, and notification infrastructure by Q3.
Check your contracts this week. Then figure out whether your product can surface the information that a proper notification would need to contain. If it canât produce that information today, youâve found the gap. Sixty days to close it is fine. 140 days isnât very different, but it feels like it is, and that feeling has a way of eating time.
đĄ Heads up
đŞđş EU | May 13 trilogue and the publication problem
The third Digital Omnibus trilogue is scheduled for May 13. April 28âs failure came down to conformity assessment architecture for AI embedded in regulated products, like medical devices, not the headline delay. The postponement of Annex III high-risk obligations to December 2027 was essentially agreed. So May 13 might actually close it.
But even if it does, the math is difficult. A political deal still needs formal Parliament endorsement, Council endorsement, and publication in the Official Journal before new dates take legal effect. That process takes two to three months minimum. A May 13 agreement gets published in July or August at the earliest. GPAI enforcement starts August 2, regardless. High-risk companies might get December 2027 confirmed before enforcement catches them, but itâs tight, and itâs not guaranteed. Watch May 13. Keep your documentation work running while you do.
đŹđ§ UK | ICO ADM consultation closes May 29
The ICOâs draft guidance on automated decision-making and profiling closes at 23:59 on May 29. Twenty-two days. This matters if you use AI to make or assist decisions about individuals, which covers more products than founders typically think. The guidance covers transparency requirements, the right to explanation and human review, and what documentation youâre expected to keep. Whatever gets finalised becomes your compliance floor for UK data protection. Responding to consultations where you have a stake in the rules is one of the cheapest things you can do. The response form is at ico.org.uk.
In focus
đşđ¸ | Bartz v. Anthropic: what the settlement benchmark actually means
The fairness hearing is on May 14. Judge MartĂnez-OlguĂn will hear objections and decide whether to approve the $1.5 billion settlement. If she does, roughly $3,000 per book becomes the established going rate for unlicensed use of copyrighted text in model training.
That number matters beyond the immediate parties. It isnât a legal precedent in a strict sense, but it functions like one. Copyright clearance lawyers who negotiate training data licensing deals now have a courtroom-endorsed figure to work with. Plaintiffsâ attorneys in future cases will cite it. Insurers pricing IP risk for AI companies will price against it.
The claim rate is striking. 91.3% of eligible works were claimed. The typical class action claim rate is around 10%. That number reflects an organised effort from authors and publishers who clearly understood their rights and participated. It also reflects the fact that $3,000 a book is meaningful money to many individual authors, even if the Authors Guild has publicly described the claims process as Kafkaesque and the compensation as inadequate.
The more complicated problem is what the settlement doesnât cover. It only applies to US-registered works. Foreign rightsholders, works without US copyright registration, and works outside the class definition donât get paid and donât release their claims. Thatâs a substantial body of ongoing exposure that $1.5 billion doesnât close. Future plaintiffs whose works werenât in this class can still sue, and theyâll have the Bartz figure as their floor.
Thereâs also the scope creep question. Books are a relatively clean category. But the same legal theory that produced this settlement applies to web scraping, code repositories, academic papers, and private documents ingested through integrations. Each of those has its own ownership structure and legal exposure profile. This settlement doesnât speak to them directly. It demonstrates what a well-organised class can extract.
For founders: if your product was trained on unlicensed copyrighted material, or if youâre building on top of a base model that was, this settlement doesnât resolve your exposure. It quantifies part of it. The question to put to your legal team now is whether you have documented whatâs in your training data and what licenses cover it. Because the next case will negotiate against $3,000 a book. Thatâs now the reference point.
The judge could approve it, request modifications, or reject it. Rejection is unlikely given the claim rate and how far the parties are invested. But watch what she says about the exclusion of foreign works. If thereâs judicial discomfort there, future international cases get more favorable treatment from plaintiffs than anyone expected.
đ˘ On the radar
đşđ¸ USA | Colorado enforcement pause holding. The federal courtâs April 27 order preventing enforcement of the Colorado AI Act through June 30 remains in place. The legislative session closes May 13. Governor Polisâs workgroup framework for a replacement bill hasnât become legislation. Donât assume the original law disappears. The xAI lawsuit is still live.
đŹđ§ UK | ICO Code of Practice regulations in force May 12. SI 2026/425 comes into force next week. It creates 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 to appear in late 2026, and plan for a consultation response at that point.
đŹđ§ UK | Childrenâs online safety consultation closes May 26. AI chatbots and generative tools accessible to under-16s are in scope. Final obligations land in 2027, but if your product reaches minors, the window to respond is 19 days.
đşđ¸ USA | Chatbot disclosure bills advancing in Oklahoma and Hawaii. Both appear poised for passage. Requirements are straightforward: disclose that users are talking to an AI. Low compliance cost, but you need to track which states youâre now caught by.
đşđ¸ USA | Bartz v. Anthropic fairness hearing: May 14. See In Focus above. If approved, $3,000 per book is the benchmark. If modifications are requested, watch for what the judge focuses on.
The one thing to do this week
Connecticutâs employment notification obligations are now law in all but signature. If you build hiring AI, map your Connecticut customers today, and check whether your product can produce the notification information theyâll need by October 1.
Deadline tracker
EU | GPAI model enforcement (AI Office powers, documentation requirements) | 2 August 2026 | 87 days; Omnibus delay does not apply to GPAI; documentation must be in progress now
EU | Annex III high-risk AI systems (employment, credit, biometrics, education) | 2 August 2026 (current law) | Omnibus deal failed April 28; May 13 trilogue is next attempt; August 2 remains legally binding
EU | Digital Omnibus political agreement | 13 May 2026 | Next trilogue scheduled; deal must precede June 30 Cypriot Presidency expiry
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 Journal publication
USA | Colorado AI Act: high-risk AI in employment, credit, housing | 30 June 2026 | Enforcement paused by court order; legislature closes May 13; rewrite still a draft
USA | Bartz v. Anthropic copyright settlement fairness hearing | 14 May 2026 | $1.5B settlement; ~$3,000/book benchmark if approved; 91.3% claim rate
USA | Connecticut AI Responsibility and Transparency Act: employment notification obligations | 1 October 2026 | Passed House 131-17 on May 1; governor to sign; effectively law
USA | Connecticut AI Responsibility and Transparency Act: companion chatbot obligations | 1 January 2027 | Same bill; minors protections, manipulative design prohibitions
USA | Texas TRAIGA high-risk AI obligations | 1 January 2026 | In force
USA | Oregon SB 1546 / Washington HB 2225 (AI companion chatbots) | 1 January 2027 | Coming
UK | SI 2026/425: ICO Code of Practice regulations | 12 May 2026 | In force from next week; ICO must now draft statutory Code
UK | ICO automated decision-making consultation | 29 May 2026 | 22 days remaining; respond at ico.org.uk
UK | Childrenâs online safety consultation | 26 May 2026 | 19 days remaining
UK | FCA Mills Review report | Summer 2026 | Coming