Skip to main content

NYC Local Law 144 · AEDT Bias Audit

Evidence-ready support for NYC Local Law 144 bias audits

Determine whether the system is in scope, prepare the required data, calculate the required selection or scoring results, document the audit method, and keep the evidence behind the result together.

In force since July 5, 2023. Formal bias audit, monitoring/readiness, and notice/disclosure support are separate workflows — not one legal verdict.

What Local Law 144 requires

Employers using an AEDT for NYC hiring or promotion decisions must meet three obligations, enforced by DCWP.

Annual bias audit

An independent auditor calculates selection or scoring rates and impact ratios by sex, race/ethnicity, and intersectional categories — before the AEDT is used and annually thereafter.

Candidate notice

Candidates must receive notice — including the AEDT used, the job qualifications and characteristics assessed, and how to request an alternative process — at least 10 business days before use.

Public disclosure

A Summary of Results — rates, impact ratios, source data explanation, unknown counts, audit date, and distribution date — must be published publicly and kept current.

Statutory penalties range from $500 for a first violation to up to $1,500 for subsequent violations per day. How daily-use and notice violations are counted depends on the violation class and the facts of your situation — scope and exposure are engagement-specific, not a fixed formula.

Three separate workflows

What HAIEC provides — and what it does not decide

A statistical signal is not a legal verdict. Each workflow produces evidence with explicit boundaries.

Formal bias audit

Audit support & calculation

Selection-rate and scoring-rate calculation, impact ratios, intersectional breakdown, documented exclusions, and the evidence chain an independent auditor reviews.

  • EEOC 4/5ths-rule analysis
  • Impact ratio calculation
  • Intersectional category breakdown
  • Documented audit method

Monitoring / readiness

Ongoing bias monitoring

Scheduled statistical monitoring of hiring decisions between formal audits — readiness evidence, not a substitute for the formal audit.

  • ATS webhooks (Greenhouse, Lever, Workday)
  • CSV upload for any system
  • Threshold alerts
  • PII hashed on ingestion

Notice / disclosure support

Candidate notice & disclosure

LL144-aligned notice workflows, delivery evidence, and hosted, versioned Summary of Results pages.

  • Notice templates & timing
  • Delivery tracking & proof
  • Hosted disclosure pages
  • Version history

Connect to your existing HR stack

REST APIs and webhook integrations that plug into the tools your team already uses

ATS webhook integrations

Receive hiring decision events automatically from your ATS. HAIEC normalizes data from multiple vendors into a single evidence format.

Greenhouse
Native webhook adapter with signature verification
Lever
Native webhook adapter with HMAC SHA-256 auth
Workday
Native webhook adapter for hiring events
Generic webhook
Works with any ATS • BambooHR, iCIMS, Jobvite, etc.
CSV Upload
Fallback option for systems without webhook support

REST API endpoints

Full API access for custom integrations. API key authentication with scoped permissions.

# Submit hiring data for bias analysis
POST /api/v1/nyc-audit
# Record hiring decision events
POST /api/v1/nyc-hiring/decision-event
# Run statistical bias audit
POST /api/v1/nyc-hiring/bias-audit
# Get audit results
GET /api/v1/nyc-audit?auditId=xxx
# Generate audit pack
POST /api/v1/nyc-hiring/audit-pack
# Configure ATS webhooks
POST /api/v1/nyc-hiring/webhook-config
# Upload CSV hiring data
POST /api/v1/nyc-hiring/csv-upload
API key authentication with Bearer tokens
Scoped permissions (nyc:hiring.write, nyc:hiring.read)
PII hashing • candidate data never stored in plaintext
Idempotency support for reliable event processing

How the audit workflow runs

From scoping to published disclosure, with the evidence bound at each step.

1

Scope the system

Determine whether the AEDT and its use are in scope: which decisions it supports, which candidates it touches, which data is required.

2

Prepare the data

Connect ATS webhooks or upload CSV. Candidate and job IDs are hashed on ingestion — raw PII is never stored.

3

Calculate the results

Selection rates, scoring rates, impact ratios, and intersectional categories are computed with a documented method and documented exclusions.

4

Audit, publish, monitor

An independent auditor reviews the analysis. The Summary of Results is published and versioned. Monitoring continues between formal audits.

Monitoring is not the formal audit

The monitoring engine produces ongoing readiness evidence — statistical signals between audits. The formal annual bias audit required by LL144 is a separate, engagement-scoped process conducted by an independent auditor. Independence is assessed and documented for the specific audit engagement; the platform itself is not the auditor.

Engagement, not a checkbox

Audit scope and pricing depend on the AEDT, the data, and the audit boundary — they are scoped per engagement, not sold as a self-serve subscription line item.

What the engagement covers

  • AEDT scoping and data readiness review
  • Documented calculation method and exclusions
  • Evidence pack for the independent auditor
  • Summary of Results publication workflow

What remains yours

  • The legal determination of whether the tool is an AEDT
  • Independent auditor independence — assessed per engagement
  • Publication and notice decisions
  • Interpreting a statistical signal as a legal verdict

Platform plans for ongoing monitoring are on the pricing page.

Scope review

Request a Local Law 144 scope review

Tell us about the AEDT and how it is used. We will scope the audit boundary, the data required, the calculation method, and the auditor relationship — then confirm what the engagement covers.

Audit boundary first
Which systems, decisions, and data are in scope before any analysis runs
Independence documented
Assessed and recorded for the specific audit engagement — not assumed
Evidence stays together
The calculation, method, exclusions, and publication trail remain bound to the result
Or email us directly: support@haiec.com

Request a scope review

Fill out the form and our team will contact you within 24 hours.

Submitting this form sends a message to our team and creates a tracking ticket. We respond within 24 hours.

Frequently asked questions

Common questions about NYC LL144 and how HAIEC supports it

NYC Local Law 144

Get the audit boundary, the calculation, and the evidence — together.

Scope review first. Formal audit, monitoring, and disclosure support stay separate — so every result carries exactly the evidence it earned.

Evidence-bound workflows
PII never stored in plaintext
Documented audit method