Paid Sick Leave Laws: A Small-Business Overview

Paid sick leave is no longer a perk reserved for large companies. As of 2026, more than 18 states plus dozens of cities and counties require private employers, including very small ones, to provide paid sick time. There is no blanket federal law for private-sector workers, so your obligations depend on where your employees physically work, and the details vary enough that a one-size-fits-all policy will eventually trip you up.

This guide walks through how accrual works, the rates and caps you will see most often, what counts as a covered use, and the records you are expected to keep. It is an overview to help you ask the right questions, not legal advice. Confirm the specifics for every state, county, and city where you have staff.

There is no single federal sick leave law

The most common misconception is that "the law" sets one number. For private employers, it does not. The Family and Medical Leave Act (FMLA) guarantees up to 12 weeks of leave, but that leave is unpaid and only applies to employers with 50 or more employees. Federal contractors have their own paid sick leave rule under Executive Order 13706.

For everyone else, sick leave is governed at the state and local level. That means a 6-person business with one remote employee in another state may be subject to two completely different sick leave laws at once. Your rule of thumb: the law that applies is the one where the employee actually performs the work, not where your company is headquartered.

How accrual-based sick leave works

Most sick leave laws use an accrual model. Employees earn paid sick time gradually as they work, rather than receiving it all at once. The mechanics are straightforward once you see them in numbers.

The dominant rate is 1 hour of paid sick leave for every 30 hours worked. Here is what that looks like in practice:

• A full-time employee working 40 hours a week earns about 1.33 hours of sick leave per week.
• Over a year, that comes to roughly 69 hours, but most laws cap annual accrual well below that, often at 40 hours.
• A part-time employee working 20 hours a week earns about 0.67 hours per week, or roughly 35 hours in a full year before any cap.

So the accrual rate and the annual cap work together. An employee earns at 1-per-30 until they hit the cap, then stops accruing until the next year (or until they use some time and free up room, depending on whether the cap is on accrual or on the balance).

Front-loading: the simpler alternative

