Can I Fire an Employee for [Performance / Attendance / Attitude] - What Holds Up

Blog Image

A COO pulls the HR leader aside after a rough week. A long-tenured employee has missed targets, arrived late repeatedly, and missed scheduled shifts. The manager wants the employee gone and describes the problem as, "They're just not a fit anymore." The COO asks the question leaders ask every day: Can I fire an employee for performance, attendance, or attitude, and what will hold up?

Good faith isn't enough. A stack of documents isn't automatically evidence. The employee's stated reason won't be accepted at face value just because it appears in a termination letter. The key question is whether the explanation remains credible when someone examines the timeline, the manager's conduct, comparable employees, protected activity, leave, and accommodation issues.

The Call No One Wants to Get Wrong

The first mistake is assuming that sincere frustration makes a termination defensible. A manager may believe an employee is underperforming or disruptive. That belief matters operationally, but it doesn't answer whether the employer can prove a legitimate reason that was applied consistently and wasn't influenced by discrimination or retaliation.

The second mistake is treating documentation as interchangeable with evidence. A late-created summary saying "poor attitude" carries far less weight than dated coaching notes identifying the specific conduct, the expectation, the employee's response, and the business impact. Documentation should show what happened close to the time it happened, not explain the decision after leadership has already chosen termination.

The third mistake is believing that the label controls. Calling a decision “performance-based” won't make it so. Courts and agencies examine the underlying facts, including whether the employee knew the standard, received a meaningful opportunity to improve, and was treated like comparable employees.

Performance, attendance, and attitude look like separate boxes on a management spreadsheet. In practice, they overlap. A missed target may relate to an accommodation request. Absences may include protected leave. “Attitude” may describe a complaint about pay, schedules, safety, or working conditions that receives legal protection.

The working question: Would a neutral reviewer reach the same conclusion after reading the entire chronology, including what happened immediately before the proposed termination?

That is the standard leaders should apply before approving the action. The rest of this article turns that question into a practical decision process.

The Credibility Test Every Termination Has to Pass

A defensible termination usually rests on three connected questions. The employer needs a legitimate reason, consistent treatment, and a record that separates the reason for termination from discrimination or retaliation.

Was the reason legitimate

A legitimate reason is specific enough to verify. “Missed the quarterly revenue target despite documented expectations and coaching” is stronger than “not committed.” “Failed to report for scheduled shifts without required notice” is stronger than “unreliable.” “Refused a lawful assignment after clarification and a prior warning” is stronger than “difficult.”

The reason should connect to the job, the policy, or a business requirement. It should also appear in records created before the termination decision, such as evaluations, coaching notes, written warnings, attendance records, or investigation materials.

Was the rule applied consistently

Consistency doesn't mean every employee receives identical treatment regardless of context. It means the employer can explain why similarly situated employees received comparable consequences, or why a different outcome was justified by a documented distinction.

Review comparable employees before final approval. Look at the same policy, similar conduct, comparable roles, relevant supervisors, and prior discipline. If other employees missed standards or violated attendance rules without termination, the file needs a credible explanation for the difference.

Does the chronology suggest pretext

Timing can change the meaning of otherwise valid records. A termination that follows an accommodation request, leave inquiry, wage complaint, workers' compensation claim, discrimination report, or group workplace complaint requires a pause. The question isn't whether the employee can ever be terminated afterward. The question is whether the employer can show that the concern predated the protected event and that the decision didn't escalate because the employee asserted a right.

The legal framework described in a Supreme Court filing on legitimate employment reasons and pretext focuses on whether the stated reason is legitimate, consistently applied, and unrelated to unlawful discrimination or retaliation. That framework is operational, not theoretical.

For small employers, payroll, leave, and personnel records often sit in different systems. A guide to payroll compliance for small businesses can help establish stronger recordkeeping habits, but HR should still build a decision-specific file before termination.

A diagram titled The Credibility Test outlining three essential questions for fair employee termination procedures.

Performance Terminations That Survive Review

Performance termination is often the most defensible category, but only when the employer measures performance instead of documenting impressions. A strong file answers five questions: What was expected? When was it communicated? What did the employee miss? What support or warning followed? How did the employee respond?

Replace impressions with proof

Measurable expectations can include deadlines, quality standards, client deliverables, production requirements, response obligations, or defined responsibilities in the job description. The standard doesn't need to be mathematical, but a neutral reader should understand how the employee fell short.

Useful records usually include:

  • Dated observations: Identify the meeting, assignment, deadline, or incident.
  • Specific missed standards: State what the employee was expected to do and what occurred.
  • Employee response: Record the explanation, disagreement, mitigating information, or commitment to improve.
  • Business impact: Explain the client delay, rework, missed deliverable, operational disruption, or other consequence.
  • Improvement steps: Show coaching, warnings, follow-up meetings, deadlines, and the result.

