A NYC bias audit is a use condition, not a hiring verdict

Decide whether the actual use is covered

The direct CHRO task is to map the configured workflow, not classify a vendor brand once. The same platform may support sourcing, screening, ranking, scheduling, assessment, or communication in different ways. Coverage and risk turn on what the tool does, how its output influences an employment decision, who uses it, and which people and locations are affected.

The inventory should name the feature, version, input data, output, decision stage, human role, employer or agency, and deployment geography. A vendor’s generic statement about Local Law 144 readiness cannot substitute for the employer’s facts or for current legal analysis.

Tie the audit to the deployed tool and period

The city describes a bias audit within one year of use. HR should verify that the public summary and underlying audit correspond to the tool, version, data categories, selection process, and use now being considered. A prior audit of a materially different configuration or workflow may not answer the current decision.

The audit record should preserve scope, methodology, data limits, excluded groups, result date, independent-auditor facts where required, and unresolved findings. It should also state what the audit did not test, including accuracy, accessibility, job relatedness, privacy, security, or the quality of the underlying employment criteria.

Operate notice as a workflow control

A notice posted somewhere on a careers site is not automatically evidence that each affected person received the required information on time. Recruiting and employee workflows should identify who receives notice, when the clock starts, which tool and job or decision it concerns, what alternatives or accommodation routes exist, and how delivery is recorded.

Changes to the tool, job family, candidate flow, language, agency, or geographic scope should reopen the notice review. HR, talent acquisition, accessibility, legal, procurement, and the hiring owner need a shared record so that a vendor launch or workflow edit does not silently bypass the approved path.

Keep compliance conditions separate from the employment decision

A completed audit, public summary, and notice are use conditions described by the city; they are not a substantive endorsement of the tool or a finding that a particular decision is fair. The CHRO still needs evidence that the assessment serves a valid job purpose, that people can seek accommodation or correction where applicable, and that humans can challenge unsupported outputs.

The approval should state the lawful and evidence-based purpose, permissible inputs, decision weight, review path, monitoring plan, and stop conditions. If outcome patterns, complaints, inaccessible interactions, unexplained exclusions, or model changes emerge, the organization should investigate the actual workflow rather than pointing to the existence of a bias-audit page.

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 29, 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: Recruiting and candidate support; Workplace AI governance and change; Performance and work allocation; People analytics and employee listening. 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.

Limitations and unknowns

This briefing summarizes New York City’s public AEDT page and is not legal, employment, labor, civil-rights, accessibility, privacy, or audit advice. It does not determine whether a tool or use is covered, whether an audit or notice is sufficient, or whether an employment decision is valid. Current rules, facts, and qualified review control.