Candidate-Level Notice Records for High-Volume Recruiting Pipelines
At a few hundred candidates a month, someone can usually reconstruct what happened from a mailbox. At a few thousand, they cannot — and the difference is not effort, it is whether the record was created at send time or is being assembled afterwards from memory.
Looking for the requirement itself? The statute, the agency, the effective date, the government source and the last-reviewed date are set out on NYC Local Law 144. This article is about running the workflow, not about what the law says.
Notice volume climbing faster than your records? Here is what a controlled workflow looks like.
Why Volume Breaks a Manual Notice Process
NYC workflows get difficult when the pipeline moves fast and the timing, the messaging and the tools are spread across teams. Everyone can know a notice is required and the process still comes apart, because each recruiter and each client account does it slightly differently.
That creates a familiar problem: the agency may have a general policy, but not a clean candidate-level trail showing what happened in a specific case.
Employment Agencies and High-Volume Candidate Workflows
Agencies push a lot of candidates through the same account in a short window, and speed is the whole point. But every skipped step, old draft and free-text note thins the evidence, and the thinning is invisible while it happens.
An operational example is a centralized recruiter team screening candidates who live in New York City for multiple client programs. A single spreadsheet may show that notices were "completed," but it may not preserve who sent the notice, what version was used, or whether provider delivery was confirmed.
Records That Should Be Easy to Retrieve
You want the candidate reference, the job, the tool or workflow, the approved notice version, the send timestamp, the provider's delivery event and the export history, all from one place rather than four.
They also reduce internal confusion when a client or stakeholder asks for proof later.
Where a Posted Policy Runs Out
A posted policy shows you have a general approach. It says nothing about one candidate on one date. That takes a record attached to an actual send.
Why Candidate-Level Evidence Matters
Candidate-level evidence matters because follow-up questions are usually specific. A client may ask about one role, one date range, or one candidate group. Internal stakeholders may want proof that an approved template version was used before a certain workflow changed. These questions are hard to answer if the process was tracked only in aggregate.
Six questions that find the gap in your current notice process.
How Notice Tracking Supports the Workflow
Notice Tracking connects the exact notice version, the candidate, the send, the delivery response, the timestamps and the export history in one place. The bias audit half of Local Law 144 stays with your auditor.
FAQs
What is the biggest risk in an NYC candidate notice workflow?
Believing you have a process because you have a policy. The question that arrives is about one named candidate on one date, and a policy cannot answer it.
Can a posted disclosure replace candidate-level notice records?
No. A posted disclosure describes what you generally do. It does not show that a particular person was told, or when.
Does Notice Tracking handle the Local Law 144 bias audit?
No. That belongs with an independent auditor. Notice Tracking handles the candidate notice half: the approved wording, the send date and the delivery record.
Send the notice, track what happened to it, and export the record when someone asks.
Written for operations teams planning a notice workflow. Your counsel decides what the law requires and approves the wording.