Co-Employment Does Not Split the Applicant in Half
A PEO configures the screening tool. The client company writes the requisition and makes the offer. When the ranked list turns out to skew, neither party can point at the other's half of the process — because from the applicant's side there was only ever one process.
Why Co-Employment Changes the Analysis
A professional employer organization, an employer of record, and a staffing firm all do the same structural thing: they insert a second legal employer between the worker and the company where the work actually happens. That structure exists to move payroll, benefits administration, and employment-tax burden onto a specialist. It was never designed to move anti-discrimination duties anywhere.
Anti-discrimination statutes ask a functional question — who controlled the terms and conditions of employment, and who had the power to grant or deny the opportunity. In a co-employment arrangement the honest answer is frequently "both," which is why charging parties name both. The AI screening tool does not create this problem; it concentrates it, because the screening step is now a single artefact that both parties touched and that leaves a durable record of exactly who it filtered out.
Where Each Party Actually Touches the Pipeline
Client Company: Requisition and Thresholds
HIGH RISKWrites the job description, sets minimum years of experience, chooses which credentials are knockouts, and often tunes the score cutoff that decides how many candidates advance
PEO: Tool Selection and Configuration
HIGH RISKChooses the screening vendor, maps the client's requirements onto model features, administers the applicant tracking system, and delivers the filtered slate
Client Company: Final Selection
HIGH RISKInterviews and hires only from the slate it was handed, which means every candidate the tool suppressed was never available to be chosen
PEO: Records and Retention
MEDIUM RISKHolds the applicant flow data, score distributions, and disposition codes that a disparate-impact analysis depends on — often on infrastructure the client cannot query
Screening Vendor: Model and Training Data
MEDIUM RISKSupplies the underlying model and any generic bias documentation, but typically disclaims deployment-specific outcomes in its terms
The Records Problem Nobody Budgets For
Defending a disparate-impact claim requires showing what the tool did across the whole applicant population — pass rates by group at each stage, the score distribution, and the business justification for the cutoff. In a co-employment arrangement that data is split. The PEO's applicant tracking system holds the flow records. The client holds the interview notes and the offer decisions. The vendor holds the model internals and will usually not produce them.
The moment a charge lands, each party discovers it can only tell part of the story, and the service agreement almost never says who has to hand over what, on what timeline, at whose cost. That gap is worth closing before it is tested, because the entity that cannot produce its share of the record is the entity that carries the adverse inference.
Contract Terms Worth Adding Before the Next Renewal
For both sides of a PEO, EOR, or staffing relationship that involves any automated screening.
Audit your AI product's compliance exposure
RatedWithAI helps tech teams understand their compliance posture across accessibility, privacy, and AI regulation requirements. Start with a free scan.
Scan Your Product for Free →Frequently Asked Questions
Our PEO says its screening vendor already completed a bias audit. Does that cover us?
Treat it as evidence, not as compliance. A vendor's model-level audit is run on the vendor's own evaluation population, not on your requisitions, your thresholds, or your applicant pool. Bias-audit statutes are written around the tool as used to screen candidates for a specific position, which is a deployment-level fact. Ask for the audit that covers your configuration, and if it does not exist, decide which co-employer is commissioning it.
We're the PEO. Can we require clients to accept sole liability for screening criteria they dictate?
You can allocate the cost between you contractually, and you should — a clause tying indemnity to client-supplied knockout criteria is reasonable. What you cannot do is contract your way off a charge. If you selected the tool, configured it, and delivered the filtered slate, you are a participant in the selection process and can be named regardless of what the agreement says about who pays.
Does an employer-of-record arrangement for a single remote hire carry the same risk?
The structure is the same, but the exposure profile differs. EOR engagements often involve a named candidate the client already sourced, so there is no algorithmic filtering of a pool and no disparate-impact surface. The risk appears when the EOR or PEO also runs sourcing and screening at volume, because that is where a scored cutoff starts suppressing groups of applicants who never reach a human.
What is the single cheapest thing to fix first?
The data-access clause. Every other question — whether the impact is real, whether the cutoff was justified, whether the audit was adequate — is answered from the applicant-flow records, and in a co-employment arrangement the party being sued frequently does not hold them. A one-paragraph right to obtain that data on request costs nothing at renewal and is the difference between defending a claim and conceding it.