Utah 2026 General Session Status: To Executive 2 R cosponsors

HB 286 — Artificial Intelligence Transparency Amendments

Last action — House/ filed

Track this bill free

No card. One bill, free forever — alerts when it moves.

  1. ✓
    Introduced
  2. ✓
    In Committee
  3. ✓
    Passed House
  4. ✓
    Passed Senate
  5. 5
    To Executive
  6. 6
    Enacted

This bill has been sent to the executive. Introduced January 19, 2026. It awaits signature.

Next likely step: the executive signs it into law or issues a veto.

Prognosis

Advancing 46% · moderate confidence

Where this bill stands today.

Odds of enactment

Moderate

How often bills like it became law.

  • To Executive

    Current position in the legislative process.

  • 2 sponsors

    1 primary, 1 co-sponsors signed on.

  • Single-party support

    Sponsorship is currently within one party (2 R).

Prognosis reads this bill's own signals — stage, sponsorship breadth, committee status, recorded votes and cross-state momentum. Odds come from a model trained on which bills have become law.

Bill Text

What changed in the latest version

414 added · 428 removed

Plain-language change summary

The updated version of HB 286 includes new requirements for developers of certain artificial intelligence models to create and publish plans focused on public safety and child protection. It also mandates that these developers disclose summaries of risk assessments and report safety incidents to a designated office, enhancing accountability. Additionally, the bill now provides protections for whistleblowers who raise concerns about AI safety, along with establishing a fund to support enforcement of these regulations. These changes aim to ensure that AI development prioritizes safety and transparency, which is essential as technology continues to evolve and impact our lives.

