A resume screener that ranks applicants, a chatbot that schedules interviews, a scoring tool that flags flight risk before promotion season: Illinois now treats AI in hiring as an employment decision governed by the state's civil rights statute. HB 3773 took effect on January 1, 2026, and it does two things that reach straight into your paperwork. It makes discriminatory AI output a civil rights violation whether or not anyone intended it, and it obligates employers to tell applicants and employees when artificial intelligence is in the loop. Most handbooks drafted before that date say nothing about either. Here is what the Illinois amendment actually demands, how Colorado and Connecticut diverge from it, and which language belongs in your employee handbook and hiring documents now.
What Illinois HB 3773 actually changed
HB 3773 is not a standalone AI statute. It amends the Employment Article of the Illinois Human Rights Act, which means the conduct it reaches is enforced through machinery that already exists: a charge filed with the Illinois Department of Human Rights, then the Human Rights Commission, with the usual remedies of damages, injunctive relief, and attorney's fees. There is no new agency, no registration, no filing.
The substance sits in three pieces. First, an employer commits a civil rights violation by using AI that has the effect of subjecting employees or applicants to discrimination on the basis of a protected class, across recruitment, hiring, promotion, renewal of employment, selection for training or apprenticeship, discharge, discipline, tenure, and the terms or conditions of employment. Effect, not intent. Second, using zip codes as a proxy for a protected class is independently unlawful, which matters because commute-distance scoring and "candidate fit by location" features are common in applicant tracking systems. Third, an employer who fails to give notice that AI is being used for those decisions has violated the Act.
The statute defines artificial intelligence broadly enough to catch tools your HR team does not think of as AI, including generative systems and machine-learning scoring layers bolted onto ordinary recruiting software. It also preserves room for predictive analytics used to widen a candidate pool rather than narrow it, so diversity sourcing tools are not swept up by accident.
Legal framework and the pieces sitting around it
The operative text is Public Act 103-0804, signed August 9, 2024, with a delayed effective date of January 1, 2026. Coverage follows the Illinois Human Rights Act definition of employer, which reaches any person employing one or more employees within Illinois during twenty or more calendar weeks in the year of the alleged violation or the year before, with no numerical threshold at all for disability, pregnancy, and sexual harassment claims. A company headquartered in Texas that hires remote workers into Illinois is squarely inside the statute. You can read the enacted language in the Illinois General Assembly text of Public Act 103-0804.
The Act directs the Illinois Department of Human Rights to adopt rules setting the circumstances requiring notice, the timing, and the means of delivery. IDHR published proposed amendments to the Illinois Administrative Code, opened a comment period, then temporarily withdrew the proposal and canceled the scheduled hearing. The withdrawal changed nothing about the statutory duty: notice is required, and the detailed mechanics simply remain unwritten. Employers who read the pause as a grace period are reading it wrong.
Illinois also has a second, older layer that predates all of this. The Artificial Intelligence Video Interview Act has applied since 2020 to employers who use AI to analyze recorded video interviews, requiring advance notice of how the technology works and what characteristics it evaluates, consent before use, deletion of the recording within thirty days of a request, and demographic reporting where AI alone screens candidates into in-person interviews. The two Illinois laws stack, and complying with one does not discharge the other.
Colorado's rewrite and Connecticut's staggered clock
Colorado spent two years as the reference point for state AI regulation and then abandoned the model. SB 24-205, the original Colorado AI Act with its duty of care against algorithmic discrimination, risk management programs, and impact assessments, never took effect. Governor Polis signed SB 26-189 on May 14, 2026, repealing and reenacting the framework around automated decision-making technology that materially influences a consequential decision, employment included. The new obligations run from January 1, 2027, and they lean on disclosure rather than governance: notice at the point of interaction, a plain-language explanation of the technology's role within thirty days of an adverse outcome, a right to request correction of inaccurate personal data, and a path to meaningful human review. Enforcement sits with the Attorney General under the Colorado Consumer Protection Act, and rulemaking on the adverse-outcome disclosures is still in progress. Litigation over the framework is live, so the January date is not entirely settled.
Connecticut moved in the opposite direction, toward breadth. The Artificial Intelligence Responsibility and Transparency Act, signed by Governor Lamont in late May 2026 as Public Act 26-15, phases in across two years. From October 1, 2026, the Connecticut Fair Employment Practices Act is amended so that an employer's reliance on automated employment-related decision technology is not a defense to a discrimination complaint, developer-to-deployer information duties begin, and WARN notices must state whether the layoffs relate to the employer's use of AI or other technological change. From October 1, 2027, the interaction disclosures and written pre-decision notices apply to newly deployed tools. There is no private right of action, and the Attorney General must issue a sixty-day cure notice for violations occurring before the end of 2027.
Layer in California, where FEHA regulations on automated decision systems have applied since October 1, 2025, and New York City, where Local Law 144 has required annual independent bias audits with published results and ten business days of candidate notice since 2023, and the practical picture is clear. A multistate employer cannot run one process and one notice.
Why your handbook is probably out of date
Handbooks written before 2026 tend to have an equal employment opportunity statement, a recruitment section describing interviews and reference checks, and nothing between them about how candidates are actually screened. That gap is now a compliance exposure in Illinois and a scheduled one in Connecticut.
The fix is not a paragraph of reassurance about fairness. It is a disclosure that identifies, in language an applicant can follow, which stages of the process involve automated tools, what those tools evaluate, and how a person can raise a concern or request human review. A well-drafted US employee handbook template gives you the structural place to put it, alongside the EEO policy and the complaint procedure it depends on. The recruitment and promotion sections need the same treatment, because HB 3773 covers promotion, discipline, and discharge, not only the front door.
Offer paperwork deserves a look too. An at-will employment agreement that incorporates the handbook by reference will carry the AI disclosure forward automatically, which is far cleaner than issuing separate notices at each decision point and then trying to prove years later that the applicant received one. Keep the record: notice you cannot evidence is notice you did not give.
Zip codes, proxies, and the vendor you never vetted
The zip code prohibition is the provision employers underestimate. Very few recruiters consciously score candidates by neighborhood, but plenty of applicant tracking configurations weight commute distance, and plenty of scoring models ingest address fields without anyone auditing what the model does with them. Under the Illinois amendment the question is not whether you meant to use geography as a stand-in for race or national origin. It is whether the tool did.
Vendor contracts matter here because liability does not travel with the software. Illinois reaches the employer's use of the tool, Connecticut's amendment says reliance on the technology is no defense, and California's rules put employers on the hook for what agents and staffing partners deploy on their behalf. Procurement language is a recovery mechanism, not a shield. A properly scoped master services agreement should extract documentation of what the model measures, testing results, indemnification, and a commitment to supply whatever the employer needs for its own notice obligations. Nonprofit employers face the identical analysis and often have thinner HR infrastructure, so a compliant nonprofit employment agreement is worth aligning with the same disclosure language.
Building the disclosure into your documents
Captain.Legal takes the ordinary route to this problem, which is to build the policy where it will actually be read. You start from the employment section, choose the handbook or the agreement you need, and answer questions about headcount, the states where you employ people, and the policies you want included: equal employment opportunity, complaint and investigation procedure, discipline, remote work, leave. The generator adjusts the clauses to the states you select rather than producing a single national text that fits none of them.
For the AI disclosure specifically, you describe where automated tools sit in your process and the document produces notice language that names the covered decisions, explains what the tools assess, and points to the human contact for questions. The output arrives in Word and PDF, so counsel can revise the Word file when IDHR eventually finalizes its notice rules, and the PDF goes into the acknowledgment file. Rebuilding the handbook from scratch each time a state moves is the alternative, and it is the reason most handbooks lag two years behind the statutes.
Mistakes employers keep making
The most frequent one is treating the Illinois rulemaking pause as permission to wait. The notice duty has been enforceable since January 1, 2026, and a charge filed today is measured against the statute, not against rules that were never adopted. Close behind is scope error: employers write a hiring disclosure and stop there, when HB 3773 covers promotion, training selection, discipline, discharge, and the terms of employment. A performance analytics tool used in promotion cycles is inside the statute.
Then there is the compliance-by-vendor reflex, the assumption that a supplier's bias audit report answers the employer's obligation. It does not. New York City requires the audit; Illinois requires notice and clean outcomes; Colorado will require explanations and human review. These are different duties with different proof. Employers also forget that Illinois has two AI laws, and that video interview analysis triggers consent and deletion duties on top of everything else. Finally, almost nobody documents delivery. The employer who can produce a dated acknowledgment is in a very different position from the one who insists the notice was in the portal somewhere.
Frequently asked questions
Does Illinois HB 3773 apply if I only have a handful of employees in Illinois?
Almost certainly yes. The Illinois Human Rights Act defines employer to include any person employing one or more employees within Illinois for twenty or more calendar weeks in the year of the alleged violation or the preceding year, and there is no headcount threshold at all where the claim involves disability, pregnancy, or sexual harassment. Physical presence of the business is not the test. If you hire remote workers who live and work in Illinois, or you recruit for Illinois-based roles, the amendment reaches your process. Small employers get no exemption from the notice duty.
What exactly has to go in the AI notice?
The statute requires notice that AI is being used for the covered employment decisions and leaves the circumstances, timing, and delivery method to the Illinois Department of Human Rights. Those proposed rules were published and then temporarily withdrawn, so no fixed template exists. In practice, notice that identifies the stages of the process involving automated tools, describes in plain language what those tools evaluate, and gives a contact for questions will satisfy the statutory duty as written. Draft it in a format you can revise, because the rules will eventually land.
Is an employee handbook a legally valid way to give the notice?
A handbook works for current employees, provided you can prove receipt and the policy is specific rather than aspirational. It does not solve the applicant side, since candidates never see it. Most employers run both: handbook language for the workforce and a disclosure on the careers page or in the application flow for candidates. Keep the two consistent, because a discrepancy between what the handbook promises and what applicants are told is exactly the kind of inconsistency that surfaces in a Department of Human Rights investigation.
Can I download an AI disclosure policy in Word or PDF?
Yes. Employment policy documents generated on Captain.Legal, including the handbook template with its EEO and recruitment sections, download in both Word and PDF. The Word version is the practical one to keep, since AI notice language will need editing once IDHR finalizes its rules and as Connecticut's 2027 obligations approach. The PDF is what you circulate for acknowledgment and archive with the signed receipt. Storing both, with the date of issue, is what turns a policy into evidence.
When do Connecticut's obligations actually bite?
The first date is October 1, 2026, when the amendment to the Connecticut Fair Employment Practices Act takes effect, along with the developer information duties and the WARN notice disclosure about AI-related layoffs. The second is October 1, 2027, when interaction disclosures and written pre-decision notices apply to automated employment decision tools deployed on or after that date. Enforcement rests with the Attorney General, and violations occurring before the end of 2027 carry a discretionary sixty-day cure period. There is no private right of action under the Connecticut act.
Does an at-will disclaimer protect me if an AI tool screened someone out?
No. At-will employment governs the duration of the relationship, not the legality of the selection criteria, and no state permits discriminatory screening simply because employment would have been terminable at will. Connecticut went further and wrote into its statute that reliance on automated employment decision technology is not a defense to a discrimination complaint. The at-will clause still matters for other reasons, and the employment document library covers the agreements that carry it, but it does nothing for algorithmic discrimination exposure.
Are zip codes really prohibited, or only when they correlate with race?
The Illinois text prohibits using zip codes as a proxy for protected classes, and the analysis turns on function rather than intent. If a location field feeds a scoring model that produces disparate outcomes, the fact that no one designed it as a racial proxy is not an answer. The practical response is to inventory which fields your tools ingest, ask the vendor what weight geography carries, and remove commute-distance scoring from screening stages unless the role genuinely requires proximity and you can document why.
Does my vendor's bias audit satisfy Illinois law?
An independent bias audit is strong evidence and worth commissioning, but it is a New York City requirement, not an Illinois one, and it does not discharge either the notice duty or the anti-discrimination standard under the Illinois Human Rights Act. California's rules treat documented anti-bias testing as evidence bearing on liability rather than as a safe harbor, and Colorado's replacement framework asks for disclosure and human review instead of audits. Treat the audit as one piece of a defense file, alongside your notices, acknowledgments, and vendor documentation.