5 times it’s OK to fire an employee on FMLA leave

Of course, you’d never to fire someone for taking FMLA leave. But perhaps the termination had been in the works long before the person took FMLA leave. It’s still a sticky situation, but a court recently outlined when it’s safe to say goodbye to someone on FMLA leave. 

The danger is, obviously, FMLA interference and retaliation claims. You never want to make it look like the taking of FMLA leave was a motivating factor in the decision to terminate someone (not that it would be).

Still, an FMLA lawsuit may likely be forthcoming if you terminate someone while they’re on, or just returning from, FMLA leave. It’s kind of a go-to move for employee-side attorneys: “Oh, you were on FMLA leave when they fired you. That’s interference and retaliation.”

But courts will side with you if you can prove the employee, FMLA leave aside, had it coming — e.g., the person was embezzling money, harassing the secretary or lying to customers.

When it’s safe to cut the cord

The U.S. Court of Appeals for the Tenth Circuit recently highlighted five separate cases in which it threw out a worker’s FMLA lawsuit against an employer after finding “undisputed evidence that the employee in question would have been terminated even if FMLA leave had not been taken.”

In then pointed out the element each employer in those five causes had on its side that allowed the court to toss the claims against it. If you can prove one of these elements exist when weighing your decision to terminate an employee on FMLA leave, it’s generally safe to say “you’re fired”:

  • employee failed to comply with a direct and legitimate order from supervisors
  • there was overwhelming evidence of performance issues that predated the leave
  • employee had repeatedly been tardy and was non-compliant with absence policy on the date she was terminated
  • employee, prior to leave, had been tardy, absent from her desk, failed to timely pay invoices or update list of services received from vendors, and
  • evidence was unequivocal that the reduction-in-force decision had already been made before the employee took FMLA leave.

The court of appeals cited these while issuing its ruling in an FMLA interference and retaliation lawsuit brought against Tulsa Winch Inc. (TWI).

Fired after returning from leave

Paul Janczak was the general manager of Canadian operations for TWI when he took FMLA leave to recover from an auto accident.

Immediately upon his return from FMLA leave, Janczak was fired. He then filed an FMLA interference and retaliation suit.

The company tried to get his lawsuit thrown out claiming it was considering a reorganization of its management structure and eliminating Janczak’s general manager position prior to his taking leave.

As the court documents indicate, it does indeed appear as though the company had started evaluating whether or not to eliminate Janczak’s position prior to his leave.

But here’s where TWI’s case fell apart: The decision to eliminate the general manager position hadn’t yet been made prior to Janczak’s leave — thus leaving room for doubt as to whether or not his need for leave actually factored into the final decision to eliminate the position.

As a result, the court said Janczak’s interference claim should proceed to trial, where TWI faces either a costly court battle or settlement.

The court said in order for it to dismiss Janczak’s interference claims before a trial, TWI had to show that his termination would’ve definitely occurred regardless of his leave.

Takeaway: Don’t evaluate whether or not someone should be eliminated while he or she’s on FMLA leave. That’s a decision that must be made prior to the person’s leave — or well after, to enable enough time to pass for the resulting termination not to appear linked to the person’s FMLA leave in any way.

The retaliation claims?

Janczak’s retaliation claim, however, didn’t survive. Why?

The court noted that, typically, retaliation occurs after an employee has been restored to his or her position only to suffer an adverse employment action after that fact.

But in Janczak’s case, he was never restored to his prior position; therefore his claims fell under the interference theory.

Another ADA checklist: The common interactive process pitfalls

The reasonable accommodation process “can be tricky,” she says in a masterpiece of understatement, and mistakes are easy to make. Some of the most common:

Not recognizing an accommodation request was made. Sounds outrageous, but think about it: Managers don’t always pick up on what employees say, and employees don’t always express themselves clearly. “A best practice is to have a policy that requires employees to consult with your human resources department – rather than supervisors – if they need an accommodation,” says Gemelli.  “By doing so, companies limit the amount of confidential information being reported to supervisors.”

Asking for too much medical information. Federal and state law limit how deeply employers can dive into employees’ medical files. The guideline: Ask only for information that directly relates to the employee’s limitations in performing the essential duties of his/her job.

Denying an accommodation request because the employee did not provide a solution. Even if the employee can’t define what he or she is seeking, the employer is still required to go through the interactive process. It’s entirely possible a reasonable answer might be found during the process.

Ending the accommodation dialogue because you can’t find a reasonable accommodation that would allow the employee to perform the job’s essential functions. “If an employee cannot perform the essential functions of the job, the employer should see if other accommodations can be made such as reassigning the employee to an open position, allowing the employee to work part time or providing the employee with an unpaid leave of absence,” says Gemelli.

Invoking the “we’ve never done things that way before” defense. No way that flies in court. A reasonable accommodation is a reasonable accommodation, no matter what company history says.

Failing to document the process. You saw this one coming, right? As the saying goes, “No paperwork, no defense.”

Stretching the “undue hardship” parameters. It’s important to remember, Gemelli says, that cost alone rarely qualifies as an undue hardship on an employer.