PART 9 – The Questions Nobody Wanted to Answer

The next morning, I arrived at the office earlier than usual.

I had slept badly, waking several times with the same questions running through my head. Every time I closed my eyes, I saw the meeting room, Claire’s expression, and the way Derek had struggled to answer a simple question.

Had I caused the equipment failures?

Nobody had given me a clear answer.

Yet my paycheck had already given me a number.

Three hundred and twelve dollars.

I had folded the pay statement and placed it in the top drawer of my desk. I hadn't thrown it away, even though looking at it made my stomach tighten.

That morning, I took it out again.

I checked the figures, although I already knew them by heart. The deductions were still there, each one listed in the same neat columns as before.

The paper looked ordinary.

That was what bothered me most.

A decision that had left me struggling to cover my expenses had been reduced to a few lines of print. Anyone looking at the statement without knowing the circumstances might have assumed everything was normal.

I put it back in the drawer.

Then I opened my laptop and began reviewing the Apex Logistics project records I had saved.

I wasn't trying to prove that I had never made a mistake. Every engineer makes mistakes, and I had never expected to be treated differently from anyone else.

I wanted to know which mistake the company believed I had made.

That distinction mattered.

If I had caused a failure, I wanted the evidence. If I had missed a warning or overlooked a maintenance requirement, I wanted to understand it.

But I couldn't accept responsibility simply because my name had been attached to the project.

I opened the oldest report first.

It contained the equipment information I had received when I was assigned to Apex. I checked the dates, the service notes, and the responsibilities listed under my name.

Nothing in those pages changed what I had already explained to Claire.

Still, I kept reading.

I wanted to be certain I hadn't overlooked something important.

Around eight thirty, Derek walked past my desk.

He slowed when he saw the documents on my screen.

"You're still reviewing Apex?"

"I want to make sure I have everything organized."

"Didn't you already provide the records?"

"I provided the records I have."

He looked at the screen for another moment.

"There's no need to turn this into something bigger than it is."

I kept my hands on the keyboard.

"I'm not trying to make it bigger."

"Then let the review proceed."

"That's what I'm doing."

Derek's mouth tightened slightly.

He didn't say anything else. He continued down the aisle toward his office, leaving me with the uncomfortable feeling that asking for evidence had somehow become an offense.

I returned to the report.

A few minutes later, my phone vibrated.

The message came from an internal administrative account.

It asked me to confirm the dates on which I had received project assignments, service instructions, and responsibility documents related to Apex Logistics.

I read it twice.

Then I replied with the information I could verify.

I attached the relevant records and made it clear whenever a date came from my own notes rather than an official company document.

I didn't want to claim certainty where I didn't have it.

That had been the problem from the beginning.

Other people had made confident statements about my responsibility, but nobody had shown me the evidence supporting those statements.

I wasn't going to make the same mistake in reverse.

By midmorning, I had returned to my regular work.

There were other projects waiting, and I couldn't spend every hour thinking about one disputed assignment. I answered emails, reviewed a technical drawing, and joined a short call with a colleague about a separate equipment issue.

For a little while, the ordinary work helped.

Then I received another message.

Claire wanted me to remain available for additional questions if the review team needed clarification.

There was no explanation of what the team had found.

I read the message, acknowledged it, and went back to work.

I had learned that every new notification could make my heart beat faster, even when it contained nothing useful.

At lunchtime, I carried my food to a small table near the windows.

Two employees were talking quietly at the next table. I wasn't trying to listen, but I heard the word accountability.

One of them said the company was reviewing how project costs were assigned.

The other replied that policies existed for a reason.

Neither mentioned my name.

I ate without looking up.

I understood why people defended policies. Rules could keep a company organized, and a business couldn't function if every decision became an argument.

But a policy wasn't supposed to replace the facts.

It was supposed to guide decisions based on them.

When I returned to my desk, I found an email asking me to clarify why I had declined to sign the responsibility form.

I opened a blank reply.

For a moment, I considered writing something short just to make the question disappear.

Instead, I explained the reason plainly.

I had declined because the form assigned responsibility for failures without identifying the specific actions that had caused them. I had requested supporting information but had not received enough to verify the claim.

I wasn't refusing to cooperate with an investigation.

I was refusing to certify something I could not honestly confirm.

I read the reply once before sending it.

Then I attached the earlier correspondence showing that I had asked for clarification.

I clicked Send.

The message disappeared from my screen, and there was nothing more I could do with it.

That afternoon, Claire passed through the engineering area with another employee.

She was speaking quietly and carrying a folder. When she reached my desk, she paused.

"Evan, do you have a moment?"

I stood.

"Yes."

"Have you received any new explanation of the deductions?"

"No."

"Has anyone shown you the technical findings behind the responsibility decision?"

"No."

She looked at the folder in her hand.

"All right."

I waited, expecting another question.

Instead, she said, "Thank you for being available."

Then she continued toward the conference rooms.

I watched her go for a second before sitting down.

Her questions were direct, but her answers remained limited. I couldn't tell whether that meant the investigation had uncovered something significant or whether it was simply taking time to gather the records.

I decided not to guess.

At the end of the day, I checked my inbox one last time.

There was no final decision.

I shut down my computer and placed the folded pay statement back in the drawer.

The number on it hadn't changed.

Neither had the questions behind it.

I left the office knowing that the review was still moving, even if I couldn't see where it was going.

For now, I could only keep my own records accurate and answer every question honestly.

That was the one part of the process I could control.

Click here to continue reading: PART 10: A Policy Was Not an Answer