FMLA Violations by Employers: 12 Common Mistakes and Fixes

Most FMLA violations don't start with a manager saying "no, you can't take leave."

They start with a missed deadline. A manager who didn't recognize a leave request. An attendance policy that quietly counted protected absences against someone.

The Department of Labor's Wage and Hour Division ran 349 FMLA compliance actions in fiscal year 2024, its highest count since 2021, recovering more than $1.4 million in back wages for 344 employees. Denial of leave and discrimination topped the violations found.

Private lawsuits add another layer, because the FMLA hands employees two separate paths to sue: interference and retaliation.

This guide breaks down the 12 violations employers actually commit, what each one costs, and the fixes that keep you out of a DOL file. It's written for the people who own this risk day to day: ER specialists, HRBPs, leave administrators, and the leaders they report to.

What Counts as an FMLA Violation by an Employer?

An FMLA violation is any action that denies, restrains, interferes with, or punishes an employee's use of their rights under the Family and Medical Leave Act.

The law entitles eligible employees at covered employers to up to 12 weeks of unpaid, job-protected leave per year, 26 weeks for military caregiver leave, with group health benefits maintained. That's the core of the FMLA's protections, and the Department of Labor's FMLA overview lays out the full machinery.

Coverage applies to private employers with 50 or more employees in 20 or more workweeks, plus public agencies and schools of any size. Eligibility requires three things: 12 months of employment, 1,250 hours worked in the prior year, and a worksite with 50 employees within 75 miles.

Violations happen when employers get any link in that chain wrong. Or get the chain right, and then mishandle what comes after.

What's the difference between FMLA interference and FMLA retaliation?

Interference happens before or during leave. Retaliation happens because of it.

Interference is blocking, denying, discouraging, or failing to inform an employee about their FMLA rights. Retaliation is discipline, demotion, exclusion, or termination connected to the fact that someone requested or used leave. Courts treat them as separate claims with separate proof standards, which means one botched termination can generate two counts in the same lawsuit.

The distinction tells you how to prevent each. Interference claims usually trace back to process failures, like missed notices and untrained managers. Retaliation claims usually trace back to decisions, like a write-up or a termination, made without checking the leave file first.

You prevent the first with workflow. You prevent the second with review gates.

What happens if an employer violates the FMLA?

Three things can happen, and they stack.

The employee can file a complaint with the DOL's Wage and Hour Division, which investigates and can require remedies. The employee can file a private lawsuit in federal or state court. And the employer can be on the hook for damages that are designed to hurt.

Damages include lost wages and benefits, front pay where reinstatement isn't workable, and liquidated damages that double the monetary award unless the employer proves it acted in good faith. Add attorney fees and costs on top. There's no damages cap the way there is under Title VII, and courts, including the Second Circuit, have held that individual HR professionals can be personally liable as "employers" under the statute.

That last point tends to get a room of HR leaders very interested in process.

The 12 Most Common FMLA Violations Employers Make

These are ranked roughly by how often they show up in DOL findings and litigation, not by how dramatic they sound. The boring ones are the frequent ones.

1. Failing to recognize an FMLA leave request

Employees don't have to say "FMLA." If a worker gives enough information for the employer to know the leave may qualify, a serious health condition, a sick family member, a new child, the obligations kick in.

In James v. FedEx Freight, decided by the Eleventh Circuit in November 2025, a freight handler told supervisors his wife had a high-risk pregnancy and that he needed to leave at the end of his shift to care for her. No one told him about his FMLA rights. When he left on time instead of working mandatory overtime, FedEx called it job abandonment and fired him. The court revived his interference claim, noting he was entitled to intermittent leave that would have protected the exact absences he was punished for.

The fix is manager training with a single rule: any absence tied to health or family gets routed to HR within 24 hours. Managers don't decide what qualifies. They escalate.

2. Missing the eligibility and designation notice deadlines

Once an employer learns leave may be FMLA-qualifying, the clock starts.

You owe the employee an eligibility notice within five business days, then a designation notice within five business days of having enough information to decide whether the leave qualifies. Miss those windows and you've handed a plaintiff's lawyer an interference claim that requires zero creativity, because the regulation is a checklist.

3. Denying or restricting intermittent leave

Intermittent leave is where employer patience goes to die, and where a lot of violations are born.

When it's medically necessary, eligible employees can take FMLA in increments as small as your payroll system tracks. A few hours for an appointment. A day for a flare-up. Denying it because it's operationally inconvenient, or pressuring someone to take it in larger blocks than they need, is a violation. The FedEx case turned on exactly this point.

4. Botching medical certification and recertification

You're allowed to require certification. The process has rails.

Fifteen calendar days for the employee to return it. A written cure notice identifying deficiencies before any denial. Tightly limited recertification triggers. The pattern in litigation is consistent: employers lose when they demand recertification out of frustration with absences rather than a documented trigger, like a changed pattern or an extended duration. The certification file should show what prompted every request.

5. Counting FMLA absences against attendance policies

No-fault attendance policies are the silent killer here.

If your point system dings an employee for a protected absence, or a perfect-attendance bonus excludes FMLA takers in a way that treats them worse than other leave types, you've interfered with the right itself. The DOL's Fact Sheet #28 names assessing negative attendance points for FMLA use as a violation in plain language. Audit the policy, then audit the actual point ledgers, because the policy is often clean while the data isn't.

6. Contacting employees excessively during leave

A brief call to ask where a file lives is fine. Turning a person on leave into a remote worker is not.

