Friday began with an unexpected message from Priya Shah.
Subject: Preliminary Findings β Reporting Audit
Daniel opened the email at eight ten.
The compliance team had completed its initial comparison of the quarterly performance reports. Investigators had identified several undocumented changes, but they had also found evidence that some adjustments were legitimate corrections made under an approved standardization initiative.
That distinction complicated the picture.
The investigation could not simply classify every revision as suspicious. It had to separate authorized corrections from changes that lacked sufficient explanation.
One finding, however, required further attention.
An email exchange showed that a manager had requested a change to a performance metric shortly before a quarterly presentation to the executive committee. The message asked the reporting team to use a revised calculation method, but it did not explain why the method was appropriate or identify the approval supporting the change.
The revised figure had subsequently appeared in the final presentation.
Daniel printed the message and read it carefully.
The sender was Victoria Hayes.
The recipient was a senior reporting analyst.
The email did not prove that Victoria had deliberately falsified information. It did, however, establish that she had personally requested at least one adjustment that required further review.
Daniel called Priya.
"Have you checked whether the revised calculation method was approved elsewhere?"
"We're still checking. The standardization initiative may explain part of it, but we haven't located the authorization for this specific change."
"Could the approval have been recorded outside the reporting system?"
"Possibly. We're checking the meeting minutes and the finance team's records."
"Good. Let's avoid reaching a conclusion until those checks are complete."
Priya agreed.
At nine, Daniel attended a meeting with Margaret Ellis and David Chen to discuss the preliminary findings.
Margaret listened without interruption as Daniel explained the difference between the legitimate corrections and the unresolved changes.
"How serious is the discrepancy?" she asked.
"We cannot yet quantify the full impact. Some figures may have been presented using inconsistent calculation methods. The main concern is that the approval records do not clearly establish why certain changes were made."
"Could the changes have affected executive decisions?"
"Potentially. We need to examine which decisions relied on the revised figures before assessing the consequences."
David opened his notebook.
"And the email from Ms. Hayes?"
"It establishes that she requested one of the changes. It doesn't establish intent or prove that she acted outside her authority."
Margaret nodded.
"Then we need her explanation, supported by the relevant records."
"Yes," Daniel replied.
The CEO leaned back in her chair.
"I want this investigation to be fair. If our processes are poorly designed, we should fix them. If someone made an honest mistake, we should understand it. If someone knowingly misrepresented information, we should deal with that appropriately."
Daniel agreed.
Before leaving, he requested that the company preserve all records relating to the reporting changes and avoid making personnel decisions connected to the investigation without appropriate review.
At eleven thirty, Victoria received a formal request from Compliance to provide documentation supporting the disputed calculations.
She read the message in her office, then immediately called her department coordinator.
"Who gave them this email?"
The coordinator looked uncomfortable.
"I believe it was retrieved from the reporting archive during the audit."
"So nobody had to give it to them?"
"Not necessarily. The archive is part of the records they're reviewing."
Victoria ended the call.
She had always assumed that the reporting system protected her because she was the manager responsible for approving its final outputs. Now she understood that the same system preserved a record of the decisions she had made.
She opened her email and searched for the original discussion.
There were several messages about the standardization initiative, including one from Finance explaining the approved method for calculating efficiency rates across different business units.
The problem was that the disputed adjustment did not clearly reference that method.
Victoria could not immediately determine whether the analyst had followed an instruction she considered obvious or whether the figures had been changed without adequate justification.
She began drafting a response.
Before sending it, she stopped.
If she explained the decision incorrectly, she might make the situation worse. If she admitted that she could not remember the details, the executive office might interpret that as evidence of incompetence.
For the first time, she wished she had documented the decision more carefully.
Meanwhile, Daniel received a message from Marcus Reed.
I found another email that may be relevant. It concerns the reporting changes before the quarterly executive presentation. I have not forwarded it because I'm unsure whether the attachment is confidential.
Daniel responded that Marcus should not distribute restricted documents outside approved channels. He asked him to provide the email reference to Compliance so the investigators could retrieve it through the proper process.
An hour later, Priya confirmed that the message had been located.
It contained a discussion between Victoria and two department employees about the presentation figures.
One employee had raised concerns that the revised calculation method could make the division appear more efficient than it actually was. Victoria had replied that the presentation needed to reflect the department's strategic progress and that the team should avoid confusing executives with unnecessary technical detail.
Again, the wording was ambiguous.
It could reflect a manager attempting to simplify a complicated presentation. It could also indicate that she had prioritized a favorable impression over a clear explanation of the underlying data.
The compliance team scheduled a formal interview with Victoria for the following Monday.
That afternoon, Daniel returned to his workstation and found her standing beside the desk.
"We need to talk," she said.
He closed the document on his screen.
"Certainly."
Victoria glanced toward the neighboring desks.
"Privately."
They entered a meeting room.
She sat opposite him, placing both hands on the table.
"I understand that you've been reviewing emails from my department."
"Compliance is reviewing the records relevant to the reporting discrepancies."
"Some of those emails were written months ago. You're interpreting them without understanding the circumstances."
"Then I hope you'll explain those circumstances during your interview."
Victoria studied him.
"You could have spoken to me before involving Compliance."
"I asked you to provide the supporting methodology and approval documentation. The independent review was necessary because the records were incomplete."
Her mouth tightened.
"Do you understand what this could do to my reputation?"
Daniel paused before answering.
"I understand that an investigation can be stressful. That's why the process needs to be fair and evidence-based. But the possibility of reputational damage cannot be a reason to avoid examining a legitimate concern."
Victoria looked away.
For several seconds, the room was silent.
Then she asked a question he had not expected.
"What happens if the records show that I made a mistake?"
"That depends on the nature of the mistake, the applicable policies, and the evidence. An honest error should be distinguished from a deliberate violation."
"And if you believe I acted deliberately?"
"Then the company will need to consider the evidence and follow its disciplinary procedures. I won't make that decision alone."
Victoria stood.
"I hope you remember those words when this is over."
"I will."
She left the room without another word.
Daniel remained seated for a moment.
He felt no satisfaction in Victoria's anxiety. Whatever the investigation revealed, the purpose was not to humiliate her or prove that his first impression had been correct.
It was to establish whether Meridian could trust the information used to make its decisions.
At five thirty, Daniel received a final update from Priya.
The compliance team had identified a second unresolved adjustment involving a different business unit. The change had been approved through the same management account, and its supporting documentation was also incomplete.
The evidence was growing.
But so was the possibility that the problem extended beyond one manager.
Daniel looked at the black portfolio resting inside his briefcase.
The company had hired him to uncover weaknesses hidden beneath impressive presentations.
Now, for the first time, the documents were beginning to reveal exactly how those weaknesses might have survived for so long.
And Monday's interview could change everything.