The following day began with an email from the review team.
It asked me to confirm whether I had received any written findings before the deductions were applied to my pay.
I checked my inbox and the project folder before replying.
I found assignment notices, service records, and messages about the Apex Logistics work. I did not find a document that clearly identified an equipment failure caused by a specific action I had taken.
I wrote that in my response.
I also made clear that I could only speak to the records available to me.
After sending the email, I sat back in my chair.
I had started to recognize the pattern.
The questions were becoming more specific, but the information available to me had not changed. The company wanted dates, documents, and explanations from my side, while I was still waiting to see the evidence used against me.
I didn't mind answering questions.
I minded being expected to defend myself against a conclusion I hadn't been allowed to examine.
Late that morning, a meeting invitation arrived.
The subject line referred to the Apex Logistics review. Claire's name appeared among the attendees, along with Derek's and Blake's.
The meeting was scheduled for the afternoon.
I accepted the invitation.
Then I opened my notes and checked the points I wanted to keep clear.
I would explain what I had been assigned to do.
I would explain what information I had received.
I would answer questions about the responsibility form and the deductions.
And I would not pretend to know why the equipment had failed if I didn't have enough information to determine the cause.
That seemed reasonable.
It also seemed like something I shouldn't have needed to defend.
Before lunch, I walked to the records area to retrieve a copy of an assignment notice. The employee there helped me locate the file and confirmed that the copy contained the same information as the version I had previously submitted.
I thanked him and returned to my desk.
The paper was ordinary, but I placed it carefully inside my folder.
I wanted every document arranged by date so nobody could mistake my explanation for a collection of vague memories.
When the meeting time arrived, I carried the folder into the conference room.
Claire was already there.
Blake sat across from her, while Derek occupied a chair near the end of the table. Two members of the review team had their laptops open.
I took the remaining seat.
Claire waited until everyone had settled.
"We're continuing our review of the Apex Logistics deductions," she said. "Today, I want to make sure we distinguish the policy from the basis for applying it."
Nobody interrupted.
She turned to Derek.
"Can you explain what evidence established that Evan caused the equipment failures?"
Derek folded his hands.
"The project was assigned to Evan, and the failures occurred during the period he was responsible for the work."
Claire waited.
He continued.
"Under the accountability policy, costs associated with failures can be assigned to the responsible engineer."
"How was responsibility established in this case?"
"The matter was reviewed internally."
"What did that review establish?"
Derek glanced toward Blake.
Blake leaned forward.
"The purpose of the policy is to ensure that employees take ownership of their assignments. When a project incurs additional service costs, we have to determine who is accountable."
Claire nodded once.
"I understand the purpose of the policy. I'm asking what the review determined about the actual cause of these failures."
The room became quiet.
I looked down at my folder.
I had heard versions of this exchange before. Each time, the conversation returned to the general principle of accountability, while the specific question remained unanswered.
Derek shifted in his chair.
"The failures fell within Evan's field responsibilities."
Claire's voice stayed calm.
"That describes the scope of his job. It doesn't establish that his actions caused the failures."
Blake crossed his arms.
"We shouldn't suggest that responsibility can only be assigned when someone personally damages a piece of equipment."
"No one has suggested that," Claire replied. "But there still has to be a basis for the decision."
One of the reviewers typed something into a laptop.
Derek looked toward him, then back at Claire.
"The internal process followed the established procedure."
"Was the technical evidence reviewed?"
"Yes."
"Can you identify the findings?"
Derek paused.
"The documentation is part of the review materials."
"Then let's identify the specific findings."
He looked down at the papers in front of him.
I couldn't tell whether he was searching for a document or trying to decide how to answer.
Blake spoke before he did.
"Claire, we need to keep the wider picture in mind. Employees are assigned projects because we trust them to manage the work. If every additional cost leads to a dispute, the policy becomes difficult to enforce."
I understood the concern he was raising.
Companies needed people to take responsibility for their work. If a person ignored a warning or failed to follow a required procedure, there could be consequences.
But that wasn't what I was asking them to establish.
"I've never said I shouldn't be held responsible for something I actually caused," I said.
Everyone turned toward me.
I kept my voice steady.
"I've asked for the findings that connect the failures to something I did. I haven't received them."
Derek looked at me.
"You were the engineer assigned to the project."
"Yes."
"You were responsible for the work."
"Yes."
"Then you understand why accountability applies."
"I understand why the policy exists. I still don't know what specific action I'm being held responsible for."
Nobody spoke for a moment.
I felt the old pressure to soften my answer, to add an apology, or to make the disagreement sound less serious.
I resisted it.
I wasn't trying to embarrass anyone.
I wanted a factual answer.
Claire turned to the review team.
"Please record that distinction. We need to establish whether the decision was supported by the technical findings, not merely whether the policy existed."
One of the reviewers nodded.
Claire then looked at Derek.
"Was Evan given an explanation of the evidence before the deductions were applied?"
Derek took a breath.
"He was informed of the responsibility decision."
"That wasn't my question."
He lowered his eyes briefly.
"I would need to check the correspondence."
"Please do."
Blake moved his chair slightly.
"The form was intended to document accountability."
"Did Evan sign it?" Claire asked.
"No," Derek replied.
"Did anyone establish why he declined?"
"He disagreed with the determination."
"Did the review address his disagreement before the deductions were made?"
Derek didn't answer immediately.
"I would need to verify the sequence."
Claire wrote something on her notepad.
"Then that's another item we need to verify."
The meeting continued for several more minutes.
The reviewers asked me to confirm the dates of the project assignment and the communications I had received. I answered each question and referred them to the documents in my folder.
When they asked why I had refused to sign the form, I repeated what I had already explained.
"I couldn't confirm that I had caused the failures when the supporting findings hadn't been shown to me."
One reviewer asked whether I had refused to participate in the review.
"No," I said. "I've answered every question I've received."
"Have you withheld any project records?"
"Not that I'm aware of. I've provided the records available to me."
The reviewer made a note.
Claire listened without interrupting.
At the end of the meeting, she said the team would continue examining the records and clarify the basis for the deductions.
She did not announce a conclusion.
She did not promise that the money would be returned.
I appreciated that she didn't make a promise she couldn't yet support.
But I also knew that the meeting had not resolved the problem.
As we stood, Blake gathered his papers.
Derek closed his folder with a sharp movement.
Neither spoke to me.
I carried my own documents back to my desk and put them in the same drawer where I kept the pay statement.
For the rest of the afternoon, I concentrated on ordinary work.
I reviewed a drawing, answered a question about a separate project, and checked a service schedule. I made myself focus on each task rather than replaying the meeting in my head.
Still, the unanswered question followed me.
The company had explained its policy repeatedly.
It had explained why engineers were expected to take responsibility.
It had explained that an internal process had taken place.
But none of those statements established what I had done wrong.
When I finally shut down my computer, I felt tired in a way that had little to do with the work itself.
I had spent days explaining the same distinction.
Responsibility was not the same as assignment.
A job title was not proof of a technical failure.
And a form was not evidence simply because it had been prepared for someone to sign.
I left the building without knowing what the review would decide.
The only thing I knew was that the questions had become harder to avoid.
Click here to continue reading: PART 11: The Cost of Staying Quiet
The Paycheck That Made No Sense Until the Company Finally Had to Explain Where My Money Went
Part 10 of 16