A manager's note that says “poor performer” is a conclusion. A note stating that a required client deliverable was late, the expectation had been communicated, the employee cited competing priorities, and the revised deadline was also missed gives a reviewer something to evaluate.

Treat the PIP as a real process

A performance improvement plan should give the employee a genuine opportunity to understand and meet the standard. Vague goals, impossible deadlines, and a plan created only to create a termination exhibit can weaken the employer's position. Use clear outcomes, realistic review points, examples of acceptable performance, and written follow-up.

Review your process against these PIP legal pitfalls to avoid, particularly if the manager already expects the employee to fail.

Weak performance-management processes can create the “attitude problem” organizations later try to document. In a Deloitte survey of nearly 10,000 leaders and HR professionals across 93 countries, 61% of managers and 72% of workers said they didn't trust their organization's performance-management process, while only 32% of executives said the approach enabled timely, high-quality decisions about high and low performers (Deloitte).

A manager discusses a performance review document with an employee during a professional business meeting.

Before final approval, ask someone outside the reporting chain to read the file. An independent HR or legal review can identify subjective language, missing employee responses, contradictory evaluations, or a timeline that changes after the employee raises a concern.

Attendance Decisions After the Protected-Absence Filter

Attendance discipline fails when leaders count misses before they classify them. A stack of absences means nothing until you sort each one by reason, notice, and legal protection.

The Bureau of Labor Statistics defines absence broadly. It includes a full-time worker who usually works at least 35 hours but works fewer than 35 hours during the reference week because of illness, injury, medical problems, child-care or family obligations, civic or military duty, or maternity or paternity leave. In 1998, the BLS reported that approximately 4.0% of full-time workers were absent during an average workweek, with a rate of 5.1% for women and 2.7% for men. That figure is a baseline for how broadly the agency treats "absence," not a current benchmark (BLS). The key issue is that a raw count blends legally different events.

Build the absence ledger

For each event tied to termination, record the date, scheduled shift, notice given, stated reason, approval status, policy category, decision-maker, and business impact. Separate unexcused no-shows and repeated tardiness from approved leave, disability-related absences, pregnancy-related limitations, military or civic obligations, workers' compensation issues, and potentially protected family or medical leave. For tardiness and no-show patterns, apply the classification rules in Paradigm International's HR guidance before any point-based discharge.

A point total may still look clean on paper and fail in review. If several absences followed a medical event and the employee told a supervisor about treatment, pause the process. Correct the ledger, test for leave or accommodation obligations, and recalculate using only unprotected events. That chronology matters, because decision-makers often create their own problem by pressing ahead after they learn facts that change the analysis.

The same rule applies when an employee misses an internal call-in step. The Department of Labor explains that failing to follow usual procedures does not automatically let an employer deny or delay potentially qualifying FMLA leave when the employee gave timely verbal or other notice (Department of Labor FMLA guidance).

Attendance rule: Do not count protected leave as misconduct, and do not let a point system hide the reason for termination.

The Department of Labor also states that FMLA leave may not be used as a negative factor in discipline or termination and may not be counted under a no-fault attendance policy (Department of Labor). State and local sick-time, leave, disability-accommodation, and retaliation rules may add more layers, especially for multi-state employers.

A five-step Attendance Termination Checklist diagram for employers to ensure legal compliance when managing staff absences.

Attitude Is a Conduct Question, Not a Personality Question

“Bad attitude” is one of the weakest termination explanations an employer can use. It usually describes a manager's reaction rather than an employee's verifiable conduct. Labels such as negative, difficult, disengaged, or not a culture fit can conceal inconsistent standards, disability-related issues, bias, or protected workplace advocacy.

Translate the label into behavior. A usable conduct record might state that the employee refused a lawful assignment after the supervisor clarified the instruction, directed abusive personal remarks at a coworker, or repeatedly disrupted client work after documented coaching. The record should identify the date, expectation, witnesses, messages, employee response, and business impact.

Separate misconduct from protected advocacy

An employee who raises concerns about pay, hours, safety, schedules, or working conditions may be acting with or on behalf of coworkers. That protection can apply even when the employee isn't in a union and even when one employee brings a group complaint to management. The National Labor Relations Board explains that employers may not discharge or discipline employees for protected concerted activity (NLRB).

That creates a critical distinction. An employee's complaint may be protected, while separate abusive conduct may still violate a neutral conduct rule. The decision-maker must identify which part of the interaction drove the proposed discipline. Firing someone because they raised a group wage concern is different from disciplining independently substantiated threats that violated a communicated conduct policy.

Ask these questions before relying on attitude:

  • What exactly happened: Can a witness, message, recording, client report, or contemporaneous note verify the conduct?
  • Which rule applied: Did the employee know the instruction, conduct standard, or collaboration expectation?
  • What was protected: Did the interaction involve pay, hours, safety, working conditions, discrimination, leave, or another legal right?
  • Was the response consistent: Did comparable employees receive the same discipline for similar conduct?

