Connecticut's AI Hiring Law: HR's 2027 Compliance Map

By Brendten Eickstaedt — June 8, 2026

Connecticut AI employment law SB 5 stages AEDT disclosure obligations on HR through October 2027. The compliance map, vendor questions, and NYC comparison.

Connecticut just became the next state to put AI hiring on a calendar. Governor Lamont signed Senate Bill 5, the Connecticut Artificial Intelligence Responsibility and Transparency Act, in late May, and it stages employer obligations across three effective dates between October 2026 and October 2027. If your HR copilot or screening vendor touches a Connecticut applicant, your contract and your candidate-facing flows need to change in the next twelve months.

In Brief:

• Three effective dates: WARN/discrimination amendments October 1, 2026; AI companion rules January 1, 2027; AEDT employer disclosure obligations October 1, 2027. The runway looks long, but vendor renewals signed in 2026 will land inside the window.
• The Connecticut AI employment law covers "automated employment-related decision technology" used as a substantial factor in any hiring, promotion, discipline, or termination decision. The bar for triggering disclosure is not "fully automated"; it is "meaningfully alters the outcome."
• Required pre-decision notice has six fields: AEDT in use, purpose and decision type, trade name, categories of personal data, sources of that data, and employer contact info. Trade secrets carry a safe harbor but require explicit withholding notice.
• For adverse decisions, employers must also give a high-level explanation of the principal reasons, the AEDT's role, the data source, and a chance to examine and correct the data the candidate did not personally provide.
• Connecticut amends the state Fair Practices Act so AI is not a defense to discrimination claims, effective October 1, 2026. Courts can consider anti-bias testing as a mitigating factor, which is the law's lone nudge toward proactive auditing.
• Only the Connecticut AG enforces. There is no private right of action and a 60-day cure window through December 31, 2027.
• WARN Act notices filed in Connecticut must, starting October 1, 2026, disclose whether the layoff is related to AI or technological change.

What Connecticut SB 5 actually requires

The Connecticut AI employment law is built around a "deployer-developer" split that mirrors the EU AI Act and Colorado's revised approach. Deployers, in the employment context, are employers using AEDT against Connecticut residents. Developers are the vendors building or marketing the technology. Under SB 5, the developer must give the employer the information the employer needs to comply, and parties can allocate notice duties by contract as long as the allocation is binding and explicit, per the Akin Gump summary. That contractual carve-out matters. If your vendor's order form does not say who is on the hook for which notice, the default falls on the deployer, which is HR.

Two thresholds drive the law. A "de minimis" factor triggers the real-time interaction disclosure: tell the candidate or employee in plain language that they are interacting with AEDT, unless a reasonable person would already know. A "substantial factor" triggers the full pre-decision written notice, defined as "a factor, including, but not limited to, a constraint, ranking, score, recommendation or classification, that meaningfully alters the outcome of an employment-related decision," per JD Supra's plain-language breakdown. Scoring resumes, ranking candidates, or recommending interview decisions all clear that bar.

The October 2027 disclosure stack

The pre-decision written notice has six fields. Build them into your candidate-facing flows now and you will not be redesigning the application experience under deadline pressure next September.

For adverse decisions, the law layers four more requirements on top: principal reasons, the AEDT's role in producing those reasons, type and source of the underlying data, and the right for the candidate to examine and correct any data they did not personally provide, per the Holland & Knight comprehensive summary. The "data they did not provide" clause is the sleeper. Most ATS systems enrich candidate records with LinkedIn pulls, GitHub crawls, employer history checks, and skills inferences. Connecticut will require you to surface that, and let the candidate fix it.

How Connecticut compares to NYC, Colorado, and the EU

The Connecticut AI employment law sits in a specific spot: narrower than Colorado, broader than NYC, and lighter on proactive obligations than the EU.

The pattern: NYC remains the only US jurisdiction requiring a bias audit. Connecticut and the revised Colorado law have moved toward disclosure and transparency rather than mandatory algorithmic discrimination testing. The EU is still the strictest regime, with risk management, conformity assessment, and post-market monitoring stacked on top of disclosure, per the Morrison Foerster client alert. If your vendor is selling into all four, the EU obligations subsume the rest, and you should be asking for EU AI Act conformity documentation as the baseline.