→
Previous
Latest
01-28 11:38 1st Sub.
HB0286S01 compared with HB0286 {Omitted text} shows text that was in HB0286 but was omitted in HB0286S01 inserted text shows text that was not in HB0286 but was inserted into HB0286S01 DISCLAIMER:
(Buff) H.B.
This document is provided to assist you in your comparison of the two bills.
286 Doug Fiefia proposes the following substitute bill:
Sometimes this automated comparison will NOT be completely accurate.
Therefore, you need to read the actual bills.
This automatically generated document could contain inaccuracies caused by:
limitations of the compare program;
bad input data;
or other causes.
Michael K.
3 LONG TITLE General Description:
McKell 3 LONG TITLE General Description:
▸ requires developers to report certain safety incidents to the Office of Artificial Intelligence Policy (office);
▸ requires developers to report certain safety incidents to the Office of Artificial IHtelligence Policy (office);
s ▸ requires the office to provide annual assessments and legislative recommendations t regarding regulation of certain artificial intelligence models;
B ▸ requires the office to provide annual assessments and legislative recommendations re2arding regulation of certain artificial intelligence models;
S ▸ establishes civil penalties for violations;
8 HB0286 compared with HB0286S01 ▸ establishes civil penalties for violations;
u b ▸ provides whistleblower protections for employees who report safety concerns of certHin artificial intelligence models;
▸ provides whistleblower protections for employees who report safety concerns of certain artificial intelligence models;
B ▸ establishes remedies for employees who suffer adverse action for whistleblower .
▸ establishes remedies for employees who suffer adverse action for whistleblower activities;
activities;
{and} ▸ creates the AI Transparency Enforcement Restricted Account to fund enforcement activities;
2 ▸ creates the AI Transparency Enforcement Restricted Account to fund enforcement activities;
1st Sub.
None Other Special Clauses:
(Buff) H.B.
286 01-28 11:38 None Other Special Clauses:
13-72b-101, Utah Code Annotated 1953 13-72b-102, Utah Code Annotated 1953 13-72b-103, Utah Code Annotated 1953 13-72b-104, Utah Code Annotated 1953 13-72b-105, Utah Code Annotated 1953 13-72b-106, Utah Code Annotated 1953 13-72b-107, Utah Code Annotated 1953 13-72b-108, Utah Code Annotated 1953 13-72b-109, Utah Code Annotated 1953 13-72b-201, Utah Code Annotated 1953 13-72b-202, Utah Code Annotated 1953 13-72b-203, Utah Code Annotated 1953 13-72b-204, Utah Code Annotated 1953 Be it enacted by the Legislature of the state of Utah:
13-72b-101 , Utah Code Annotated 1953 13-72b-102 , Utah Code Annotated 1953 13-72b-103 , Utah Code Annotated 1953 13-72b-104 , Utah Code Annotated 1953 13-72b-105 , Utah Code Annotated 1953 13-72b-106 , Utah Code Annotated 1953 13-72b-107 , Utah Code Annotated 1953 13-72b-108 , Utah Code Annotated 1953 13-72b-109 , Utah Code Annotated 1953 13-72b-201 , Utah Code Annotated 1953 13-72b-202 , Utah Code Annotated 1953 13-72b-203 , Utah Code Annotated 1953 13-72b-204 , Utah Code Annotated 1953 Be it enacted by the Legislature of the state of Utah:
Section 13-72b-101 is enacted to read:
Section 1 is enacted to read:
CHAPTER 72b.
13-72b-101.
AI Transparency Act Part 1.
Artificial Intelligence Transparency and Child Protection 13-72b-101 .
As used in this chapter:
72b.
AI Transparency Act - 2 - HB0286 compared with HB0286S01 1.
Artificial Intelligence Transparency and Child Protection As used in this chapter:
(3)(a) "Catastrophic loss" means:
(3) (a) "Catastrophic loss" means:
or - 2 - 01-28 11:38 1st Sub.
or (ii) damage to property, or loss of property, exceeding $1,000,000,000.
(Buff) H.B.
286 (ii) damage to property, or loss of property, exceeding $1,000,000,000.
(4)(a) "Catastrophic risk" means a foreseeable and material risk that a frontier developer's development, storage, use, or deployment of a frontier model will materially contribute to a catastrophic loss in a single incident by:
(4) (a) "Catastrophic risk" means a foreseeable and material risk that a frontier developer's development, storage, use, or deployment of a frontier model will materially contribute to a catastrophic loss in a single incident by:
(6) "Child safety incident" means an occurrence in which a covered chatbot, when interacting with a minor, engages in behavior that, if engaged in by a human, would be considered to intentionally or recklessly:
- 3 - HB0286 compared with HB0286S01 (6) "Child safety incident" means an occurrence in which a covered chatbot, when interacting with a minor, engages in behavior that, if engaged in by a human, would be considered to intentionally or recklessly:
(a) allows an ordinary person to have conversations in which humanlike responses are - 3 - 1st Sub.
(a) allows an ordinary person to have conversations in which humanlike responses are generated by a foundation model;
(Buff) H.B.
286 01-28 11:38 generated by a foundation model;
(11)(a) "Deploy" means to make a frontier model available to a third party for use, modification, copying, or combination with other software.
(11) (a) "Deploy" means to make a frontier model available to a third party for use, modification, copying, or combination with other software.
(b) "Deploy" does not include making a frontier model available to a third party for the primary purpose of developing or evaluating the frontier model.
- 4 - HB0286 compared with HB0286S01 (b) "Deploy" does not include making a frontier model available to a third party for the primary purpose of developing or evaluating the frontier model.
(13)(a) "Frontier developer" means a person who has used, or initiated the use of, a quantity of computing power of at least 10^26 integer or floating-point operations to train a frontier model, including computing used for the original training run and for any subsequent fine-tuning, reinforcement learning, or other material modifications.
(13) (a) "Frontier developer" means a person who has used, or initiated the use of, a quantity of computing power of at least 10^26 integer or floating-point operations to train a frontier model, including computing used for the original training run and for any subsequent fine-tuning, reinforcement learning, or other material modifications.
Show all 124 changed rows (84 more)
Previous
Latest
(14) "Frontier model" means a foundation model that was trained using a quantity of computing power of at least 10^26 integer or floating-point operations, including - 4 - 01-28 11:38 1st Sub.
(14) "Frontier model" means a foundation model that was trained using a quantity of computing power of at least 10^26 integer or floating-point operations, including computing for the original training run and for any subsequent fine-tuning, reinforcement learning, or other material modifications the developer applies to a {preceding } foundation model.
(Buff) H.B.
(15) "Large frontier developer" means a frontier developer who together with the frontier developer's affiliates, had annual revenue of at least $500,000,000 in the {preceding } calendar year.
286 computing for the original training run and for any subsequent fine-tuning, reinforcement learning, or other material modifications the developer applies to a preceding foundation model.
(15) "Large frontier developer" means a frontier developer who together with the frontier developer's affiliates, had annual revenue of at least $500,000,000 in the preceding calendar year.
Section 13-72b-102 is enacted to read:
Section 2 is enacted to read:
13-72b-102 .
13-72b-102.
(1) A large frontier developer shall write, implement, comply with, and clearly and conspicuously publish on the large frontier developer's internet website a public safety plan that describes in detail how the large frontier developer:
- 5 - HB0286 compared with HB0286S01 (1) A large frontier developer shall write, implement, comply with, and clearly and conspicuously publish on the large frontier developer'sinternet website a public safety plan that describes in detail how the large frontier developer:
(c) applies mitigations to address the potential for catastrophic risks based on the results of assessments undertaken pursuant to Subsection (1)(b);
(c) applies mitigations to address the potential for catastrophic risks based on the results of assessments undertaken {pursuant to } Subsection (1)(b);
(f) revisits and updates the public safety plan, including any criteria that trigger updates and how the large frontier developer determines when the large frontier developer's frontier models are substantially modified enough to require disclosures pursuant to - 5 - 1st Sub.
(f) revisits and updates the public safety plan, including any criteria that trigger updates and how the large frontier developer determines when the large frontier developer's frontier models are substantially modified enough to require disclosures {pursuant to } Section 13-72b-104;
(Buff) H.B.
286 01-28 11:38 Section 13-72b-104;
Section 13-72b-103 is enacted to read:
Section 3 is enacted to read:
13-72b-103 .
13-72b-103.
(1) A large frontier developer that operates a covered chatbot shall write, implement, comply with, and clearly and conspicuously publish on the large frontier developer's internet website a child protection plan that describes in detail how the large frontier developer:
- 6 - HB0286 compared with HB0286S01 (1) A large frontier developer that operates a covered chatbot shall write, implement, comply with, and clearly and conspicuously publish on the large frontier developer's internet website a child protection plan that describes in detail how the large frontier developer:
(c) applies mitigations to address the potential for child safety risks based on the results of assessments undertaken pursuant to Subsection (1)(b);
(c) applies mitigations to address the potential for child safety risks based on the results of assessments undertaken {pursuant to } Subsection (1)(b);
(e) revisits and updates the child protection plan, including any criteria that trigger updates and how the large frontier developer determines when the large frontier developer's foundation models are substantially modified enough to require disclosures pursuant to Section 13-72b-104;
(e) revisits and updates the child protection plan, including any criteria that trigger updates and how the large frontier developer determines when the large frontier developer's foundation models are substantially modified enough to require disclosures {pursuant to } Section 13-72b-104;
and (g) institutes internal governance practices to ensure implementation of the processes described in this Subsection (1).
and (g) institutes internal governance practices to ensure implementation of the processes described in thisSubsection (1).
- 6 - 01-28 11:38 1st Sub.
(2) If a large frontier developer makes a material modification to the large frontier developer's child protection plan, the large frontier developer shall clearly and conspicuously publish the modified child protection plan and a justification for that modification within 30 days after the day on which the large frontier developer makes the material modification.
(Buff) H.B.
286 (2) If a large frontier developer makes a material modification to the large frontier developer's child protection plan, the large frontier developer shall clearly and conspicuously publish the modified child protection plan and a justification for that modification within 30 days after the day on which the large frontier developer makes the material modification.
Section 13-72b-104 is enacted to read:
Section 4 is enacted to read:
13-72b-104 .
13-72b-104.
(1) A large frontier developer shall conspicuously publish on the developer's internet website summaries of the following before deploying a new or substantially modified foundation model as part of a covered chatbot operated by the developer:
(1) A large frontier developer shall conspicuously publish on the developer's i website summaries of the following before deploying a new or substantially modified foundation model as part of a covered chatbot operated by the developer:
(a) assessments of child safety risks conducted pursuant to the developer's child protection plan;
(a) assessments of child safety risks conducted {pursuant to } the developer's child protection plan;
(2) A large frontier developer shall conspicuously publish on the large frontier developer's website summaries of the following before deploying a new frontier model or a frontier model that was substantially modified by the large frontier developer:
- 7 - HB0286 compared with HB0286S01 (2) A large frontier developer shall conspicuously publish on the large frontier developer's website summaries of the following before deploying a new frontier model or a frontier model that was substantially modified by the large frontier developer:
(a) assessments of catastrophic risks from the frontier model conducted pursuant to the developer's public safety plan;
(a) assessments of catastrophic risks from the frontier model conducted {pursuant to } the developer's public safety plan;
Section 13-72b-105 is enacted to read:
Section 5 is enacted to read:
13-72b-105 .
13-72b-105.
(1)(a) A frontier developer may not make a materially false or misleading statement or omission about covered risks from the developer's activities or the developer's management of covered risks.
(1) (a) A frontier developer may not make a materially false or misleading statement or omission about covered risks from the developer's activities or the developer's management of covered risks.
(b) A large frontier developer may not make a materially false or misleading statement or omission about the large frontier developer's implementation of, or compliance - 7 - 1st Sub.
(b) A large frontier developer may not make a materially false or misleading statement or omission about the large frontier developer's implementation of, or compliance with, the large frontier developer's public safety plan.
(Buff) H.B.
286 01-28 11:38 with, the large frontier developer's public safety plan.
(2)(a) When a frontier developer publishes documents to comply with this part, the frontier developer may make redactions to those documents that are necessary to protect:
(2) (a) When a frontier developer publishes documents to comply with this part, the frontier developer may make redactions to those documents that are necessary to protect:
(b) If a frontier developer redacts information in a document pursuant to Subsection (2)(a), the large frontier developer shall:
- 8 - HB0286 compared with HB0286S01 (b) If a frontier developer redacts information in a document {pursuant to } Subsection (2)(a), the large frontier developer shall:
Section 13-72b-106 is enacted to read:
Section 6 is enacted to read:
13-72b-106 .
13-72b-106.
(3) A large frontier developer that discovers a critical safety incident that poses an imminent risk of death or serious physical injury, shall disclose that incident within 24 - 8 - 01-28 11:38 1st Sub.
(3) A large frontier developer that discovers a critical safety incident that poses an imminent risk of death or serious physical injury, shall disclose that incident within 24 hours to a law enforcement agency or public safety agency with appropriate jurisdiction based on the nature of the incident.
(Buff) H.B.
286 hours to a law enforcement agency or public safety agency with appropriate jurisdiction based on the nature of the incident.
or (b) pursuant to an alternate schedule if:
or (b) {pursuant to } an alternate schedule if:
(5) The office may transmit the reports described in Subsections (2) and (4) to the Legislature, the governor, the federal government, or appropriate state agencies, but may consider risks related to trade secrets, public safety, cybersecurity, or national security when transmitting reports.
(5) The office may transmit the reports described in Subsections (2) and (4) to the Legislature, the {r, } governor, the federal government, or appropriate state agencies, but may consider risks related to trade secrets, public safety, cybersecurity, or national security when transmitting reports.
(7) On or before November 1, 2027, and annually thereafter, the office shall prepare a report for the Business and Labor Interim Committee that includes recommendations for modifying this chapter as well as anonymized, aggregated information about reports received pursuant to this chapter, without including information that would compromise the trade secrets or cybersecurity of a frontier developer, public safety, or the national security of the United States or that would be prohibited by any federal or state law.
- 9 - HB0286 compared with HB0286S01 (7) On or before November 1, 2027, and annually thereafter, the office shall prepare a report for the Business and Labor Interim Committee that includes recommendations for modifying this chapter as well as anonymized, aggregated information about reports received {pursuant to } this chapter, without including information that would compromise the trade secrets or cybersecurity of a frontier developer, public safety, or the national security of the United States or that would be prohibited by any federal or state law.
Section 13-72b-107 is enacted to read:
Section 7 is enacted to read:
13-72b-107 .
13-72b-107.
Section 13-72b-108 is enacted to read:
Section 8 is enacted to read:
13-72b-108 .
13-72b-108.
AI Transparency Enforcement Restricted Account -- Creation -- Deposits into account -- Distribution.
{Transfer of frontier developer obligations -- Severability} AI Transparency Enforcement Restricted Account -- Creation -- Deposits into account -- Distribution.
- 9 - 1st Sub.
{(1) {If any provision of this chapter or the application of any provision to any person or circumstance is held invalid by a final decision of a court of competent jurisdiction, the remainder of this chapter shall be given effect without the invalid provision or application.} } (1) There is created within the General Fund a restricted account known as the "AI Transparency Enforcement Restricted Account." (2) The account consists of:
(Buff) H.B.
286 01-28 11:38 (1) There is created within the General Fund a restricted account known as the "AI Transparency Enforcement Restricted Account." (2) The account consists of:
(c) expert witnesses, consultants, and technical advisors with expertise in artificial intelligence safety and frontier models;
- 10 - HB0286 compared with HB0286S01 (c) expert witnesses, consultants, and technical advisors with expertise in artificial intelligence safety and frontier models;
and (f) other expenses related to the administration and enforcement of this chapter.
and (2){(f)} {The provisions } other expenses related to the administration and enforcement of this chapter {are severable} .
Section 9.
{(3) {The duties and obligations imposed by this chapter are cumulative with any other duties or obligations imposed under other law and shall not be construed to relieve any party from any duties or obligations imposed under other law and do not limit any rights or remedies under existing law.} } Section 9.
Section 13-72b-109 is enacted to read:
Section 9 is enacted to read:
13-72b-109 .
13-72b-109.
Section 13-72b-201 is enacted to read:
Section 10 is enacted to read:
Part 2.
13-72b-201.
Public Safety and Child Protection Whistleblower Protections 13-72b-201 .
- 10 - 01-28 11:38 1st Sub.
2.
(Buff) H.B.
Public Safety and Child Protection Whistleblower Protections As used in this part:
286 As used in this part:
(f) immunities;
- 11 - HB0286 compared with HB0286S01 (f) immunities;
Section 13-72b-202 is enacted to read:
Section 11 is enacted to read:
13-72b-202 .
13-72b-202.
(a) reasonably believe that an act poses a specific and substantial threat to public health or safety or to the health or safety of a minor, or is a violation of Part 1, Artificial Intelligence Transparency and Child Protection;
(a) reasonably believe that an act poses a specific and substantial threat to public health or safety or to the health or safety of a minor, or is a violation of Part 1, Artificial Intelligencend Child Protection;
(2)(a) Notwithstanding Title 63G, Chapter 2, Government Records Access and Management Act, and except as provided in Subsection (2)(b), the office may not disclose information that could reasonably be expected to reveal the identity of a reporter.
(2) (a) Notwithstanding Title 63G, Chapter 2, Government Records Access and Management Act, and except as provided in Subsection (2)(b), the office may not disclose information that could reasonably be expected to reveal the identity of a reporter.
(3) A large frontier developer shall provide a reasonable internal process through which an employee may anonymously report information if the employee believes in good faith - 11 - 1st Sub.
(3) A large frontier developer shall provide a reasonable internal process through which an employee may anonymously report information if the employee believes in good faith that:
(Buff) H.B.
286 01-28 11:38 that:
or (b) the large frontier developer has violated Part 1, Artificial Intelligence Transparency and Child Protection.
or (b) the large frontier developer has violated Part 1, Artificial Intelligence and Child Protection.
(5)(a) Except as provided in Subsection (5)(b), disclosures and responses under this section shall be shared with officers and directors of the large frontier developer at least once each quarter.
- 12 - HB0286 compared with HB0286S01 (5) (a) Except as provided in Subsection (5)(b), disclosures and responses under this section shall be shared with officers and directors of the large frontier developer at least once each quarter.
Section 13-72b-203 is enacted to read:
Section 12 is enacted to read:
13-72b-203 .
13-72b-203.
or (c) knows that, or has a reckless disregard as to whether, the disclosure is of information - 12 - 01-28 11:38 1st Sub.
or (c) knows that, or has a reckless disregard as to whether, the disclosure is of information that is false or frivolous.
(Buff) H.B.
(4) Information provided {pursuant to } this section may be classified as a protected record under Subsections 63G-2-305(1) and (2) if the requirements of Subsection 63G-2-309(1)(a)(i) are met.
286 that is false or frivolous.
(4) Information provided pursuant to this section may be classified as a protected record under Subsections 63G-2-305(1) and (2) if the requirements of Subsection 63G-2-309(1)(a)(i) are met.
Section 13-72b-204 is enacted to read:
Section 13 is enacted to read:
13-72b-204 .
13-72b-204.
(1)(a) An employee who alleges a violation of Section 13-72b-203 may bring an action for injunctive relief, actual damages, or both, in a court with jurisdiction under Title 78A, Judiciary and Judicial Administration.
(1) (a) An employee who alleges a violation of Section 13-72b-203 may bring an action for injunctive relief, actual damages, or both, in a court with jurisdiction under Title 78A, Judiciary and Judicial Administration.
(b) An employee may not bring an action under this section more than:
- 13 - HB0286 compared with HB0286S01 (b) An employee may not bring an action under this section more than:
(4)(a) An employer may file a counterclaim against an employee who files a civil action under this section seeking attorney fees and costs incurred by the employer related to the action and the counterclaim.
(4) (a) An employer may file a counterclaim against an employee who files a civil action under this section seeking attorney fees and costs incurred by the employer related to the action and the counterclaim.
Effective date.
- 13 -
1-27-26 10:28 AM - 14 -
View plain text versions (3)

