13 claims checked against the article's verified sources. 13 ✓ Verified, 0 ⚠ Partial, 0 ✗ Issue, 0 🕐 Outdated. Coverage spans the federal floor (FMLA at 29 U.S.C. § 2601 requires only unpaid leave at 50+ employee employers), the list of 13 jurisdictions currently paying PFML benefits in 2026 with the Maryland and Virginia launches in 2027–2028, the payroll-tax funding structure, the work-location rule that determines which state's program applies, the back-contribution-plus-interest enforcement mechanism, the four most common employer mistakes the article identifies, and the through-line claim that tracking by work state rather than headquarters is the single highest-leverage prevention move. Source authority is inherited from the article's fact-check (Tier 1: 29 U.S.C. § 2601, state PFML agency programs and statutes across CA, CO, CT, DE, DC, ME, MA, MN, NJ, NY, OR, RI, WA, plus the Maryland and Virginia enabling statutes, and DOL FMLA implementing regulations at 29 CFR Part 825).
4 claims
"There's no federal paid family leave"
The federal Family and Medical Leave Act of 1993 guarantees up to 12 weeks of unpaid job-protected leave. No federal statute requires paid family or medical leave. The article's opening sentence makes the same point: "The federal floor is still zero."
"13 places require it, and one remote employee in a covered state means you owe contributions there"
13 US jurisdictions (12 states + DC) are paying PFML benefits in 2026 — California, Colorado, Connecticut, Delaware, DC, Maine, Massachusetts, Minnesota, New Jersey, New York, Oregon, Rhode Island, Washington. The work-location rule (sometimes called the "localization test") attaches the obligation to the employee's work state, not the employer's headquarters.
"Federal FMLA only requires UNPAID leave, and only at companies with 50+ employees"
FMLA's employer-coverage threshold is 50 employees within a 75-mile radius for 20+ workweeks in the current or preceding calendar year. The leave is up to 12 weeks unpaid in a 12-month period (26 weeks for military caregiver leave). Both thresholds appear in the article's Federal Baseline section.
"13 places — California, Colorado, Connecticut, Delaware, D.C., Maine, Massachusetts, Minnesota, New Jersey, New York, Oregon, Rhode Island, Washington — require PAID family leave"
The article's Quick Reference section lists these 13 jurisdictions verbatim. Each has its own enabling statute and agency-administered benefit program; the article's State-by-State section anchors each one independently (CA EDD, CO FAMLI, CT Paid Leave, DE Paid Leave Division, DC OPFL, ME Paid Leave, MA DFML, MN DEED, NJ DOL, NY WCB, OR Paid Leave, RI DLT TDI/TCI, WA Paid Family & Medical Leave).
7 claims
"funded by state payroll contributions"
State PFML programs are structured as social-insurance payroll taxes — the article describes this as "state-administered social insurance, not employer-funded leave." Most states split the contribution between employer and employee, but California, New York, Connecticut, and Rhode Island are employee-paid, while D.C. is employer-paid.
"The rule follows where your employee actually works, not where your business is"
Washington (RCW 50A) and Oregon (ORS 657B) both apply a localization test borrowed from unemployment insurance — coverage attaches to the employee's actual work location. The article's "5 Most Expensive PFML Mistakes" identifies this as the #1 failure mode: applying employer-headquarters rules to a remote employee.
"One remote employee in one of those 13 states means you owe contributions to that state's program, back to that employee's start date"
The article's mistake #1 names exactly this scenario: "A Texas-headquartered company with a single remote engineer in Washington, Colorado, or Massachusetts owes that state's PFML contributions back to the employee's start date — with interest." State PFML obligations are not waivable or backfillable; the contribution liability attaches as of the employee's hire date in a covered state.
"The state usually finds out the first time the employee files a benefit claim — and you get billed for back contributions plus interest"
Same parent claim as above. The article's framing: "The first the employer usually hears about it is when the employee files a benefit claim and the state finds no contribution record. The state then bills the employer for back contributions plus penalties."
"A Texas company with a remote engineer in Washington — you owe Washington contributions back to day one"
Direct restatement of the article's mistake #1 worked example. Washington's PFML program (RCW 50A) covers any employee whose work is localized in Washington, regardless of employer headquarters. "Day one" mirrors the article's "back to the employee's start date" framing.
"Taking deductions from employees for a 'private plan' that lapsed — you owe the state plus the employees"
Direct restatement of the article's mistake #3 — the private-plan opt-out trap. When approval lapses or gets disapproved retroactively, the employer owes contributions to the state plus owes the employees who paid into the disapproved plan. Most state PFML programs (Massachusetts, Washington, Oregon, etc.) allow private-plan substitution but require annual re-approval and financial-soundness reviews.
"Thinking paid family leave is a perk you can choose — it's a payroll tax, not a benefit"
The article's framing is that the expensive mistake is treating PFML as a benefit you can opt into rather than as a payroll-tax obligation that follows the employee's work location, not the employer's headquarters. Every covered state's PFML statute structures the funding as a mandatory state-administered payroll tax; the employer cannot opt out except via an approved private plan that meets or exceeds the state benefit.
1 claim
"Maryland and Virginia are next; their programs start in 2027–2028"
The article's Quick Reference and "Enacted, not yet paying benefits" sections both name these dates: Maryland (contributions January 2027, benefits January 2028); Virginia (contributions April 2028, benefits December 2028). Virginia became the first Southern state to enact PFML in April 2026.
1 claim
"Firing an employee soon after they took paid family leave — state laws prohibit it, even at small employers"
Direct restatement of the article's mistake #5. Most state PFML statutes include their own anti-retaliation provisions with private rights of action and attorney fees, independent of federal FMLA's 50-employee threshold. The Massachusetts PFML statute (MGL c. 175M) is one such example; a 2025 Suffolk Superior Court ruling confirmed anti-retaliation protection applies whenever an employee uses PFML, regardless of FMLA eligibility.
1 claim
"Almost every paid-family-leave mistake traces back to tracking the wrong state. List your employees by where they actually work — not where you are, not their address, not where they were hired — and you'll catch the exposure before the state does"
Synthesis claim from the article's through-line — "the single highest-leverage move for a distributed workforce is auditing every existing remote employee against their actual work-state's PFML program today, before the gap grows another quarter." The three "not where X" carve-outs (HQ, residence, hire state) trace to the work-location rule in Washington and Oregon's localization tests, which the article's mistake #1 expands on.
14 unique sources cited across the report — click to audit any claim directly against its evidence.
Every claim above links to the source we used. Open any source to compare the wording here with the underlying rule, guidance, court opinion, or product behavior.
If a source has changed or a claim looks wrong, tell us. We would rather correct the page than leave a stale answer online. See how we fact-check.
Clockspot helps small businesses track employee time and keep payroll-ready records. Used in all 50 states since 2007, we focus on getting time and pay right — including the wage-and-hour rules that shape both.
We build Clockspot for the same reason we publish these reports: time records should be understandable, reviewable, and tied to the rules that affect payroll. See how Clockspot works.