The NLRB recognizes limits to protected activity, including egregiously offensive conduct and knowingly or maliciously false statements. That doesn't eliminate the need for careful analysis. It means the employer should preserve the actual words and context rather than rely on a manager's summary that the employee had a “terrible attitude.”

Triggers That Force a Pause Before Termination

Chronology is where many otherwise supportable terminations become exposed. A performance concern may be genuine, but if the manager accelerates discipline after an accommodation request or complaint, a reviewer may ask whether the protected event changed the outcome.

Pause the decision when the employee recently:

  • Reported discrimination, harassment, retaliation, or another workplace concern.
  • Requested an accommodation or disclosed a medical limitation.
  • Asked about FMLA, state leave, sick time, or another protected absence.
  • Raised a wage, schedule, safety, or working-condition concern.
  • Filed or discussed a workers' compensation claim.
  • Participated in an investigation or supported a coworker's complaint.
  • Engaged in protected concerted activity.

For each trigger, build a chronology. Identify when the underlying concern first appeared, who observed it, what records existed before the protected event, who recommended termination, and whether the proposed action changed afterward. A manager's sudden demand for termination, harsher language in later evaluations, or new scrutiny after a complaint deserves independent review.

Recent federal reporting highlights why this timing matters. In FY2025, reasonable-accommodation matters increased 72% year over year, termination matters rose 240%, and time-and-attendance matters increased 14.29%, according to the cited federal reporting summary (retaliation and accommodation reporting). These figures don't decide an individual case, but they reinforce the need to treat chronology as evidence.

Make the decision file tell one consistent story

The final file should state the legitimate reason in concrete terms and separate it from protected events. If the reason is attendance, identify the unprotected dates. If it is performance, identify the missed standards that predated the complaint. If it is conduct, identify the rule violation rather than the employee's personality.

A workers' compensation claim deserves its own review because state rules and process requirements may apply. Leaders who need broader context can find Florida workers comp help while coordinating with qualified employment counsel on the termination decision.

Protected activity isn't automatic immunity for misconduct. The employer may still enforce a neutral, communicated rule applied to everyone. The Department of Labor explains that an employer may apply a nondiscriminatory substance-abuse policy during FMLA leave when the decision is based on the policy violation, not on the employee's exercise of FMLA rights (Department of Labor FMLA opinion letter). That distinction should appear plainly in the file.

A Decision File and Termination Checklist

A termination meeting should be the final step in a disciplined review, not the moment when the employer starts assembling its explanation. The file should allow a neutral reader to understand what happened without relying on the manager's memory or executive frustration.

Before approval

  • Define the rationale: Write the reason in observable, job-related language. Replace “bad attitude” with the specific conduct, rule, and impact.
  • Check contemporaneity: Confirm that evaluations, warnings, coaching notes, attendance records, and witness accounts were created close to the relevant events.
  • Review the employee's response: Include explanations, disagreements, medical information, accommodation requests, and evidence the employee offered.
  • Filter protected events: Remove protected absences from attendance calculations and assess leave, accommodation, workers' compensation, complaint, and retaliation issues.
  • Compare treatment: Review similarly situated employees and document legitimate reasons for any different outcome.
  • Test the timeline: List the first concern, every warning, every protected event, changes in decision-maker behavior, and the date termination was proposed.
  • Confirm independence: Have HR or another neutral leader review the file, particularly when the recommending manager received the complaint or request.

During the meeting

State the decision briefly and consistently. Don't introduce a new reason, debate every historical incident, or make comments about leave usage, complaints, medical issues, or personality. The written reason, termination letter, payroll instructions, and manager script should match.

Operational details matter too. If the employee works in Texas, verify final paycheck deadlines in Texas and coordinate the payment process before the meeting. If the business employs workers under specialized arrangements or visa-related programs, outside resources such as H-2B compliance advice from Contigo Labor Solutions may help identify obligations that sit outside the immediate performance file.

After the decision

Preserve the complete record, including the policy version in effect, attendance ledger, warnings, employee responses, comparator review, approval notes, and final decision rationale. Don't rewrite history after termination. Late edits and newly invented explanations can damage credibility.

For complex employers, the strongest process combines manager training, consistent documentation standards, and a pre-termination review that examines both the rationale and the chronology. Paradigm International Inc. provides HR risk and decision advisory for leaders reviewing performance documentation, attendance records, protected activity, comparable treatment, and multi-state requirements.

The central test remains simple: Is the stated reason legitimate, was it applied consistently, and can the employer show that protected activity didn't cause the decision? If the answer isn't clear, pause before the meeting.


Paradigm International Inc. helps owners, COOs, HR directors, and leadership teams review high-stakes terminations, strengthen documentation, and separate legitimate performance or conduct issues from protected leave and retaliation risk. Visit Paradigm International Inc. to discuss an outside review of an existing file or a defensible process for future decisions.

Recommended Blog Posts