Managing an Employee Out: Warning Signs and Legal Risk

Some exits are engineered. A manager decides an employee should go, but instead of documenting a performance problem or making a case for termination, they start adjusting conditions. Assignments get worse. Meeting invites stop arriving. Feedback goes quiet, then cold.

Nobody says the word "fired." The employee just eventually leaves, and the manager treats that as a clean outcome.

It is not clean. Managing someone out is one of the highest-risk patterns in employee relations, and it usually reaches HR late, in a form that looks like a routine performance conversation. This guide covers how to recognize the pattern, what the law actually says about it, how to intervene without burning your relationship with the manager, and how to build the record that protects your organization if the employee resigns and calls a lawyer.

What does it mean to manage an employee out?

Managing an employee out means changing the conditions of someone's job so that quitting becomes their most reasonable option, rather than addressing performance directly or making a termination decision. The employee is never told to leave. The environment is adjusted until leaving feels inevitable.

The practice goes by several names, and the distinctions matter because they carry different legal weight.

Quiet firing, managed out, and constructive discharge

These three terms get used interchangeably in HR conversations, but they describe different things.

Quiet firing is the informal term for the behavior pattern. It came into wide use after 2022 as the counterpart to quiet quitting, and it describes managers who withdraw support, opportunity, and communication instead of managing performance.

Managing someone out is the intent behind it. A decision has been made, but nobody has documented it or delivered it.

Constructive discharge, sometimes called constructive dismissal, is the legal claim. It is what an employee alleges when they resign and argue the resignation should be treated as a firing because conditions were made unbearable. That is the version that ends up in front of a jury.

One important note on how common this is. In a 2025 ResumeTemplates survey of more than 1,100 business leaders, 53% of US businesses said they were using quiet-firing tactics, including delaying raises, cutting benefits, and adding in-office requirements. On the employee side, Zety's 2025 Layoff Lifeline Report found that 73% of 1,000 US workers surveyed believed they had experienced tactics meant to push them out, with heavier workloads and micromanagement cited most often.

This is not a fringe behavior. It is a mainstream management default, and most of the people doing it do not think of it as a legal event.

What managing someone out actually looks like day to day

The tactics are rarely dramatic. That is what makes them hard to catch and easy to defend as ordinary business decisions.

• Reassigning someone to lower-visibility or dead-end work without explanation
• Removing them from meetings, accounts, or projects they previously owned
• Raising performance targets to a level nobody on the team is hitting
• Withholding information they need, then criticizing the resulting mistakes
• Going silent on feedback, then producing a negative review with no prior documentation
• Denying schedule flexibility that peers receive
• Changing shifts, territory, or reporting lines in ways the employee did not ask for
• Telling other leaders the employee has "checked out" before anyone has asked them what changed

A 2022 Harvard Business Review analysis of 1,000 US workers identified unreasonable performance targets and unfair evaluation as two of the most commonly reported quiet-firing signals. Both look like performance management on paper. Both read very differently once a plaintiff's attorney lines them up on a timeline.

Why managers do this instead of having the conversation

Most managers who push people out are not being strategic. They are avoiding discomfort.

Delivering hard feedback is a learned skill, and plenty of otherwise strong operators never learned it. A manager who is excellent at running a site, hitting numbers, or shipping product may have no framework for saying "your work has changed and I need to understand why." So they do the thing that requires no conversation at all.

There is also a paperwork motive. Some managers know that a termination requires documentation they never created, so they engineer a resignation instead. A resignation appears to need no justification.

That instinct is exactly backwards. A resignation you engineered is harder to defend than a termination you documented.

Why managing an employee out is a legal risk

Managing someone out exposes your organization to constructive discharge, retaliation, discrimination, and leave-interference claims, even though no termination ever occurred. The absence of a formal action is not a defense. Courts look at what changed, when it changed, and why.

