Your ATS vendor will not show up to your lawsuit. Neither will your sourcing platform. When a candidate claims your AI screened them out unfairly, the name on the complaint is yours. That is not a scare tactic. It is how these laws are written.
Three things changed in late 2025, and together they moved AI compliance from a legal-team footnote to a C-suite problem.
New York City stepped up enforcement of Local Law 144. Colorado rewrote its AI Act weeks before it took effect. And a federal case, Kistler v. Eightfold AI, is testing whether AI screening platforms fall under the Fair Credit Reporting Act. If that case lands the way plaintiffs want, a whole category of staffing tech gets pulled into FCRA territory.
Here is the part that matters for you. In every one of these frameworks, the staffing agency cannot hand off the liability to the vendor. You use the tool. You made the decision. You own the risk.
What Actually Changed
Let me give you the plain version of each one.
NYC Local Law 144. If you use an automated tool to screen or rank candidates for jobs in New York City, you need a bias audit done within the last year by an independent auditor. You have to post the results publicly. You have to tell candidates before you use the tool. For two years the city was quiet on enforcement. In late 2025 that changed. Firms are now getting requests to produce audit records, and "we forgot" is not an answer that holds up.
Colorado AI Act. Colorado passed a broad AI law, then rewrote major pieces of it right before the effective date. The moving target is the problem. Firms that built compliance around the original text had to rebuild. The core idea stuck: if your AI makes a "consequential decision" about employment, you have duties to disclose, to guard against bias, and to give candidates a way to appeal. Staffing decisions count as consequential.
Kistler v. Eightfold AI. This one is the sleeper. The claim is that an AI screening platform functions like a consumer reporting agency, which would drag it under FCRA. If a court agrees, staffing firms using these tools inherit FCRA obligations they never planned for: written notice, candidate consent, and the right to dispute. The case is still moving. You do not want to be the firm that finds out how it ends by getting served.
Why "The Vendor Handles It" Is a Trap
Pull up your ATS contract right now. Find the section on compliance and indemnification. I will bet money it says some version of this: the customer is responsible for lawful use of the product.
That sentence is doing a lot of work. It means the vendor sells you the engine and you drive the car. If you run a red light, the ticket is yours.
Vendors are not being sneaky. They cannot know how you use the tool, in which states, for which candidates. So they push that responsibility to you in writing. The trouble is that most staffing leaders never read that far, and their sales rep said "don't worry, we're compliant" during the demo.
A demo is not a defense. A signed audit report is. A candidate notice with a timestamp is. A record of who reviewed the AI's recommendation is. Those are the things a regulator or a plaintiff's attorney will ask for.
The Multi-State Problem
Most staffing firms do not operate in one place. You source in one state, place in another, and your candidates live everywhere. That is where this gets messy.
The law follows the candidate, not your office. A candidate working in NYC triggers Local Law 144 even if you sit in Dallas. A Colorado resident triggers the Colorado AI Act. FCRA is federal, so it applies everywhere.
You cannot run a different compliance process for every ZIP code. It falls apart in a week. The fix is to build to the strictest standard and apply it across the board. Yes, that means firms in low-regulation states do more than the law technically requires. It also means you stop guessing, and you stop tracking rules candidate by candidate. Cheaper. Cleaner. Safer.
What To Do This Week
You do not need a six-month project. You need to close the biggest gaps fast. Start here.
- List every tool that touches a candidate decision. ATS matching, sourcing platforms, screening chatbots, resume parsers. If it ranks, scores, filters, or recommends, it goes on the list.
- Ask each vendor one question in writing. "Has this tool been audited for bias in the last 12 months, and can you send me the report?" Save the answers. Silence is an answer too.
- Pull your contracts and read the compliance clause. Know exactly what you agreed to own. If the language surprises you, that is the point.
- Check your candidate notices. If you use AI to screen and you are not telling candidates before you do it, that is your fastest fix.
- Put a human in the loop on rejections. If your AI is auto-rejecting candidates with no person reviewing, stop that today. A named reviewer is your best protection across all three frameworks.
None of this requires new software. It requires you to know what you already run and to have proof it runs the way the law expects.
The firms that get sued will not be the ones with the most AI. They will be the ones who could not produce a single record when asked. Do the inventory this week. Send the vendor emails today. That one step puts you ahead of most of your competitors and most of your PE peers.