Chapter 8: The Evidence They Couldn't Erase
The following morning, I arrived at Hawthorne Global with three priorities.
First, I wanted the threat documented.
Second, I wanted the false approval records preserved.
Third, I wanted to understand why someone had used my identity to conceal work that had never been properly delivered.
I wasn't going to let a threatening phone call decide what I did with my career.
But I wasn't going to behave recklessly, either.
Before opening any project files, I met with Adrian and Elena.
The company had recorded the call as a potential intimidation incident and referred it to its security team.
They couldn't identify the caller from the number alone, and nobody was prepared to claim the threat was connected to a particular executive.
I understood why.
A suspicious phone call was not proof of who was responsible for the discrepancies.
But it was a reason to be cautious.
"Has anyone else reported similar contact?"" I asked.
Adrian exchanged a glance with Elena.
"One employee reported receiving an anonymous message last month," Elena said.
"The message was vague, and the employee didn't initially connect it to the project review.""
"Who was the employee?""
"We're not sharing that person's identity until we've spoken with them and determined what information can be disclosed.""
I nodded.
"Fair enough.""
Adrian placed a folder on the table.
"We've also preserved the relevant access logs and restricted the ability to modify the disputed records while the review is underway.""
"Does Martin know?""
"He's been informed that certain records are under review. He has not been given unrestricted access to the investigation materials.""
I looked at the folder.
"Has he responded?""
"He says he has no knowledge of any unauthorized approvals.""
I absorbed that information.
Martin might have been telling the truth.
Someone else might have used his account.
Or he might have known more than he was admitting.
I had to keep those possibilities separate.
The same was true of Gavin.
His emails were suspicious, but I still didn't know whether he had participated in the false approvals or merely pushed an aggressive proposal.
The distinction mattered.
I wanted answers, not a convenient villain.
Elena opened her laptop.
"We've recovered a version history for one of the disputed reports. It shows that the document existed in several versions before the final approval record was attached.""
"Can we see them?""
"Yes. We've exported the available versions and preserved the originals.""
She displayed the first document.
It contained the initial project plan, the original timeline, and the expected deliverables.
The second version included revised dates and altered performance targets.
The third showed the project as completed.
But several deliverables had been marked as accepted without supporting evidence.
I compared the versions carefully.
The changes were not random.
In the initial plan, each deliverable had an assigned owner and a verification step.
In the later versions, several verification fields had disappeared.
The final report treated the absence of a rejection as proof of acceptance.
I pointed to the section.
"This is a problem.""
"Why?"" Adrian asked.
"Because a client not rejecting something doesn't necessarily mean they accepted it. If the contract requires formal approval, there should be a record of that approval.""
Elena nodded.
"And this report treats the lack of a rejection notice as sufficient.""
"Exactly. That could make incomplete work appear finished.""
I examined the document history again.
The person who revised the report had changed the language from "awaiting client confirmation" to "accepted.""
Then another user had approved the revised status.
I leaned closer to the screen.
"Can we identify who made the change?""
Elena opened the audit trail.
"The change was made through a shared administrative account.""
"Another shared account?""
"Yes.""
"Who had access to it?""
"We're still confirming the authorized users.""
I exhaled slowly.
Shared accounts were common in some older business systems, but they made accountability difficult.
If several people could use the same credentials, the records might reveal which account performed an action without establishing who had actually done it.
That was exactly the kind of uncertainty someone could exploit.
"Do we have any independent evidence of delivery?"" I asked.
Adrian opened a client correspondence folder.
"There are emails, meeting notes, and several invoices.""
I read through them.
The client had repeatedly requested missing materials.
The agency had promised revised delivery dates.
Then the internal report had been marked complete, even though the client was still asking for the work.
I felt a familiar anger rising.
Someone had recorded success while the people paying for the project were still waiting for results.
"Has the client been contacted?"" I asked.
"Not yet. The legal team is determining how to approach them without compromising the review.""
"That's sensible.""
I continued examining the records.
By late morning, we'd established that the disputed project had gone through at least four major revisions.
The original plan was reasonable.
The first revised version was ambitious but potentially achievable.
The second revision removed several safeguards.
The final report described the work as complete without evidence that all deliverables had been accepted.
What we still couldn't establish was who had directed the changes and why.
At lunch, I stepped outside to call Emily.
She answered while loading dishes into the dishwasher.
"How are you holding up?""
"Better than yesterday.""
"Did they find anything?""
"More discrepancies. Nothing that proves who's responsible yet.""
I told her about the revised reports and the shared administrative accounts.
She listened carefully.
Then she asked, "Does any of this involve Gavin directly?""
"His emails are part of the review, but I haven't seen evidence linking him to the false approval under my name.""
"Do you think he knew what was happening?""
"I don't know.""
The answer frustrated me.
I'd spent years working with Gavin.
I knew his habits, his temper, his tendency to demand results before considering the resources required to produce them.
But I had never believed he would deliberately falsify an approval under my name.
Then again, I'd never believed he would fire me for helping someone who was dying.
People could surprise you in ways you never expected.
"Chris," Emily said, "remember that you don't have to solve the entire company.""
"I know.""
"You just have to do your part honestly.""
I smiled.
"You should write motivational speeches.""
"I'd charge you full price.""
I laughed.
For a moment, the fear loosened its grip.
Then I returned to the office.
That afternoon, Elena sent me a message.
She had identified an additional source of evidence: an archived correspondence thread involving the disputed project.
The emails had been retained on a company server, even though several related documents had been removed from the active project folder.
We met in a secure conference room.
Elena opened the thread.
The first messages were routine.
The project team discussed timelines, approval requirements, and the need to verify the final deliverables.
Then, halfway through the correspondence, the tone changed.
One message from a senior manager instructed the team to close the project before the end of the reporting period.
Another employee replied that the client had not accepted the outstanding materials.
The response came minutes later.
"Close the file now. We can reconcile the remaining items afterward.""
I read it twice.
"Who sent that?""
Elena enlarged the sender details.
The account belonged to Martin Shaw.
Adrian remained silent.
I continued reading.
A few messages later, someone asked whether the final approval could be recorded under the project reviewer's account.
The reply did not explicitly authorize falsifying an approval.
It said the administrative team should use the standard process to ensure the report could be finalized.
That wording was ambiguous.
But in the context of the other records, it raised serious questions.
"Can you establish who actually applied my approval?"" I asked.
"Not from this thread alone," Elena said.
"But we've found a separate authentication record that may help.""
She opened another file.
The approval had been submitted through a workstation associated with the communications division.
The workstation was located in a restricted office area.
The account used to submit the approval was linked to my name, but the session had been initiated from a device that was not registered to me.
I leaned forward.
"So it wasn't my laptop.""
"Correct.""
"Could someone have copied my credentials?""
"That's one possibility. We need more evidence.""
Adrian studied the record.
"Can we determine who was present in that office at the time?""
Elena nodded.
"Potentially. Building access records and system logs may help narrow the window, although neither source alone will establish who performed the action.""
She brought up a list of people who had accessed the restricted area that evening.
Several names appeared.
Martin Shaw's was among them.
So was the name of another executive.
I stared at the list.
The evidence was getting stronger, but it still didn't tell the entire story.
I remembered Margaret's warning that the person responsible might have more to lose than a contract.
Now I understood why.
If the company had paid for work that wasn't delivered, the financial consequences could be substantial.
If performance reports had been deliberately manipulated, the problem could extend beyond one department.
And if employees' identities had been used to approve questionable transactions, the company's internal controls might have failed in a way that affected far more people than I realized.
"What's the next step?"" I asked.
Adrian closed the file.
"We'll preserve the records, interview the relevant employees, and have the findings reviewed by legal and internal audit. No one will be accused based on circumstantial evidence alone.""
I nodded.
It was the right approach.
Still, I couldn't ignore the possibility that the people involved might try to interfere before the review was complete.
That evening, as I was preparing to leave, my office telephone rang.
The caller ID showed an internal extension.
I answered.
"Christopher.""
A woman's voice spoke quickly.
"My name is Laura Bennett. I work in project administration.""
"All right.""
"I heard you're reviewing the communications approvals.""
I sat down.
"Who told you that?""
"That doesn't matter. I need to speak with you.""
I glanced at the closed office door.
"What about?""
There was a pause.
"I think I know why your name appeared on that report.""
My heart began to pound.
"How?""
"I processed some of the documents. Not the approvals themselves, but the paperwork around them.""
"Can you explain what you saw?""
"Not over the phone.""
"Then we can arrange a meeting with Elena and the legal team.""
"No.""
Her answer came so quickly that I stopped.
"Why not?""
"I'm afraid.""
The words were barely audible.
I softened my voice.
"Laura, if you have information, the review team can help you report it through the proper process.""
"You don't understand. People who ask questions get blamed.""
I thought of my desk at the old agency.
My access card lying beside Sophie's mug.
The sound of Gavin telling me to leave.
"I understand more than you think.""
She was quiet.
Then she said, "I have copies of some of the original approval requests. They show that the reports were changed after the project teams submitted them.""
My fingers tightened around the receiver.
"Where are the copies?""
"At home.""
"Are they original emails or screenshots?""
"Some are emails. Some are printed forms.""
"Please don't alter them or send them to me directly. We need to preserve them properly. Can you contact Elena?""
Laura began to breathe faster.
"I can't. Not yet.""
"Why?""
"Because the person who changed the records is still working here.""
The line went silent.
I waited.
"Laura?""
She whispered one final sentence.
"Check the project files for the name Eleanor Price.""
Then the call disconnected.
I sat motionless.
I'd never heard that name before.
I immediately contacted Adrian and Elena, reporting the call and the information Laura had provided.
They instructed me not to search for restricted records independently and said they would verify whether Eleanor Price was connected to the disputed projects.
I followed their instructions.
But as I gathered my belongings, I couldn't shake the feeling that someone inside Hawthorne Global had finally decided to tell us the truth.
And that the truth might be more dangerous than any of us had anticipated.
The next morning, Elena arrived at my office carrying a printed report.
"Christopher," she said, "we checked the name you provided.""
I stood.
"What did you find?""
She placed the report on my desk.
"Eleanor Price was the internal auditor assigned to the communications division before the previous review was closed.""
I looked at the page.
"Was?""
"She left the company two months ago.""
"Why?""
Elena hesitated.
"Her departure was recorded as a voluntary resignation.""
I studied the report.
Then I noticed a second line.
Eleanor Price had been the person who initially flagged discrepancies in the same project records we were now investigating.
Her original findings had been marked as resolved.
But the documents showed no evidence that the underlying problems had actually been corrected.
I looked up at Elena.
"Who signed off on that resolution?""
She turned the page.
The signature belonged to Martin Shaw.
And beneath it was a note stating that the matter had been reviewed and cleared.
I felt a chill move through me.
Eleanor had raised the alarm.
The records had been declared clean.
She had left the company.
And now Laura was afraid to speak.
May you like
I stared at the report, realizing that we were no longer investigating a handful of questionable approvals.
We were investigating what had happened to the person who first tried to expose them.