What HR should do between now and October 2027

The fast moves are contractual. Open every existing AEDT contract and check two clauses. First, does the developer commit to providing the deployer with information sufficient for compliance with applicable law? Second, who is responsible for the candidate-facing notice, and is the allocation explicit? If either clause is missing or vague, push an amendment now while the renewal window is open.

The medium-tempo moves are operational. Map your AEDT footprint by hiring stage and identify which steps clear the "substantial factor" bar. Resume screening, ranking, and structured interview scoring almost always will. Build the six-field notice into the application flow now, even before October 2027, because the cleanest implementation is one that fires for every candidate, not just Connecticut residents. The same logic applied when NYC LL144 went live and most multistate employers ended up bias-auditing everywhere, per the Ogletree client alert.

The slow moves are governance. Adverse-action explanations under the Connecticut AI employment law will require you to explain the AEDT's role in the decision, not just the human reviewer's. That is a data engineering project. Systems that surface "why" alongside "what" today will look very different from systems that ship a score and a screenshot. Pick now.

Quick Hits

• Workday previews an Agent Passport concept. At its developer event Workday unveiled Agent Passport, a portable identity construct for AI agents that ties standards like OWASP LLM Top 10, NIST AI RMF, and MITRE ATLAS to verifiable vendor disclosure. If passports become the norm, HR finally gets a shared language for "is this agent safe to deploy in this environment." Worth asking about at every renewal.
• Phenom highlights Spring 2026 releases with AI profile summaries. Phenom rolled out AI-generated candidate profile summaries inside the Hiring Manager experience. Convenient, and a clear "substantial factor" candidate under Connecticut SB 5. Make sure the summary is logged, surfaceable to the candidate, and editable before any adverse decision.
• Fosway and Phenom benchmarks show a deployment gap. New data shows only about a quarter of claimed AI hiring features are actually in production with customers. The compliance implication: if your vendor's compliance posture is built around features that have not shipped, your disclosure obligation is built around features that do not exist. Verify shipped functionality before signing.

The Operator's Take

The Connecticut AI employment law is being read by HR teams as a 2027 problem. It is a 2026 problem. The October 2026 amendment to the Fair Practices Act takes the "the AI made the decision" defense off the table immediately. The October 2026 WARN amendment requires every Connecticut layoff notice to disclose whether AI was a factor, which means any RIF tied to AI deployment is going to be on the public record. And the October 1, 2026 developer obligation to give deployers compliance information has no grace period: your vendors have to be ready next October, and the only way to know if they are is to ask now.

The smart move for HR is to treat the six-field disclosure as the new minimum data model for every AEDT contract, not a Connecticut-specific carve-out. Build it once, deploy it everywhere, and you will be compliant for NYC, Connecticut, Colorado, Illinois, and whatever the next four states put on the calendar. The teams that try to handle each law as a separate project will be doing this exercise five times in two years. The teams that build the disclosure stack as a permanent fixture will be doing it once.

If you only have one hour to spend on this before the end of June, spend it on your top three AEDT vendor contracts. Look for the developer-compliance clause and the notice-allocation clause. If they are not in there, your renewal terms have just changed.

Resource

Start the contract review with three templates built for exactly this work:

• Get the AI Hiring Vendor RFP Question Bank ($29 — included with Pro subscription). A drop-in question set for vendor evaluations.
• Get the AI Vendor Red Flags Checklist ($29 — included with Pro subscription). Spot the gaps before the renewal lands.
• Get the HR Copilot Configuration Audit Workbook ($29 — included with Pro subscription). Audit the AI features already running inside Workday, SAP, Oracle, UKG, BambooHR, and ADP against Connecticut SB 5 disclosure obligations.

Related Reading

• How to Run an AI Hiring Bias Audit for HR Leaders 2026
• Illinois AI Video Interview Act: Employer Compliance Guide
• Local Law 144 Compliance Guide: What AI Hiring Tools Need in 2026