The financial exposure is real even when you win. Hiscox's Guide to Employee Lawsuits reported an average of $160,000 in combined defense and settlement costs for claims that resulted in payment, with an average of 318 days to resolve. A claim that never becomes a verdict still consumes a year of legal spend and leadership attention.

The constructive discharge standard courts actually apply

The Supreme Court set the framework in Pennsylvania State Police v. Suders (2004). An employee who resigns can pursue a Title VII claim if working conditions became, in the Court's words, "so intolerable that a reasonable person" in their position would have felt compelled to quit.

Two features of that test matter enormously for HR.

First, the test is objective, not subjective. The question is not whether this particular employee found the conditions unbearable. It is whether a reasonable person in the same role would have. That means your defense does not rest on the employee being unusually sensitive, and it does not rest on the manager's intent being benign.

Second, the bar is high but cumulative. A single unpleasant assignment will not clear it. A six-month pattern of demotion-in-effect, exclusion, and unexplained schedule changes can, particularly when the record shows the employer knew and did nothing.

Courts weigh how severe the conditions were, how long they lasted, whether the employee reported the problem internally before resigning, whether the employer fixed it after being told, and whether the resignation followed within a reasonable window.

That fourth factor is where HR sits. If an employee raised concerns and your file shows no response, the claim gets substantially stronger.

The filing clock starts later than most employers assume

In Green v. Brennan (2016), the Supreme Court held that the limitations clock for a constructive discharge claim begins when the employee gives notice of resignation, not on the date of the employer's last problematic act.

The practical effect is that conduct from many months earlier stays live. A manager who spent nine months making someone's job miserable does not age out of exposure simply because the worst of it happened early. The clock waits for the resignation letter.

For HR, that changes how long you need to retain and be able to reconstruct the record. A departure that felt resolved in March can surface as a charge in the fall, and the file you need is the one covering the whole preceding year.

When the conduct crosses into retaliation

Retaliation is the most-filed charge category at the EEOC and has been for nearly two decades. In fiscal year 2024, the agency received 88,531 total charges, and 42,301 of them included a retaliation allegation, which is 47.8% of all filings and the seventeenth consecutive year retaliation led the list.

The retaliation standard is different from the discrimination standard. Under Burlington Northern & Santa Fe Railway v. White (2006), an employee must show a materially adverse action, meaning something significant enough to dissuade a reasonable worker from making or supporting a complaint. Withdrawn assignments, exclusion from meetings, and schedule changes have all cleared that bar in various circuits when they followed protected activity.

The sequence is what kills you. If an employee complained about harassment, requested leave, raised a safety issue, or reported a policy violation, and their assignments deteriorated afterward, the timeline does most of the plaintiff's work. Intent becomes almost secondary.

Our breakdown of retaliation in the workplace walks through the specific fact patterns that draw claims.

What Muldrow changed, and what it did not

In April 2024, the Supreme Court decided Muldrow v. City of St. Louis unanimously, holding that a Title VII discrimination plaintiff challenging a job transfer needs to show only "some harm" to an identifiable term or condition of employment. The prior standard in most circuits required harm that was material or significant.

This matters directly to managing-out behavior, because the classic tactics are exactly the kind of lateral, no-pay-change moves that used to get dismissed as too trivial to sue over. A transfer to a worse territory at identical pay is now much harder to wave away.

One accuracy note that most HR commentary gets wrong. Courts have largely declined to extend Muldrow's lower standard to retaliation claims and to constructive discharge claims, which keep their own tests. So Muldrow did not lower the constructive discharge bar. What it did was make the individual steps along the way easier to challenge as discrimination if a protected characteristic is in the mix.

The operational takeaway from Muldrow is documentation. Employers now need a defensible reason on file for changes in duties, assignments, shifts, and reporting lines, not just for pay and title.

The protected situation hiding behind the silence

The most dangerous version of this pattern is the one where a manager acts on an assumption about why performance changed, and the real reason is legally protected.

