At 10:17 Monday morning, HR gets a message from a department manager:
“Terminate Daniel today. Performance has been terrible for months.”
Fine. Maybe Daniel really does need to go.
Then HR opens his file.
No written warning.
No performance plan.
His last documented review says “Meets Expectations.”
And six days ago Daniel emailed HR complaining that the same manager was treating him differently after he raised a workplace concern.
Now this isn’t a routine termination anymore.
The worst possible response is also the easiest:
“The manager wants him gone, so let’s process it.”
No. First figure out what the hell happened.
“Bad Performance for Months” Should Leave Some Evidence
If Daniel’s performance has genuinely been terrible since May, HR should be able to find something.
Emails.
Coaching notes.
Missed deadlines.
Quality problems.
Customer complaints.
Previous conversations.
Performance metrics.
Something.
Instead, the manager says:
“I talked to him plenty of times.”
Okay. When?
What was discussed?
What was Daniel told to improve?
Did the problem continue afterward?
The manager doesn’t need a 40-page legal brief every time an employee screws up. But if someone supposedly performed badly for four months and the first meaningful record appears on termination day, that’s a weak file.
Then HR Finds the Complaint
Last Tuesday, Daniel emailed HR.
He wrote that his manager had been singling him out after Daniel complained about how overtime assignments were being handled.
Six days later, that manager wants Daniel fired immediately.
That timing doesn’t automatically prove retaliation.
It absolutely deserves attention.
Those are two different statements.
HR doesn’t need to declare the manager guilty because the dates look ugly. It does need to stop pretending the complaint doesn’t exist.
Ask the Manager a Very Simple Question
Why today?
Not:
“Why don’t you like Daniel?”
Not:
“Can you give me some general concerns?”
Why did the termination decision happen today?
Maybe there’s a perfectly legitimate answer.
Perhaps Daniel deleted an important customer file that morning.
Maybe he failed a required procedure after repeated documented coaching.
Maybe the termination decision was already being developed before the complaint.
Good. Get the dates.
But if the answer is:
“I’m just done with him.”
that’s not much of an explanation.
Build the Timeline Before Making the Decision
Daniel’s file might look like this:
August 3: Manager tells Daniel his response times need improvement.
August 18: Daniel misses a project deadline.
August 20: Manager documents a second discussion.
September 2: Another documented performance problem.
September 8: Manager asks HR about possible termination.
September 10: Daniel files complaint.
September 14: Final termination review.
That’s one story.
Now compare it with:
September 10: Daniel files complaint.
September 11: Manager sends first-ever written criticism.
September 12: Manager documents four supposedly old performance problems from memory.
September 14: Manager demands immediate termination.
That’s a very different-looking file.
Same employee.
Same manager.
Same proposed outcome.
Completely different chronology.
Don’t Manufacture Documentation After the Fact
This is where managers sometimes make things worse.
HR asks:
“Where are the previous performance records?”
Suddenly the manager creates a document dated today describing every problem Daniel supposedly had since April.
Historical notes can still be useful if they’re accurate.
But don’t pretend a memo written September 14 was actually created in May.
And definitely don’t backdate documents.
If the manager is reconstructing earlier events, say that.
For example:
“On September 14, I documented the following prior incidents based on my records and emails…”
That’s honest.
Fake contemporaneous documentation isn’t.
The Last Performance Review Matters
Daniel’s manager says:
“He’s been one of my worst employees all year.”
HR opens Daniel’s June review:
Quality: Meets Expectations
Reliability: Meets Expectations
Communication: Meets Expectations
Overall: Meets Expectations
Well, now somebody has explaining to do.
Maybe Daniel’s performance collapsed after June.
That’s possible.
Show what changed.
But the company can’t comfortably rely on “terrible all year” while its own formal record says the opposite.
Progressive Discipline Isn’t Automatically Required Everywhere
Another mistake is assuming an employee can never be terminated unless the company has issued exactly:
Verbal Warning → Written Warning → Final Warning → Termination
That’s not universally true.
Circumstances matter, and employer policies matter.
Serious misconduct can obviously be different from ordinary performance problems.
But if the company has a progressive discipline policy and normally follows it for comparable performance issues, skipping every stage for Daniel needs an explanation.
Especially when the timing already looks questionable.
Check What Happened to Other Employees
Suppose Daniel missed three deadlines and is being terminated.
Last month, another employee in the same department missed four similar deadlines and received coaching.
That doesn’t automatically make Daniel’s termination improper.
Maybe there are important differences.
Daniel had prior issues.
The other employee had an emergency.
The deadlines weren’t comparable.
Fine.
Write down the actual difference.
What you don’t want is:
“We gave Melissa another chance because she’s usually great.”
while Daniel gets fired under an unwritten zero-tolerance rule invented that morning.
Recent Leave or Accommodation Activity Can Matter Too
The same pre-termination review should catch other obvious issues.
Did Daniel recently request medical leave?
Did he ask for a workplace accommodation?
Did he report an injury?
Did he complain about discrimination or harassment?
Did he raise a wage issue?
Again, the existence of one of these events does not make an employee immune from legitimate discipline.
Employees who engage in protected activity can still have real performance problems.
The point is simpler:
If the termination happens right after a legally sensitive event, HR should know that before approving it.
Finding out afterward is a stupid way to run the process.
Don’t Change the Reason Halfway Through
At 10:17 AM the manager says:
“Performance.”
At noon, HR points out the lack of performance documentation.
Now the manager says:
“Actually, it’s attitude.”
At 2:00 PM:
“It’s really insubordination.”
By 4:00 PM:
“We’re eliminating the position.”
Stop.
If the reason keeps changing every time the previous explanation becomes inconvenient, the file is getting worse, not better.
Determine the real reason.
Use the real facts.
Don’t shop around for a nicer label.
“At-Will” Isn’t a Magic Spell
Someone inevitably says:
“We’re at-will. We don’t need a reason.”
At-will employment doesn’t mean every termination is legally risk-free.
It doesn’t erase anti-discrimination rules, retaliation protections, contractual obligations, protected leave rights, or other applicable restrictions.
And from a basic management perspective, “we technically don’t have to explain ourselves” is a lousy substitute for knowing why you’re firing someone.
The company should still be able to articulate the legitimate business reason behind the decision.
Sometimes the Review Confirms the Termination
HR review doesn’t mean every termination gets blocked.
Maybe Daniel’s file actually contains:
Four documented performance discussions
Two written warnings
Repeated missed deadlines
A final warning issued before his complaint
Another documented failure afterward
Now the chronology supports a very different picture.
Daniel’s complaint still needs to be handled appropriately.
But the company also has an established performance history that predates it.
The existence of a complaint doesn’t erase legitimate performance management.
That’s why the review matters.
It separates a real employment decision from a knee-jerk one.
And Sometimes HR Should Tell the Manager “Not Yet”
Suppose there is no documentation.
The complaint is six days old.
The manager’s explanation keeps changing.
Nobody has investigated Daniel’s allegation.
Comparable employees were given warnings.
And the manager wants him out before lunch.
HR doesn’t need to dress that up in corporate language.
This is a bad termination file.
That doesn’t mean Daniel can never be terminated.
It means firing him right now, on these facts, may create a mess the company could have avoided by doing its job properly.
Where Trion Solutions Fits
With Trion Solutions supporting HR administration, employee relations, policies, documentation, and workforce processes, the useful part isn’t simply processing the separation after a manager says “fire him.”
The useful part is having enough structure around the decision to catch contradictions before they become permanent.
A termination record should make sense six months later when nobody remembers the office conversation.
Why was Daniel terminated?
What happened?
When did it happen?
What did the company know at the time?
What had Daniel previously been told?
Was there a recent complaint or protected issue that needed review?
Those answers matter far more than how quickly somebody can remove an employee from the roster.
Don’t Let Monday-Morning Anger Become the Official Record
Maybe Daniel deserves to be fired.
Maybe he doesn’t.
HR doesn’t know that from:
“Terminate him today.”
Open the file.
Read the complaint.
Check the dates.
Make the manager explain the performance problem with actual facts.
If the story holds together, proceed according to the company’s process.
If it falls apart after three basic questions, that’s useful information too.
Because once the company fires someone, it can’t go back and create the careful decision-making process it should have had beforehand.
And “the manager was pissed off on Monday morning” is a terrible reason to discover that too late.