Two prominent topics that sit at the heart of leave and disability program management are: i) the rapidly evolving paid leave landscape and, ii) the strategic decision of how to structure leave administration (which we blogged about last year¹). This year, we want to connect those threads because the external pressure and the internal program are not separate conversations. They're the same one.

The Ground Is Still Moving. 
If you've been managing leave programs for any length of time, the last few years have probably felt less like steady progress and more like navigating a moving floor. And while multiple, long-standing federal proposals remain active in concept and/or reintroduction, Congress has not made meaningful progress toward enacting a universal paid family and medical leave (PFML) law. Hence, PFML laws have proliferated and expanded from a handful of states to a growing national patchwork. Paid sick leave (PSL) laws have broadened in scope, flexibility, and family definition, making even well-designed company policies feel outdated. And the pace isn't slowing.

Here's where things stand in 2026 and beyond.

On the PFML front, Delaware and Minnesota recently went live with benefits, and Maine joins the group on May 1, 2026. Maryland will begin benefits on January 1, 2028, a delay from earlier projections, but it is still coming. Amendments to the New Jersey Family Leave Act (NJFLA) adds job protection effective July 17, 2026, and employers should take note that it’s a meaningful expansion in terms of cost, benefit, and covered employers. And Virginia is widely anticipated to be establishing a PFML program with benefits beginning around 2029, signaling that state-mandated paid leave is not a regional experiment. It's becoming the norm.

On the paid sick leave side, the evolution has been less about new states going live and more about existing laws getting broader and more nuanced. A few trends worth noting:

Expanded qualifying reasons. Many states and localities now cover safe leave for victims of crime or domestic violence, organ and bone marrow donation, bereavement, and public health emergencies, among others.

Greater flexibility in how leave can be used. Some laws allow employees to use paid sick leave for any reason, giving those programs a structure that looks more like flexible PTO than traditional sick leave.

Broader family definitions. Coverage has expanded well beyond the traditional spouse-parent-child triad to include domestic partners, grandparents, grandchildren, siblings, and others.

Each of these changes requires policy updates, notice revisions, and payroll reconfigurations on relatively short timelines. For employers with workers across multiple states, including the cross-border workforces common throughout New England, even a small employee presence in a new or updated state can create real exposure if those rules aren't applied correctly.

The takeaway: Compliance cannot be treated as a periodic project. It has to be wired into your program's ongoing operations.

The Hidden Problem Isn't the Laws. It's the Program.

When an employer’s leave program breaks down, it isn’t always because the HR team missed a regulatory update. It's because the underlying program may not have been designed to absorb change without breaking.

Most leave programs were built incrementally. FMLA administration was set up first. Then, a state PFML program was launched, and a process was added to it. Short-term disability was layered in, managed by a separate carrier with a separate workflow. Over time, what looks like a leave program is actually a collection of overlapping processes, each technically functional but disconnected from the others.

The result is familiar: employees who receive conflicting communications depending on which program their absence touches. Payroll teams are processing corrections because leave status and earnings codes were out of sync. Managers are routing employees to the wrong place. HR is fielding escalations that likely shouldn’t have reached them.

This isn't a compliance failure in the traditional sense. It could be a program design failure, and no regulatory update will fix it.

A related pattern compounds the problem: employers often assume that because they have a TPA or vendor managing leave administration (e.g. “outsourced”), compliance is being handled. The vendor handles the workflow. But internal governance — verifying that administered reality matches policy intent, that payroll configurations are accurate, that manager behavior is consistent — requires someone on the inside to own it. When that ownership isn't established, compliance gaps grow quietly until something surfaces them.

What Integration Actually Looks Like.

The goal is straightforward, even when the execution isn't: one absence event, one coordinated workflow. An employee shouldn't have to navigate multiple programs, repeat the same information to different administrators, or receive different answers about their job protection and pay depending on which program their leave triggers.

In practice, a few things need to be true simultaneously.

One front door. Employees, managers, and HR should all route to the same intake process, regardless of whether the absence will touch FMLA, a state-paid leave program, employer policy, or short-term disability (STD). Intake captures what's needed to triage accurately before a designation is made, not after.

Coordinated eligibility and designation. Leave laws, STD, and state-paid leave programs each have their own eligibility rules, timelines, and definitions, and they don't always align neatly. When programs run concurrently, determining what an employee qualifies for, what pays, in what order, and under what conditions, requires deliberate coordination. That logic has to be established upfront and applied consistently, not worked out case by case.

Pay sequencing that's actually configured. A well-written policy that was never translated into payroll and HRIS configuration will generate errors. How does PTO coordinate with state wage replacement? What happens during the STD elimination period? How are arrears handled when a leave falls across a pay period? These scenarios need to be mapped and built into the system.

Compliance mapped by work location, not headquarters. Eligibility rules, notice requirements, documentation timelines, and wage replacement coordination all vary by the jurisdiction in which the employee works. For employers with cross-border or remote workforces, this distinction matters more than ever.

Sustaining It: The Work That Happens After Go-Live.

Implementation gets attention. Sustainment rarely gets enough.

Programs that hold up over time treat compliance as continuous, not cyclical. That means quarterly tracking of state PFML and PSL changes, including rate adjustments, form updates, and nuances in job protection. It means annual refreshes of handbook language, and vendor alignment, as well as episodic or virtual, on-demand manager training. Not because something went wrong, but because administered reality tends to drift from policy intent without deliberate maintenance.

It also means measuring the right things across three categories:

Operational: Time to case opening, certification completion rates, payroll correction frequency.

Risk and compliance: Notice timeliness, audit findings, and reinstatement exceptions.

Workforce outcomes: Average STD duration, return-to-work success, 90-day retention post-leave.

Programs that struggle tend to share a recognizable profile: leave, disability, PTO, and state benefits are managed as silos. Vendors are assumed to be compliant, with no internal governance to verify it. Payroll configurations don't reflect leave policy decisions. Manager behavior is inconsistent. Intermittent leave tracking is under-resourced. These aren't mystery failures. They're predictable, and they're preventable.

The Question Worth Asking.

The complexity of the leave landscape isn't going to decrease. What's going to separate programs that hold up from programs that don't isn't whether an employer knows all the rules. It's whether their program was designed to absorb change without breaking, and whether they've embedded the ongoing disciplines, metrics, and performance checks to keep it sustainably calibrated.

The question worth asking, right now, not after the next regulatory update, is: if we stress-tested our leave program against everything coming in the next 18 months, what would break first?

The answer to that question is where the real work begins.

Jim Jantz, Director of Compliance and Jim Reardon, Senior Consultant, Marsh McLennan Agency / Absence Disability and Life  

Marsh McLennan Agency's Absence, Disability & Life practice works with employers to design, implement, and sustain integrated leave and disability programs. If you'd like to talk through what this looks like for your organization, we'd welcome the conversation. You can reach us through [email protected]