An employee who goes quiet may be managing a serious illness, caring for a parent or child, navigating a mental health condition, or dealing with harassment they have not reported yet. They often stay silent for the same reason in every case: they do not want to be seen as a liability.

Several protections can attach the moment those facts surface.

• FMLA. Eligible employees at covered employers get up to 12 workweeks of unpaid, job-protected leave for a serious health condition affecting them or an immediate family member. Interfering with that right, or retaliating against someone for using it, is itself a violation.
• ADA. An employee with a qualifying condition may be entitled to reasonable accommodation. The ADA's association provision separately prohibits adverse action against someone because of their known relationship with a person with a disability.
• Caregiver-related discrimination. EEOC guidance issued in 2022 is specific and useful here. Federal law generally does not require accommodation for caregiving itself, and it does not require you to excuse performance that falls short. But taking adverse action against a caregiver based on an assumption that they will not have enough time to do the job can be unlawful. Assumption is the operative word.

Read that last point carefully, because it describes the exact scenario HR sees most often. A manager decides the employee cannot handle the job anymore, never asks, and starts reallocating work. That is not a performance decision. That is a decision based on a stereotype about a protected status, and it is the kind of fact pattern the EEOC's guidance was written to address.

How to tell real underperformance from a manager problem

Compare the documentation to the timeline. Legitimate performance management leaves a paper trail that starts before the consequences. Managing someone out produces consequences first and paperwork later, usually after HR starts asking questions.

When a manager brings you a performance concern about a previously solid employee, the first job is not to accept the narrative or reject it. It is to test it.

Questions to ask the manager before you accept the story

Ask these in order, and listen for what is missing rather than what is offered.

1. When did the change start, specifically? A manager who can name a month but not a triggering event has been reacting to a vibe, not a metric.
2. What is the measurable gap? "Attitude," "engagement," and "not a culture fit" are not performance data. Missed deadlines, error rates, and quota shortfalls are.
3. Have you told the employee directly? If the answer is no, everything that follows is not underperformance. It is an unaddressed change.
4. What did they say when you asked what was going on? If the manager never asked, that is your finding.
5. What have you changed about how you manage them? This is the question that surfaces the reassignments and the exclusion.
6. Who else have you discussed this with? This tells you how far the informal narrative has traveled before you got involved.
7. What is documented, and when was it written? Contemporaneous notes and notes written last Tuesday about events from March are different artifacts.

The gap between question three and question five is where most managed-out cases live. A manager who has changed the job substantially but never had one direct conversation has already created the risk.

Documentation red flags

Certain patterns in a file should stop you cold.

• Performance concerns that appear in writing only after the employee complained, requested leave, or disclosed a condition
• A negative review that contradicts every prior review with no documented intervening conversation
• Notes created in a single sitting that describe events across several months
• A performance improvement plan with targets nobody else on the team is meeting
• Metrics applied to one employee that are not tracked for peers in the same role
• Emails documenting the decision to remove work, with no email documenting a conversation about why

None of these is dispositive on its own. Two or more together mean you are looking at a constructed record rather than a contemporaneous one.

The accommodation consistency problem

Here is the trap that catches even careful HR teams. You supported one employee generously through a medical crisis, letting them work remotely for months. A second employee asks for the same arrangement for a routine recovery, and you say no because the circumstances are not comparable.

You may be entirely right on the merits. But if the file does not explain the reasoning, the difference looks like favoritism, and favoritism is the raw material of a discrimination claim.

Document the reasoning, not just the outcome. What was requested, what was granted, what was denied, and the specific factors that produced different answers. Consistency is not treating every request identically. It is applying the same framework and being able to show your work.

How HR should respond when a manager is pushing someone out

Talk to the employee first, ask permission before sharing anything, then address the manager's behavior as its own issue separate from the performance question. Sequence matters more than speed here.

