Answer capsule
Bias audits, published summaries, and notices turn vendor and employer process into a reviewable record.
What the source establishes
- Local Law 144 covers certain automated employment decision tools.
- Covered use requires a recent bias audit and public summary.
- Candidate or employee notice requirements apply.
Scope before audit
The first question is whether the configured tool and actual use fall within the definition. A vendor's generic label cannot answer that for the employer.
An audit is not absolution
A published metric can reveal important disparities but does not prove job relatedness, accessibility, data quality, or nondiscrimination in every decision.
Notice needs an experience
A notice should connect to an understandable explanation, accommodation route, data policy, and human contact—not merely satisfy a posting step.
Maintain deployment evidence
Keep the use dates, version, job groups, audit scope, public posting, notices, changes, and responsible owners in one record.
Turn this source into a reviewable decision
For AI for CHROs, use this briefing as a dated decision record rather than a substitute for the source. Preserve New York City Department of Consumer and Worker Protection, the exact URL, the July 20, 2026 review date, the supported facts above, the editorial interpretation, the limitations, and any buyer-specific evidence. Link that record to the decisions most directly affected: Workforce and capacity planning; Recruiting and candidate support; Skills intelligence and internal mobility; Learning and capability development. State whether the source changes the scope, evidence requirement, control, sequence, or only the language used to describe the decision.
Before action, name the accountable owner, affected population and workflow, exact offering or configuration, source data and rights, human decision point, exception and appeal path, complete cost, expected benefit, failure and stop conditions, retained evidence, and next review date. Keep official facts, provider statements, buyer observations, representative tests, measured outcomes, editorial inferences, and unknowns visibly separate. Reopen the record when the source, offer, model, integration, data, policy, population, responsible person, or measured result changes.
Decision test
Ask whether the source changes the decision itself, the evidence required, the implementation sequence, or only the language used to describe an existing capability. Record which claims are directly supported, which are provider statements, which require an independent test, and which remain unknown. A source-linked review should make uncertainty easier to see, not bury it inside a blended score.
Questions to take into review
- Which business demand and skills definitions drive the model?
- How are contingent and affected worker populations represented?
- Does the tool materially influence who advances?
- What validated job criteria support the output?
- Who owns the skills taxonomy?
- Can employees inspect and correct their profile?
- Which learning outcome is being assessed?
- What data is visible to managers or used in employment decisions?
The publication supports research and executive decision preparation. It does not provide legal, financial, accounting, employment, clinical, cybersecurity, investment, procurement, or implementation advice.