Skip to content
ParamergeParamerge
Stephen Lieberman
Through Paramerge
Contact

PAN Lab example

Workday AI screening

One model across thousands of employers and testing no one can see

One vendor's screening model runs inside thousands of employers' hiring pipelines at once. Modeled on a platform under a live collective action. Two structures to watch, both independent of how the case is decided: one defect propagates across every employer at once, and the vendor's bias-testing exists but was held legally privileged - so no outside party can tell whether it was pulled, passed, or set aside. The litigation is ongoing; nothing here is a finding, only what the structure exposes.

Stylized model of a documented deploymentHiring & employment screening AI

Open this example in PAN Lab v0.1 to apply pressures and levers and watch what the system does.

What this models

This example runs on the Vendor-screening-class multiplied across employers network: 5 components and 11 pathways between them. Every context in the Lab is a stylized model, never a reconstruction of any actual deployment, and each assumption behind it carries a provenance label.

Evidence base: 3 assumed · 2 published baseline. In the Lab, the shaded evidence band behind each headline readout draws its width from the least-established class below.

  • assumed

    The dynamics carry the platform's reach rather than a single employer's. The one-model-many-employers pathway is drawn at full strength, the catalogue's strongest such coupling: the record has one vendor's screening features operating inside thousands of employer customers at once, and a lead plaintiff rejected more than a hundred times across employers on that one platform. Demand runs high against very limited capacity for the same reason - the recommendations multiply with the platform while each deployer staffs only its own recruiting function, so manual review never scales with reach. Topology is left as derived; this deployment's distinguishing evidence is its dynamics and its vendor-deployer seam, not an extra component.

  • baseline

    This models the vendor-seam pattern documented in the case file - not a reconstruction of the actual platform - and the litigation is live: the agent theory (that the vendor is liable as the employers' agent) survived dismissal in 2024 and a nationwide age-discrimination collective was preliminarily certified in 2025, but these are procedural rulings and allegations, not an adjudicated finding of discrimination. Nothing drawn here is a verdict.

  • assumed

    The multiplication is drawn on the model-to-model edge: one vendor screening model operates inside thousands of employers at once, so one learned defect propagates as widely as the platform reaches, correlated across separate legal employers. The accountability diffusion is drawn on the recruiter-to-vendor operator edge: the employer and the vendor each hold part of the governance the other points to.

  • baseline

    The shielded-testing configuration is drawn as the latent independent model check, empty at baseline: a 2026 discovery ruling held the vendor's internal bias-testing data privileged because counsel curated it, so the testing record exists and is legally unreachable. This is a distinct rung from an absent test - audit opacity as testing shielded from external verification, where no outside party can tell whether the lever was pulled, passed, or set aside. The survey backdrop is that assessment vendors' validation and bias-mitigation claims are frequently unverifiable from outside.

  • assumed

    No applicant outcome and no allegation is adjudicated here. This Lab reads institutional propagation only, and applicants are boundary-only. The litigation posture, the certification, and the privilege ruling live in the case file as what they are - live proceedings, not findings - and are never computed from anything in this diagram.

What this example does not show

  • No applicant outcome and no allegation is adjudicated. The Lab reads institutional propagation only; applicants are boundary-only, and the litigation posture, the collective certification, and the privilege ruling live in the case file as live proceedings - not findings - never computed on this diagram.
  • The litigation is ongoing and the agent theory is novel; the rulings to date are procedural (agent theory sustained at dismissal, a collective certified, testing held privileged), and nothing here is a finding that the platform discriminated - the diagram draws the vendor-seam structure, not a verdict.

Sources and evidence

What this example rests on, claim by claim. Every entry resolves to the same ledger the Evidence Registry publishes.

  • An applicant-tracking platform whose AI screening and recommendation features operate inside thousands of employers' hiring pipelines at once is the subject of a live federal collective action testing whether the vendor is directly liable as the employers' agent. On the litigation record, the court sustained the agent theory at the dismissal stage in 2024 and preliminarily certified a nationwide age-discrimination collective in 2025, covering applicants forty and over since September 2020, on a record in which the lead plaintiff reported more than one hundred rejections across employers using the platform. The litigation is ongoing and nothing here is an adjudicated finding of discrimination; these are allegations and procedural rulings, not a verdict.

    empirical
    • Reference Mobley v. Workday, Inc., No. 3:23-cv-00770 (N.D. Cal.): agent-theory vendor liability (2024), preliminary nationwide ADEA collective certification (2025), bias-testing privilege ruling (2026); via Holland & Knight LLP analysis. https://www.hklaw.com/en/insights/publications/2025/05/federal-court-allows-collective-action-lawsuit-over-alleged

  • A 2026 discovery ruling in the same matter held the vendor's internal bias-testing data privileged because counsel had curated it — meaning the testing record exists and is legally unreachable, a configuration in which audit opacity is not the absence of testing but testing shielded from external verification. The case surfaces two further structural facts: a single vendor's screening model multiplied across many employer boundaries, so one learned defect can propagate as widely as the platform, and accountability diffusion between deployer and vendor, each holding part of the governance the other points to, against a survey backdrop showing assessment vendors' validation and bias-mitigation claims are often unverifiable from outside.

    empirical
    • Academic Raghavan, M., Barocas, S., Kleinberg, J., & Levy, K. (2020). Mitigating Bias in Algorithmic Hiring: Evaluating Claims and Practices. In Proceedings of FAT* '20, 469-481. https://doi.org/10.1145/3351095.3372828 https://arxiv.org/abs/1906.09208
    • Government U.S. EEOC (2023, May 18). Select Issues: Assessing Adverse Impact in Software, Algorithms, and Artificial Intelligence Used in Employment Selection Procedures Under Title VII. Technical assistance document (removed from eeoc.gov early 2025; archived). https://web.archive.org/web/20250102220802/https://www.eeoc.gov/laws/guidance/select-issues-assessing-adverse-impact-software-algorithms-and-artificial

Where this connects

Institutional pressures in this domain

  • Workload surge — Demand outruns staffing; per-case attention shrinks and review becomes triage.
  • Vendor opacity — The deploying institution cannot inspect the model, data, or update pipeline it is accountable for.
  • Compliance over substance — Paper controls (sign-offs, checklists) satisfy audits while the behavior they describe erodes.
  • Data & policy drift — The world, the intake process, and the rules change under a system trained on how things used to be — two mechanisms with different remedies: the statistical properties of what the system processes move (concept drift), or the mixture of inputs arriving in deployment differs from the mixture it was trained on (covariate shift).
  • Reviewer bottleneck — One fixed-capacity checking stage sits between AI output and consequence; everything queues behind it.

All of them in context on the Hiring & employment screening AI domain page.

Levers available here and the patterns behind them

Documented case histories