Can an HR manager be personally sued for an FMLA mistake? In most of the country — yes.
If you run leave for a multi-state employer, the exposure is not only the company’s. Here are the five questions HR managers actually ask about personal FMLA liability, answered plainly and keyed to the underlying regulation.
This is general information about the FMLA, not legal advice for a specific situation. Consult employment counsel for your case.
Can an HR manager be sued personally for an FMLA mistake, or only the company?
In much of the country, an HR manager or supervisor can be held individually liable for an FMLA violation, separately from the company. The FMLA defines "employer" to include "any person who acts, directly or indirectly, in the interest of an employer" (29 U.S.C. § 2611(4)(A)(ii)(I)), and in Haybarger v. Lawrence County Adult Probation & Parole (3d Cir. 2012) a court held a supervisor could be personally liable where he had sufficient control over the employee's FMLA-relevant decisions. Note the honest nuance: this is a circuit split — the 3rd, 5th, and 8th Circuits recognize individual liability while the 6th and 11th have declined to extend it to public-agency supervisors. For a multi-state employer, the safe assumption is that some managers are exposed somewhere in the footprint. What reduces the exposure is consistent, documented, by-the-book handling and a cited record of correct process.
I have 5 business days to designate FMLA leave. When does the clock actually start?
The clock starts when you have enough information to know the leave is FMLA-qualifying — not when the employee first mentions being out. 29 CFR 825.300(d)(1) requires the employer to notify the employee whether leave is designated as FMLA within 5 business days, absent extenuating circumstances, of having enough information to determine that the leave qualifies. The common trap is sitting on a vague absence thinking the clock has not started when you already had enough to know it qualified. Document the date you learned enough; that date is your defense.
An employee gave me a vague doctor's note. Can I ask for more, and how long do they have?
Yes. You can require a complete medical certification, and the employee generally gets at least 15 calendar days to return it under 29 CFR 825.305(b). If the certification is incomplete or insufficient, you must state in writing what is missing and give the employee a chance to cure it (825.305(c)) — you cannot simply deny. Denying leave off an incomplete note without the written cure step is itself a violation. The defensible move is the documented request-and-cure, not the fast no.
An employee used all 12 weeks of FMLA but is still out. Do I have to keep their job open?
Under the FMLA, the job-restoration right runs out when the 12 weeks are exhausted (29 CFR 825.214 covers restoration for employees returning within the entitlement). But you are not necessarily done: additional unpaid leave can be a reasonable accommodation under the ADA, and terminating at exactly week 12 without an ADA analysis is a common, expensive mistake. The defensible move is a documented FMLA-to-ADA hand-off and interactive-process analysis before any adverse action.
If I follow our HR software, am I personally protected when we still get it wrong?
No tool makes you immune. Individual liability turns on what you did and whether you caused the violation, so the best protection is contemporaneous proof that you followed the regulation — the right notice, on the right day, citing the right rule. That record is hard to assemble by hand across a multi-state footprint, which is where mistakes and personal exposure cluster. Sentel checks a proposed HR action against the underlying federal and state regulation and keeps the cited, time-stamped audit trail of why the decision was defensible. It is compliance software and a defensible process, not insurance — it makes no promise to pay any fine, judgment, or third-party loss. What it does is make the by-the-book record the default.
Sentel keeps the cited, time-stamped record that makes the by-the-book decision the default — compliance software and a defensible process, not insurance.