Instead of tracking accrual hour by hour, many employers front-load the full annual amount on the first day of the benefit year. If a law requires 40 hours, you simply grant all 40 on January 1 (or on the employee's start date for new hires).

The trade-off is clear:

• Accrual ties the benefit to hours actually worked, which protects you from giving a large balance to someone who leaves in week three. The cost is more tracking.
• Front-loading is far simpler administratively and, under most laws, lets you skip the carryover requirement entirely. The cost is that you may grant time an employee never "earns."

For very small teams, front-loading is often worth the slightly higher exposure because it removes a whole category of bookkeeping. You can model either approach with our PTO accrual calculator to see the real annual numbers before you commit.

Common rates and caps at a glance

While every jurisdiction is different, the numbers cluster around a few patterns. The table below shows the most common combinations you will encounter. Treat these as typical examples, not the rule for your specific location.

A few things to notice. First, the accrual rate is remarkably consistent at 1-per-30 across most laws, so the real variation is in the caps. Second, some laws distinguish between an accrual cap (how much you can bank) and a use cap (how much you can actually take in one year). A common combination is a 48-hour accrual cap with a 40-hour annual use limit. Third, employer size still matters in some places: smaller employers sometimes get a lower required minimum or, in a few jurisdictions, may provide the time unpaid.

What sick leave can be used for

Covered uses are broader than the name suggests. Calling it "sick" leave undersells it; most laws cover a family of safe and health-related reasons. While the exact list varies, the following uses appear in nearly every paid sick leave statute:

1. The employee's own illness, injury, or health condition, including preventive care like a routine checkup or a vaccination appointment.
2. Care for a family member who is ill, injured, or needs preventive care. The definition of "family member" is often generous and may include a spouse, domestic partner, child, parent, grandparent, grandchild, or sibling.
3. Safe leave related to domestic violence, sexual assault, or stalking, which can cover things like seeking counseling, relocating, or attending legal proceedings.
4. Public health closures, such as when a business or a child's school is closed by order of a public official for a health reason.

A key compliance point: you generally cannot demand documentation, like a doctor's note, for short absences. Many laws only allow you to request reasonable documentation when an employee is out for more than three consecutive days. Asking for proof of a one-day absence is one of the most common ways small employers accidentally violate these laws.

You also cannot retaliate against an employee for using their protected sick time. That includes obvious actions like termination, but also subtler ones like assigning worse shifts or counting protected absences against someone in a no-fault attendance system.

Separate sick leave or combined PTO?

A frequent question from small-business owners is whether they can fold sick leave into a single combined PTO bank instead of running a separate accrual. In most jurisdictions, yes, you can use a single PTO policy as long as it meets two conditions:

• The bank provides at least as much time as the sick leave law requires.
• Employees can use that time for all the covered reasons above, under the same conditions (no doctor's note for short absences, no retaliation, and so on).

The appeal is simplicity: one balance, one accrual, one number on the pay stub. The catch is on the back end. Because combined PTO is typically treated like vacation, several states require you to pay out the unused balance at termination, including the portion that came from the sick leave requirement. Pure sick leave, by contrast, usually does not have to be paid out when someone leaves.

So the decision often comes down to your turnover and your state's payout rules. If you are weighing the dollar cost of a combined bank versus a separate one, the PTO cost calculator can help you put a number on the payout exposure. And if you would rather generate a clean, ready-to-edit policy document, the PTO policy generator covers both structures.

Recordkeeping: the part that gets employers in trouble

Even employers with a generous policy can run into penalties for one reason: bad records. When a complaint or audit happens, the burden is usually on you to prove compliance, and "we definitely gave them the time" is not a record.

At a minimum, keep the following for each employee:

• Hours worked (which drives accrual under the 1-per-30 model).
• Sick leave accrued in each period.
• Sick leave used, with dates.
• Running balance, so an employee can see it, often required on or with each pay stub.

Most laws require you to retain these records for three to four years. Some go further and create a presumption against the employer if records are missing, meaning if you cannot show the data, regulators may assume a violation occurred.

Two confidentiality rules matter here. First, the reason for any sick leave is medical information and must be kept confidential and separate from general personnel files. Second, you should not create a paper trail that even looks like you are tracking who uses protected leave for the purpose of discipline.

This is exactly the kind of thing that breaks down in a spreadsheet. Manual tracking tends to fail when an employee changes from part-time to full-time mid-year, when accrual needs to pause at a cap and resume after use, or when you need to produce a clean balance history two years later. To convert work schedules into accrual periods accurately, the working days calculator is a useful starting point, and you can browse the full set of free planning tools to map out your policy.

A worked example

Say you run a 9-person retail shop in a city that requires 1 hour of sick leave per 30 hours worked, with a 40-hour annual use cap and a 48-hour accrual cap.

• A full-time cashier working 1,560 hours over the year accrues 52 hours at the 1-per-30 rate, but stops banking at the 48-hour accrual cap.
• She can use up to 40 hours this year because of the use cap, even though she has 48 banked.
• At year end, she has unused time. If your policy uses accrual with carryover, she carries her balance forward (still subject to the 48-hour ceiling). If you had front-loaded 40 hours instead, you could reset the balance and skip carryover.
• When she leaves the company, you generally do not owe a payout for the unused sick hours, unless you run a combined PTO bank or your state requires it.

That single example touches accrual, both kinds of caps, carryover, and payout, which is why writing the policy down in concrete numbers beats relying on memory.

Putting it together

Paid sick leave for a small business comes down to a handful of decisions: accrual versus front-loading, the right rate and caps for each location, which uses you cover, whether to combine with PTO, and how you keep records. Get those right and the law is manageable. Leave them vague and you inherit risk you cannot see until a complaint lands.

SimplyPTO tracks accrual at any rate, enforces caps and carryover automatically, keeps a clean per-employee history for audits, and handles different rules for staff in different locations, so your sick leave policy actually runs the way you wrote it. Start a free trial and set your policy up correctly from day one.