Black CEO Mistaken for a Janitor — Told to Clean, Then She Fired Everyone

Chapter 15

Theme:
Font Size:
24px

It could be coincidence.

It could be a routine contract review.

Or someone could be trying to make a problem disappear by removing the people who had witnessed it.

She would not assume which explanation was correct.

She would investigate.

Victoria opened her notes and recorded the call.

Then she sent a message to Evelyn.

Please preserve Facilities communications regarding the executive-floor cleaning contract, including inspection records, complaints, and any proposed changes made today. No conclusions yet; I want the timeline established.

Evelyn replied:

Already requested. We will review the records before drawing conclusions.

Victoria put away her phone.

Outside, the city had begun to shift into the gray light of late afternoon.

The board meeting was less than forty minutes away.

She had intended to reveal herself in a controlled setting, present the findings that could be established, and begin a proper investigation.

Now she was beginning to understand that the situation might already be moving faster than she had expected.

If people were attempting to hide records, she needed to preserve them.

If employees were being threatened, she needed to protect them.

If allegations were mistaken, she needed to ensure the investigation did not become a mechanism for punishing someone without evidence.

And if Richard Keller had spent years building a system that made people afraid to speak, the most important part of the investigation would not be what he said in a boardroom.

It would be what happened to everyone else after he left it.

 The Files Nobody Wanted to Read

At 3:30 p.m., Evelyn Hart placed a printed timeline on the conference table in her office.

Susan Bell sat opposite her, reviewing a list of employee complaints. A compliance analyst named Peter Shaw joined them through a secure video call. They had less than thirty minutes before the board meeting, but Evelyn had no intention of presenting a conclusion that the evidence could not support.

“We need to distinguish three things,” she began. “What we know, what we suspect, and what we need to investigate.”

Susan nodded.

Peter adjusted his headset.

Evelyn pointed to the first section.

“Known facts: several complaints involving the East Division were closed without complete documentation. At least four entries mention concerns about retaliation or degrading treatment. We have not yet established whether those allegations are substantiated.”

She moved to the second section.

“Potential corroborating evidence includes performance reviews, meeting invitations, payroll records, resignation dates, and internal correspondence. We also need to identify who approved each complaint disposition.”

Peter typed a note.

“Do we have access to the underlying records?”

“We have access to some. Others are held by the department or the payroll system. We need to preserve the originals before requesting additional explanations.”

Susan looked uneasy.

“Some of these employees have already left. We may not be able to reach them.”

“Then we document that limitation,” Evelyn said. “We don't treat an unavailable witness as proof that the allegation is false.”

“And we don't treat the allegation as proof that the manager is guilty,” Susan replied.

“Correct.”

For the first time that afternoon, Evelyn smiled.

“Exactly.”

She turned to the payroll records.

“The next issue is the hours.”

Peter shared his screen.

A summary appeared, showing several project teams with unusually high utilization rates. In some periods, reported project hours were lower than the hours employees had entered into the preliminary timekeeping system.

“Could these be normal corrections?” Susan asked.

“Yes,” Peter answered. “There are legitimate reasons for adjustments. Some entries may be duplicates. Some may involve time assigned to different projects. We need the underlying audit trail.”

“Can we identify who made the changes?”

“Usually. But I need to verify the system permissions and retention periods.”

Evelyn made a note.

“Please do that.”

Susan folded her hands.

“If the numbers are wrong, we can correct them. But I don't want us to assume that a discrepancy means someone deliberately withheld pay.”

“Neither do I,” Evelyn said. “The question is whether the records are accurate, whether employees were paid correctly, and whether any adjustments were authorized and explained.”

She moved to the final page.

“Then there is the contractor issue.”

Susan looked up.

“What contractor issue?”

Evelyn described the request to preserve Facilities communications.

Susan frowned.

“I hadn't heard about a proposed notice.”

“Then we'll establish whether one exists.”

“Richard may have legitimate concerns about the service.”

“He may. The investigation must consider that possibility.”

Evelyn closed the folder.

“But if the notice was initiated in response to a complaint, the timing matters. We need the records.”

Peter spoke from the screen.

“I'll begin with the audit logs.”

“Thank you.”

After the call ended, Susan remained seated.

“You know what worries me?” she asked.

“What?”

“I can remember several of these complaints. I remember the conversations. I remember trying to find a solution.”

“Were you successful?”

“Sometimes.”

“And the other times?”

Susan looked toward the window.

“I thought keeping the situation quiet was better than letting it become a bigger conflict.”

Evelyn did not interrupt.

Susan continued.

News in the same category

Black CEO Mistaken for a Janitor — Told to Clean, Then She Fired Everyone

45 Part