Chapter 13 - The Signature in My Name
“YOU CAN TAKE MY TITLE, BUT YOU CANNOT MAKE ME CONFESS TO SOMETHING I DIDN'T DO.”
I said those words after reading the authorization for the fourth time.
David stood across from my desk.
Julia sat beside him, carefully reviewing the file's metadata.
The signature looked official.
It carried my name, my executive title, and the digital reference number associated with an internal approval workflow.
To someone unfamiliar with the system, it appeared convincing.
That was what made it dangerous.
An ordinary forged handwritten signature might contain visible irregularities.
A fraudulent electronic authorization could hide behind valid-looking corporate formatting and system-generated records.
“Where did this come from?” I asked.
Julia answered.
“The maintenance exception system retained a summary showing an approval attributed to your executive office. We're obtaining the underlying access and authentication records.”
“Was it submitted directly from my account?”
“That's what we need to determine.”
I looked toward David.
“At 2:16 that morning, I was asleep in my apartment.”
He nodded.
“We have your building entry records and other corroborating information, but a remote electronic approval doesn't require physical presence. We need to trace the session.”
I appreciated that he didn't offer false reassurance.
“Then let's trace it.”
We called an emergency meeting with the digital forensics team.
The investigators explained how the company managed privileged access.
Certain administrative functions were assigned to specific employees. Others could be performed through temporary access credentials issued during approved support sessions.
Those temporary sessions were supposed to be carefully controlled, logged, and reviewed.
In practice, the oversight had become weak.
One investigator displayed the relevant timeline.
“At 2:11 a.m., a privileged session was initiated from a corporate network associated with the finance executive suite.”
I leaned forward.
“Finance?”
“Yes.”
“At 2:13 a.m., that session accessed the maintenance exception workflow.”
He highlighted another entry.
“At 2:16 a.m., a chair-office approval credential was used to complete the authorization.”
“Was it my personal credential?”
“Not exactly. It was a delegated approval role configured under your office's authority.”
I stared at the screen.
“Who had permission to use that role?”
The investigator opened a list.
Six people were authorized to request specific administrative actions through that workflow.
One was Claire Donovan.
My chief of staff.
I had worked with Claire for four years.
She was intelligent, hardworking, and fiercely loyal to the company.
She handled scheduling, correspondence, board materials, and many of the daily issues that never reached my desk.
I trusted her.
Now I needed to find out what that trust had allowed others to do.
When Claire entered my office, she looked pale.
I asked David and Julia to remain.
“Claire, we're reviewing a delegated authorization issued under my office's name.”
She glanced at the report.
Her face changed.
“Oh, God.”
I felt my stomach tighten.
“Do you recognize it?”
She nodded slowly.
“Yes.”
“Tell me what happened.”
She sat down.
Her hands trembled.
“Evelyn's office contacted me about an urgent system access problem. They said a finance certification workflow had stopped functioning and needed temporary approval rights.”
“When?”
“The night before Flight 604.”
I stared at her.
“Who contacted you?”
“An executive support manager working for Evelyn.”
“Did they say the request involved aircraft maintenance?”
“No.”
“Did they explain why a finance workflow needed delegated authority from my office?”
“They said it was part of the refinancing process.”
I took a slow breath.
“What did you do?”
Claire looked down.
“I approved the temporary access request through the internal support portal.”
“Without asking me?”
“Yes.”
“Why?”
She began crying quietly.
“I thought it was routine. You were preparing for the board meeting, and everyone was working late. They said the request was time-sensitive.”
I leaned back.
Claire wiped her face.
“I know I should have checked.”
Julia spoke gently.
“We need you to walk us through the exact request and preserve all the communications.”
Claire nodded.
“I'll give you everything.”
I looked at her.
“Did you know the approval would be used to close a safety discrepancy?”
“No.”
“Did you ever authorize anyone to falsify maintenance records?”
“Never.”
Her answer was immediate.
I believed she was telling us the truth as she understood it.
But belief was not enough.
The investigators would verify her account.
“Claire, why didn't you tell me when the safety concerns first surfaced?”
She stared at me.
“Because I didn't know the access request was connected to them.”
“I'm also asking about the earlier safety complaint routed through my office six months ago.”
Her face changed again.
I felt something cold settle in my stomach.
“You remember it.”
She nodded.
“Yes.”
“What happened?”
Claire pressed her hands together.
“The complaint entered the executive-office review queue. It was categorized as an operational grievance.”
“By whom?”
“An automated triage rule.”
“And did you read it?”
“Not personally. The system routed it to the responsible department.”
“Which department?”
“Executive Operations.”
I stared at her.
“Adrian's department.”
“Yes.”
“And the case came back marked closed?”
She nodded.
“That's what the system showed.”
“Did you tell me?”
“No.”
“Why not?”
Claire looked ashamed.
“Because our office receives hundreds of messages every week. The system was designed to keep routine matters from overwhelming your schedule.”
I said nothing.
The explanation made procedural sense.
That was the terrible part.
A system intended to make leadership more efficient had helped create a barrier between the people raising concerns and the person ultimately responsible for overseeing the company.
“Claire,” I said quietly, “a safety complaint should never have been treated as routine correspondence.”
“I know.”
“Then why was it?”
Her eyes filled.
“Because that's how the workflow was configured.”
I looked away.
There was no easy place to put the blame.
Someone had exploited the system.
But I had allowed the system to exist without sufficient independent safeguards.
That was a leadership failure I could not explain away.
After Claire left, Julia reviewed the newly recovered communications.
The original request to activate the delegated approval role had been submitted through an executive-support account.
The account was assigned to Evelyn's finance organization.
The forensics team also found evidence that the temporary credentials had been used outside the stated purpose of the request.
That gave us important support for Claire's explanation.
But we still needed to identify who controlled the session at 2:16 a.m.
At five that afternoon, the forensic team located a retained authentication log from the company's identity-management provider.
The log had been stored separately from the maintenance platform.
Unlike the summary record, it included a more detailed history of the privileged session.
The investigators compared the timestamps, network data, and associated support-ticket records.
Then they found the original administrative request.
The requester's name was listed as an executive-services account.
But its underlying employee identifier belonged to Nathan Sloan's contractor-support team.
I stared at David.
“Asterion again.”
“Yes.”
“And the request was initiated from Finance?”
“Yes.”
“So someone at the contractor obtained access by using an approval role from my office, then used it to create the appearance that I had authorized the exception.”
“That is what the evidence currently supports.”
I closed my eyes.
The fraud had crossed three layers.
An outside contractor.
The finance department.
And my executive office.
No single careless employee could explain the entire chain.
Someone had designed it to exploit the gaps between them.
Julia's phone rang.
She listened carefully, then asked the caller to repeat something.
Her expression changed.
After hanging up, she turned toward me.
“Jana Hayes found a retained project message from Operation Clear Sky.”
“What does it say?”
She placed the verified copy in front of me.
The message was attributed to Evelyn's project account.
It read:
IF CARTER REFUSES EXECUTIVE APPROVAL, USE THE EXISTING CHAIR-OFFICE DELEGATION. DO NOT ELEVATE THE MAINTENANCE EXCEPTION TO HER PERSONAL REVIEW.
I read it slowly.
Then I looked at David.
Evelyn had known I would not approve the exception.
So the records suggested she had found a way to make it appear that I already had.
But the final sentence was worse.
ADRIAN HAS CONFIRMED THAT CARTER WILL BE KEPT OCCUPIED AT THE GATE UNTIL FLIGHT 604 DEPARTS.
The seat confrontation had not merely been convenient.
May you like
According to the message, it had been incorporated into their plan.
And the woman who thought she was stealing my seat had unwittingly helped cover an attempted fraud.
