Compliance Guide

Illinois HB 3773 AI Employment Compliance Guide

Illinois HB 3773 amends the Illinois Human Rights Act to prohibit AI-driven discrimination in employment decisions, restrict ZIP code as a proxy variable, and require employee notice when AI informs hiring, promotion, discipline, or termination decisions. It takes effect January 1, 2026 and is enforced by the Illinois Department of Human Rights. Compliance requires inventorying in-scope AI systems, reviewing input features for proxy discrimination risk, implementing notice mechanisms, and maintaining decision records that support IDHR inquiries.

HB 3773 at a Glance

Effective Date
January 1, 2026
Enforcement Body
Illinois Department of Human Rights (IDHR)
Covered Decisions
Recruitment, hiring, promotion, training selection, discipline, termination
Key Restriction
ZIP code prohibited as a proxy for protected class status

What HB 3773 Changes

HB 3773 amends the Illinois Human Rights Act to address employer use of artificial intelligence, including generative AI, in employment decisions. Signed by Governor JB Pritzker in August 2024, the law takes effect January 1, 2026. It does not create a standalone AI statute; instead, it folds AI-related discrimination into the existing IHRA enforcement framework, meaning violations are pursued through the same complaint and investigation process IDHR already uses for other employment discrimination claims.

The law applies to AI used across the employment lifecycle, from recruitment and hiring through promotion, training selection, discipline, and termination. Its definition of artificial intelligence is broad enough to cover both traditional statistical or algorithmic scoring tools and generative AI systems, which expands scope beyond the narrower automated employment decision tool definitions used in some other state and local laws.

Core Obligations

Three obligations sit at the center of HB 3773:

  • Non-discrimination: employers may not use AI in a way that subjects employees or applicants to discrimination based on protected classes recognized under the IHRA.
  • ZIP code restriction: the law specifically prohibits using ZIP code as a proxy for protected class status when AI informs an employment decision. This implies that employers need visibility into which input features their AI tools rely on, since ZIP code and similar geographic variables can correlate with race, national origin, or other protected characteristics even when not explicitly used as inputs.
  • Employee notice: employers must notify employees when AI is used to make decisions affecting them. The statute does not specify exact notice language or delivery mechanics; organizations should expect further detail through IDHR rulemaking rather than the bill text itself.

What the Law Does Not Prescribe

Unlike NYC Local Law 144, which mandates independent bias audits for automated employment decision tools, HB 3773 does not specify a bias-audit methodology or a technical testing standard. It also does not prescribe a required audit trail or logging architecture in the statute text.

The compliance obligations as written center on discrimination outcomes and notice, not on a defined system architecture. This gives employers latitude in how they implement compliance, but it also means organizations cannot point to a checklist of technical requirements in the statute itself. IDHR rulemaking was pending as of the most recent available research, and procedural or documentation requirements may be added once implementing regulations are finalized. Compliance programs built now should be treated as provisional and revisited when those rules are published.

Where Runtime Controls Fit

HB 3773 does not mandate a specific technical architecture, but its non-discrimination and notice obligations create practical dependencies on system-level visibility. Employers need to know which AI systems are actually making or influencing employment decisions at the point of use, not just what a vendor's documentation claims.

This is where runtime governance and monitoring become relevant as an operational control, distinct from legal compliance itself. Runtime policy enforcement can restrict which AI agents or tools are permitted to access employment-related data or invoke decision-influencing functions, based on least-privilege permissions rather than static role assignments. Audit logging at the runtime layer can record when an AI system was invoked, what inputs it processed, and what output it produced for a given employment action, which supports the kind of decision-level record keeping HB 3773's notice provisions imply.

Trussed AI provides runtime governance and security for enterprise AI agents, including access controls, tool approval workflows, and audit logging, which organizations can apply to AI systems operating in employment workflows as one component of a broader HB 3773 compliance program. This is not a substitute for legal review or IDHR rule compliance, but it addresses the technical visibility gap that statute text alone does not resolve.

Systems and Data Flows in Scope

Before notice or documentation controls can work, organizations need a clear map of where AI actually touches employment decisions.

  1. 1

    AI/ADT Inventory

    Catalog every AI or automated tool used in recruitment, screening, promotion, discipline, or termination workflows.

  2. 2

    Feature Transparency

    Identify which input features each tool uses, with particular attention to ZIP code and other geographic or demographic proxies.

  3. 3

    HRIS Integration Points

    Map where AI/ADT tools connect to core HR information systems to confirm which decisions are AI-influenced versus human-only.

  4. 4

    Decision Logging

    Capture when and how AI outputs influenced a specific employment decision, to support notice obligations and potential IDHR review.

  5. 5

    Access Boundaries

    Restrict configuration and model-tuning access to designated, accountable personnel rather than broad HR or vendor access.

Building a Compliance Program

A practical sequence for operationalizing HB 3773 ahead of the January 1, 2026 effective date.

Inventory every in-scope tool

Complete an inventory of AI and automated tools used across the full employment lifecycle, including vendor-supplied tools embedded in HR platforms.

Review input features for proxy risk

Review input features in each in-scope tool for correlation with protected class status, with specific attention to ZIP code and other geographic variables.

Build and test notice mechanisms

Develop and test notice language and delivery mechanisms for employees and applicants affected by AI-informed decisions.

Establish decision-level record keeping

Establish record keeping that can demonstrate what role AI played in a given hiring, promotion, discipline, or termination outcome.

Assign cross-functional ownership

Assign ownership across HR, legal, AI/data science, and IT security, since the law spans employment law, anti-discrimination law, and AI system oversight.

Track IDHR rulemaking

Monitor IDHR rulemaking activity and revise compliance documentation once implementing regulations are published.

Frequently Asked Questions

Does HB 3773 apply to third-party AI hiring vendors?

The statute addresses employer use of AI in employment decisions. Employers using third-party AI hiring or HR tools should review vendor contracts to clarify responsibility for compliance, data handling, and audit support, since liability under the IHRA framework generally attaches to the employer.

Does HB 3773 require a bias audit like NYC Local Law 144?

The statute text does not specify a bias-audit mandate comparable to NYC Local Law 144. Compliance mechanics beyond non-discrimination and notice may be clarified through forthcoming IDHR rulemaking.

What counts as "artificial intelligence" under HB 3773?

The law defines artificial intelligence broadly, covering both traditional algorithmic or statistical scoring tools and generative AI systems. Organizations should verify the exact statutory language against the enacted bill text for precise scope.

Is Illinois HB 3773 similar to Colorado's AI Act?

Both address AI use affecting individuals, but they differ in scope and mechanics. Colorado's AI Act has been subject to legislative delay and revision, so organizations operating in both states should track each law's current requirements separately rather than assume equivalence.

Prepare for HB 3773 Before It Takes Effect

Illinois HB 3773 takes effect January 1, 2026. Employers using AI in employment decisions need visibility into which systems are in scope and how those systems are governed at runtime.

Talk to an Expert