Why "we offer PTO" is not an answer

Plenty of small employers assume that because they offer generous paid time off, they are covered on sick leave. Often they are not. A growing number of states and cities have passed mandatory paid-sick-leave laws, and many of them impose specific requirements your blanket PTO policy does not satisfy on its own — minimum accrual rates, carryover, permitted reasons for use, and anti-retaliation protections that a discretionary vacation balance simply does not address.

There is no single federal paid-sick-leave statute covering private employers generally. Instead you have a layered patchwork: some states mandate it statewide, some cities and counties mandate it locally (sometimes more generously than their own state), and many places mandate nothing at all. The result is that the same company can owe completely different obligations to two employees depending on where each one physically works. This is general HR education, not legal advice, and because this area is intensely local and changes often, confirm the exact rules for every jurisdiction where you have workers before you finalize anything.

The one mistake almost everyone makes: one bucket

The single most common error is lumping vacation and sick time into one undifferentiated "PTO" pool. It feels simpler, and where no sick-leave law applies it is perfectly legal. But in a jurisdiction with a paid-sick-leave mandate, a combined bucket frequently fails — because sick-leave laws regulate things vacation policies do not:

  • Permitted reasons. Sick-leave laws let employees use the time for their own illness, a family member's illness, preventive care, and often "safe time" related to domestic violence. You generally cannot require a doctor's note for short absences, and you cannot deny use for a covered reason.
  • No advance notice for unforeseeable need. You can ask for reasonable notice when the need is foreseeable, but you cannot require it when someone wakes up sick.
  • Anti-retaliation and no-discipline rules. Many laws bar counting protected sick-leave use as an "occurrence" in a no-fault attendance policy. If your points system dings someone for a legally protected absence, that is a violation.

If you run a combined PTO bucket in a mandate jurisdiction, it generally has to be at least as generous as the law on every one of these dimensions, with no waiting period or note requirement the law forbids. That is a high bar, which is why tracking sick time as its own balance is usually the cleaner path. As covered in writing a PTO policy and getting accrual right, distinct balances — vacation, sick, unpaid, bereavement — are easier to keep compliant than one pool stretched to satisfy every rule at once.

The mechanics these laws actually regulate

Where a mandate applies, the rules tend to govern four mechanics. The exact numbers vary by jurisdiction, but the categories are consistent:

  • Accrual rate. Commonly framed as one hour of sick leave per some number of hours worked, up to an annual cap. Part-time and hourly workers accrue too; coverage usually is not limited to full-timers.
  • Frontloading as an alternative. Many laws let you skip accrual tracking by granting the full annual amount up front at the start of the year. Frontloading is administratively simpler and often lets you avoid carryover obligations — frequently worth it for a small team.
  • Carryover. If you accrue rather than frontload, unused sick time usually carries into the next year up to a cap, even though you can limit how much is used per year.
  • Reinstatement on rehire. Several laws require restoring accrued, unused sick leave if you rehire someone within a set window, so your offboarding and rehire process needs to preserve those balances rather than zeroing them out.

Two things sick-leave laws typically do not require, which surprises employers in both directions: most do not require paying out unused sick leave at separation the way vacation often must be paid out, and most cap the annual usage you must allow even when accrual carries over.

Remote and multi-state teams: it follows the worker

The hardest part for a distributed small employer is that paid-sick-leave obligations generally follow where the employee physically works, not where your company is headquartered. Hire one remote employee in a mandate state or city and you may owe that benefit to that one person even though no one else on the team gets it. This is exactly the kind of obligation that the broader multi-state compliance checklist is built to catch — sick leave is one line in a longer list of things that reset to local law the moment you hire across a state or city line.

The practical move is to maintain a small jurisdiction matrix: for each state and locality where you have a worker, note whether a paid-sick-leave mandate applies and its accrual, carryover, and usage rules. When you add a hire in a new place, check the matrix before you set their PTO terms.

Notice, recordkeeping, and the handbook

Most paid-sick-leave laws come with paperwork and posting duties that are easy to overlook:

  • Notice to employees of their rights, often at hire and sometimes via a workplace poster.
  • Showing the balance, frequently on or alongside the pay stub, so employees can see accrued and used amounts.
  • Recordkeeping of hours worked and sick time accrued and used, typically retained for several years — overlapping with the recordkeeping discipline you already maintain for hiring records.

Your employee handbook should state the policy clearly for each jurisdiction it covers, including how time accrues, what it can be used for, and the promise that using protected sick leave will not be held against the employee. Writing it down once, correctly, is far cheaper than reconstructing it during a complaint.

The bottom line

There is no federal paid-sick-leave law for private employers generally, but the state and local patchwork is real, it follows your workers wherever they sit, and a generous PTO policy does not automatically satisfy it. Track sick time as its own balance, get accrual or frontloading right for each jurisdiction, never discipline a legally protected absence, and keep a simple location matrix so a single remote hire in a mandate city does not quietly put you out of compliance. When the rules for a specific state or city are ambiguous, that is the moment to confirm with counsel rather than guess — the mandates are local, they change, and the penalties attach per violation.