Why does a remote team with employees in several states need state-specific sick leave rules?

The law follows the employee, not the headquarters

Paid sick leave in the United States is a patchwork. There is no general federal requirement for private employers, but a growing number of states, plus a number of cities and counties, mandate it. Which law applies is generally determined by where the employee physically works. A company headquartered in a state with no mandate that hires a remote employee in a state with one is covered for that employee, and sometimes by a city ordinance layered on top of the state rule.

This surprises small teams that grew remote without planning to. The first hire in a new state often happens because a great candidate lived there, not because anyone reviewed the leave rules. The practical consequence is that a team of twenty people in six states may be operating under four or five different sick leave regimes, each with its own accrual formula, cap, carryover rule, and list of permitted uses. Related: How can managers approve time-off requests fairly without leaving the team short?

Keep reading: Why does tracking employee PTO in a spreadsheet eventually break down for teams?, How do PTO accruals actually work and how should a small business set them up?, How can managers approve time-off requests fairly without leaving the team short?. See how LeaveLedgr helps you employee pto and leave balance tracking.

Where the rules actually differ

The variations are not cosmetic. Accrual formulas differ, commonly expressed as one hour of sick leave per set number of hours worked, with that number varying by jurisdiction. Annual accrual caps and usage caps differ. Some laws require carryover of unused time into the next year while allowing a cap on the total; others permit front-loading a full year's amount instead, with different carryover consequences. Waiting periods before a new hire can use sick time are capped at different lengths. Increments of use, such as whether an employee can take a single hour or must take a larger block, are sometimes specified.

The permitted reasons vary too. Most cover the employee's own illness and care for a family member, but the definition of family member ranges from narrow to very broad, and many laws add safe time for domestic violence, public health closures, or school closures. Several require specific notice postings, written policy language, and records of accrual and use kept for a set number of years. Getting one of these wrong for one employee is a small problem; getting it wrong for a category of employees for two years is not.

Choose a strategy: one generous policy or per-state rules

There are two workable approaches. The first is to adopt a single policy that meets or exceeds the most demanding rule that applies to anyone on the team: the most generous accrual, the largest cap, the broadest set of permitted reasons, the shortest waiting period. This is simple to administer and easy to explain, and it treats everyone the same. The cost is that you give more than required in most states, and you still need to confirm that your single policy satisfies every specific requirement, since a generous accrual does not cure a missing notice posting.

The second approach is to maintain a base policy plus a short state addendum for each jurisdiction where you have people. This is more precise and less costly in leave hours, but it requires someone to track new hires by location, update addenda when laws change, and configure the leave system with a separate sick leave rule per state. For a team under a few dozen people, the single generous policy usually wins on total effort. As the team grows and clusters in particular states, addenda start to make sense. Related: What are the real benefits of giving your whole team a shared leave calendar?

Set up tracking so compliance is automatic

Whichever strategy you choose, the tracking system has to know each employee's work location and apply the right rule. That means sick time as its own balance, separate from vacation, with accrual driven by hours worked where the law requires it. It means caps, carryover, and waiting periods configured per rule rather than remembered by a manager. And it means a record of every accrual and every hour used, with the reason category, retained for as long as the strictest applicable law requires. Related: Why does tracking employee PTO in a spreadsheet eventually break down for teams?

Review the setup at least once a year and whenever someone is hired in a new state, because these laws change and new local ordinances appear regularly. Keep a simple register: for each state and city where you have staff, the accrual rule, cap, carryover, waiting period, notice requirements, and the date you last verified them against the labor department's official guidance. The small software team behind LeaveLedgr built per-location sick leave rules for exactly this situation, but the register and the annual review matter regardless of which tool you use. Related: How do PTO accruals actually work and how should a small business set them up?