A vendor telling you their AI is bias-free is telling you about their product. It says nothing about your legal exposure. Those are two different things, and the gap between them is where staffing firms are getting caught in 2026.

The laws moved fast. NYC Local Law 144 has been on the books for a while, and enforcement is picking up. Illinois HB 3773 went live in January 2026. Connecticut signed its AI Responsibility Act in June 2026. More states have bills in motion right now. This is no longer a coastal problem you can watch from a distance.

SIA has been direct about it. Leaning on vendor assurances alone is an indefensible compliance posture. When a candidate or a regulator comes asking, a marketing PDF from your software provider is not a defense. The responsibility lands on the firm making the hiring decision. That is you.

What "bias-free" actually means when a vendor says it

When a vendor says their tool is bias-free, they usually mean one of three things. They ran a fairness test on their training data. They passed a single audit at one point in time. Or they simply have a line in their marketing deck that legal has not challenged yet.

None of those cover how the tool behaves in your shop.

Bias is not a fixed property baked into software. It shows up in use. It depends on your candidate pool, the roles you fill, the way your recruiters set filters, and the data you feed the system every day. A tool that scores fair on the vendor's test set can produce skewed results on your Chicago light industrial reqs. The vendor's certificate does not know that. It cannot.

The laws know this too. That is why they put the obligation on the employer and the employment agency, not just the software maker.

Three live laws, one clear pattern

The specifics differ by state, but the shape is the same. Here is what the three active laws expect from you.

NYC Local Law 144

If you use an automated employment decision tool for candidates or employees in NYC, you need an independent bias audit within the last year. You have to post a summary of the results. You have to give candidates notice before you use the tool. The audit is tied to how the tool is used, not to the vendor's general claims.

Illinois HB 3773

Live since January 2026. It amends the Illinois Human Rights Act to cover AI in employment decisions. You cannot use AI in a way that discriminates based on protected classes. You have to tell candidates when AI is being used. The state can act on complaints. A vendor's fairness claim does not satisfy the notice requirement or the anti-discrimination standard.

Connecticut AI Responsibility Act

Signed June 2026. It sets duties around high-risk AI systems used in employment. It leans on documentation, risk assessment, and transparency. Again, the burden sits with the party deploying the tool to make decisions about people.

Read those three together and the message is plain. You must know how your tools work, prove it with records, and tell candidates what is happening. A vendor cannot do any of that for you. They do not have your candidate data. They do not send your candidate notices. They do not control your recruiters.

Why the vendor's word leaves you exposed

Think about what you can actually produce if a complaint lands on your desk next month.

  • Your own audit results. Tied to your usage, your states, your candidate pool. Not the vendor's lab test.
  • Proof of candidate notice. Records showing you told candidates when AI touched their application.
  • A human review step. Evidence that a person, not just an algorithm, made or reviewed the decision.
  • A contract that shares the risk. Language that puts the vendor on the hook if their tool fails an audit.

Most firms have none of these. They have an email from the vendor and a good feeling. That is the indefensible posture SIA warned about.

The fix is not to rip out your AI. These tools work. They speed up sourcing and screening in ways that matter. The fix is to stop treating vendor claims as your compliance program and start building one that belongs to you.

What to build now

You do not need a legal team of ten to get ahead of this. You need a short, honest inventory and a few controls.

Start with the inventory. List every tool that screens, ranks, scores, or filters candidates. For each one, write down what it does, which states you use it in, and what the vendor has actually given you in writing. Most firms find they own more automated decision tools than they thought, because features got bundled into their ATS and their sourcing software.

Then check the contract. Look for who is responsible if the tool fails a bias audit. If the answer is you and only you, that is a conversation to have with the vendor at renewal.

Then close the two easy gaps. Turn on candidate notices where the tool is used. Add a human review step to any decision the AI influences. Those two moves alone put you ahead of most of the field.

This is a Build and Change problem, and the Change part is where firms stall. New rules only protect you if recruiters actually follow them. A policy nobody uses is worth nothing in front of a regulator.

Your move this week

Pick one tool. The one that touches the most candidates. Ask your vendor three questions in writing this week. When was your last independent bias audit, and can I see it? What documentation do you provide to help me meet NYC, Illinois, and Connecticut requirements? If your tool fails an audit, who carries the liability under our contract?

Their answers will tell you exactly how exposed you are. If they dodge, you have your answer, and you have a decision to make. Start with one tool, one email, one week. That beats waiting for a complaint to teach you the same lesson at a much higher price.