Chapter 4: The Termination Request She Thought Nobody Would See
Daniel Brooks read the email twice.
The first time, he focused on the date.
The second time, he focused on the authorization record attached to it.
Victoria Hale stood across Marcus Reed's desk, her arms stiff at her sides. The confidence she had worn all morning had disappeared, replaced by the careful expression of someone calculating how much damage a single answer might cause.
Daniel looked up.
“Did you submit a termination request before this morning?””
Victoria adjusted the cuff of her white blouse.
“I submitted a performance review recommendation.””
“That isn't what I asked.””
“I had concerns about Marcus's conduct.””
Marcus remained beside his chair, his black work bag resting against his leg. His shirt was still damp, and the skin beneath his eyes felt tight from exhaustion. He wanted to sit down, but the email on the monitor had made his fatigue feel suddenly distant.
A performance review recommendation.
He remembered the meeting three weeks earlier when Victoria had criticized him for refusing to approve an untested software deployment. She had called him inflexible in front of two department heads. He had explained that the deployment could compromise financial records.
She had smiled at him afterward and said, “You need to learn when to stop hiding behind technical details.””
Two days later, she had asked him to sign a document acknowledging that he had failed to meet a project deadline.
He had refused because the project had been delayed by an executive decision she had approved.
Now Daniel was asking whether she had tried to fire him before the morning's incident.
“Victoria,” Daniel said, “I need a direct answer.””
She glanced at the coworkers still pretending to work around them.
“Can we discuss this privately?””
“No. You made an employment decision in front of this entire department. I need to understand what happened.””
Victoria's jaw tightened.
“I submitted the recommendation last Friday.””
Marcus felt something shift inside him.
Last Friday.
He had spent that evening repairing a data-validation problem that had appeared during a scheduled release. He had worked until nearly midnight, then returned early Saturday to verify that the fix had held.
Nobody had told him his employment was under review.
Daniel opened the attachment.
The authorization record contained a summary of Victoria's request, a proposed termination date, and a list of alleged performance concerns.
He scrolled slowly.
“Repeated failure to demonstrate leadership,” he read aloud.
“Inadequate responsiveness to management direction. Unprofessional workplace conduct.””
Marcus stared at the screen.
“Unprofessional conduct?”” he repeated.
Victoria looked at him.
“You have challenged my decisions in meetings.””
“When those decisions risked the system.””
“You don't get to decide which management decisions deserve your cooperation.””
“I wasn't refusing to cooperate,” Marcus replied.
“I was asking you to let me test the deployment before we put customer transactions at risk.””
Victoria turned back to Daniel.
“This is exactly what I'm talking about. He always has an answer.””
Daniel continued reading.
Another allegation stated that Marcus had failed to complete an assigned technical migration within the approved timeframe.
Daniel frowned.
“Who approved the migration?””
“I did,” Victoria said.
“And who changed the deployment date?””
Victoria hesitated.
“The executive team requested an accelerated schedule.””
“Did you document the additional testing time Marcus requested?””
“That isn't relevant to his performance.””
“It is if you're using the deadline as evidence against him.””
Daniel opened the next page.
A table listed three incidents. Each had a date, a brief description, and a performance rating.
Marcus leaned closer.
The second incident was dated September 18.
He remembered that day clearly. The company had experienced an unexpected interruption in a financial reporting service. Marcus had isolated the fault and restored normal operation within forty minutes.
The report described the incident as a failure to maintain system availability.
“That isn't accurate,” Marcus said.
Victoria looked at him sharply.
“You were responsible for the service.””
“I was responsible for restoring it, which I did. The interruption started after the vendor pushed a configuration change. I documented that in the incident report.””
“Your report was unnecessarily technical.””
“It included the cause of the interruption.””
Daniel turned toward Marcus.
“Do you still have the original report?””
“Yes. In the incident archive.””
“Can you retrieve it?””
Marcus nodded and signed into the reporting portal. His hands moved automatically across the keyboard, despite the ache in his wrists.
He located the September incident, opened the archived report, and turned the screen toward Daniel.
The document included the original timestamps, the vendor's configuration change, the first failed health check, and the corrective action Marcus had taken.
At the bottom was Victoria's electronic acknowledgment.
Daniel looked from the report to the termination request.
“You acknowledged this incident report on the day it happened.””
Victoria leaned toward the screen.
“I acknowledge dozens of reports.””
“Then you should understand why the description in your termination request is misleading.””
Her face reddened.
“I didn't write every technical detail.””
“You didn't need to. You received the report, and you signed it.””
Daniel moved to the next allegation.
Marcus watched the senior director's expression change as he read. The more he examined, the less the document resembled a fair assessment of performance.
One complaint criticized Marcus for escalating a security concern without first obtaining managerial approval.
The attached email showed that Marcus had raised the concern with Victoria twice before contacting the security team.
Another complaint accused him of failing to communicate a critical system change.
The attached incident log showed that he had posted the change in the designated operations channel and received an acknowledgment from Victoria herself.
Marcus felt his stomach tighten.
These weren't simply disagreements about how he worked.
Someone had collected ordinary decisions, removed the context, and turned them into evidence against him.
Daniel closed the attachment.
“Victoria, I want this request reviewed independently. No one should approve it until the original records have been examined.””
She crossed her arms.
“You're making a serious mistake by letting one employee's version of events outweigh a manager's judgment.””
“I'm not accepting anyone's version without evidence.””
“Then examine the evidence.””
“I am.””
Daniel's voice remained controlled, which somehow made the words more intimidating.
He turned toward Marcus.
“Don't delete or modify anything related to these incidents. Keep your original records and preserve the relevant communications. Let the review team handle the investigation.””
Marcus nodded.
“Understood.””
Victoria let out a short breath.
“This is ridiculous. I made a recommendation through the proper process. It hasn't even been approved.””
“Which is why I'm asking for a review rather than treating it as a completed decision,” Daniel said.
“But this morning, you told Marcus he was fired, took his badge, and publicly humiliated him. That is a separate issue.””
Victoria looked toward the entrance aisle.
Several employees immediately returned their attention to their monitors.
She lowered her voice.
“I was frustrated. I had no idea he was going to make such a scene out of being corrected.””
Marcus stared at her.
He had not raised his voice once.
He had apologized, explained the system failure, packed his belongings, and prepared to leave.
He had not made a scene.
She had thrown water in his face.
She had called him useless.
And now she was describing him as the problem.
Daniel seemed to reach the same conclusion.
“Marcus didn't make a scene,” he said.
“You did.””
Victoria's lips parted, but she said nothing.
Daniel took his phone from his pocket.
“I'm contacting Human Resources. Until the review is complete, don't make any changes to Marcus's employment record or interfere with his access.””
“Are you suspending my authority over my own team?””
“I'm telling you to preserve the status quo while we establish what happened.””
“That sounds like a suspension.””
“It isn't a final decision about your role.””
Victoria looked at Marcus again.
“You must be very pleased with yourself.””
Marcus felt the sting of the accusation, but this time he didn't look away.
“No,” he said.
“I'm tired.””
For the first time, Victoria seemed unable to find a reply.
Daniel placed a hand on the edge of the desk.
“Marcus, save the incident notes and then step away from the workstation. I'll arrange coverage. You need rest.””
Marcus saved the document and closed the reporting portal.
As he reached for his bag, a new message appeared on his screen.
It came from the Human Resources director.
The subject line read: *Confidential — Original Approval Record Required.*
Daniel opened it on his phone.
He read the message, then slowly raised his eyes toward Victoria.
“This says your recommendation was based on a prior approval record,” he said.
“But the attachment you've just sent me doesn't include it.””
Victoria's expression changed.
“That's an administrative issue.””
“Then it should be easy to resolve.””
Daniel turned the phone so Marcus could see the final line.
*The approval record identifies the executive who authorized the original performance review request.*
Marcus leaned forward.
Daniel opened the attachment.
And the name at the top wasn't Victoria's.
May you like
It belonged to someone Marcus had never expected to see connected to his employment.
Someone whose signature could turn a manager's questionable recommendation into something much more serious.
