If almost nobody on your payroll ever calls in sick, congratulations — you may have just flagged your own business for investigation. New York City's Department of Consumer and Worker Protection (DCWP) now compares each employer's sick-leave use rates against national health survey data, and unusually low usage counts as strong evidence that workers are being blocked from time off they are legally owed. Back in February the city mailed compliance warnings to more than 56,000 employers, and the agency has been pursuing companywide cases ever since. If you employ anyone who works in the five boroughs, here is what the expanded law requires, what violations cost, and how to get your records in order before the data does the talking for you.
What changed, and when
New York City's leave law has been renamed, expanded, and given sharper teeth in three waves:
- January 1, 2025: New York State began requiring all employers to provide up to 20 hours of paid prenatal personal leave per year, separate from sick time.
- February 22, 2026: City amendments (Local Law 145) folded that prenatal leave into the city law — now called the Protected Time Off Law, formerly the Earned Safe and Sick Time Act — added 32 hours of unpaid leave available immediately on hire, and widened the list of qualifying reasons. Around the same time, DCWP mailed its enforcement-blitz warning letters to more than 56,000 employers, including every restaurant in the city.
- July 23, 2026: DCWP's amended implementing rules took effect, spelling out exactly how employers must administer the new leave banks, what pay statements must show, and what records must be kept.
If your last policy update predates any of these dates, your handbook is already behind the law.
The three leave banks you must track
The law now creates three separate buckets, and mixing them up is one of the fastest routes to a violation:
1. Paid protected time off. Employers with 100 or more employees must provide up to 56 hours per year; employers with 5 to 99 employees must provide up to 40 hours. Businesses with 4 or fewer employees also owe up to 40 hours, though it may be unpaid if net income falls below the statutory threshold. Leave accrues at one hour for every 30 hours worked.
2. Thirty-two hours of unpaid leave, available immediately. Every employee gets 32 additional hours of unpaid protected time off on their hire date and again each January 1, usable from day one. Employees tap this bucket only when they have not accrued enough paid time yet, have hit the annual cap, or specifically ask to use it. Unused hours do not carry over, and you may set a daily minimum increment of up to four hours. You may also satisfy part or all of this obligation with paid leave — sometimes necessary to preserve exempt employees' salary basis — and you must reinstate unused hours when rehiring someone within the same calendar year.
3. Twenty hours of paid prenatal leave. A standalone bank of 20 paid hours per 52-week period, covering prenatal medical appointments, testing, and related care. It sits entirely outside the other two balances and cannot be debited against them.
Employees may now use protected time off for an expanded set of reasons: child care needs including school holidays and disruptions, caring for a family or household member with a disability, benefits or housing appointments and hearings, government-declared public emergencies such as snowstorms and power outages, and needs arising from workplace violence — on top of the long-standing medical, family-care, and safe-time reasons.
How the data-driven enforcement sweep works
The enforcement strategy DCWP announced alongside the February expansion is what makes this round different. Instead of waiting for individual complaints, the agency compares an employer's actual leave-use rates with national benchmarks from the federal Centers for Disease Control and Prevention's annual National Health Interview Survey. The city's position is that the need for sick leave is essentially universal across industries and demographics — so a workforce that never takes leave looks less like a healthy team and more like a workforce under pressure not to call out.
When the numbers look anomalous, DCWP treats that as strong evidence of potential violations and opens companywide investigations seeking relief for every affected employee, not just whoever complained. The agency published its methodology in a public report and built a Protected Time Off Usage Compliance Tracker, available through its website, so employers can benchmark themselves the same way investigators do.
Common violations that produce suspiciously low use rates include having no real leave benefit at all, missing or thin written policies, absence-control systems that punish last-minute callouts or no-call-no-show incidents, and informal restrictions — the manager who sighs every time someone calls in sick, or the schedule that quietly penalizes anyone who uses a day.
What non-compliance costs
The penalties stack per employee, per year, which is how a small business ends up facing a large number:
- General civil penalties run from $250 to $2,500 per employee, plus back pay owed to workers.
- An employer found to maintain a policy of not providing protected time off must grant each affected worker relief of up to twice the annual maximum in hours, $500 per employee per calendar year, and the 32 hours of unpaid leave.
- A paid prenatal leave violation requires adding 20 hours of paid prenatal leave to the worker's balance plus $500 per employee for each calendar year the unlawful practice was in effect.
- Repeat violations can reach $1,000 per employee per year.
The city's own example makes the math concrete: an employer with 100 workers in violation for three years could owe $300,000, split evenly between employee relief and civil penalties. And DCWP is not the only audience — employees can also pursue relief through private civil actions, so one investigation can easily become many.
The paperwork that keeps you safe
Under the amended rules, missing paperwork is not a minor demerit. It creates a legal presumption against you: fail to maintain or distribute a compliant written policy, or fail to keep adequate records, and DCWP presumes you are violating the law. Here is what compliant administration looks like:
One written policy, widely distributed. You must maintain a single written policy covering both protected time off and paid prenatal leave, addressing accrual, prenatal leave, notice and documentation rules, minimum increments, discipline for misuse, confidentiality, carryover, and the 32 immediately available hours. Distribute it at hire, within 14 days of any change, and whenever an employee asks for it.
Pay statements that show the split. Pay stubs must distinguish paid from unpaid protected time off, both used and available. If you use an electronic system, departing employees must retain six months of continued access — or receive, within one week after their final payday, a written statement showing leave accrued and used that period (split by paid and unpaid), total balances, leave available for use, and prenatal leave used and remaining.
Three years of per-employee records. Keep records for every employee showing protected time off used and available, broken out by paid and unpaid, plus accrued protected time off and accrued prenatal leave. Three years is the minimum retention period, and gaps are presumed to be violations.
Notice rules that run in the worker's favor. You must give employees written notice of their rights. You may require advance notice only for foreseeable uses such as scheduled appointments or hearings — never for sudden illness or a child care disruption. Workers do not have to explain why they took leave, and you may request documentation only after more than three consecutive workdays out, with you reimbursing any fees the documentation costs them.
Where payroll and bookkeeping usually break down
Most violations DCWP describes are not acts of defiance; they are systems that were never updated. The 2026 amendments punish exactly the gaps that accumulate in a small business running payroll on autopilot:
- Commingled leave banks. If your payroll system has one generic PTO bucket, it cannot produce the paid-versus-unpaid split your pay statements must show, and it cannot prove the 20 prenatal hours were ever available. Each bank needs its own ledger.
- Paid-before-unpaid sequencing. The rules expect paid accrued time to be used before the unpaid 32-hour allotment, unless the employee requests otherwise. Hard-coding that order into your leave administration prevents the most common sequencing errors.
- Rehire reinstatement. Rehiring a former employee within the same calendar year revives their unused balances. Purge-on-termination routines in HR software will silently violate this rule.
- Documentation-fee reimbursement. Those small fees for doctor's notes are now your cost when you request documentation. They need an expense category and a paper trail, not a petty-cash shrug.
- Retention discipline. Three years of per-employee, per-period balances is a records-management commitment. A version-controlled, exportable record beats a payroll portal you can no longer log into after switching vendors.
Running the city's Usage Compliance Tracker against your own numbers is the cheapest audit you will ever perform. If your use rates sit far below the national benchmarks, assume an investigator will eventually notice, and fix the policy and the culture before the letter arrives.
Five mistakes to stop making this month
- Disciplining last-minute callouts. Attendance-point systems that punish short-notice absences are explicitly on DCWP's violation list. Rewrite the policy so protected leave can never trigger a point.
- Asking why. "What's wrong with you?" in a callout conversation is now a compliance event. Train managers to record the absence and move on.
- Demanding a doctor's note on day two. Documentation is allowed only after more than three consecutive workdays, and you pay for it.
- Forgetting the January 1 reset. The 32 unpaid hours refresh every calendar year and post on each new hire's start date. Calendar it twice.
- Treating prenatal leave as regular sick time. Twenty separate paid hours, its own balance, its own tracking. Every pay stub should prove it exists.
What to do this week
Start with a self-audit while it is still voluntary: pull your current written policy and check it against the required topics, verify your payroll system tracks three distinct banks with a paid/unpaid split, confirm departing employees get their post-separation statements, and run your use rates through the city's compliance tracker. Then update the handbook, redistribute it, retrain anyone who approves time off, and file the whole package where you can find it three years from now. The employers who sailed through the February warning letters were the ones whose records already told the right story.
Keep Your Leave Records Audit-Ready
Staying ahead of a data-driven enforcement sweep is ultimately a record-keeping exercise: distinct leave banks, per-employee balances, compliant pay stubs, and three years of history you can produce on demand. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
