Is This AI Hiring Tool Deployable in NYC?

The Pre-Deployment Gate: What "Deployable in NYC" Actually Means

Your talent acquisition team just finished a demo of a new resume-screening tool. The sales rep was sharp, the interface is clean, and the pilot group loved how fast it ranked two hundred applicants down to a shortlist of twelve. Legal wants a green light by Friday. Someone on your team asks the question that stops the whole rollout: has this vendor actually had its tool audited under Local Law 144, and can you prove it if DCWP ever asks?

That question — not the demo, not the price, not the integration timeline — is the real gate between a tool sitting in a sales pipeline and a tool you can legally run against New York City resident candidates. Deploy first and check later, and you're the one holding the liability, not the vendor. Vendors don't get fined under Local Law 144. Employers do.

An automated employment decision tool, under the law, is any computational process derived from machine learning, statistical modeling, data analytics, or AI that issues a simplified output — a score, classification, or recommendation — used to substantially assist or replace discretionary hiring or promotion decisions (Perkins Coie, 2023). If the tool you're evaluating ranks, scores, or filters candidates, it's almost certainly in scope. Local Law 144 took effect January 1, 2023, with enforcement beginning July 5, 2023, after a delay from an originally announced April 15 start date (Epstein Becker Green / Workforce Bulletin, 2023).

Is an AI Hiring Tool Deployable in NYC Without a Current Audit?

No. Not legally, not defensibly, and not in a way that survives a records request. Local Law 144 imposes three core obligations before an AEDT can touch a NYC-resident candidate or employee: an annual independent bias audit; a public summary of the most recent audit results posted on the employer's website, including the AEDT's distribution date; and candidate or employee notice at least 10 business days before the tool is used, with a path to request an alternative process or accommodation (Crowell & Moring LLP, 2023; Epstein Becker Green, 2023). Miss any one of the three, and the tool is not deployable in NYC in any way that holds up under scrutiny — regardless of how well the demo went.

This is where vendor claims get slippery. A vendor telling you "we're audited" isn't the same as a vendor that has a current, independent audit conducted by a firm with no financial or employment relationship to either the vendor or your company. That independence requirement is structural, not optional — it's the reason a vendor cannot audit its own tool, and it's the first thing to verify, not the last.

Civil penalties for deploying without meeting these obligations run up to $500 for a first violation (and each additional violation on the same day), escalating to $500–$1,500 for each subsequent violation, with penalties accruing per violation, per day (Office of the NY State Comptroller, 2025). That's exposure that compounds the longer an unaudited tool stays live.

The Vendor Due Diligence Checklist Before You Sign

Before a contract is signed — not after, not during onboarding — run a short verification pass. This isn't legal advice; it's an operational gate, and it belongs in procurement, not just in legal review. If you want the full walkthrough, our AEDT vendor due diligence checklist covers the complete process. At minimum, confirm:

• The audit date is within the last twelve months and covers the specific tool version you're licensing, not an earlier release.
• The auditor has no financial or employment relationship to the vendor — ask directly, and get it in writing.
• A public summary exists somewhere, or the vendor can produce one on request.
• The vendor can tell you the tool's original distribution date, which anchors your own 10-business-day notice clock.

If a vendor can't answer these cleanly, that's not a red flag to note and move past — it's the answer to whether the tool is deployable in NYC at all. Our guide on how to check if an AEDT vendor has a bias audit walks through the exact questions to ask and what a real answer sounds like versus a dodge.

Checking the Public Audit Summary and Registry

Once you have a vendor's claim in hand, verify it independently rather than taking it at face value. A 2024 study of 391 employers subject to Local Law 144 found that only 18 had posted audit reports and only 13 had posted the required transparency notices (ACM FAccT, Wright & Muenster et al., 2024). Public posting is the exception, not the norm — which means you often can't just search for a vendor's compliance page and find it. You may need to request the summary directly, in writing, and keep the response.

We've built a step-by-step process for this in our vendor audit registry lookup guide — there's no single government-run lookup tool today, so it's a manual verification workflow, not a database query. We're building toward a live hosted registry lookup as part of our future SaaS platform; if that's useful to your team, join the waitlist and we'll let you know when it ships.

What Happens If You Deploy Anyway

Enforcement has been inconsistent, and it's tempting to read that as low risk. Resist that read. A December 2025 audit by the Office of the NY State Comptroller, covering the July 2023–June 2025 enforcement window, found Local Law 144 enforcement "ineffective": DCWP found only one of 32 reviewed companies non-compliant, while the Comptroller's own auditors found 17 non-compliant across the same 32 (OSC, 2025). Separately, 75% of test calls to DCWP's complaint intake line were improperly routed and never reached the agency (DLA Piper, 2026).

That gap between weak enforcement and real statutory exposure is exactly the trap. The penalties on the books don't disappear because the agency hasn't caught up yet, and an enforcement environment can tighten quickly. This is operational guidance, not legal advice — confirm your specific exposure and any recent DCWP guidance with counsel or directly with the agency before finalizing a deployment decision.

Documenting the Decision: Your Audit-Status Tracker

The point of all this verification isn't just to make a go/no-go call once — it's to have a defensible record of why you made that call, dated, with the vendor's response attached. That's the difference between "we checked" and "we can prove we checked."

This is exactly what the AEDT Vendor Bias-Audit Status Tracker Workbook is built to run. It's a downloadable tracker — not software, not a subscription — for logging each vendor's audit date, auditor identity, independence confirmation, distribution date, and your own notice timeline against every AEDT in your stack. It doesn't perform or certify a bias audit and it never scores an individual candidate; it documents the rationale behind your deployment decision so you have a defensible record, not a guess. For the fuller mechanics of what counts as adequate verification, see our guide on AEDT vendor bias-audit verification, and for the broader compliance picture beyond vendor vetting, our Local Law 144 compliance guide covers the notice and posting obligations end to end.

First Action Item

Before you sign the next AEDT contract — or before Friday's launch deadline arrives — pull the vendor's audit date, auditor identity, and distribution date into one place. Download the AEDT Vendor Bias-Audit Status Tracker Workbook and start the log with the tool that's closest to going live. A tool without a current, independent audit isn't deployable in NYC — full stop — and now you have the record to prove you checked.