Action History

  1. House/ filed

  2. House/ strike enacting clause

  3. House/ 3rd Reading Calendar to Rules [House Rules Committee]

  4. House/ circled

  5. House/ 3rd reading

  6. LFA/ fiscal note publicly available for HB0286S01

  7. LFA/ fiscal note sent to sponsor for HB0286S01

  8. House/ 2nd reading

  9. House/ comm rpt/ substituted [House Economic Development and Workforce Services Committee]

  10. House Comm - Favorable Recommendation [House Economic Development and Workforce Services Committee]

  11. House Comm - Substitute Recommendation [House Economic Development and Workforce Services Committee]

  12. LFA/ bill sent to agencies for fiscal input for HB0286S01

  13. LFA/ bill assigned to staff for fiscal analysis for HB0286S01

  14. House/ to standing committee [House Economic Development and Workforce Services Committee]

  15. House/ received fiscal note from Fiscal Analyst

  16. LFA/ fiscal note publicly available for HB0286

  17. LFA/ fiscal note sent to sponsor for HB0286

  18. House/ 1st reading (Introduced)

  19. House/ received bill from Legislative Research

  20. LFA/ bill sent to agencies for fiscal input for HB0286

  21. LFA/ bill assigned to staff for fiscal analysis for HB0286

  22. Numbered Bill Publicly Distributed

  23. Bill Numbered but not Distributed

