Paid Family and Medical Leave Laws by State

Where each state stands on PFML — hover any state for the specific program.

Paid family leave is not one federal rule. Federal FMLA is unpaid; paid leave comes from state programs that follow where your employee actually works.

That matters most when you have remote employees. A Texas company with one remote engineer in Washington can owe Washington PFML contributions back to that employee's start date, with interest, even if the company has no office there. The state usually sees the gap when the employee files a benefit claim and no contribution record exists.

As of 2026, 13 jurisdictions (12 states + DC) are paying PFML benefits to workers, and two more states (Maryland, Virginia) are mid-implementation. Delaware, Minnesota, and Maine all launched benefits in 2026. Virginia became the first Southern state to enact PFML in April 2026, with contributions starting in 2028.

The federal floor is still zero dollars of paid leave. The Family and Medical Leave Act of 1993 guarantees 12 weeks of unpaid job-protected leave at employers with 50+ employees, but it does not pay the employee while they are out.

The compliance gap that matters most is that PFML is state-administered social insurance, not employer-funded leave you can choose to offer or skip. Depending on the state, the payroll contribution may be paid by the employer, the employee, or both. Get the funding model wrong and you owe back contributions plus interest plus penalties to the state — typically on a per-employee, per-quarter basis going back to the date the obligation attached. The highest-cost failure mode is treating PFML as a benefit choice instead of a payroll-tax obligation tied to the employee's work location, not the employer's headquarters.

Quick reference

• States paying PFML benefits in 2026 (12 + DC): California, Colorado, Connecticut, Delaware, District of Columbia, Maine, Massachusetts, Minnesota, New Jersey, New York, Oregon, Rhode Island, Washington.
• States enacted but not yet paying benefits: Maryland (contributions Jan 2027, benefits Jan 2028 after multiple delays); Virginia (contributions April 2028, benefits December 2028).
• States with voluntary state-sponsored insurance markets: New Hampshire (Granite State Paid Family Leave, opt-in since 2023); Vermont (VT-FMLI, phased rollout since 2023).
• States with no PFML program: the rest of the South, Mountain West, and Midwest other than Minnesota. Federal floor for these workers is FMLA's 12 weeks unpaid and only at employers with 50+ employees.

The 5 Most Expensive PFML Mistakes

Before the state-by-state grid, here are the failure modes that produce most PFML exposure. Three are compliance gaps, two are litigation risks, and all five surface during state audits or employee benefit claims.

1. Applying employer-headquarters rules to a remote employee. PFML follows the employee's work location, not the employer's state. 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. 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, and the employee gets the benefit anyway. The "localization test" Washington and Oregon both use (borrowed from unemployment insurance) means there's no escape: the work-state determines coverage even for a single employee.

2. Failing to designate FMLA concurrently with PFML. PFML and FMLA run concurrently for events that qualify under both — the DOL's January 14, 2025 opinion letter made this explicit. But if HR treats PFML as a separate "benefit," doesn't formally designate FMLA, and doesn't send the FMLA designation notice, the FMLA clock never starts. The employee then takes PFML benefits, returns, and later takes additional FMLA leave the employer thought they wouldn't owe. The fix is procedural: every PFML claim that qualifies under FMLA gets formally designated as FMLA leave within five business days of notice, with the designation notice telling the employee how many FMLA weeks are being counted.

3. Mishandling the private-plan opt-out. Most state PFML programs let employers substitute an approved private plan that meets or exceeds the state benefit. The trap is failing to maintain approval — plans expire, rates change, the state requires re-approval, and the employer keeps deducting from employee paychecks without remitting to either the state or a valid insurer. Annual re-approval, financial-soundness reviews, and benefit-equivalence checks are the standard state-agency compliance hooks; when a plan lapses or gets disapproved retroactively, the employer owes contributions to the state plus owes the employees who paid into the disapproved plan.

4. Tax mishandling on the employer pick-up. Per IRS Rev. Rul. 2025-4 and Notice 2026-6, when an employer pays some or all of an employee's required PFML contribution (a "pick-up"), the pick-up is taxable wages to the employee. Subject to federal income tax, FICA, and FUTA. Employers picking up the employee share without grossing up wages create W-2 reporting errors at year-end — and wage-statement violations under state statutes that require every deduction (including the PFML employee-share contribution) to appear on the pay stub. See our pay stub requirements by state guide for the per-state itemization rules. The cost is small per employee but compounds across a workforce and across years.