Assigning work, requiring attendance at meetings, or expecting steady availability is interference. Set a contact protocol before leave starts: who may reach out, about what, and how often.

7. Failing to restore the employee to an equivalent job

Reinstatement means the same position or one genuinely equivalent in pay, benefits, shift, location, and status.

"Equivalent" doesn't mean the same title with a quietly gutted scope, or a transfer to the branch across town. Returning someone to a diminished job is one of the cleaner retaliation fact patterns an employee can bring.

8. Terminating too close to a leave request

Temporal proximity isn't proof of retaliation. It's the evidence courts let juries weigh first.

Terminating someone two weeks after they requested leave puts the entire burden on your documentation. If the performance case wasn't in writing before the leave request existed, you don't have a performance case. You have a settlement negotiation. Route any adverse action involving a recent leave-taker through a second set of eyes, every time.

9. Treating leave-takers differently in reviews and promotions

Lowering a rating because goals went unmet during protected leave, or passing someone over because they were "out a lot this year," uses FMLA leave as a negative factor in an employment decision. That's unlawful.

Calibrate reviews for leave-takers by prorating goals, and document that you did it.

10. Mishandling the FMLA-to-ADA handoff

FMLA exhaustion is not a termination trigger.

When 12 weeks run out and the employee still can't return, the ADA's reasonable accommodation analysis begins, and additional unpaid leave can itself be a reasonable accommodation. Employers with automatic "terminate at week 13" practices have paid dearly for them in EEOC actions. Treat the end of FMLA as the start of an interactive process, not the end of the conversation.

11. Ignoring state and local leave laws

The FMLA is the floor, not the ceiling.

State family leave laws frequently cover smaller employers, more family members, and longer durations, and several states' paid programs layer on their own job-protection rules. An employer can be perfectly FMLA-compliant and still violate state law, which is exactly the trap in states like California, where the labor law requirements extend well past the federal baseline. Map every employee to their state's rules, especially with remote workers scattered across jurisdictions.

12. Enforcing leave policies inconsistently

Inconsistency converts ordinary decisions into evidence.

If one employee's late certification gets grace and another's gets a denial, the difference between them becomes the lawsuit. The same goes for how managers question absences and how return-to-work is handled. Consistency requires a system of record, not a folder of email threads, which is the problem a centralized HR case management platform exists to solve. Every leave-related issue, conversation, and decision logged the same way, visible to the people who need it, with timelines that prove what happened when.

What FMLA Violations Cost Employers

The direct math is brutal, and liquidated damages are why.

Take a wrongfully terminated employee earning $85,000 who is out of work for a year. That's roughly $85,000 in back pay. Liquidated damages double it to $170,000 before front pay, benefits losses, and fee awards. The employer pays its own defense costs on top, and plaintiff-side fee awards in FMLA cases routinely exceed the underlying damages. That combination is why these cases settle, and why insurers price them the way they do.

This isn't theoretical. In one 2024 enforcement action, the DOL recovered $200,000 for a public-health worker who was fired a day after requesting FMLA paperwork, because the employer never sent the required notices and never evaluated whether the leave qualified.

The indirect costs hit the ER team hardest. Employees can go straight to the Wage and Hour Division or straight to court, so you may get no internal warning before an investigator calls. Every leave decision your organization made in the lookback period becomes discoverable, and inconsistencies you never noticed become Exhibit A. The retaliation exposure compounds it, because leave-takers are one of the most common claimant profiles, and the patterns in our guide to preventing workplace retaliation apply to them with full force.

How to Prevent FMLA Violations: A Practitioner's Checklist

Prevention is unglamorous and it works. Here's the operating system.

Train managers on one behavior, not the whole statute. They don't need eligibility math. They need to recognize a potential leave request and route it within 24 hours. Test it in training with realistic phrasing like "my mom's surgery is next month," not textbook language.

Run notices on a clock, not a memory. Five business days for eligibility, five for designation, 15 calendar days for certification returns, cure notices before denials. Automate the timers. Humans forget. Workflows don't.

Gate every adverse action against the leave file. Before any discipline, demotion, or termination touches an employee with FMLA activity in the past 12 months, someone outside the reporting line reviews the timeline. If the paper trail postdates the leave request, stop.

Document the why behind every recertification and denial. A one-line note, like "pattern changed: six unscheduled Mondays in eight weeks," is the difference between a defensible request and an interference claim.

Treat patterns as investigation triggers, handled properly. Suspected leave misuse deserves a real process, not manager vigilantism. Apply the same discipline you'd use when conducting a workplace investigation: defined scope, neutral fact-gathering, documented findings. An overly aggressive probe creates the very interference claim you were trying to avoid.

Track leave-related complaints centrally. When someone says "my manager keeps texting me on leave" or "I got written up right after I asked for FMLA," that report needs a timestamped home, an owner, and a resolution path. Scattered inboxes are how small complaints become federal cases.

FMLA Compliance Is an Employee Relations Problem, Not Just a Legal One

Legal owns the statute. ER owns the moments where violations actually happen.

The manager who rolls his eyes at an intermittent leave request. The write-up that lands a week after a certification. The return-to-work that quietly comes with a worse shift. These are employee relations events, and they're visible early if you're tracking them. Teams that log leave-adjacent complaints and watch the trends catch a problem manager after the second incident instead of after the lawsuit.

Done right, this flips from defense to signal. Leave friction clusters by manager, by department, and by policy, and those clusters tell you exactly where to retrain, rewrite, or intervene before the DOL or a plaintiff's firm finds the same pattern in discovery. You can see how People teams put that into practice across real organizations.