Sen. Mary Edly-Allen (D) and Rep. Daniel Didech (D), with bipartisan cosponsors including Sen. Sue Rezin (R) and House Republican Leader Tony McCombie · 2026
Illinois's frontier AI law, signed July 6, 2026 after passing the House 110–0, and effective January 1, 2027. It takes the SB 53 transparency model and adds verification. Large frontier developers (frontier models above 10^26 operations, developer revenue over $500M) must write, implement, publish, and annually update a frontier AI framework covering catastrophic-risk thresholds and assessment, mitigations, third-party evaluation, cybersecurity for model weights, internal governance, and — explicitly — catastrophic risk from internal use of their models, including models circumventing oversight. Transparency reports are due before or with each new or substantially modified deployment. From 2028, large developers must retain an independent third party for an annual compliance audit, publish a summary within 30 days, and send summaries of internal-use risk assessments to the state every three months. Critical safety incidents go to the Illinois Emergency Management Agency and the Attorney General within 72 hours, or to law enforcement within 24 hours when lives are at risk. Developers must register and pay fees to operate in the state. Penalties, enforced exclusively by the Attorney General, run to $1M for a first violation and $3M for subsequent ones. An interoperability clause lets the state designate federal regimes with equivalent incident reporting and independent audits as satisfying the Act.
SB 53 with an auditor. Illinois keeps California's disclosure architecture — frameworks, transparency reports, incident reporting, whistleblowers — and closes its largest gap by requiring someone outside the company to check compliance every year. It goes further than either California or New York on internal use, the risk that the most capable models are run inside the lab long before, or without, public release. And it is written to be absorbed: the interoperability clause invites a federal regime to satisfy it, anticipating national legislation rather than resisting it.
This proposal is one of the frontier framework family built on California's SB 53. Compare the family side by side →
Where the burden falls
In contrast
Illinois copied California's structure and most of its definitions — the 10^26 threshold, the $500M large-developer line, frameworks, transparency reports, incident reporting, whistleblowers — and then added what SB 53 lacks. An independent auditor checks compliance every year. Internal use of frontier models is assessed and reported quarterly. Developers register and pay for their own oversight. Incident reporting is faster, at 72 hours rather than 15 days. California has since moved in the same direction with SB 813's verification framework, and Illinois's interoperability clause points beyond both: it is written to stand down in favor of an equivalent federal regime.
Compare with CA SB 53→Derived from the proposal’s own policy documents
From the perspective of political opposition
Verbatim from podcast transcripts; each links to the moment it was said
“Rather than sitting back and waiting for those [risks] to emerge, our legislation proactively seeks to find risk to embed safety and accountability into the industry and to promote public trust.”
“California and New York now, and Illinois, the three of them together, they represent forty percent of the American AI market. Which means three governors in three state houses have effectively written an AI standard, while Congress never even voted on it.”
“Illinois just passed a bill requiring massive tech companies to audit their AI safety because apparently politicians think they can put a digital leash on a Terminator. If you think a $3 million fine is going to stop Meta, you probably still believe in the Tooth Fairy.”
Enforcement Mechanism vs. Regulatory Scope
Prevention vs. Liability & Regulatory Authority
Innovation Priority vs. Worker Protection
Pre-deployment Obligations vs. Federal Preemption