Fourteen Minutes

Chapter 20

Theme:
Font Size:
24px

One represented the work that had created the company.

The other represented the work the company might yet do.

Between them lay a question that the acquisition could not answer.

What was Sterling Aviation willing to become in order to grow?

And what would it refuse to become, even if refusing cost money?

Olivia left the conference room.

Outside, the airport continued its work.

Her aircraft remained secured on the ramp.

The compass star still pointed nowhere in particular.

But Olivia knew the direction she needed to take.

 The Engineer Who Refused to Sign

At 2:17 p.m., the first person to offer Olivia a useful answer was not a lawyer, an executive, or a board member.

It was an engineer named Maya Chen.

Maya was thirty-four, a specialist in aircraft systems integration, and one of the most careful people Olivia had ever hired. She had a habit of reading a technical report twice before commenting on it and asking questions that sounded simple until someone attempted to answer them precisely.

She had worked at Sterling Aviation for seven years.

Olivia had first met her during a review of a maintenance tracking project. At the time, Maya had been a junior engineer responsible for checking the compatibility of several legacy systems. She had discovered that a data conversion tool was rounding certain inspection intervals to the nearest whole day.

The difference seemed insignificant.

It was not.

Under the wrong circumstances, rounding could make a maintenance item appear due later than it actually was.

Maya had refused to approve the conversion until the defect was corrected. The project manager had complained that she was delaying the rollout. Maya had replied that a schedule was not evidence of correctness.

Olivia had remembered her.

Now Maya stood outside the executive conference room holding a tablet against her chest.

"Ms. Sterling? Do you have a minute?"

Olivia looked at the clock.

"Of course. Come in."

Maya entered and closed the door.

"I heard there was an issue with the aircraft authorization this morning."

Olivia gestured toward a chair.

"We're investigating it. What have you found?"

Maya sat down.

"I haven't investigated the flight change directly. I work on system integration, not dispatch. But yesterday afternoon, I was asked to verify a legacy authorization template for the executive operations team."

Olivia felt her attention sharpen.

"Who asked you?"

"Lauren Pike sent me a request. She said someone needed to confirm that the old template could still be opened in the new document system."

"Did she say why?"

"She said it was needed for a continuity test."

"What kind of continuity test?"

"She didn't know. The request was described as an administrative check."

Olivia remained still.

"Did you verify the template?"

"No."

"Why not?"

Maya took a breath.

"Because the request asked me to confirm that the document could be edited and that the old signature field remained visible. It didn't ask me to verify the approval process. I opened the file, confirmed that it displayed correctly, and then noticed that the signature field accepted a pasted image."

"Was that unusual?"

"It was unacceptable for a document that could be used to authorize an aircraft movement."

Olivia leaned forward.

"What did you do?"

"I replied that the template should not be used for operational approval. I recommended that it be disabled and replaced with the current signing workflow."

"Did anyone respond?"

"Lauren thanked me. Later, someone from executive operations asked whether I could make the signature field non-editable while preserving the old layout."

"Who?"

Maya looked down at her tablet.

"The request came from a shared departmental account. I don't know who wrote it."

"Did you make the change?"

"No."

"Why not?"

"Because the request was ambiguous. Making the signature field non-editable might have prevented accidental changes, but it would not have made the document an approved authorization. I asked for written confirmation from the system owner."

"Did you receive it?"

"No."

Olivia was silent for several seconds.

Maya continued.

"I should have escalated the request when I didn't receive a response. I didn't. I assumed the team would stop using the old template because I'd documented the problem."

"Did you tell anyone that the template could accept a pasted signature image?"

"I told my manager. I also included it in my technical note."

"Was the note formally recorded?"

"Yes. I saved it to the integration project folder and sent the link to the system migration team."

"Can you show me?"

Maya opened her tablet and displayed the document.

The technical note was dated two days earlier.

Its wording was precise.

The legacy authorization template remained editable. Its signature field did not require verification through the current signing service. Any image inserted into the field would appear visually similar to a legitimate signature block, but the resulting document would not contain the digital verification record required for an approved authorization.

The note ended with a recommendation:

News in the same category

Fourteen Minutes

45 Part