Local Law 144, Remote Workers, and NYC Candidates

The Recruiter Who Wasn't Sure Which Rulebook Applied

A recruiter at a 140-person fintech company in White Plains posts a fully remote engineering role. The job ad says "remote — U.S." No office requirement, no hub city. Three hundred applications come in through the applicant tracking system, which uses an AEDT to rank resumes before a human ever looks at them. Forty of the applicants list a New York City ZIP code. The role itself isn't "based" anywhere in particular — there's no NYC office, no hybrid schedule, no expectation anyone reports to a Manhattan address.

Does Local Law 144 apply here? Is it the candidate's location that matters, or the job's? What if the company has no NYC office at all, but hires NYC residents into remote roles every quarter? These aren't rhetorical questions — they're the exact scenario that trips up HR teams at distributed and hybrid employers, and the useful news is that DCWP's published guidance resolves the main version of it more cleanly than most teams expect. By the end of this article you'll have a working framework for documenting your own determination on the Local Law 144 remote worker NYC candidate question — and know exactly where to stop guessing and confirm with DCWP or counsel.

What Local Law 144 Actually Triggers On

Start with the parts of the law that are settled. Local Law 144 covers automated employment decision tools — any computational process derived from machine learning, statistical modeling, data analytics, or AI that produces a simplified output (a score, classification, or recommendation) used to substantially assist or replace discretionary decision-making in hiring or promotion (Perkins Coie, 2023). The law took effect January 1, 2023, with enforcement beginning July 5, 2023 (Epstein Becker Green / Workforce Bulletin, 2023). Covered employers carry three obligations: an annual independent bias audit, a public summary of the most recent audit results posted on the employer's website, and candidate or employee notice at least 10 business days before the tool is used, along with an alternative-process or accommodation avenue (Crowell & Moring LLP, 2023; Epstein Becker Green, 2023).

None of that is in dispute. What's less settled — and what the law's text and public guidance address only partially — is exactly how those obligations map onto a workforce that isn't sitting in a single NYC office five days a week.

The Remote-Work Ambiguity: Residence vs. Role Location

Here's the actual gray area. Local Law 144 was written with a fairly conventional employment picture in mind: a job located in New York City, filled by candidates who apply for that NYC-based position. A distributed workforce breaks that picture in at least three ways:

• A role has no fixed location at all ("remote — U.S.").
• A candidate lives in NYC but the role, if filled, would never require a NYC presence.
• An employer has no NYC office, but its screening tool touches applicants who happen to reside in the five boroughs.

On the central question — whether the candidate's residency alone is enough, or whether the position's association with a NYC office is what matters — DCWP has actually answered. Its FAQ guidance and its May 2023 roundtable both tie the audit and notice obligation to whether the employer maintains a physical NYC office and whether the remote role is "associated" with that office. An employer with no NYC office at all is not brought into scope merely because some candidates reside in the five boroughs. Once a position is otherwise in scope, the 10-business-day notice requirement — unlike the audit requirement — runs specifically to candidates and employees who are NYC residents. Law-firm summaries of that guidance from Gibson Dunn and Seyfarth Shaw are consistent on both points.

What DCWP does treat as fact-specific is the narrower case of an employer with offices in several locations, one of them New York City. That is where the permutations genuinely run out of published guidance — not the fully-remote, no-NYC-office scenario the opening example describes.

Where the rule is clear we state it; where it genuinely isn't, we won't manufacture one. What follows is a defensible way to reason through the fact-specific cases, document your reasoning, and know when to pick up the phone.

The safest posture for a distributed employer isn't guessing at the answer — it's writing down which facts you weighed, the date you weighed them, and confirming the close calls with DCWP or outside counsel before you rely on your own read.

Why This Matters More for a Distributed Workforce Than a Single-Office One

If your company operates one office in Midtown and every applicant is expected to show up there, the trigger question basically answers itself — you're in scope, full stop. The ambiguity scales with how distributed you already are. A company with hybrid roles tied loosely to a NYC hub, a company with candidates scattered across state lines applying to the same remote req, and a PEO managing AEDT screening across a client roster with mixed office footprints are all facing a version of the local law 144 remote worker nyc candidate question that a single-city employer never has to ask.

This is also where the operations-not-legal-advice line matters most. Nothing in this article, and nothing in any WorkforceNewYork workbook, is a legal opinion on whether your specific role or your specific candidate pool puts you in scope. That determination is a legal judgment call for your counsel to make, informed by your actual facts. What a workbook can do is force the facts onto paper in a consistent format — role location, candidate residency pattern, office association, decision date — so that whoever makes the legal call has a clean record to work from, and so the same reasoning gets applied consistently the next time the question comes up.

A Practical Framework for Documenting Your Determination

Rather than trying to resolve the ambiguity in the abstract, document it per requisition. A workable framework looks like this:

1. Record the role's location status — NYC-based, hybrid with a NYC hub, or fully remote with no city association.
2. Record the candidate pool's residency pattern — are NYC-resident applicants a meaningful share of who applies, or an edge case?
3. Record whether the AEDT screens all applicants uniformly or only a subset, since the tool's actual use matters as much as the job posting language.
4. Note the date and who made the call — this is the piece that turns a guess into a documented rationale you can defend later, whether that's to your own leadership or in response to an inquiry.
5. Flag anything genuinely unresolved for your attorney rather than deciding it internally and hoping.

That fifth step is the one teams skip, usually because nobody wants to be the person who says "I don't know" in a compliance meeting. Saying it in writing, with the specific fact pattern attached, is exactly what protects you later.

Once You've Decided You're In Scope, the Three Obligations Still Apply the Same Way

If your determination — made by you, ideally with counsel weighing in on the close calls — lands on "yes, this AEDT use is in scope," the mechanics from there aren't ambiguous. You still need the annual independent bias audit, conducted by an auditor with no financial or employment relationship to you or your AEDT vendor. You still need the public summary posted on your website with the AEDT's distribution date. And you still need the 10-business-day candidate notice with an alternative-process option (Crowell & Moring LLP, 2023). None of that changes because the workforce is remote — only the upstream question of whether the obligation attaches changes with a distributed footprint.

Penalties for getting the downstream mechanics wrong aren't small: up to $500 for a first violation, $500 to $1,500 for each subsequent one, and violations can accrue per day (Office of the NY State Comptroller, 2025). That's a separate risk from the scope question, and it's the one you control most directly once scope is settled — which is exactly why the documentation habit matters regardless of how the residency question resolves.

Build the Record Before You Need It

If you're running requisitions across a mixed office/remote/hybrid footprint, the worst time to figure out your Local Law 144 position is after a candidate asks why they didn't get a notice, or after a new NYC hire flags that the posted audit summary doesn't seem to cover their role. The NYC Candidate-Residency & AEDT-Trigger Determination Worksheet gives you a standard form to run every requisition through — role location, candidate residency pattern, tool usage, decision date, and a flag field for anything you're sending to counsel — so your reasoning is consistent across every recruiter and every req, not reinvented each time someone asks.

Download the NYC Candidate-Residency & AEDT-Trigger Determination Worksheet and start applying it to your open reqs this week. For the baseline scope question — whether Local Law 144 applies to your company at all — see Does Local Law 144 Apply to My Company?. For a deeper look at the residency trigger mechanics specifically, see NYC Candidate Residency & the AEDT Trigger and Does Local Law 144 Apply to Candidates Outside NYC?. And if you need the full obligation set once scope is confirmed, the NYC Local Law 144 Compliance Guide walks through the audit, notice, and posting requirements end to end.