Sponsors

Sponsorship breakdown

Export CSV (upgrade) →

1 sponsors · 1 co-sponsors · 102 not signed on

Sponsors (1)

Co-sponsors (1)

Not signed on (102)

102 members have not signed on to this bill.

Show all 102 →

"Not signed on" means a member has not sponsored or co-sponsored this bill — it does not imply opposition. Members flagged Voted No have a recorded No vote on this bill.

Whip count is in markup. Polling the chamber and every recorded vote this session. Only the first open is slow. It’s instant for you after this. Calling the roll · Tallying · Engrossing

Subjects

Cross-referencing the record. Reading this bill against every other bill in the corpus by meaning, not keywords. Only the first open is slow. It’s instant for you after this. Matching · Ranking · Engrossing

Frequently asked questions

Who sponsors HB 286?
HB 286 is sponsored by Michael K. McKell (Republican) and Doug Fiefia (Republican).
What is the current status of HB 286?
This bill has been sent to the executive. Introduced January 19, 2026. It awaits signature.
Where can I track HB 286?
Track HB 286 free on One Click Politics — get push/email alerts when it moves.

Make your voice heard on HB 286

Find the representatives who decide this bill and tell them where you stand — for yourself, or mobilize your whole list in one click with One Click Politics advocacy software.

Stay ahead of HB 286

Last checked for changes 3 months ago · updated continuously

One Click Politics tracks every bill in Congress and all 50 states.

Track this bill →