Setting Up an Annual Bias Audit Renewal Reminder

The Deadline That Doesn't Send You an Email

Somewhere around month fourteen, someone on your team pulls up the AEDT vendor's audit report to check a date — maybe because a candidate asked about it, maybe because a new hire in HR was curious — and realizes the audit behind your resume-screening tool expired two months ago. No one flagged it. The vendor didn't call. DCWP didn't send a notice. The public summary on your website is still showing last year's results, quietly out of date, for anyone who bothers to look.

This is not a hypothetical. It's the default outcome for any employer who treats an annual bias audit renewal reminder as something the vendor, the law, or the calendar app will handle automatically. None of them will. Local Law 144 puts the audit-renewal obligation on the employer using the AEDT, not on the vendor building it, and there is no government system that pings you when your window is closing.

By the end of this article, you'll know exactly what to track, when to start tracking it, and how to build a renewal reminder routine that survives staff turnover, vendor contract changes, and the fact that "annual" doesn't mean what most people assume it means.

Why "Annual" Doesn't Mean What You Think

Local Law 144's core obligations are simple to list and easy to get wrong in practice: an independent bias audit conducted at least once a year the AEDT is in use, a public summary of the most recent audit results posted on the employer's website alongside the tool's distribution date, and candidate or employee notice at least 10 business days before the tool is used (Crowell & Moring LLP, 2023; Epstein Becker Green, 2023).

The trap is in the word "annual." It doesn't reset on January 1. It resets on the anniversary of the last audit — which means every AEDT your organization runs can have a different expiry date, staggered across the calendar, tied to whenever that specific tool was last audited. If you deploy three tools from three vendors on three different audit cycles, you don't have one deadline. You have three, and none of them line up with your fiscal year, your HR team's planning cycle, or each other.

That's the structural reason a single mental note — "we did the audit last spring" — doesn't function as a renewal system. Confirm the exact cadence and any grace period for your specific AEDTs directly with DCWP; this is an operations question, not a legal one, but it's worth getting the underlying legal interpretation checked by counsel if your renewal timing is close to the line.

Building a Renewal Reminder Routine You Own

An annual bias audit renewal reminder routine has three parts, and all three need to live somewhere more durable than one person's inbox.

A per-tool expiry register. For every AEDT in use — screening, ranking, interview scoring — log the vendor name, the date of the most recent audit, the calculated expiry date (audit date plus the applicable interval), and who at your organization owns re-verifying it. This is the backbone. Without it, every other reminder step has nothing to count down from.

A staggered notice schedule. Set reminders at 90, 60, 30, and 10 days before each tool's expiry — not one reminder the week it lapses. The 90-day flag gives you time to confirm the vendor's next audit is scheduled and to check whether your independent auditor relationship is still active. The 10-day flag is your last chance to pause use of the tool if the new audit isn't going to land in time.

A posting-and-notice checkpoint tied to each renewal. A completed audit isn't the finish line. The public summary on your website has to be updated with the new results and the AEDT's distribution date, and any candidate-notice language referencing audit currency needs a fresh review. Build that into the same reminder, not a separate one you might forget.

None of this requires anything exotic. A shared tracker with a name, an owner, and four calendar triggers per tool will outperform relying on memory or on your vendor to flag it — and it's exactly the structure the AEDT annual bias audit expiry and renewal tracking method walks through in more detail. If you're still unsure how the underlying cadence rule applies to your specific tools, how often a bias audit is required in NYC breaks the interval question down further.

What Happens When the Reminder Fails (or Never Existed)

It's tempting to assume a missed deadline gets caught somewhere downstream — by DCWP, by a candidate complaint, by the vendor. The enforcement record doesn't support that assumption. A December 2025 audit by the Office of the NY State Comptroller, covering the review period from July 2023 through June 2025, characterized DCWP's enforcement of Local Law 144 as ineffective (Office of the NY State Comptroller, 2025). Reviewing the same set of companies DCWP had cleared, the Comptroller's auditors found compliance gaps DCWP's own review had missed — far more than DCWP's review had flagged (Office of the NY State Comptroller, 2025). Separately, DCWP received only two AEDT-related complaints during the entire scope of the audit, and the Comptroller found no evidence DCWP had tested whether its own complaint intake actually worked — a related test found the large majority of test calls were never properly routed to the agency at all (DLA Piper, 2026).

That gap is the whole argument for owning your own renewal reminder: the agency isn't reliably catching lapses, so nothing outside your organization is going to catch yours.

A separate academic review of 391 employers with AEDT disclosure obligations found only 18 had posted an audit report and only 13 had posted a transparency notice (ACM FAccT, Wright & Muenster et al., 2024) — meaning the vast majority of covered employers were already out of compliance on the basics before renewal timing even entered the picture. Civil penalties for a violation run up to $500 for a first offense and $500 to $1,500 for each subsequent violation, and penalties accrue per violation, per day (Office of the NY State Comptroller, 2025) — confirm the current schedule with DCWP before treating any figure as final. For a fuller walkthrough of what a lapse actually triggers, see what happens if you miss the bias audit deadline.

This is operations guidance, not legal advice — if a lapse has already happened, or you're unsure whether your notice language or audit timing meets the statute, that's a question for outside counsel or DCWP directly, not a workbook.

The Reminder Routine vs. the Reminder Engine We're Not Selling Today

To be clear about what this article is describing: a workbook-based routine you run yourself, on a schedule you set, checked by a person you've named as the owner. We are not describing — and don't currently sell — an always-on system that watches your AEDT roster and pings you automatically. We're planning a hosted renewal-reminder engine and a live vendor-audit-status lookup as part of a future application; if that's useful to you, join the waitlist to hear when it ships. Until then, the reliable version of "annual bias audit renewal reminder" is the one you build into a tracker and a calendar yourself.

If you want the full statutory backdrop before you build your tracker — obligations, notice windows, and how the deadline math interacts with multi-tool deployments — the Local Law 144 compliance deadline calendar and the NYC Local Law 144 compliance guide cover that ground.

Your First Action Item

Don't start by building a tracker from scratch. Start with the Annual Re-Verification & Audit-Expiry Renewal Planner — a workbook built specifically to hold the per-tool expiry register, the staggered notice schedule, and the posting checkpoint described above, so the first annual bias audit renewal reminder you set up isn't the one you build under deadline pressure next year. Download it, log every AEDT you currently run, and set your first 90-day flag today.