5. Retaliation for PFML use — at sub-FMLA-threshold employers. Most state PFML statutes carry their own anti-retaliation provision with a private right of action and attorney fees. A small employer (under 50 employees, so FMLA doesn't apply) who terminates or demotes an employee after a PFML claim faces state-law retaliation exposure even though FMLA would never have covered the leave. Massachusetts saw this play out in a 2025 Suffolk Superior Court ruling on PFMLA scope — the court confirmed that anti-retaliation protection applies whenever an employee uses PFML, regardless of FMLA eligibility. Plaintiff-side attorney fees make these claims economically viable down to one-employee class sizes.

Federal Baseline (FMLA)

The Family and Medical Leave Act of 1993, 29 U.S.C. §§ 2601-2654, guarantees unpaid job-protected leave. It is the floor — every state PFML program either layers wage replacement on top of FMLA-qualifying events or extends to events FMLA doesn't reach (safe time, parental leave at small employers, broader family definitions).

What FMLA provides. Up to 12 workweeks of unpaid, job-protected leave in a 12-month period for the employee's own serious health condition, care for a spouse/child/parent with a serious health condition, birth/adoption/foster placement with bonding, or qualifying military exigencies. Up to 26 weeks for military caregiver leave.

Employer coverage. Private employers with 50+ employees in 20+ workweeks in the current or preceding calendar year. All public agencies and schools regardless of count.

Employee eligibility. 12+ months of tenure, 1,250+ hours worked in the prior 12 months, and 50+ employees within a 75-mile radius of the worksite. This is the gap PFML fills: state programs typically cover employees of much smaller employers and with much shorter tenure.

Designation + maintenance. Employer must designate qualifying leave as FMLA within 5 business days (29 CFR § 825.300). Group health benefits must be maintained at the same level as if the employee were working (29 CFR § 825.209). Anti-retaliation: 29 U.S.C. § 2615(a).

How PFML actually works (the funding mechanism)

This is the structural feature most competitor articles bury. PFML programs are social insurance, closer to state Unemployment Insurance than to employment-law leave statutes. Five mechanics:

1. Payroll tax. Both employers and employees (or just employees, in DC, NY, CA, and a few others) pay a percentage of wages into a state fund. Wage base typically capped at the Social Security taxable maximum ($184,500 for 2026). Rates set annually based on the fund's actuarial solvency.

2. State-administered benefit. When an employee qualifies, they apply directly to the state agency. The state determines eligibility (typically wage-based, much broader than FMLA's hours test) and pays benefits directly — either from the fund or through a state-approved private insurer.

3. Progressive wage replacement. Most states use a tiered replacement curve: a higher percentage of low wages, a lower percentage of high wages, subject to a state-set weekly maximum tied to the State Average Weekly Wage (SAWW). Massachusetts pays 80% of wages up to 50% of SAWW, then 50% above. Minnesota pays 90% / 66% / 55% across three earnings tiers.

4. Private plan opt-out. Most states allow employers to substitute a state-approved private plan that meets or exceeds state benefits at no greater employee cost. Common in MA, NY, NJ, OR, CO, WA, DE, MN, ME. The opt-out is administratively complex — annual filings, separate accountings, state re-approval — and the bar for "as good as or better than" is policed actively.

5. Tax treatment. Per IRS Rev. Rul. 2025-4 and Notice 2026-6: employee contributions are withheld after-tax; employer pick-ups of the employee share are taxable wages; family leave benefits are gross income to the employee (state issues Form 1099); medical leave benefits generally are not wages but the state must still issue a 1099. Transition relief through 2026 for the medical-leave portion's third-party-sick-pay reporting.

California — the largest program

California's State Disability Insurance (SDI, since 1946) and Paid Family Leave (PFL, since July 1, 2004) are the largest state PFML programs by enrollment and the longest-running combined disability + paid-family-leave system. Rhode Island's TDI is the original — enacted in 1942, four years before California — but Rhode Island didn't add its family-leave component (TCI) until 2014. California has the longest continuous track record running both halves of the modern PFML model. Both California programs are administered by the Employment Development Department (EDD) and funded entirely by employee contributions through the same SDI payroll tax.

Rule	Details
Programs	SDI (own disability + pregnancy) since 1946; PFL (family care + bonding + military exigency) since 2004
Duration	SDI: up to 52 weeks. PFL: up to 8 weeks per 12-month period
Wage replacement (2026)	70-90% of average weekly wages, with the higher percentage for lower earners (per SB 951, effective Jan 1, 2025)
Maximum weekly benefit	$1,765 for 2026 (up from $1,681 in 2025)
Contribution rate (2026)	1.3% of all wages — no taxable wage ceiling (the wage cap was eliminated effective 2024 by SB 951). Employee-paid; no employer contribution.
Job protection	Not under SDI/PFL directly. Provided by the California Family Rights Act (CFRA), which applies to employers with 5+ employees — broader than FMLA's 50+.
Eligibility	$300+ in base-period earnings subject to SDI deductions, and an SDI-eligible work history. Much broader than FMLA's 12-month/1,250-hour test.

Worked example — what the numbers look like in 2026. SB 951's two-tier replacement structure (effective Jan 1, 2025) anchors the math against 70% of the 2026 State Average Weekly Wage of $1,789 — about $1,252/week, or ~$65K/year. Below that threshold workers get 90% replacement; above it, 70%; the absolute cap is $1,765/week.

• Low-earner case. An employee earning $30,000/year ($577/week) pays $390 in SDI/PFL contributions in 2026 (1.3% × $30,000). If they file an 8-week PFL claim, the benefit is 90% of average weekly wages — about $519/week, or $4,152 over the 8 weeks — paid directly by EDD.
• High-earner case. A senior engineer earning $250,000/year pays $3,250 in 2026 contributions (1.3% × $250,000, no cap since 2024). If they file an 8-week PFL claim, the benefit hits the $1,765/week maximum — $14,120 over the 8 weeks — even though 70% of their actual wages would be much higher. The contribution rate is uncapped; the benefit cap is fixed. This regressive contribution-vs-cap feature is a deliberate design choice that funds the post-SB 951 higher replacement rates for low-wage workers.

Things California employers consistently miss

• The SDI wage cap was eliminated in 2024. Pre-2024, only wages up to a fixed ceiling were subject to SDI withholding. SB 951 removed the cap entirely, so the 1.3% rate now applies to every dollar of wages. A senior engineer earning $400,000 owes $5,200 in SDI withholding for 2026; pre-2024 the same employee would have owed roughly $1,200. Payroll systems that didn't update for the cap removal have been under-withholding for two years.
• CFRA — not FMLA — is the relevant job-protection statute. CFRA covers employers with 5+ employees (FMLA covers 50+). A small California employer must restore an employee to the same or comparable position after PFL leave under CFRA, even though FMLA wouldn't have applied.
• PFL and SDI are sequential, not parallel. An employee with a pregnancy disability uses SDI for the disability period (typically 4 weeks pre-birth + 6-8 weeks post-birth), then transitions to PFL for the bonding period (up to 8 weeks). Two separate claims, two separate benefit calculations. Payroll mishandlings treat them as one continuous claim.
• Voluntary plan substitutions are tightly regulated. California allows employer-sponsored voluntary plans in lieu of SDI, but the Voluntary Plan Office requires annual filings, separate accounting, and majority employee consent. Plans drift out of compliance quickly when employer headcount changes.

How These Laws Actually Get Enforced

PFML enforcement is structurally different from sick-leave or overtime enforcement. The state agency is also the benefit administrator, which means contribution compliance and benefit eligibility are checked against each other in real time. Three patterns drive most of the litigation and audit exposure:

State audits triggered by benefit claims. The fastest way an employer learns they should have been remitting PFML contributions is an employee filing a benefit claim from a state where the employer never paid in. The state agency cross-references the claim against contribution records, finds the gap, and opens an audit. The employer owes back contributions, including any employee share it should have withheld, plus interest plus penalties — typically per quarter, per employee. This audit-on-claim mechanic is the structural feature that makes PFML enforcement different from sick-leave or overtime enforcement: the enforcement agency and the benefit administrator are the same office, so the gap surfaces automatically.

Retaliation private rights of action. Most state PFML statutes have a private right of action with attorney fees: Massachusetts M.G.L. c. 175M § 9, Washington RCW 50A.40.010, Colorado C.R.S. § 8-13.3-509, New York Workers' Compensation Law § 203-b. The combination of statutory damages + reinstatement + attorney fees makes these economically viable down to one-employee cases. A 2025 Massachusetts Suffolk Superior Court ruling confirmed that anti-retaliation protections run against the corporate employer but not against individual board members or co-employees — a procedural limitation on which defendants can be named, not a substantive defense to the underlying retaliation claim.

Class actions on systemic policy gaps. Same shape as wage-and-hour class actions. An employer applies a uniform policy across a multi-state workforce, the policy violates one state's PFML rule (typically: failing to remit contributions for remote employees in covered states, or denying private-plan benefits below the state minimum), and every affected employee becomes a class member. Tax-statement violations under state §226-style itemization statutes can layer on top, because PFML pick-ups are taxable wages that the wage statement must itemize.

The defensive posture is the same as for overtime: capture all the data the state auditor would want to see. Hours worked per state, contributions remitted per quarter, designation notices for FMLA-qualifying leaves, private-plan approval status if applicable. PFML audits go badly when records are thin, and the records the state needs are the same records HRIS and time-tracking systems already capture — they just have to be reconciled to the right state.

State-by-State PFML

The 13 jurisdictions paying benefits in 2026, with the 2026 rates and the underlying statute. Numbers shift annually with state SAWW updates — verify against the state agency before relying on a 2026 figure post-year-end.

State	Statute	Duration	Wage replacement / max weekly benefit (2026)	Contribution rate (2026)	Employer threshold for job protection
California (SDI/PFL)	Cal. Unemp. Ins. Code §§ 2601-3306, 3300-3306	SDI 52w / PFL 8w	70-90% wages; $1,765 max	1.3% of all wages (no cap); employee-paid	CFRA: 5+ employees
New York	N.Y. WCL §§ 200-242 (Article 9)	12w family leave	67% of wages; $1,228.53 max	0.432% of wages; employee-paid; max annual $411.91	NY PFL § 203-b: any employee with 30+ days in NY
New Jersey (TDI/FLI)	N.J.S.A. 43:21-25 et seq	TDI 26w / FLI 12w	85% of wages; $1,119 max	TDI 0.19% (+ employer experience-rated); FLI 0.23%; both employee-paid on wages up to $171,100	NJFLA: 30+ employees
Rhode Island (TDI/TCI)	R.I. Gen. Laws §§ 28-39, 28-41	TDI 30w / TCI 7w (rising to 8w)	~4.62% of high-quarter wages; $1,103 max	1.1% of wages up to $100,000; employee-paid; max $1,100	RIPFMLA: 50+ employees
Washington	RCW Title 50A	12w family/medical (16-18w combined)	90% / 50% sliding; $1,647 max	1.13% of wages up to $184,500; employer 28.57% / employee 71.43%; <50-employee employers exempt from employer share	RCW 50A.35: 25+ employees (lowered from 50+ effective Jan 1, 2026)
Massachusetts	M.G.L. c. 175M	12w family / 20w medical / 26w combined cap	80% / 50% sliding; $1,230.39 max	25+ employees: 0.88% (employer 0.42% / employee 0.46%); <25: 0.46% employee-only	All covered employers
Connecticut	Conn. Gen. Stat. §§ 31-49e-31-49k	12w (+ 2w for pregnancy complications)	95% / 60% sliding; $1,016.40 max (= 60× CT min wage)	0.5% of wages up to $184,500; employee-paid; max $922.50	CTFMLA: all covered employers
Oregon	ORS Chapter 657B	12w (+ 2w for pregnancy complications)	100% / 65% / 50% tiered; $1,636.56 max (120% of SAWW)	1.0% of wages up to $184,500; employee 60% / employer 40%; <25-employee employers exempt from employer share	ORS 657B.060: all covered employers
Colorado (FAMLI)	C.R.S. §§ 8-13.3-501 et seq	12w (+ 4w pregnancy complications + 12w NICU)	90% / 50% sliding; $1,381 max	0.88% of wages up to $184,500; employer 0.44% / employee 0.44%; <10-employee employers exempt from employer share	C.R.S. § 8-13.3-509: after 180 days of employment
District of Columbia	D.C. Code §§ 32-541.01 et seq	12w family / 12w medical / 12w parental / 2w prenatal	90% / 50% sliding; $1,190 max	0.75% of wages; employer-paid only (the only PFML program with no employee contribution)	DC FMLA: 20+ employees
Delaware	Del. Code Title 19, Ch. 37	Parental 12w / Medical+Family 6w combined (12w cap)	80% of wages; $900 max	0.4% total (parental 0.32% / medical 0.4% / family 0.08%); employer 50% min, remainder employee; max $738	Title 19 § 3710: 10+ employees parental, 25+ medical/family
Minnesota	Minn. Stat. Ch. 268B	12w medical / 12w family / 20w combined cap	90% / 66% / 55% tiered; $1,423 max (= SAWW)	0.88% (medical 0.61% / family 0.27%); employer 0.44% / employee 0.44%; max employee $814	§ 268B.08: 90+ days of employment
Maine	26 M.R.S.A. Ch. 7, Subch. 6-D	12w family / 12w medical (12w combined cap)	90% / 66% sliding; $1,198.84 max	15+ employees: 1.0% (employer up to 0.5% / employee up to 0.5%); <15: 0.5% employee-only	§ 850-G: 120+ days of employment

States not listed have no statewide PFML program. Workers there rely on FMLA's 12 weeks unpaid (and only at employers with 50+ employees), employer-provided short-term disability if offered, or accrued PTO. The federal-floor argument is most visible in this gap.

Enacted, not yet paying benefits

Maryland (FAMLI). Signed April 9, 2022. After multiple delays, contributions now begin January 1, 2027, and benefits no later than January 3, 2028. Initial contribution rate 0.9% of covered wages, split 50/50 between employees and employers with 15+ workers. Maximum weekly benefit $1,000 (initial cap; adjusted annually thereafter). Job protection for employers with 15+ employees. Maryland FAMLI.

Virginia (PFML). Enacted April 22, 2026 by Governor Spanberger and the General Assembly — the first Southern state to mandate PFML. Contributions begin April 1, 2028; benefits begin December 1, 2028. Up to 12 weeks per benefit year. Fiscal Impact Statement estimated ~0.72% contribution rate to support the enacted benefit level, split evenly between employer and employee. Employers with ≤10 employees exempt from the employer share (fund absorbs). Final rate set by VEC rulemaking before April 2028. VEC announcement.

Voluntary state-sponsored insurance markets

Two states offer state-sponsored but voluntary PFML insurance — employers opt in and purchase a policy through a state-contracted carrier.

New Hampshire — Granite State Paid Family Leave. Voluntary since January 2023. Underwritten by MetLife. State government employees enrolled by default; private employers can opt in. About 3% of NH workers enrolled as of mid-2025 per a Carsey UNH analysis.

Vermont — VT-FMLI. Phased rollout since July 2023. Underwritten by The Hartford. State employees first; private employers since 2024-2025. About 10,000 enrolled as of mid-2025 (~1,800 in private-employer plans). VT-FMLI.

These voluntary markets do not create a mandatory PFML obligation — they're optional insurance products. For multi-state employers, an employee in NH or VT is otherwise treated as having no state PFML coverage; only FMLA's federal unpaid floor applies.

How PFML coordinates with FMLA (the DOL guidance employers miss)

The DOL's January 14, 2025 opinion letter FMLA2025-01-A clarified the interaction between state PFML and federal FMLA. Three rules:

1. They run concurrently. When an employee takes state PFML leave and the leave also qualifies under FMLA, the employer must designate the leave as FMLA and count the weeks against the employee's FMLA entitlement. Failure to designate is the #2 mistake above — the FMLA clock never starts, and the employee can stack additional unpaid FMLA on top of PFML benefits.

2. The substitution provision doesn't apply during PFML-paid weeks. FMLA's traditional rule lets the employer (or, in some cases, the employee) require accrued PTO be used to cover unpaid FMLA leave. The DOL clarified that because PFML weeks are paid (by the state), the substitution provision is inapplicable. Neither party can unilaterally require concurrent use of employer-provided PTO during the PFML-paid weeks.

3. Supplementation is permissible by agreement. If state PFML pays less than 100% of wages, the employer and employee may agree to use accrued PTO to top up the wage replacement, if state law permits. After PFML benefits exhaust, the standard FMLA substitution rule applies to any remaining unpaid FMLA leave.

The structural takeaway: PFML doesn't extend FMLA, it just adds wage replacement to most of the same events. The employer's FMLA paperwork obligations are unchanged.

Multi-State and Remote Employees

PFML follows work location, not employer headquarters. This is the single most consequential rule for distributed workforces in 2026 — and the most frequently missed.

• A Texas-headquartered company with a remote employee living and working in Washington → WA PFML applies. 1.13% of wages up to $184,500, split 28.57% employer / 71.43% employee. The employer remits to Washington's ESD.
• A California-headquartered company with a remote employee in New York → NY PFL applies for the employee. 0.432% of wages, employee-paid (no employer contribution).
• A remote employee who relocates from Texas to Colorado → CO FAMLI applies starting the day of the move. Employer must begin remitting 0.44% employer share + withholding 0.44% employee share.
• A digital-nomad employee with rotating residences → the work-location rule applies wherever the employee is physically performing work at the time. The "localization test" Washington and Oregon use (borrowed from unemployment insurance) is the same: the state where work is "localized" — where the substantial majority of work happens — gets the contributions and provides the benefits.

Where coverage gets murky. An employee who works in two PFML states regularly creates a coordination question. Most states use the unemployment-insurance localization test as the tiebreaker: the state to which the employer reports the employee's wages for UI purposes is typically also the state to which PFML contributions are owed. New York is the most aggressive: a single NY-resident employee who works 30+ days in NY in a year is enough for NY PFL to apply.

The single highest-risk practice for distributed workforces is treating PFML as a benefit that applies only to employees in the employer's home state. The defensive options:

1. Per-state addenda + payroll remittance setup. A base handbook with state-specific addenda for every state with PFML, plus payroll integrations that remit to each state agency on schedule. Complex but precise.
2. Centralize through a payroll provider that handles PFML remittance. Many of the larger payroll providers will manage state PFML contributions, eligibility determinations, and benefit applications for an additional fee.
3. Audit existing remote employees against the work-state PFML rules now. The earlier the gap is identified, the smaller the back-contribution exposure.

What's NOT PFML (don't confuse them)

Several leave categories sit adjacent to PFML and get confused with it.

• FMLA leave — federal Family and Medical Leave Act provides up to 12 weeks of UNPAID, job-protected leave. PFML overlays partial wage replacement on top of FMLA-qualifying events; it doesn't replace FMLA. See the DOL FMLA page for the full federal framework.
• State sick leave — employer-funded, short-duration, event-triggered. PFML is state-administered, partial wage replacement, for serious health conditions. See our paid sick leave laws by state guide for the sick-leave cluster and the explicit FMLA-vs-PFML disambiguation.
• Short-term disability (STD) insurance — employer-purchased private insurance for the employee's own disability. PFML's medical-leave component overlaps with STD; many employers in PFML states are restructuring STD policies to avoid double-payment.
• ADA reasonable accommodation — extended unpaid leave as a reasonable accommodation for a disability is governed by the ADA, separate from PFML and FMLA. No contribution model; the leave duration depends on what's reasonable.
• Workers' compensation — time off for work-related injury or illness. PFML is for non-work-related events.
• Vacation / PTO — see our vacation and PTO payout laws by state guide. Treated as wages in payout states.
• Pregnancy disability leave — separate state statutes in some places (CA PDL is a distinct entitlement from CA PFL). The disability period is covered by SDI/STD; the bonding period is covered by PFL.
• Lactation accommodation — federal PUMP Act (29 U.S.C. § 218d) + state laws (NY § 206-c 30 min paid × 3 years; MN § 181.939 paid + no time limit; IL SB 212 paid effective Jan 1, 2026) cover the post-leave return-to-work period when the employee is nursing. See our lactation break laws by state guide — different statutory framework from PFML, but operationally sequential (PFML covers the time away; lactation accommodation covers the return).

The line: PFML is state-administered partial wage replacement for extended absences. Everything else either is fully employer-funded, doesn't include wage replacement, or doesn't bolt onto a state insurance fund.

Recent Changes (2024-2026)

PFML is the fastest-moving area of state employment law in 2026. Eight events between 2024 and 2028 shape the current landscape — five new state launches, two delays, and one job-protection threshold change.

2026

• Jan 1, 2026 — Delaware Paid Family and Medical Leave benefits begin. Contributions started January 2025. Maximum weekly benefit $900. Eleventh state to enact mandatory PFML.
• Jan 1, 2026 — Minnesota PFML contributions and benefits both begin. The only state to launch both simultaneously. Total payroll tax 0.88%, split evenly. Maximum weekly benefit $1,423 (= SAWW).
• Jan 1, 2026 — Washington PFML threshold changes. Job-protection threshold lowered from 50+ employees to 25+ employees under RCW 50A.35. Weekly-hours minimum for benefits eligibility lowered from 8 consecutive hours to 4.
• May 1, 2026 — Maine PFML benefits begin. Contributions started January 2025. 1.0% rate for employers with 15+ employees; 0.5% for smaller. Maximum weekly benefit $1,198.84.
• April 22, 2026 — Virginia enacts PFML. First Southern state to mandate PFML. Contributions begin April 2028; benefits begin December 2028. Estimated 0.72% contribution rate.
• Annual rate updates for CA SDI (1.3%, no cap), NY PFL ($1,228.53 max), MA PFML ($1,230.39 max), CT (0.5% / $1,016.40 max), RI TDI (1.1% / $1,103 max), NJ TDI/FLI ($1,119 max), CO FAMLI (0.88% / $1,381 max), DC PFL (0.75% / $1,190 max), Oregon ($1,636.56 max).

2025

• January 14, 2025 — DOL FMLA opinion letter FMLA2025-01-A. Clarified that state PFML and FMLA run concurrently and that the FMLA substitution provision doesn't apply during PFML-paid weeks.
• January 15, 2025 — IRS Revenue Ruling 2025-4. First formal federal tax guidance on state PFML — distinguishes employee contributions (after-tax), employer pick-ups (taxable wages), family-leave benefits (gross income), and medical-leave benefits (generally not wages). Transition relief through 2026 via Notice 2026-6.
• January 1, 2025 — Delaware contributions begin (benefits launched a year later).
• January 1, 2025 — Maine contributions begin (benefits launched May 1, 2026).

Pending — Maryland and Virginia 2028 launches

Maryland FAMLI contributions begin January 1, 2027 after multiple delays; benefits no later than January 3, 2028. Virginia PFML contributions begin April 1, 2028; benefits December 1, 2028. Both states are setting initial contribution rates through agency rulemaking; the rates published in 2026 are preliminary and subject to change before launch.

Patterns Across the Laws

Thirteen-jurisdiction PFML programs on the books, but the structure is more coordinated than it looks. Once you see the five core dimensions, every program is a permutation within them.

Contribution rates cluster around 0.5% to 1.0%. California's 1.3% is the outlier high (it covers both SDI and PFL on the same tax). New York is the outlier low at 0.432%. Most programs land between 0.5% (CT) and 1.13% (WA). Smaller programs (DE 0.4%, ME for small employers 0.5%) sit at the low end; larger programs (MN 0.88%, CO 0.88%, MA 0.88%, OR 1.0%) cluster in the middle.

Wage replacement is progressive in all but one program. Every PFML program except California uses a tiered replacement curve — higher percentage of low wages, lower percentage of high wages. California's flat 70-90% (with the higher rate for lower earners) is the closest analogue but doesn't use the same SAWW-band structure. The default formula across MA, OR, MN, CO, WA, ME is some variant of "90% up to 50% of SAWW, then 50% above."

Maximum weekly benefits track SAWW. The 2026 maximums range from $900 (Delaware) to $1,765 (California). The median is around $1,200. The high cap is structurally important: PFML programs aren't designed to fully replace executive wages — they're income protection up to a state-determined ceiling.

Job-protection thresholds vary widely. California's CFRA: 5+ employees. Massachusetts: all covered. Washington (after Jan 1, 2026): 25+. Maryland (when it launches): 15+. New Jersey NJFLA: 30+. FMLA: 50+. The smaller the employer, the more likely PFML wage replacement applies but FMLA job protection does NOT — a structural gap that the state programs without their own job-protection statutes don't close.

Contribution split varies but employee usually pays the majority. California, New York, Connecticut, and Rhode Island are 100% employee-paid. DC is 100% employer-paid (the only such program). The rest split: WA 28.57% / 71.43% employee, CO 50/50, MN 50/50, MA roughly 60/40 employee-favored, OR 60/40 employee, DE 50% minimum employer share, ME variable by employer size.

Industry-Specific Patterns

PFML exposure concentrates in industries with multi-state workforces, high-turnover hourly staff, or specific demographic profiles that drive benefit usage.

Multi-state professional services and tech

The single biggest PFML compliance gap in this vertical is contribution remittance across state lines. A NY-HQ or CA-HQ software company with engineers in WA, CO, MA, and OR owes contributions to each of those state programs independently — and state agencies cross-reference benefit claims against contribution records, so the missing remittance surfaces the first time a remote employee files a claim. Centralized payroll providers that handle the remittance are the defensive structure; the trap is treating PFML as "the home state's program" rather than as four (or seven, or twelve) separate state obligations.

Healthcare and home health

Healthcare generates a disproportionate share of PFML claims — staff exposed to patients catch what patients have, and home-health workers care for family members with the same serious conditions they see at work. The compliance trap unique to healthcare is contribution attribution for traveling-nurse and agency-placement staff, who may work across three or four state lines in a single quarter. Most state programs include carve-outs for healthcare staffing arrangements; confirm against the state agency's enforcement guidance before assuming the home state covers the contribution.

Retail and hospitality

High turnover masks PFML obligations — most workers quit before they'd ever file a claim, so employers under-estimate the exposure. But contributions are remitted on every covered employee from day one regardless of whether they claim, and the wage-based eligibility threshold ($300+ in CA base period, similar in others) is low enough that even short-tenure workers may qualify. The retroactive exposure is small per employee but compounds across high-turnover workforces — a single state audit covering 24 months of missed contributions across 200 turnover roles is a meaningful assessment.

Construction and trades

Variable hours and seasonal employment create base-period earnings volatility, which is the PFML-specific enforcement angle for this industry. A worker with strong earnings in two quarters and weak earnings in two others may qualify for PFML in some claim windows but not others, and the state agency audits the base-period earnings calculation when a benefit dispute arises. Documentation of hours per state per quarter is the defense — without it, the worker's wage history is the state's word, not the employer's.

Government and unionized workforces

CBAs typically grant more generous leave than the state PFML floor, but the layer-cake creates its own enforcement risk: the state law is the floor, the CBA is the ceiling, and government employers often have a pre-existing paid-leave system that pre-dates the state PFML statute. The compliance trap is reconciling all three — letting the CBA's more-generous benefit displace the state PFML claim doesn't relieve the employer of the contribution obligation, and the state will still bill for missed remittance even if the worker ultimately took CBA leave.

Frequently Asked Questions

If You Discover You've Been Doing This Wrong

PFML audits often reveal accumulated gaps: remote employees on the wrong state's PFML, missing FMLA designations on past PFML claims, employer pick-ups not grossed up for tax, private plans that lapsed. Here's the unwinding playbook:

1. Audit by work location. Pull every employee's actual work state (not residence, not hire state, not employer HQ). Compare to the state's PFML program — is the employee covered, and have contributions been remitted? The biggest exposure is usually distributed employees in covered states with no contribution record.

2. Reconcile contributions retroactively. If you missed a state, calculate what should have been remitted to date, including any employee share you should have withheld. The state will typically assess back contributions plus interest and may waive penalties for voluntary disclosure. Document the calculation against each state's published rate history — rates change annually and the assessment runs at the correct rate for each year missed. Pull source records from your payroll system; the retention windows in our recordkeeping requirements by state guide determine how far back you can reconstruct.

3. Audit FMLA designations on past PFML claims. For every PFML claim in the past 12-24 months, confirm the employee was given a formal FMLA designation notice within 5 business days, and that the PFML weeks were counted against the FMLA entitlement. If not, the FMLA clock didn't start — and you may still owe unpaid FMLA on top of the PFML you already paid.

4. Verify private plan approval status. If you opted out of state PFML via a private plan, confirm the plan is currently approved by the state agency. Annual filings, rate changes, and re-approval requirements catch employers who set up a plan years ago and haven't maintained it. If the approval lapsed, you owe contributions to the state for the lapsed period.

5. Gross up employer pick-ups for tax. If you've been paying the employee's PFML share without including the pick-up in taxable wages, fix the W-2 reporting and gross up going forward. Some states require corrected wage statements; the federal piece is W-2 amendment and back FICA / FIT calculation. The amounts are small per employee but the IRS picks these up on payroll audits.

6. Consult counsel if there's a retaliation claim risk. Termination, demotion, or attendance-point penalties tied to PFML use creates state-law exposure independent of FMLA. If any adverse action followed a recent PFML claim, get counsel involved before the employee files. Voluntary remediation (reinstatement, back pay, settlement) shrinks exposure dramatically vs litigation.

The Through-Line

PFML compliance has three structural failure modes that compound across employees, states, and years: misunderstanding the funding model (it's state-administered social insurance with a payroll-tax obligation, not employer-funded leave that you can choose to offer), tracking the wrong state (PFML follows the employee's work location, not the employer's headquarters — a single remote employee in a covered state triggers full contribution liability), and failing to designate FMLA concurrently (state PFML doesn't extend the federal FMLA clock; it just adds wage replacement to most FMLA-qualifying events). Get all three right and PFML is mostly remittance math against a state agency. Get any one wrong and the exposure surfaces years later when an employee files a benefit claim or the state runs an audit.

For multi-state employers, the operational answer is the same as for breaks, overtime, and sick leave: standardize the data model to work location, not headquarters. Hours worked per state, contributions remitted per quarter to each state's agency, FMLA designation notices for every qualifying claim. The records the state PFML auditor wants are the records HRIS and time-tracking systems already capture — they just have to be tied to the right state. 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.