Chapter 3 - THE REPORT THAT DIDN’T ADD UP
The next morning, I woke to seventeen missed calls and a string of messages from Derek.
The first was an apology.
The second said I had misunderstood his humor.
The third claimed that I had embarrassed him by allowing the admiral to turn a private disagreement into a public spectacle.
By the ninth, he had begun asking me to call Halston Marine’s communications director before the story spread.
I read them all while my coffee cooled beside the kitchen sink.
Not one message asked whether I was hurt.
I set the phone down and opened the secure review portal for the fleet-support contract. The technical submissions had arrived the previous week, and I had planned to spend Saturday reviewing maintenance intervals and parts traceability. After the gala, I found it difficult to concentrate, but work had always been the place where facts mattered more than appearances.
Halston Marine’s proposal looked polished. It promised rapid repairs, reliable parts, and a lower lifecycle cost than its competitors. The supporting charts were persuasive at first glance.
Then I noticed a discrepancy in the replacement schedule for a critical hydraulic assembly.
The report claimed the component could safely remain in service for a longer interval than the manufacturer’s documentation allowed. The claim was supported by a test summary, but the summary referred to a different model number.
I checked the source files.
The model numbers did not match.
I checked the serial numbers.
They appeared to have been copied from a previous test.
I checked the dates.
Two of the inspections were listed as completed before the parts had been delivered to the test facility.
My pulse slowed as my attention sharpened. This was no longer a small administrative error. If the contract relied on the submitted information, crews could be sent into the field with equipment whose reliability had not been established.
I documented each discrepancy and sent a formal request for clarification through the procurement portal. I did not contact Derek. I did not discuss the findings with anyone outside the authorized review group.
At noon, a message arrived from Halston Marine’s chief operating officer, Martin Shaw, asking for an “informal conversation” about the review.
I declined and reminded him that all communication had to go through the official channel.
Ten minutes later, Derek called.
“What are you doing?” he demanded.
“Reviewing the bid.”
“You’re flagging our documents over a model-number mismatch?”
“I’m requesting verification.”
“It’s a clerical error.”
“Then it should be easy to correct.”
“You know how much is riding on this contract.”
“Yes. That’s why the data has to be accurate.”
His voice dropped. “Mara, I need you to understand something. If this proposal fails, hundreds of people could lose their jobs.”
“Then the people responsible for the proposal should have verified it before submitting.”
A sharp silence followed.
“You’re enjoying this,” he said.
I almost laughed. “You think I want a safety review to turn into a scandal?”
“I think you’re angry about last night and using your position to punish me.”
“That accusation is serious. If you believe I have a conflict of interest, file it with the review office. I’ll cooperate with an independent audit.”
“You’d really do that to me?”
“I would do the job I agreed to do.”
He hung up.
I sat still for several seconds, staring at the phone. It hurt that Derek could turn an obvious professional concern into a personal attack. But underneath the hurt was something else: relief. I had finally said no without adding an apology to make it easier for him to hear.
That afternoon, Admiral Reddick called.
“I’ve been told you submitted a technical clarification request,” he said.
“I’m required to report discrepancies.”
“Good. Keep doing exactly that. I don’t want you to change your process because of what happened at the gala.”
“I won’t.”
“Are you comfortable continuing the review?”
“Yes, sir.”
“Then you have my support. Not because you saved my son. Because your work stands on its own.”
I thanked him.
Before ending the call, he added, “One more thing, Commander. My son would like to speak with you. He’s in Chicago this week. He’s been trying to find a way to thank you without making you feel obligated to accept.”
“I’d be glad to see him.”
“Then I’ll send you his number.”
When I hung up, I looked again at Halston Marine’s submission.
The discrepancy was no longer just a technical question. It was a test of whether I would let Derek’s pressure change my judgment.
I opened a new review note and wrote one sentence at the top:
All claims must be supported by verifiable evidence, regardless of who submitted them.
Then I continued working.
I built a comparison table from the manufacturer’s public service bulletins and the submitted test summary. The differences were too specific to ignore. One file described a hydraulic assembly with a revised seal design; Halston’s proposal used the performance results from the older version, even though the two parts had different operating tolerances. A second document claimed that the test had run for hundreds of hours, but the log showed a gap long enough to make the reported total impossible.
I checked the files again, then checked them a third time. Technical reviews require humility. A reviewer who assumes every anomaly proves wrongdoing can cause damage just as surely as a reviewer who ignores a genuine problem. My job was not to guess at intent. It was to establish what the records could support.
I called the review administrator, Ms. Patel, and explained that I had identified potential discrepancies in one submission. I did not name Derek beyond the disclosure already on file. Ms. Patel instructed me to preserve the original files, submit a formal clarification request, and avoid any informal contact with the bidder.
“Even if you know someone there?” she asked.
“Especially then,” I replied.
The question seemed to satisfy her. She assigned a second technical specialist to independently review the model numbers and requested that I document the basis for every concern.
By midafternoon, I had six pages of notes and a headache building behind my eyes. I went for a walk along the harbor, where the wind carried the smell of salt and diesel. A tugboat moved slowly past the piers, its crew visible only as dark shapes behind the windows. I watched it turn and thought about the people who would eventually rely on the equipment described in the proposal.
A contract was never just a stack of numbers. It became maintenance crews working overnight, sailors trusting a repaired system, and families expecting someone to return home. That was why I could not pretend the mismatch was trivial.
When I returned, an email from Derek was waiting in my personal inbox. He had written that the company was under “extraordinary pressure” and that a delay could jeopardize the future of the entire division. He did not directly ask me to change the review, but the message was designed to make me feel responsible for what might happen if I did not.
I forwarded it to the review administrator and asked whether it should be added to my conflict disclosure. Her response was brief: yes, preserve it and do not engage.
I felt a flash of sadness. I had once believed that if Derek understood the stakes, he would respect the process. Instead, he was treating my integrity as another resource he could negotiate.
That evening, I wrote down three questions on a notepad: What do the documents prove? What do they fail to prove? What evidence would resolve the gap? The questions steadied me. They reminded me that I did not have to decide whether Derek was a good man or a bad one to do my job properly.
I only had to be accurate.
The next morning, the second specialist independently confirmed the model-number mismatch. The review office issued a formal request for original test data and traceable supplier records. It was now an official matter, no longer something Derek could persuade me to soften over dinner.
May you like
I printed the confirmation and placed it in the review file.
Then I went back to work.
