Illinois AI Employment Law: The Notice and Non-Discrimination Duties Need a Record
Illinois House Bill 3773 amended the Illinois Human Rights Act, effective January 1, 2026, to make it a civil-rights violation for an employer to use AI that discriminates in employment decisions, and to require notice when AI is used. Both duties turn on evidence: proving what the AI was asked and what it returned. This article shows where that record gets written.
Illinois House Bill 3773 amended the Illinois Human Rights Act and took effect January 1, 2026. It makes it a civil-rights violation for an employer to use artificial intelligence in a way that discriminates against a protected class in recruitment, hiring, promotion, discipline, discharge, or other terms of employment. It also requires employers to notify employees when AI is used for those decisions. The Illinois Department of Human Rights enforces it. Both duties, the non-discrimination duty and the notice duty, come down to the same practical question when a complaint lands: can you show what the AI actually did. That evidence gets produced, or missed, at the point where the AI call happens.
The two duties
HB 3773 creates two obligations that operate differently. The non-discrimination duty is substantive: the AI must not produce discriminatory outcomes in covered employment decisions. The notice duty is procedural: employees have to be told when AI is being used to make or inform those decisions. An employer can satisfy the notice duty with a policy statement, but defending against a discrimination claim requires something more specific. It requires the record of the individual decisions, because a claim is about a particular person and a particular outcome.
Why the defense is an evidence problem
When an employee alleges that an AI system contributed to a discriminatory decision, the employer's defense rests on facts about that decision. Which system was involved. What inputs it received. What it returned. Which human reviewed it. Whether the same policy applied to comparable candidates. An employer that cannot produce those facts is arguing from absence, which is a weak position in front of the Department of Human Rights. The discrimination question may be substantive, but the ability to answer it is an evidence question, and the evidence has to have been captured when the decision was made.
Application logs miss the decision context
Most HR systems log outcomes. A candidate advanced or did not. An employee was flagged for review or was not. Those logs record what the application decided, not the identity and policy context of the AI call that informed it. When the model call goes to an external LLM, the HR system often has no record of the prompt or the response at all. The record that matters for HB 3773 is the one at the AI request boundary: which identity made the call, what content it carried, which model answered, and what policy applied. That is a different record than the ATS keeps, written at a different layer.
Notice disputes turn on the record too
The notice duty looks procedural, but disputes about notice still turn on evidence. If an employee claims they were never told AI was used, a record showing that AI was in fact used for their decision, and when, anchors the discussion in facts. The same per-decision log that supports the non-discrimination defense also documents where and when AI touched an employment decision, which is exactly the scope the notice duty covers. One record serves both duties. For the parallel treatment under EU law, see HR hiring AI under the EU AI Act.
A wave, not a one-off
Illinois is part of a broader 2026 movement of state AI-employment rules, alongside Colorado's AI Act and other measures. The Colorado AI Act compliance guide covers a related regime. The common thread across these laws is that they hold the deploying employer accountable for AI decisions and expect the employer to be able to show what happened. Building the record once, at the AI request layer, is what makes an organization ready for the next state law rather than scrambling for each one.
DeepInspect
This is the gap DeepInspect closes. DeepInspect sits inline between your HR and employment systems and the models they call. For every AI call tied to an employment decision, it records the calling identity, the model, the content policy applied, and the outcome, which gives you the per-decision evidence both HB 3773 duties depend on. It also applies policy to what each request carries, so categories of employee data you choose to withhold do not reach an external model.
DeepInspect does not decide whether your model is fair; that is your model-governance work. It produces the record that lets you demonstrate what each AI-informed employment decision involved, and documents where AI was used so the notice duty is backed by facts. When the Department of Human Rights asks what the AI did, the answer is a log, not a shrug.
If you deploy AI in employment decisions in Illinois, let's talk today.
Frequently asked questions
- What does Illinois HB 3773 require?
It amended the Illinois Human Rights Act, effective January 1, 2026, to make it a civil-rights violation for an employer to use AI that discriminates against a protected class in employment decisions, and to require notice to employees when AI is used for those decisions. The Illinois Department of Human Rights enforces it.
- How do you defend against an AI discrimination claim?
With the facts of the specific decision: which system was involved, what it received, what it returned, who reviewed it, and whether consistent policy applied. That evidence has to be captured when the decision is made. An employer that cannot produce it is arguing from absence, which is a weak position before the enforcing agency.
- Do HR system logs satisfy the requirement?
Usually not on their own. HR systems log outcomes, not the identity and policy context of the AI call that informed them, and when the model call is to an external LLM the HR system may have no record of the prompt or response. The record HB 3773 defenses rely on is written at the AI request boundary, a different layer than the ATS.
- Does one record cover both the notice and non-discrimination duties?
Yes. A per-decision log that captures where and when AI touched an employment decision supports the non-discrimination defense and documents the scope the notice duty covers. Building that record once at the AI request layer serves both duties and prepares you for the other state AI-employment laws emerging in 2026.