Both orders carry risk. Go to the manager first and you may accelerate the harm while tipping off the person creating it. Go to the employee first and the manager may feel undermined. The employee-first order is still correct, because the employee is the one currently absorbing damage and the one whose trust you cannot rebuild if you spend it.

How to open the conversation with the employee

Lead with concern and give them control over how much they disclose. You are not investigating them.

A version that works:

"I wanted to check in with you. I've noticed some changes in how things have been going, and before anyone draws conclusions I wanted to hear from you directly. You do not have to tell me anything you are not comfortable telling me. If something is going on that is affecting work, I would rather know so we can figure out support."

Three things that opener does. It signals the change was noticed by someone other than their manager. It removes the obligation to disclose. It offers support instead of consequence.

Then ask the question that determines everything downstream: "What would you be comfortable with me sharing with your manager?"

That question is not a formality. It keeps the employee in control of their own information, and it gives you a documented basis for what you passed along, which matters if the disclosure later becomes central to a claim.

What you can and cannot promise about confidentiality

Never promise absolute confidentiality before you know what you are about to hear. Some disclosures carry a legal duty to act, and a promise you have to break costs more than a promise you never made.

The honest framing is straightforward. Tell them you will share only what is necessary, with as few people as possible, and that if what they tell you involves harassment, discrimination, or a safety issue, you may be obligated to act on it. Then let them decide how much to say.

Employees handle that framing better than most HR teams expect. What they do not handle well is discovering later that a guarantee was not real.

What to say to the manager

Address the behavior directly, and treat it as a separate matter from the employee's performance. Combining them lets the manager relitigate the performance question instead of answering for their own conduct.

The question to ask is some version of: walk me through why your response to a performance change was to reduce this person's assignments rather than to ask them what was going on.

Then stop talking and listen to the answer. You are sorting for one of three things.

• A skills gap. They did not know how to have the conversation. This is coachable, and most cases land here.
• Avoidance. They knew and did not want the discomfort. Also coachable, with clearer consequences attached.
• Intent. They wanted the person gone and chose a route that avoided documentation. This is a conduct issue, and it belongs in their own file.

The distinction determines whether you are coaching or disciplining. Do not skip the sorting step to get to a faster resolution.

How to handle the narrative that already spread

Make the manager correct the record themselves. Do not do the repair work on their behalf.

By the time this reaches HR, the manager has usually already told peers, skip-levels, or their own leader that the employee has checked out. That story is now shaping how other people read the employee's work, and it will affect their next internal opportunity if nobody unwinds it.

The manager should go back to everyone they spoke with and correct what they said. Not a full disclosure of the employee's private circumstances, which would create a new problem. Something closer to: "I drew a conclusion about this person's performance before I had the full picture, and I was wrong to share it. Please disregard what I said."

Two reasons this has to be the manager and not you. First, a correction from HR reads as HR overriding a manager, which does not repair the employee's standing. Second, the discomfort of saying it out loud is the most durable lesson available. A manager who has to walk that back in front of peers does not do it twice.

Track that the correction happened. If the manager refuses, you no longer have a coaching situation.

What to do instead when a good employee's performance drops

Ask first, document from the beginning, and treat the drop as a change to understand rather than a problem to prove. Nearly every managed-out case would have been avoidable with one honest conversation held early.

The practical sequence looks like this.

1. Notice and name it early. A conversation two weeks after a change is a check-in. The same conversation five months later is a confrontation, because by then the employee knows they have been watched and not asked.
2. Separate the observation from the conclusion. "Your last three reports came in late" is an observation. "You've disengaged" is a conclusion, and stating it as fact closes the conversation before it starts.
3. Ask what changed and what would help. Leave room for the answer to be personal without requiring that it be.
4. Write it down the same day. What you observed, what you said, what they said, what you agreed to. Contemporaneous notes are the only kind with real defensive value.
5. Adjust support before adjusting consequences. Workload, deadlines, coverage, leave, or an accommodation conversation. Try the thing that keeps a good employee first.
6. Set a real check-in date. Two weeks or thirty days, on the calendar, not "let's see how it goes."
7. Escalate formally only when support has genuinely failed. If you reach a performance improvement plan, it should be a real attempt at improvement with achievable targets, not a documentation exercise for a decision already made.

