Leave is where competent HR quietly goes wrong

There is no federal paid sick leave law.

What exists instead is a patchwork. States, counties and individual cities each set their own rules, and they don’t align — different accrual rates, different carryover caps, different definitions of who counts as a family member, different notice requirements. They also don’t defer to one another. An employee can be covered by a state law and a city ordinance at the same time, and you owe the more generous of the two on every individual term, not the more generous law overall.

Hire two people in Philadelphia, one in New Jersey, one in Chicago and one in California, and you have four sets of obligations and one policy that probably doesn’t match any of them.

California is the clearest illustration of why headcount alone tells you nothing. Federal family leave doesn’t reach you until 50 employees. California’s own family rights act reaches you at five. A six-person company with one employee in Sacramento already has family leave obligations it would have none of federally — and most companies that size have no idea.

Most companies find this out the same way: someone requests leave, and nobody can answer with confidence.

The thresholds arrive on headcount, not on readiness

At 50 employees, FMLA applies. Twelve weeks of unpaid, job-protected leave with health benefit continuation — and an administrative process with legal deadlines attached to it. The ACA employer mandate lands at the same headcount.

The counting rules are less obvious than they look. FMLA coverage is 50 or more employees for at least 20 workweeks in the current or preceding calendar year. But an individual employee is only eligible if they’ve been with you 12 months, worked 1,250 hours in the previous 12, and work at a site with 50 or more employees within 75 miles.

That last clause is where remote hiring causes trouble. Distributed teams make the 75-mile calculation genuinely non-obvious, and getting it wrong in either direction is expensive — deny leave to someone eligible and you have an interference claim; grant it to someone who isn’t and you’ve set a precedent you’ll be held to.

The stacking problem

This is the part that separates leave administration from leave policy.

Entitlements run alongside each other rather than neatly end to end. An employee out for their own serious health condition might be simultaneously on FMLA, on a state medical leave, drawing a state paid family leave benefit, and have an ADA accommodation obligation attached to the end of it. Those aren’t alternatives. They’re concurrent, they have different durations, and the sequencing determines when job protection actually runs out.

Get the sequencing wrong and you terminate someone who still had protection left. That is the single most expensive leave mistake there is, and it is almost always made by someone competent who thought the twelve weeks were up.

Intermittent leave is where tracking fails

Continuous leave is administratively simple — someone is out, then they return. Intermittent leave is taken in hours or part-days over months, often unpredictably, and it has to be tracked against an entitlement balance in real time.

Most companies track it in a spreadsheet, or in an HRIS that wasn’t designed for it, or in a manager’s memory. All three fail the same way: when there’s a dispute about whether someone exhausted their entitlement, you need records you can defend, and reconstructing them afterward isn’t possible.

Leave you didn’t declare properly may not count

This is the trap almost nobody sees coming, and it is entirely a documentation problem.

Once you have enough information to know that leave is FMLA-qualifying, you have five business days to give the employee a written designation notice — and to tell them how much time is being counted against their entitlement (29 CFR 825.300(d)). That notice is not a formality. It is the mechanism by which the clock actually starts.

Miss it and you are not automatically sunk: the regulation permits retroactive designation, provided the failure to designate on time didn’t cause the employee harm (29 CFR 825.301(d)). But if it did cause harm, that can constitute interference with their FMLA rights, and the exposure includes lost compensation and benefits, other actual monetary losses, and equitable relief including reinstatement (29 CFR 825.301(e)).

So the practical picture: an employee who was out for eight weeks that nobody designated has not necessarily used eight weeks. If they come back, request leave again, and you tell them their entitlement is nearly gone — and they were harmed by never having been told the first time — you have a problem that no amount of good intent fixes.

The same applies to the smaller notices. Eligibility notice, rights and responsibilities, certification deadlines, and written confirmation of time counted. Disputes about whether leave qualifies have to be documented as well (29 CFR 825.301(c)).

None of this is difficult. It is simply a sequence of things that must happen on time, in writing, every time — which is precisely what falls apart when leave administration lives in a finance leader’s inbox between other priorities.

Why the usual answer doesn’t fit a company your size

Third-party leave administrators will technically take you at 50 employees. Almost nobody buys one at 50.

Budget for dedicated leave administration doesn’t appear until a company is several hundred people. Research from Marsh McLennan Agency found that around 70% of businesses in the 500 to 1,000 employee range outsource leave management or run a hybrid of outsourced and in-house. Below that, companies are largely doing it themselves — AbsenceSoft’s research puts in-house FMLA administration at 79% of organizations overall.

So there’s a long stretch, call it 50 to 500 employees, where every obligation is fully in force and the answer is that somebody absorbs it. In a 60-person company that somebody is the finance lead, between other priorities, learning the certification deadlines on the day they matter.

And the vendor model carries a limitation its own suppliers are candid about. AbsenceSoft’s research notes that leave vendors handle straightforward FMLA requests well — the process is codified and the steps are clear — but that entitlements often stack, and nuanced cases get handed back to HR anyway. Their finding is that employers who outsource leave need roughly the same internal headcount to support it as employers who don’t.

Which is exactly backward for a company your size. The straightforward FMLA request is the one you could have handled. The stacked, intermittent, ADA-adjacent case is the one you needed help with — and that’s the one that comes back.

We do it the other way round. We’re embedded, we know your business and your people, and the complicated case is the reason we’re there.

What we’ve built

A single paid sick and safe leave policy that holds up across more than a dozen jurisdictions. One policy, not a dozen parallel ones.

That distinction matters more than it sounds. A manager approving time off cannot be expected to know which of eleven policies applies to the person in front of them. A single policy written to satisfy the most generous requirement on each individual term is something they can actually apply — consistently, without calling you first.

What’s included

• One unified sick and safe leave policy across the jurisdictions you operate in
• FMLA eligibility determination, designation notices within the five-business-day window, certification and recertification, and the deadlines attached to each
• Written confirmation of time counted against entitlement — the step that determines whether the leave actually counted
• Coordination of concurrent entitlements so job protection is tracked accurately
• Intermittent leave tracking against entitlement balances, with records built to be defended
• The ADA interaction: when leave becomes an accommodation question, and what the interactive process requires
• Return-to-work planning, including fitness-for-duty and restriction handling
• Manager guidance, so a request is handled correctly at the point it’s made

Where we stop

We are not your employment counsel. Leave sits on top of ADA, state case law and, in some situations, workers’ compensation — and when a case needs a legal opinion we say so and bring your attorney in early, while it’s still a question rather than a claim.

We’re also not a claims administrator or an insurance carrier. If your state’s paid family leave program runs through a carrier, we coordinate with it; we don’t replace it.