Search
The Employer Handbook Blog
He Complained. He Got Fired Six Days Later. The Employer Still Won. Here’s How.
The termination decision-maker didn’t know about the complaint. That gap cost the employee everything.
TL;DR: A security supervisor reported his manager for favoring female employees, then got fired days later over training failures and performance issues. The Tenth Circuit affirmed summary judgment for the employer because the employee couldn’t show the branch manager who fired him knew about the sex discrimination complaint, and without that knowledge, there was no causal link to support a retaliation claim.
The Complaint That Never Made It Up the Chain
The employee worked as a day-shift supervisor for a contract security company at an Oklahoma industrial facility. In early 2020, while the site manager was on leave, the employee told the branch manager and a client representative that the site manager gave preferential treatment to female employees.
Months later, a different employee filed a racial discrimination complaint against the site manager. During the investigation, the employee met with the HR vice president on June 10 and flagged his sex discrimination concerns again. The HR vice president told neither the site manager nor the branch manager what was said.
Simultaneously, the site manager and the employee clashed over mask compliance, COVID exposure protocols, and temperature-check training. The branch manager decided to fire the employee on June 16, citing training failures, performance problems, a client’s request for removal, and a missed Saturday training session. The Tenth Circuit affirmed summary judgment for the employer.
Knowledge Gap Breaks the Causal Chain
The branch manager was the undisputed decision-maker. He had no knowledge of the June 10 sex discrimination report. The HR vice president never told him. The employee never told him. No one did.
The employee tried two paths. First, direct retaliation: he argued the branch manager knew because the site manager probably told him. But evidence that two people were in “regular communication” about the employee’s performance doesn’t show they discussed the protected activity. Opportunity to share information, the Tenth Circuit held, is not a substitute for evidence that it was shared.
Second, he tried a cat’s paw theory, arguing the site manager harbored retaliatory animus and used the branch manager to get him fired. That failed too: the site manager had to know about the June 10 report for his motive to be retaliatory. No evidence.
The employee also raised pretext, arguing the termination reasons were fabricated. Without first establishing that the decision-maker knew about the complaint, pretext evidence doesn’t rescue the claim. Pretext might show the stated reason was false; it doesn’t show retaliation was the real reason.
Employers facing retaliation claims often spend their energy defending whether the termination reasons were legitimate. This case is a useful corrective: examine the knowledge element first, because without it, the pretext analysis never gets off the ground.
What Employers Should Bear in Mind
Compartmentalization during HR investigations creates a real evidentiary defense, but it cuts both ways
When HR keeps complaint disclosures internal and decision-makers remain unaware of protected activity, that separation can be outcome-determinative, as it was here. But compartmentalization isn’t always feasible; decision-makers often need to know about complaints to manage workflow and monitor for retaliation. The more useful lesson is documentation: record who was told what and when, so the employer can reconstruct the information chain if litigation follows.
Pre-existing documentation of performance problems is the cleanest defense available
Three of the five reasons cited for the firing predated the June 10 complaint: the mask incident, the COVID exposure reporting failure, and the ongoing training deficiencies. Those pre-existing issues are what made the termination defensible. Performance concerns documented before protected activity puts employers in a fundamentally stronger position than documentation assembled after the fact.
Cat’s paw liability depends on what the biased subordinate actually knew
A supervisor can try to get an employee fired for all kinds of reasons without triggering retaliation liability, as long as the supervisor wasn’t aware of the protected activity. A hostile relationship, even a fabricated termination reason, doesn’t prove the motive was retaliatory unless the connection to the protected activity is established. Personal animus and retaliatory animus are not the same thing.
Retaliation claims live and die on what the decision-maker knew. Everything else, the timing, the pretext, the subordinate’s bad motives, is noise without that foundation. Employers who understand that tend to build better records before terminations happen, not after.