That last point deserves emphasis, because a PIP built as cover is worse than no PIP at all. It creates a written record showing the employer setting targets it did not expect to be met, which is precisely the document a plaintiff wants.

Our guide to addressing poor work performance covers the conversation mechanics in more depth.

How to keep managers from pushing people out

Train managers on the specific conversation they are avoiding, then build enough visibility that HR learns about these situations early rather than at the exit interview. Policy alone will not fix this, because nobody managing someone out believes they are violating a policy.

Manager capability is where intervention pays back the most. Gallup's research has consistently found that managers account for at least 70% of the variance in team-level engagement, a figure from its State of the American Manager report. Gallup's 2026 data adds an uncomfortable detail: manager engagement itself dropped from 30% to 27%, with the steepest declines among managers under 35. Disengaged managers are the ones most likely to avoid hard conversations.

What to actually train on

Skip the general management course. Train the specific skill.

• How to open a conversation about a performance change without accusing
• How to distinguish an observation from a conclusion
• What to do when an employee discloses something personal, including when to loop in HR
• Which requests must be routed to HR immediately, especially anything touching leave, health, or accommodation
• How to document a conversation the same day in a way that would read fairly to a stranger
• Why removing work from someone is an employment decision that requires a reason on file

The last item is where Muldrow lands operationally. Managers need to understand that reassignment is not a neutral act.

Build more than one path for the signal to reach you

If the only way you learn about this pattern is a manager choosing to tell you, you will learn about it after the resignation.

Give employees more than one route. That means a reporting channel that does not run through their manager, exit interviews that ask specifically about changes in assignments and support, engagement or pulse questions that surface manager behavior at the team level, and enough HR presence that people know who to call before things get bad.

Presence is the underrated part. HR teams that are physically or operationally distant from the workforce, which is the norm in retail, hospitality, healthcare, and distributed frontline environments, consistently find out last. An HR function that only appears when something has already broken is structurally guaranteed to see these cases too late.

Audit for the pattern

Look for it deliberately, at least annually. A few queries surface most of it.

• Which managers have the highest voluntary turnover on their teams, adjusted for role and location
• Which resignations followed a documented assignment change, schedule change, or reporting change within 90 days
• Which negative reviews had no documented performance conversation in the preceding quarter
• Which employees resigned within six months of requesting leave or an accommodation
• Where accommodation decisions diverged without documented reasoning

Individually these are noise. Clustered under one manager, they are a finding.

Centralizing this in an employee relations case management system is what makes the pattern visible at all. Cases scattered across email threads, notes apps, and individual managers' memories cannot be queried, which means the manager who has done this four times looks like four unrelated departures.

What this costs when it goes wrong

The EEOC's fiscal year 2025 numbers make the exposure concrete. The agency received more than 91,000 charges and secured $660 million for 17,680 individuals, its third-highest recovery total in recent history. Most of that came through pre-litigation resolution rather than court.

The detail HR should sit with: discharge or constructive discharge was the most commonly asserted issue in the lawsuits the EEOC filed in FY 2025, appearing in 64 cases, ahead of reasonable accommodation at 40 and harassment at 29.

Separation is where employment claims concentrate. And the separations that generate claims are disproportionately the ones nobody documented, because the decision was never formally made.

The cost also lands in places no legal ledger captures. Every person who watched a colleague get eased out learned something about how this organization handles people who hit a rough patch. They will remember it the next time they consider telling their manager that something is going on at home.

That is the real bill. A team that has watched one person get managed out will not tell you anything early ever again.