Chapter 9 - PAUL VOSS
Paul Voss did not look like a man expecting to be exposed.
That bothered me.
Sixty-two.
Sentinel regional vice president.
Good suit.
No security uniform.
He arrived with two company lawyers and a binder thicker than my arm.
Andrea asked about August 2018.
He remembered.
Not every detail.
Enough.
“Yes, I called Mason.”
“Yes, the facility was over capacity.”
“Yes, contract metrics mattered.”
Then:
“No, I never instructed anyone to classify unclaimed baggage falsely.”
He produced emails from that night.
CLEAR PHYSICAL OVERFLOW. DO NOT CLOSE ITEMS WITHOUT DISPOSITION SUPPORT.
That helped him.
Mason had not mentioned that email.
Voss looked at Grant.
“You had this.”
Grant nodded.
“Yes.”
Then Andrea showed him the red-book entry.
Voss frowned.
“I don't remember S14.”
“Did you control the password?”
“Regional operations did.”
“You were regional operations.”
“I supervised them.”
“Who actually had the credential?”
Voss listed six names.
Shared more widely than Mason remembered.
Bad.
Then the early-release incident.
Voss admitted Sentinel discovered the wrong AB-90 coding two days later.
Why not self-report immediately?
He said:
“We corrected every item we could.”
“That is not the question.”
“No.”
He looked uncomfortable.
“I waited for confirmed loss.”
“How long?”
“Five business days.”
Contract required:
Twenty-four hours.
There.
Why wait?
Because reporting a control failure during storm operations could trigger:
Penalty.
Independent audit.
Possible suspension of baggage services.
He wanted to determine whether anyone had actually lost property first.
A practical instinct.
A breach of the agreement.
Both.
Then I asked:
“Why was my father fired?”
Voss looked at me.
“Because he falsified time records.”
“Seven scans.”
“Yes.”
“Did that cause the status changes?”
“We could not determine.”
“That isn't what your termination letter says.”
His expression tightened.
The letter stated:
Carter's intentional record manipulation directly compromised disposition integrity and resulted in premature release.
Voss looked toward company counsel.
“I signed that.”
“Was it accurate?”
“Not as precisely as it should have been.”
I laughed.
He did not blame lawyers.
Good.
Then:
“We believed his practices created the chain failure.”
“Believed.”
“Yes.”
“After Thomas Bennett told you someone changed disposition after Dad left.”
Voss looked surprised.
“Thomas was an airline auditor.”
“He interviewed Dad.”
“He interviewed everyone.”
“Did you read his memo?”
“I don't remember.”
Ava looked ready to throw something.
She did not.
Progress.
Then Andrea asked about the red book destruction.
Voss said:
“I ordered all unofficial operational notebooks destroyed after counsel confirmed preservation was complete.”
“Why?”
“Because staff were keeping passenger names and bag tags in personal notebooks.”
That was a legitimate privacy concern.
Then an email appeared.
Voss to site managers:
Red books create side narratives nobody can reconcile. Once legal hold clears, eliminate them. Official system is the record.
Andrea read it aloud.
“Side narratives.”
Voss looked uncomfortable.
“Poor wording.”
“Did you know the official system was incomplete?”
“Yes.”
Silence.
There.
He knew the electronic record had gaps.
Still made it the only surviving record.
Not necessarily to hide the 2018 incident.
Still reckless.
Then Andrea brought up current Sentinel performance metrics.
Storage dwell.
Resolved property.
Customer claims.
The same basic incentive remained.
Voss said controls had improved.
Independent audit found two recent cases where overflow bags were almost classified abandoned too early.
Caught before release.
No passenger loss.
Still.
The same pressure could produce the same mistake.
Sentinel's renewal committee paused its vote that afternoon.
Not canceled.
Paused.
May you like
Paul Voss left without handcuffs.
But for the first time in eight years, the company had to explain the system instead of one fired supervisor.
