{"id":37664,"date":"2026-05-13T15:09:14","date_gmt":"2026-05-13T15:09:14","guid":{"rendered":"https:\/\/www.europesays.com\/ai\/37664\/"},"modified":"2026-05-13T15:09:14","modified_gmt":"2026-05-13T15:09:14","slug":"ai-responsibility-and-transparency-act-key-workplace-impacts-cbia","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ai\/37664\/","title":{"rendered":"AI Responsibility and Transparency Act: Key Workplace Impacts \u00bb CBIA"},"content":{"rendered":"

The following article was first published on Shipman & Goodwin attorney Dan Schwartz\u2019\u00a0Connecticut Employment Law Blog<\/a>.\u00a0It is reposted here with permission.<\/p>\n

On May 1, the General Assembly gave final approval SB 5, now rebranded as the\u00a0Connecticut Artificial Intelligence Responsibility and Transparency Act<\/a>.<\/p>\n

It is a wide-ranging \u201conline safety\u201d and artificial intelligence bill with several provisions that directly affect hiring and employers.<\/p>\n

Gov. Ned Lamont has confirmed he plans to sign it. The bill includes staggered effective dates beginning Oct. 1, 2026.\u00a0<\/p>\n

In this post, we\u2019ll cover the provisions that impact the workplace. In brief, SB 5 sets disclosure and notice requirements for employers that deploy automated tools in recruiting or personnel decisions, clarifies that using such tools is not a defense to discrimination claims, creates whistleblower-style protections and internal reporting obligations for certain high-end AI developers, and adds an AI-related disclosure to WARN notices filed with the Connecticut Department of Labor.\u00a0<\/p>\n

Employers should begin mapping their talent systems, templates, and vendor contracts now so they can build toward compliance ahead of the 2026\u20132027 implementation timeline.<\/p>\n

Automated Tools in Hiring and HR<\/p>\n

SB 5 regulates \u201cautomated employment-related decision technology,\u201d defined broadly to include any technology that processes personal data and produces an output\u2014such as a score, rank, constraint, recommendation, or classification\u2014that is a substantial factor in making, or materially influences, an employment-related decision.<\/p>\n

This definition is intentionally broad and could apply to many commonly used tools, including third-party hiring platforms, resume screening software, assessment tools, scheduling algorithms, and performance analytics systems.<\/p>\n

SB 5 regulates \u201cautomated employment-related decision technology.\u201d<\/p>\n

Certain routine technologies\u2014such as word processing, spreadsheets, email, basic data storage, or tools used only incidentally\u2014are excluded.<\/p>\n

Beginning Oct. 1, 2027, if an employer deploys such a tool that is intended to interact with applicants or employees, the employer must disclose\u2014in plain language\u2014that the person is interacting with the technology, unless a reasonable person would find that fact obvious.\u00a0<\/p>\n

When the tool will be used to generate output as a substantial factor in a decision, the employer must also provide a written notice before the decision. That notice must identify:<\/p>\n

That an automated employment decision tool is being used\u00a0<\/p>\n

The purpose of the tool and the type of employment decision involved\u00a0<\/p>\n

The trade name of the technology\u00a0<\/p>\n

The categories and sources of personal data analyzed\u00a0<\/p>\n

How the data is assessed\u00a0<\/p>\n

Employer contact information\u00a0<\/p>\n

SB 5 contains a trade-secret safe harbor, but if information is withheld on that basis, the employer must provide a notice that identifies what is being withheld and the legal basis for withholding it.\u00a0<\/p>\n

For employers that rely on third-party systems, the statute places duties on \u201cdevelopers\u201d of these automated tools to provide information a \u201cdeployer\u201d (i.e., the employer) needs to meet its obligations, if the tool was sold, licensed, or configured to materially influence employment decisions.<\/p>\n

The developer and deployer may contract for the developer to assume the deployer\u2019s notice duties, but those allocations must be explicit.\u00a0<\/p>\n

Employers will need to inventory resume screeners, interview analyzers, candidate-ranking tools, and similar systems.<\/p>\n

Violations of these automated employment provisions are deemed unfair or deceptive trade practices enforceable solely by the attorney general\u2014there is no private right of action.<\/p>\n

For violations occurring on or before Dec. 31, 2027, the attorney general may issue a cure notice providing 60 days to remedy before filing suit.<\/p>\n

Practically, HR, legal, and privacy teams will need to inventory any resume screeners, interview analyzers, candidate-ranking tools, internal promotion engines, and similar systems, then build a workflow to surface plain-language disclosures early and deliver the more detailed pre-decision notices on time.<\/p>\n

AI Is Not a Defense<\/p>\n

SB 5 amends the Connecticut Fair Employment Practices Act<\/a> to state explicitly that the use of an automated employment-related decision technology is not a defense to a complaint alleging a discriminatory employment practice.\u00a0<\/p>\n

The Commission on Human Rights and Opportunities or a court may, however, consider evidence of anti-bias testing or similar proactive efforts to avoid discrimination, including the quality, efficacy, recency, scope, results, and the employer\u2019s response to those results.\u00a0<\/p>\n

The same \u201cno defense\u201d clarification appears in the statute that prohibits discrimination based on sexual orientation or civil union status.<\/p>\n

The use of an automated employment-related decision technology is not a defense to a discrimination complaint.<\/p>\n

This framing encourages employers to carry out thoughtful pre-deployment and ongoing validation of automated tools, to document mitigation measures, and to ensure human-in-the-loop review for high-stakes decisions\u2014even though such steps do not create a safe harbor.<\/p>\n

For employers, here are the practical steps: work with vendors to secure bias-testing results, methodology summaries, and update cadences, and then align those with internal audits keyed to Connecticut\u2019s definition of a \u201csubstantial factor\u201d and the specific decisions in scope\u2014hiring, promotion, discipline, discharge, or terms and conditions of employment.\u00a0<\/p>\n

In addition, counsel should consider reviewing the data sources and feature sets referenced in the required notice to confirm they are accurate and do not inadvertently signal protected characteristics or proxies.<\/p>\n

Whistleblower-Style Protections, Internal Reporting<\/p>\n

SB 5 creates sector-specific protections for employees of \u201cfrontier developers,\u201d defined as persons doing business in the state who train a foundation model using at least 10^26 floating-point or integer operations across training, fine-tuning, or reinforcement learning.\u00a0<\/p>\n

The law prohibits rules or contracts that allow discharge, discipline, or other penalties against employees for whistleblowing under existing Connecticut law or for reporting, with reasonable cause, activity that poses a specific and substantial danger to public health or safety due to a \u201ccatastrophic risk\u201d\u2014such as expert-level assistance in creating a CBRN weapon or an unmonitored cyberattack causing serious harm.\u00a0<\/p>\n

By Jan. 1, 2027, \u201clarge frontier developers\u201d must establish an anonymous internal reporting process for covered employees, provide status updates on investigations and responses, and elevate reports to officers and directors at least quarterly, with an exception where the report alleges officer or director wrongdoing.<\/p>\n

Violations carry civil penalties enforced by the attorney general.<\/p>\n

Frontier developers must also provide clear notice of these rights via postings, new-hire notices, and periodic notices to remote workers.<\/p>\n

Violations carry civil penalties enforced by the attorney general, with recovery of investigation costs and attorney\u2019s fees available to the state.<\/p>\n

While this regime will be niche for most employers, any Connecticut company operating or partnering on cutting-edge model training should review non-retaliation policies, create an AI safety reporting channel, and verify governance workflows for board-level reporting.<\/p>\n

Leadership should also confirm that confidentiality measures for reports do not conflict with statutory posting and notice obligations.<\/p>\n

WARN Notices<\/p>\n

Beginning Oct. 1, 2026, any employer that serves written notice to the Department of Labor under the federal WARN Act<\/a> must also disclose whether the layoffs are related to the employer\u2019s use of artificial intelligence or another technological change, in the form and manner the labor commissioner prescribes.\u00a0<\/p>\n

This is a straightforward add-on, but it will require coordination between HR, legal, operations, and communications when force reductions implicate automation, redeployment of work, or adoption of AI-enabled systems.<\/p>\n

Employers should draft internal guidance now for characterizing the layoff rationale and tracking the causal link\u2014if any\u2014to AI or technology changes.<\/p>\n

An Unusual Twist<\/p>\n

One of SB 5\u2019s quirkier but important HR-facing features is the requirement to tell applicants or employees\u2014up front and in plain language\u2014when they are interacting with an automated system, unless a reasonable person would find it obvious.\u00a0<\/p>\n

This is a cultural as well as legal shift, especially for chat-based candidate screeners, asynchronous interview platforms that analyze voice or facial expressions, and automated schedulers that look and feel \u201chuman.\u201d\u00a0<\/p>\n

Employers will need to adjust user interfaces, email and SMS templates, and recruiter talking points so that these disclosures are consistent and prominent.<\/p>\n

At the same time, the trade-secret notice mechanism underscores that transparency does not require disclosing proprietary logic\u2014so long as the employer notifies the person that trade-secret information is being withheld and identifies the legal basis for withholding it.\u00a0<\/p>\n

What to Do Now<\/p>\n

SB 5 uses a staggered implementation schedule. Here are the key dates:<\/p>\n

Oct. 1, 2026:\u00a0The automated employment-related decision technology framework and the developer\u2013deployer allocation provisions take effect. The \u201cAI is not a defense\u201d amendments to anti-discrimination statutes become effective. The frontier developer whistleblower provisions take effect. The WARN AI\/technology-change disclosure requirement begins.<\/p>\n

Jan. 1, 2027:\u00a0Large frontier developers must have their anonymous internal reporting process in place.\u00a0<\/p>\n

Oct. 1, 2027:\u00a0The interactive disclosure and pre-decision notice obligations apply to deployments of automated employment-related decision technology.\u00a0<\/p>\n

The attorney general is the exclusive enforcer for the automated employment sections, with an optional 60-day cure period available for violations occurring on or before Dec. 31, 2027. There is no private right of action under these specific sections.<\/p>\n

From a planning standpoint, employers should take these steps now:<\/p>\n

Inventory your tools.\u00a0Identify where automated decision tools touch the employee lifecycle \u2014 from sourcing and screening through performance management and discipline \u2014 and determine whether any system\u2019s output is a \u201csubstantial factor\u201d in decisions.\u00a0<\/p>\n

Standardize your disclosures.\u00a0Build pre-decision notices that accurately describe purpose, trade names, data categories, and sources, and stand up a process to deliver notices early enough to be meaningful.\u00a0<\/p>\n

Operationalize bias testing.\u00a0Work with vendors to memorialize update frequencies and audit access, and document corrective action\u2014recognizing that such efforts do not create a defense but may be considered by CHRO or a court.\u00a0<\/p>\n

Prepare your WARN playbook.\u00a0Address whether AI or other technology changes triggered or contributed to planned reductions, and develop a cross-functional review process to ensure consistent, supportable disclosures to the Department of Labor.\u00a0<\/p>\n

Conclusion<\/p>\n

With SB 5 now through both chambers and\u00a0Gov. Lamont confirming he will sign it<\/a>, employers should launch a cross-functional workstream that inventories automated decision tools, maps decision points, and identifies where SB 5\u2019s disclosures and notices must be layered into recruiting and HR workflows.<\/p>\n

Legal and compliance teams should review vendor agreements to secure the information needed to meet deployer duties, negotiate responsibility allocations where appropriate, and mandate bias testing and remediation protocols aligned with the statute\u2019s factors.<\/p>\n

For organizations close to the \u201cfrontier developer\u201d threshold, add non-retaliation and internal AI-safety reporting to governance programs and ensure board-level visibility into safety reports and responses.\u00a0<\/p>\n

Thoughtful early planning will minimize disruption and reduce risk.<\/p>\n

The first effective date\u2014Oct. 1, 2026 \u2014 is coming up fast for the automated employment framework, the CHRO clarifications, and the WARN AI disclosure.<\/p>\n

Build a detailed timeline that back-plans from Oct. 1, 2027, to pilot and finalize disclosure and notice templates with adequate employee and candidate experience testing.<\/p>\n

Thoughtful early planning will minimize disruption and reduce risk when the new requirements take effect.<\/p>\n

About the author:\u00a0Dan Schwartz<\/a>\u00a0is a partner at Shipman & Goodwin and has decades of experience solving complex, employment law problems for companies.<\/p>\n

\t\t