Skip to content

Session Expired

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

Sign In Again

IL HB5322: ALGORITHMIC IMPACT ASSESSMENTS

Dead/Failed Illinois · 2023–2024 session

Last verified Oct 11, 2026 · official bill text

HB5322 · where it stands

This bill did not become law (dead/failed) · last action Jan 7, 2025.

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

Illinois's HB 5322 (103rd General Assembly) would have created the Illinois Commercial Algorithmic Impact Assessments Act. By January 1, 2026, and annually after, deployers and developers of an automated decision tool would have to complete and document an impact assessment, and developers would have to give deployers documentation on intended uses and limitations. It was not passed before the 103rd General Assembly ended (Session Sine Die, January 7, 2025).

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 developers and deployers of automated decision tools to complete annual impact assessments and give documentation to deployers.

Key provisions

  1. By January 1, 2026 and annually after, a deployer of an automated decision tool would have to complete and document an assessment of the tool's nature and extent, how it is used, and its risks, among other things
  2. On or after January 1, 2026 and annually after, developers would have to complete and document a similar assessment
  3. On the Attorney General's request, a developer or deployer would have to provide that Office any impact assessment it performed
  4. A developer would have to give a deployer a statement of intended uses and documentation of known limitations (including foreseeable algorithmic discrimination risks), the types of data used to program or train the tool, and how it was evaluated for validity and explainability
  5. A deployer with fewer than 50 employees would be exempt unless, at the end of the prior calendar year, it deployed a tool that affected more than 999 people per year
  6. Introduced February 9, 2024; assigned to the Executive Committee March 12, 2024; re-referred to Rules April 5, 2024; Session Sine Die January 7, 2025

Latest legislative action

Jan 7, 2025. Session Sine Die

Sponsors

NameRoleDistrict
D Sponsor HD-021

Related and companion bills

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