Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice
Connecticut's Discrimination Rule for Automated Employment Tools: No Defence, No Safe Harbour
The short answer: Since October 1, 2026, under Connecticut's Public Act 26-15 framework as carried in the kit's checker data, using an automated employment-related decision tool is not a defence to a discrimination complaint under the Connecticut Fair Employment Practices Act. The checker adds the sentence employers most need to hear precisely: evidence of bias testing may be considered, but it is not a safe harbour. The rule is already in force — it does not wait for the October 1, 2027 notice duties — and it reshapes how an employer should hold its testing evidence and its vendor claims.
Check your duties and dates — free Build your first notice — free
What is the no-defence rule? It is the removal of a specific argument: 'the tool did it' — or 'the tool was tested' — as an answer to a discrimination complaint about an automated employment decision. The employer's responsibility for its employment decisions remains exactly where it always was; the rule forecloses outsourcing that responsibility to the software. It sits in the checker's Connecticut employment result among the duties in force, next to the WARN disclosure from the same date.
What the rule forecloses: the vendor-shield argument
Before such rules, a familiar defensive posture existed in outline: the employer bought a reputable tool, the vendor represented it as validated, and the outcome — however it landed on a protected group — was the tool's work. The Connecticut rule addresses that posture directly. The decision remains the employer's; the tool's involvement is a fact about the decision, not an answer to a complaint about it.
Practically, this moves vendor diligence from procurement theatre to evidence the employer itself holds: your own evaluation of the tool for your population, your own monitoring of your outcomes, your own review records. A vendor's certificate in a drawer is the weakest form of that evidence; your dated, own-population testing file is the strongest. The deployer-duty principle behind this is the same one that assigns the notices: the duty sits with the deployer.
'Evidence may be considered, but it is not a safe harbour': reading the sentence correctly
The sentence cuts in two directions, and both matter. Against complacency: testing does not immunise — a tested tool whose outcomes discriminate has a documented problem, not a defence. In favour of testing: evidence of bias testing may be considered — the testing file is not pointless; it is part of how the employer's conduct gets evaluated. The rational response is therefore more and better testing, held properly, not less.
'Held properly' means: testing done on your applicant population or a defensible proxy, repeated when the tool or the population changes, with results and responses recorded — a finding acted on is evidence of diligence; a finding filed unread is evidence of knowledge. The record discipline is the same one the notice duties demand: dated, specific, retained.
Worked example: Unionville Health System
Example — fictional business, real duty structure. Unionville is a fictional Connecticut health system using an automated tool for high-volume role screening. Under the no-defence rule, it rebuilt its evidence position:
- Posture changed: the vendor's validation certificate is moved from 'the compliance file' to one input among several; the system's own evaluation becomes the primary document.
- Own testing: bias testing run on its own applicant pool for the screened role families — 2 role families flagged for outcome disparities, put under enhanced human review with outcomes sampled weekly while remediation is assessed.
- Monitoring: outcome rates by role family reviewed monthly from the decision record — 1,150 screening decisions in the first monitored quarter, each carrying its notice and reasons data.
- Review evidence: the human-review queue's changed-outcome rate for the quarter is 7% — recorded evidence that reconsideration is real, filed alongside the testing results.
- File assembled: inventory entry, vendor documentation with limitations, own testing with responses, monitoring reports, and review records in one chain — the file the rule rewards, built from duties that already existed.
What the rule does not do
Precision about limits keeps the rule useful. It does not ban automated employment tools in Connecticut. It does not itself impose the notice duties — those arrive for tools deployed on or after October 1, 2027. It does not make bias testing mandatory in so many words; it changes what testing evidence does in a complaint. And it does not convert every adverse outcome into discrimination: complaints still turn on their facts. The rule removes a shield; it does not create a sword, and this guide does not present it as one.
The checker also notes the Act's own exclusions — decisions about nonmaterial workplace changes and health and safety, scheduling and planning, and productivity monitoring sit outside the Act's listed scope — and its enforcement frame (Attorney General, deceptive trade practice; no private right of action; a 60-day cure period through December 31, 2027 for the Act's violations). Keep those boundaries in the same file as the rule itself, so the position is stated whole.
Preparing under the rule: an employer's evidence file
Build the file the rule implies. Contents: the tool inventory entry (tool, decisions, population); the vendor's technical documentation, including known limitations; your own evaluation and bias-testing results with dates and responses; outcome monitoring by the categories your testing examines; the review queue's records showing human reconsideration with real outcomes; and the notice versions in force. Every item is something the other duties already ask for — the no-defence rule is best read as the reason the file must be genuine rather than assembled.
Refresh triggers matter: a material vendor update, a new role family screened, a shift in applicant volume or mix — each stales the testing file. The vendor's material-update notice duty (Colorado's developer data) exists partly to feed this file; contract for it, and diary the re-test when the notice arrives, per the vendor questions guide.
Interaction with the 2027 notices
When the notice duties arrive for new deployments on October 1, 2027, they will generate the very records this rule makes valuable: notices given per person, opt-outs recorded, decisions explained to the standard the employment track requires. An employer who builds the 2027 notice workflow well is simultaneously building the evidence file the 2026 rule rewards — which is the efficient way to sequence the work: notices as designed in Connecticut AEDT Notices, records as designed in the records guide, testing refreshed on vendor updates.
Run the whole Connecticut employment position through the free checker — its result separates the in-force items from the 2027 notices cleanly, which is the distinction this guide exists to keep visible.
- Retire the vendor-shield assumption in writing: the decision is yours; the tool's involvement is a fact, not a defence
- Hold your own evaluation and bias-testing file — own population, dated, repeated on material change — with responses to findings recorded
- Monitor outcomes from your decision record on a cadence, and route disparities to enhanced review while they are assessed
- Keep the review queue's records as part of the evidence file: real reconsideration, with changed outcomes, is the strongest exhibit
- Re-test on triggers — vendor material updates, new role families, volume or mix shifts — not just on anniversaries
Sources, as carried in the kit's own data: the duty summaries in app/rules.py and the checker data in app/checker_data.py, verified against primary or authoritative sources on October 28, 2026. Run the free duties checker for your jurisdiction, decision type, and the tool's role, and compare the kit's plans for the record, builder, and review queue. More from Ingenious AI is on the hub.
Related guides
- Connecticut WARN Notices and AI Layoffs: The Disclosure in Force Since October 1, 2026
- Vendor vs Deployer: Who Owes the ADMT Notice?
- What to Ask Your AI Vendor Before January 1, 2027: Twelve Questions With the Answers You Need in Writing
- Connecticut Automated Employment Decision Tool Notices: What Employers Must Send and When
See all ADMT guides for the full set.
Frequently asked questions
What is Connecticut's no-defence rule?
Since October 1, 2026, using an automated employment-related decision tool is not a defence to a discrimination complaint under the Connecticut Fair Employment Practices Act.
Does bias testing protect an employer?
Evidence of bias testing may be considered, but it is not a safe harbour. Testing remains worth doing — and worth documenting with its responses — but it does not immunise the employer.
Does the rule ban automated hiring tools in Connecticut?
No. It removes a defensive argument; it does not ban the tools. The notice duties for such tools arrive separately, for deployments on or after October 1, 2027.
Who enforces Public Act 26-15?
The Attorney General, as a deceptive trade practice matter, per the kit's checker data. There is no private right of action, and a 60-day cure period applies to violations through December 31, 2027.
What should an employer do now?
Build the evidence file the rule rewards: own-population evaluation and testing with recorded responses, outcome monitoring, genuine human review records, and vendor documentation — refreshed on material updates.