validate

Chapter 5 - The Audit Trail Led Past Rebecca and Into the Executive Floor

Caroline Bates was interviewed for seven hours.

Maya did not attend.

The board’s outside counsel briefed her afterward because Caroline reported to Maya operationally, but only after the investigators completed their first round.

Caroline admitted receiving the screenshot.

She denied recognizing the names.

She said the image could have been fabricated.

She said employee privacy limited the company’s ability to inspect personal group chats.

All of that was partly true.

Then counsel asked why she did not interview the employees named in the complaint.

Caroline said resources were limited.

Why did her office close the complaint in six days?

She could not remember.

Why did she later email a base manager telling staff to keep informal passenger coordination off company systems?

She said that was separate.

Could she provide documentation showing a different incident prompted the email?

No.

Facts did not yet prove conspiracy.

They proved failure.

Possibly deliberate.

Possibly cowardly.

Possibly both.

Maya sat with the board’s lead director, Helen Park, after the briefing.

“Do I remove Caroline now?”

Helen shook her head.

“Not your call during this review.”

“Good.”

Maya meant it.

CEOs often complained boards slowed them down.

That week, Maya was grateful for friction.

It kept anger from becoming process.

The investigation found a second ethics complaint.

Then a third.

One involved the same private crew group.

Another described a gate supervisor telling employees to “trust your eye” when premium passengers “look questionable.”

The supervisor denied saying it.

Three employees remembered similar language.

One had written notes after the meeting.

Culture stopped being abstract.

It had phrases.

Shortcuts.

Jokes.

Side channels.

Maya asked HR for discipline data related to passenger disputes across three years.

Patterns appeared.

Employees were more likely to receive coaching than formal discipline when complaints involved subjective treatment rather than explicit policy violations.

Why?

Managers preferred cases with clean rules.

Wrong seat assignment.

Failure to scan.

Unauthorized upgrade.

Verbal disrespect and discriminatory assumptions were harder to prove.

So they became softer outcomes.

The company had unintentionally taught staff that ambiguous harm produced ambiguous consequences.

Maya wrote one sentence on a legal pad:

If a system only punishes what is easy to measure, people learn where the invisible boundaries are.

She carried that page for weeks.

The board hired an external civil-rights consultant and an operational safety specialist.

Maya insisted both be involved.

Bias and safety could not be placed in separate rooms when the crew chat had mixed legitimate threat reporting with prejudice.

Some employees defended the group publicly.

“We were trying to protect crews.”

That could be true.

Others said the company was sacrificing frontline workers to protect the CEO.

Maya took that seriously too.

Flight attendants dealt with assaults, harassment, seat fraud, intoxication, medical emergencies, and passengers who treated uniforms like invitations to abuse.

A good reform had to give them better tools, not simply remove informal ones.

The airline created a temporary hotline staffed by security and customer-resolution specialists who could verify passenger issues within minutes.

Usage was immediate.

So were complaints that the hotline was slow.

Good.

Real systems reveal flaws quickly.

Then Maya learned something she did not expect.

Rebecca had used the official fraud-verification tool on the morning of Flight 417.

The result had come back:

VALID RESERVATION. NO FRAUD INDICATOR.

Twenty minutes later, Rebecca entered her own note:

POSSIBLE TICKET MISUSE.

Maya stared at the timeline.

“So she checked.”

“Yes,” counsel said.

“And the system cleared me.”

“Yes.”

“And she overrode the result.”

“She entered an unofficial concern.”

“Why?”

Counsel turned the page.

In her interview, Rebecca said she did not trust the tool because “those systems miss sophisticated abuse.”

Maya almost laughed.

Sophisticated abuse.

She had booked online with a credit card.

The phrase did not describe evidence.

It described conviction looking for support.

That finding narrowed Rebecca’s responsibility.

It also expanded the company’s.

Why did an employee feel comfortable disregarding an official verification system without documenting contrary facts?

Caroline’s department had encouraged “service discretion” for years.

The phrase appeared in training decks.

Use professional judgment.

Trust crew experience.

Resolve at point of contact.

Those concepts were not wrong.

But no training defined when discretion had to stop.

The shadow watchlist had grown inside that gap.

At the end of the week, Helen Park called Maya at home.

“The board is placing Caroline on administrative leave.”

Maya closed her eyes.

“Based on?”

“Failure to escalate known risk, incomplete ethics review, and credibility concerns in her interview.”

Not a final finding.

A protective measure.

Maya accepted it.

Then Helen added:

“There’s more.”

The outside team had recovered archived messages from an old company-issued tablet used by Caroline’s office.

One message was from Caroline to Rebecca Torres, dated nine months earlier.

It read:

I cannot officially approve the list. Just keep names off customer records unless there is a real incident.

Rebecca replied:

Understood. We know how to handle it.

Maya went still.

Caroline had not created the group.

May you like

She had known enough to know it should never become official.

And instead of stopping it, she had taught them how to hide it.

Related Stories

Other posts