Fourteen Minutes

Chapter 21

Theme:
Font Size:
24px

Do not use this template for operational approvals. Disable access until the system owner confirms a compliant replacement.

Olivia read the paragraph twice.

"Who received the note?"

Maya listed four recipients.

Her manager.

The system migration lead.

Thomas Bell.

And the executive operations account.

Olivia looked up.

"So the people responsible for the system were warned that the template could be used to create a document that looked signed without producing a verified approval."

"Yes."

"Did you see the authorization from this morning before it was submitted?"

"No."

"Did you create it?"

"No."

"Did you provide anyone with a signature image?"

"No."

"Did you know my aircraft was being reassigned?"

"No."

Maya's answers were immediate but not defensive.

Olivia appreciated that.

"Why did you come to me now?"

Maya looked at the document on the tablet.

"Because I learned this morning that the aircraft had been held. Then I heard people discussing whether the authorization was a system error. I thought the technical note might be relevant."

"It is."

"I didn't want to overstate what I knew. I don't know who used the template. I don't know whether anyone deliberately misrepresented your approval. But I know the risk had been identified before the document was created."

Olivia closed the tablet cover.

"Thank you for bringing this forward."

Maya's shoulders lowered slightly.

"I was worried I should have done more."

"Could you have escalated the warning more forcefully?"

"Yes."

"Could the system owner have disabled the template after receiving your note?"

"Yes."

"Could the operations team have refused to accept a document without the current verification record?"

"Yes."

Olivia held her gaze.

"Then we'll examine each of those failures. But the fact that you didn't escalate the note beyond the established process doesn't make you responsible for someone else's use of the template."

Maya looked relieved, though not entirely convinced.

"I appreciate that."

"Please preserve the original note, the email headers, and any responses you received. Don't edit the file or add commentary to the original. If you have additional observations, record them separately with the date and time."

"I can do that."

"And Maya?"

"Yes?"

"You were right not to modify the signature field without a clear system-owner instruction. A technical fix can create the appearance of control without actually establishing authority."

Maya nodded.

"That's what concerned me."

After Maya left, Olivia forwarded the technical note to Naomi Patel and Thomas Bell.

She also sent it to Margaret Shaw with a short explanation.

The discovery changed the nature of the investigation.

Until then, the unauthorized document could have resulted from confusion during the system migration, a careless reuse of an old template, or a deliberate attempt to bypass the approval process.

Now there was evidence that the template's weakness had been identified before the incident.

The warning had been documented.

The risk had been explained.

The recommendation had been clear.

Someone had chosen not to act on it.

That choice might have been negligent rather than malicious. It might have been overlooked amid other priorities. It might even have been delayed because the team believed the old template was no longer being used.

But the company could no longer describe the problem as an unforeseeable technical defect.

The defect had been foreseeable.

Olivia called Thomas.

"I've received Maya Chen's technical note."

Thomas sighed.

"I was afraid that might come up."

"Why?"

"Because I received a copy of the warning, but I didn't follow up to confirm that the template had been disabled."

"Why not?"

He was quiet for a moment.

"The migration team was dealing with several urgent issues. We had a backlog of maintenance records that needed reconciliation, and two aircraft were waiting on parts documentation. I believed the template was a low-priority administrative item because the new system was already in use."

"Did you ask anyone to verify that it was no longer accessible?"

"No."

"Did you tell Maya or the migration lead that you were postponing the recommendation?"

"No."

"Did you tell the executive operations team not to use the template?"

"No."

Olivia closed her eyes briefly.

Thomas was not trying to hide the failure.

That mattered.

It did not erase the failure.

"Thomas, I need you to understand that the issue is not simply whether the template should have been disabled. It's whether a warning about a document that could falsely represent approval was allowed to sit in a folder without an owner, a deadline, or a verified corrective action."

"I understand."

"Do you?"

"Yes."

"Then I need a complete review of the unresolved control recommendations from the migration project. Not just the ones connected to today's incident. I want to know which items were deferred, who accepted the risk, and what evidence exists that the risks were controlled."

"I'll prepare it."

"Have it reviewed independently."

"All right."

After the call, Olivia wrote another line in her notebook.

An unanswered warning is still a decision.

News in the same category

Fourteen Minutes

45 Part