Can I Fire an Employee for Poor Performance?
Yes, you can generally fire an employee for poor performance when the reason is legitimate. But before you make the decision, make sure you can clearly explain what the employee failed to do, what you expected instead, how you communicated those expectations and why termination is the appropriate next step.
Poor performance can support a legitimate employment decision. But “they just aren't working out” becomes much harder to defend when the employee's file tells a different story—or no story at all.
Before you terminate, slow the decision down long enough to answer a more useful question:
Are we ready to terminate this employee for poor performance?
Those are not the same question.
Poor Performance Is a Reason—But Make Sure You Can Explain It
Managers often know when an employee isn't performing.
The problem comes when they cannot explain how the employee isn't performing.
Consider the difference:
“Jordan isn't meeting expectations.”
versus:
“Jordan's position requires weekly client reports by Friday at 3:00 p.m. During the last six weeks, Jordan submitted four reports late and two contained errors that required another employee to correct them. We discussed the requirement on September 8 and again on September 22.”
The second statement gives you something you can evaluate.
Before moving toward termination, define the performance problem as specifically as possible.
Ask:
What does the job require?
What expectation isn't being met?
How do we know?
How often has the problem occurred?
What impact is it having?
Did the employee know what we expected?
What have we already done about it?
If you cannot answer those questions, you may have a management problem hiding inside a performance problem.
Before You Fire an Employee for Poor Performance, Ask These Five Questions
1. Did We Clearly Define the Expectation?
You cannot fairly evaluate an employee against an expectation they never understood.
That doesn't mean every performance standard must appear in a 12-page job description or formal performance improvement plan.
But the employee should reasonably understand what successful performance looks like.
Look at:
the job description;
productivity or quality standards;
deadlines;
attendance or scheduling requirements;
customer-service expectations;
manager instructions;
previous performance reviews;
written goals;
policies; and
other expectations communicated to the employee.
Then ask:
Would a reasonable employee in this position know what we expected?
Don't Confuse “I Told Them” With “I Made the Expectation Clear”
A manager may say:
“We've talked about this several times.”
That tells HR very little.
What did you discuss?
When?
What did you tell the employee needed to change?
Did you explain what acceptable performance looked like?
Did you give a timeframe?
Did the employee understand that the issue was serious?
Did anything improve afterward?
Sometimes the manager has been frustrated for six months while the employee thinks they've received six months of coaching.
Those are very different realities.
2. Did We Tell the Employee There Was a Problem?
This is one of the first places I look when reviewing a proposed termination.
I ask:
“What does the employee know?”
Not:
“What does the manager know?”
A manager may have months of notes about missed deadlines, customer complaints or errors.
But if no one discussed those concerns with the employee, the termination may feel sudden even when the manager has been thinking about it for months.
That does not automatically make the termination unlawful.
It does tell us something important about the process.
The Employee Shouldn't Learn the Entire Performance History at the Termination Meeting
When possible, address performance problems while the employee still has an opportunity to correct them.
A useful performance conversation should tell the employee:
What isn't working.
What needs to change.
What acceptable performance looks like.
When you expect improvement.
What may happen if the performance does not improve.
That doesn't require threatening the employee.
It requires clarity.
A Manager Can Say:
“I want to be clear about the concern. We need the weekly client report completed accurately by 3:00 p.m. every Friday. You've missed that deadline four times during the last six weeks, and two reports required corrections. Going forward, I need you to meet the Friday deadline and submit the report accurately. We'll review your progress over the next 30 days. If your performance doesn't improve, we may need to take additional corrective action, up to and including termination.”
The employee now knows where they stand.
That is much more useful than:
“You really need to step it up.”
3. Does Our Documentation Match the Decision We're About to Make?
Before terminating someone for poor performance, read the employee's file as though you know nothing about the situation.
What story does it tell?
Suppose the manager says:
“This employee has been a performance problem for a year.”
But the employee's most recent review says:
“Meets expectations.”
There are no written warnings.
No documented coaching.
No missed-goal records.
And three months ago, the employee received a merit increase.
That does not necessarily mean you cannot terminate the employee.
It means you need to understand the disconnect before you do.
Don't Manufacture Documentation at the End
One of the worst times to start documenting a performance problem is the day you decide to terminate someone.
Document performance issues when they happen.
Good documentation should help someone understand:
what happened;
when it happened;
what expectation applied;
what the manager discussed with the employee;
how the employee responded;
what improvement you expected;
what timeframe you provided; and
what happened afterward.
Documentation should preserve facts—not create a case against someone.
The “Six-Month File Test”
Before approving the termination, imagine someone opens this employee's file six months from now.
They know nothing about the employee.
Could they understand:
What wasn't working?
How did the employee know?
What opportunity did the employee have to improve?
What happened after that?
Why did the company ultimately choose termination?
If the file cannot answer those questions, determine what is missing before you act.
4. Have We Handled Similar Performance Problems Consistently?
Consistency does not mean every employee must receive exactly the same outcome.
Circumstances differ.
An employee with three prior warnings may reasonably receive a different consequence than someone experiencing the problem for the first time.
A senior employee may have responsibilities that differ from an entry-level employee.
The seriousness or impact of the performance problem may also differ.
The important question is:
Can we explain the difference?
Before terminating, ask:
Have other employees had similar performance problems?
How did we handle those situations?
If we handled this employee differently, why?
Does the difference make sense based on legitimate business factors?
Did we follow our own policy or normal practice?
If we deviated from it, can we explain why?
Federal anti-discrimination laws prohibit employers from basing discipline or termination decisions on protected characteristics, and inconsistent treatment can become important when employees compare how the company handled similar situations.
Don't Compare Employees by Outcome Alone
Two employees may both miss deadlines without being similarly situated.
One may have missed one deadline.
The other may have missed eight after repeated coaching.
One delay may have caused little disruption.
The other may have cost the company a major client.
So don't ask only:
“Have we ever let someone else do this?”
Ask:
“Are these situations actually comparable, and if we treated them differently, can we explain why?”
That is a much stronger consistency check.
5. Is There Anything About the Timing or Circumstances That Should Make Us Stop and Review?
This is the question that can prevent an employer from turning a legitimate performance decision into a much more complicated problem.
Before terminating, ask whether anything else has happened recently.
For example, has the employee:
complained about discrimination or harassment;
participated in a workplace investigation;
requested a disability accommodation;
disclosed a medical condition in connection with the performance issue;
requested or taken protected leave;
raised a wage or overtime concern;
reported a safety concern;
raised another potentially protected workplace issue;
recently returned from leave; or
experienced another situation that may carry legal protections?
The presence of one of these circumstances does not automatically prevent termination.
An employee does not receive permanent protection from legitimate performance consequences simply because they engaged in protected activity. EEOC guidance specifically recognizes that employers may still discipline or terminate employees for legitimate, non-discriminatory and non-retaliatory reasons.
But the circumstances may change what you need to review before making the decision.
Timing Matters
Imagine this sequence:
January: Manager says employee is performing well.
February 5: Employee files a harassment complaint.
February 12: Manager begins documenting serious performance problems.
February 28: Manager recommends termination.
Maybe the performance problems are completely legitimate.
But you should understand why the documentation changed so dramatically immediately after the complaint.
Now compare that with:
October: Manager documents missed deadlines.
November: Employee receives written coaching.
December: Employee receives a performance warning.
January: Performance remains below expectations.
February: Employee files a complaint.
March: Performance problems continue and the manager recommends termination.
The employee's complaint still matters.
But the existing timeline gives you much more information about the employer's reason for the decision.
A timeline can be one of the most useful tools in a termination review.
What If the Employee Says a Medical Condition Is Affecting Their Performance?
Don't diagnose the employee.
Don't assume the employee has a disability.
And don't automatically abandon legitimate performance expectations.
Instead, listen carefully to what the employee is telling you.
Under the ADA, employers may generally hold employees with disabilities to the same job-related performance standards as other employees. A reasonable accommodation does not ordinarily require an employer to erase poor performance that already occurred. However, when an employee requests an accommodation that may help them perform the job going forward, the employer may need to address that request rather than simply dismissing it because performance problems already exist.
For example, an employee says:
“I'm missing these deadlines because of a medical condition, and I need a change to my schedule.”
That statement deserves a different response than:
“I'm just not good at meeting deadlines.”
The performance expectation may remain.
But the employer may now need to determine whether the employee's statement may amount to a request for accommodation and whether a reasonable accommodation could help the employee meet that expectation.
A Manager Should Not Say:
“If you couldn't do the job because of your medical condition, you should have told us sooner.”
Instead, pause and determine whether the employee may be requesting workplace accommodation.
This is one of those moments where the performance conversation may need to become an HR conversation.
What If the Employee Recently Took Leave?
Look carefully at what you're counting as poor performance.
If an eligible employee used protected FMLA leave, an employer cannot count that leave against the employee when making disciplinary decisions or use the employee's use of FMLA leave as a negative factor in an employment decision.
That does not mean an employee returning from protected leave receives immunity from legitimate performance expectations.
It means you should separate:
performance problems that actually belong to the employee
from
consequences caused by protected leave.
State and local leave laws may provide additional protections, so employers should also determine which leave requirements apply where the employee works.
For example, ask:
Are we criticizing the employee for work they could not complete because they were on protected leave?
Did deadlines change while they were absent?
Are attendance points improperly including protected absences?
Did the performance problem exist before the leave?
Do we have documentation showing that?
Are we evaluating the employee based on the time they actually worked?
Those questions help keep the decision focused on legitimate performance.
Do I Have to Put the Employee on a Performance Improvement Plan First?
Not necessarily.
There is no universal federal rule requiring every employer to put every poorly performing employee on a formal Performance Improvement Plan before termination.
But that doesn't mean you should automatically skip the opportunity to improve.
Ask what makes sense based on:
your policies;
your past practices;
the employee's position;
the seriousness of the problem;
how long the problem has existed;
previous coaching or discipline;
whether the employee can realistically correct it; and
how you've handled comparable employees.
A PIP should serve a purpose.
It should not become paperwork you create simply so you can say:
“We put them on a PIP.”
A Good PIP Answers Four Questions
What's wrong?
What does acceptable performance look like?
What needs to happen during the improvement period?
What happens if performance doesn't improve?
If your PIP cannot answer those questions clearly, adding more pages will not make it better.
Does “At-Will Employment” Mean I Can Just Fire Them?
This phrase causes a lot of confusion.
Employers sometimes interpret at-will employment as:
“We don't need a reason.”
That is not the safest way to think about it.
At-will employment generally means either the employer or employee may end the employment relationship, subject to applicable law and any contractual limitations. It does not give an employer permission to terminate someone for an unlawful reason. Federal, state or local protections may still apply.
And from a practical HR perspective, even when you may have the legal ability to terminate without progressive discipline, you should still know:
Why are we making this decision?
If the answer is poor performance, you should be able to explain the poor performance.
“At will” should not replace good decision-making.
Do I Need Three Write-Ups Before I Can Fire Someone?
This is another common HR myth.
There is no universal federal “three write-ups” rule for poor-performance termination.
Your own policies, employment agreements, collective bargaining obligations, state or local requirements, and past practices may affect the process you should follow.
But HR should not turn discipline into a punch card:
Warning 1. Warning 2. Warning 3. Termination.
The number of warnings matters less than whether the company handled the situation fairly, consistently and in accordance with its obligations and policies.
Sometimes an employee needs additional coaching.
Sometimes a formal warning makes sense.
Sometimes a PIP makes sense.
Sometimes the facts support moving directly to termination.
The circumstances determine the appropriate response.
What Should the Termination Conversation Sound Like?
If you've made the decision, the termination meeting is usually not the time to retry the entire performance case.
Be clear.
Be respectful.
Be concise.
A manager might say:
“We've discussed the performance expectations for your position and the areas that needed to improve. Unfortunately, the required improvement has not occurred, and we've made the decision to end your employment effective today. I know this is difficult news. I'm going to explain what happens next regarding your final pay, benefits and company property, and I'll answer the questions I can about that process.”
Then move into the logistics.
Avoid:
arguing;
introducing brand-new performance complaints;
exaggerating;
debating every past incident;
blaming other leaders;
saying the decision “wasn't my choice” when it was a company decision;
making promises about unemployment benefits; or
improvising explanations that differ from the documented reason.
The reason communicated in the termination meeting should align with the reason the company actually made the decision.
When Should You Pause Before Terminating?
You don't need outside HR or legal counsel before every performance termination.
But consider pausing when:
the documentation does not match the manager's description;
the employee recently complained about discrimination, harassment or another protected issue;
the employee requested or used protected leave;
the employee raised a medical condition or accommodation request;
managers treated comparable employees differently;
the manager wants to skip the company's normal process;
the employee works in a state with requirements you're unsure about;
the employee has an employment agreement or other contractual protection;
the termination involves a senior leader or sensitive position;
the reason for termination keeps changing;
the manager says, “I just want them gone” but cannot clearly explain why; or
something about the timing simply doesn't feel right.
Pausing does not mean you cannot terminate.
It means you want to make the decision with the full picture in front of you.
Sometimes a short review confirms:
Yes. The performance issues are legitimate, the documentation supports them, we've treated the employee consistently and termination is appropriate.
That's valuable.
Other times, the review reveals something you should address before ending employment.
That's valuable too.
The Bottom Line
Yes, you can generally terminate an employee for legitimate poor performance.
But before you do, run the decision through five questions:
Did we clearly define the expectation?
Did we tell the employee there was a problem?
Does our documentation support what we're saying?
Have we handled comparable situations consistently?
Is there anything about the timing or circumstances that requires another look?
If those answers line up, you are in a much stronger position to make a thoughtful employment decision.
If they don't, don't use the termination meeting to discover what's missing.
Find out first.
And if you're looking at the file thinking:
“I think we need to terminate this employee, but I want someone else to look at this before we do,”
that's exactly the kind of situation where experienced HR review can help.
The HR Remedy can help you review the documentation, identify potential issues, determine the appropriate next step and prepare for the conversation before you make the final decision.
Important Note
HR Answers provides general educational information and is not legal advice. Employment laws and requirements can vary by jurisdiction and individual circumstances. When appropriate, consult qualified HR or legal counsel regarding your specific situation.
