The room became completely silent.
Richard looked toward the window.
For years, he had considered himself a practical man. He had believed that people who complained about his management style were too sensitive, too inexperienced, or too unwilling to accept the demands of a competitive business.
He had never considered that the behavior he called practical might simply have been cruelty protected by success.
Evelyn turned to the next section.
“We also need to address the employee complaints.”
Richard's expression changed.
“I have not seen the complaints you're referring to.”
“That is part of the review,” Evelyn said. “We are examining how the complaints were handled, who participated in their resolution, and whether the decisions were supported by adequate documentation.”
“Are you suggesting that HR failed to do its job?”
“We are not suggesting a conclusion. We are reviewing the records.”
Richard looked at Susan Bell.
Susan did not meet his eyes.
He felt something cold settle in his stomach.
For the first time, he was uncertain whether the people who had supported him would continue to do so.
The payroll review began the following morning.
Victoria had asked Evelyn to establish a separate review team before the board meeting ended. The team included representatives from legal, compliance, payroll auditing, and an external employment specialist who had no prior relationship with Pinnacle's leadership.
Their mandate was narrow and specific.
They would determine whether reported working hours matched the available records, whether adjustments had been authorized, whether employees had been paid correctly, and whether any discrepancies resulted from errors, policy misunderstandings, or deliberate interference.
They would not assume wrongdoing merely because numbers differed.
They would not dismiss a discrepancy merely because a senior manager approved it.
At 8:30 a.m., Marcy Ellis entered a small conference room carrying three folders and a laptop.
She had slept poorly.
The previous afternoon, she had received a confidential invitation to speak with the review team. The message explained that the interview was voluntary, that the company was examining payroll procedures, and that she could request clarification about how her information would be used.
It also included a direct contact for reporting any concern about retaliation.
Marcy had read the message six times.
She wanted to believe it.
But she had seen too many reassuring emails followed by uncomfortable meetings with managers.
She had watched colleagues become cautious after raising questions. She had seen minor errors corrected while larger issues remained unresolved. She had learned that a policy could be beautifully written and still fail the people it was supposed to protect.
When she entered the room, Evelyn stood to greet her.
“Good morning, Marcy. Thank you for coming.”
Marcy glanced at the others.
“Am I in trouble?”
“No,” Evelyn said. “You are here because we want to understand the payroll process. You are not being investigated for making a good-faith report.”
Marcy remained standing.
“Will Richard see what I say?”
“The review team will determine which information needs to be shared to investigate the concerns fairly. We cannot promise absolute confidentiality in every circumstance, because people accused of misconduct must have an opportunity to respond to relevant evidence. But we will limit access to those who need the information, and we will take retaliation concerns seriously.”
Marcy considered the answer.
It was not a perfect guarantee.
But it was more honest than a promise that nobody would ever know.
She sat down.
The interview lasted nearly two hours.
Marcy explained how the payroll system recorded scheduled hours, submitted hours, and approved adjustments. She described the difference between legitimate corrections and changes that required additional review. She showed the team examples of records where an employee's submitted hours differed from the final payroll entry.
She did not claim that every discrepancy was intentional.
In fact, she repeatedly cautioned the investigators against drawing conclusions too quickly.
“This one may be a duplicate,” she said, pointing at a row on her screen. “The employee entered the same shift twice. That happens.”
She moved to another record.
“This one is different. The submitted time was reduced after the manager approval stage, but I can't tell from this screen who authorized the change.”
The auditor made a note.
“Can you identify the adjustment history?”
“Yes. If the audit log is intact.”
“Would you be able to retrieve it?”
“I can show you where it should be.”
“Please do.”
Marcy opened the relevant system.
A sequence of entries appeared.
The original hours had been submitted by an employee. A supervisor had approved them. Two days later, the total had been reduced. The record contained a note stating that the adjustment was related to project allocation.
But the project allocation report did not show where the missing hours had gone.
The auditor leaned closer.
“Is this normal?”
“It can happen,” Marcy said. “Sometimes hours are moved from one project code to another. But the total should still reconcile unless there is a separate correction.”
“Can you reconcile this one?”
“Not with the information available here.”
“Then what would you need?”
“The original submission, the approval history, the adjustment request, and the final payroll record.”