Skip to content

Session Expired

Your session has expired. Please sign in again to continue where you left off.

Sign In Again

UT HB0286: Artificial Intelligence Transparency Amendments

Dead/Failed Utah · 2026 session

Last verified Oct 10, 2026 · official bill text

HB0286 · where it stands

This bill did not become law (dead/failed) · last action Mar 6, 2026.

What do these statuses mean?
Introduced
Filed in the legislature; may be waiting for a committee hearing.
Passed a chamber
Approved by one or both chambers; awaiting further action.
Enacted
Signed into law, or became law without a signature or over a veto.
Effective date
The date the law says it takes effect. Once it has passed, the page shows "Effective" and the date. A court order can still block a law; if we know of one, the summary says so.
Dead / vetoed
Vetoed, failed, or the session ended without action.

In one paragraph

Utah's HB 286 (2026), Artificial Intelligence Transparency Amendments (first substitute), would have enacted the AI Transparency Act: a large frontier AI developer would have to write, implement and publish a public safety plan for catastrophic risks; per the bill's highlighted provisions, developers would also publish child protection plans and risk assessment summaries and report safety incidents to the Office of Artificial Intelligence Policy, with civil penalties and whistleblower protections. It never passed the House; the enacting clause was struck and the bill filed on March 6, 2026.

Plain-English summary, written with AI assistance. The official text controls.

What it means for business

None: the bill died and never became law. It would have required large frontier AI developers to publish safety plans and report safety incidents, with civil penalties.

Key provisions

  1. Would apply to frontier developers (who used at least 10^26 operations to train a frontier model; academic research by colleges excluded); a large frontier developer (with affiliates) has at least $500,000,000 in annual revenue
  2. A large frontier developer would have to write, implement, comply with and publish on its website a public safety plan for catastrophic risks
  3. Per the bill's highlighted provisions, developers would also publish child protection plans and risk assessment summaries, and could not make materially false or misleading statements about covered risks
  4. Per the bill's highlighted provisions, developers would report certain safety incidents to the Office of Artificial Intelligence Policy, which would give annual assessments and legislative recommendations
  5. Per the bill's highlighted provisions, it would establish civil penalties, whistleblower protections and remedies for employees who suffer adverse action, and an AI Transparency Enforcement Restricted Account
  6. "Covered chatbot" would mean a service with humanlike responses from a foundation model, foreseeably accessible by minors, with at least 1,000,000 monthly active users
  7. House committee recommended it favorably 8-0-2 (substitute); circled on third reading February 5, 2026; enacting clause struck and filed March 6, 2026

Latest legislative action

Mar 6, 2026. House/ strike enacting clause; House/ filed (House file for bills not passed)

Sponsors (showing 5 of 8)

NameRole
Primary
R Primary
Primary
Primary
Primary

Topics and industries

Affected industries

This page is general information, not legal advice. Summaries are AI-assisted and may contain errors; read the statute for the controlling text and talk to a lawyer about your situation. Full disclaimer · Report an error