"Martin Keller?"
"Yes. He's responsible for part of the reporting infrastructure. We haven't established whether he altered any records."
"Have you contacted him?"
"Not yet. We want to understand the access logs before we interview him."
"Good."
Elena shared a secure screen.
A spreadsheet appeared.
The first column listed complaint identification numbers. The second contained the date each complaint had been submitted. The third showed the date it had been closed. The final columns listed the reviewing manager and the reason given for the outcome.
Vanessa scanned the entries.
Several caught her attention.
CASE 18-4472 β Passenger discrimination allegation β Closed: insufficient evidence.
CASE 18-4519 β Accessibility assistance complaint β Closed: customer misunderstanding.
CASE 18-4631 β Employee retaliation allegation β Closed: performance management issue.
CASE 18-4708 β Premium seating dispute β Closed: unsubstantiated.
She looked at the dates.
"What do these cases have in common?"
"Three were handled by the same review team," Elena said. "The fourth was reassigned to that team after the original reviewer requested additional witness interviews."
"Why?"
"We don't know yet."
"Who made the reassignment?"
Elena enlarged the spreadsheet.
A name appeared in the reviewer-authorization column.
MARTIN KELLER.
Vanessa leaned forward.
"That's the data infrastructure manager."
"Correct."
"Why would a data infrastructure manager reassign a customer complaint?"
"That's one of the questions we're trying to answer."
Vanessa studied the entries again.
"How many cases did he reassign?"
"At least thirty-seven in the period we've reviewed. We don't yet know whether all of them were improper."
"How many involved discrimination or retaliation allegations?"
"Twenty-one."
Vanessa sat back.
The numbers were not proof of misconduct.
But they were too significant to dismiss.
"Do we have the original complaints?"
"Some. Others are missing from the primary database. We're searching backup archives and email attachments."
"Who closed the cases?"
"Different reviewers. But the final summaries often contain nearly identical language."
Elena opened another document.
Vanessa read the paragraph on the screen.
Following a review of the available information, the complaint could not be substantiated. The employee's actions were consistent with operational requirements, and no further action is recommended.
She read it again.
"How many times does this wording appear?"
"One hundred and eighty-six."
Vanessa stared at the number.
"Across how many cases?"
"Different types of complaints. Passenger service, accessibility, employee conduct, scheduling disputes, and customer discrimination allegations."
"Was the wording generated automatically?"
"We're checking. It may have been a standard template. But some of the cases contain individual details that don't appear to have been considered in the final decision."
"Such as?"
"One complaint describes a passenger being called a liar in front of other customers. Another describes an employee being told to change a witness statement. A third includes the names of four passengers who offered to provide statements. The final review says there were no independent witnesses."
Vanessa felt a familiar chill settle over her.
That was no longer simply a matter of employees behaving badly.
It suggested that the review process might have been designed to produce the same outcome regardless of the evidence.
"Can we establish who created the template?"
"Not yet."
"Then find out."
Elena nodded.
Vanessa looked at the screen again.
A company could survive a rude employee.
It could survive a bad manager.
It could even survive an isolated failure of leadership, provided the organization was willing to acknowledge the mistake and correct it.
But a system that repeatedly dismissed complaints using identical language was different.
Such a system could create the appearance of accountability while ensuring that accountability never arrived.
"Elena," Vanessa said, "I want the investigation expanded to include every complaint that was closed using that language. We need to determine whether the wording was merely administrative or whether it concealed a failure to examine the evidence."
"I'll coordinate with the audit committee."
"And I want the original records preserved before anyone contacts the reviewers."
"Already underway."
"One more thing."
Elena waited.
"Someone changed Priya Shah's schedule after the incident. She also received an anonymous message warning her about discussing internal matters."
Elena's expression changed.
"I've seen it. The report came in earlier this afternoon."
"Do we know who initiated the schedule change?"
"Not yet. The system shows the change was approved by a scheduling supervisor, but we're tracing the original request."
Vanessa looked down at her notes.
"Don't let the investigation become a reason to make her life harder."
"We won't."
"I mean it, Elena. If we need to separate her from the people involved, do so without penalizing her. If she needs a temporary reporting line outside the existing management structure, arrange one."
"Understood."
Vanessa paused.
"And make sure she is paid for any time spent participating in the investigation."
"I'll have human resources review the appropriate arrangements."
"Good."
The meeting continued for another forty minutes.
When it ended, Vanessa remained alone in the room.
She looked at the list of complaints on the screen.
One hundred and eighty-six cases.
Different passengers.
Different employees.
Different airports.
The same language.
The same result.
She thought of Margaret Ellis, the retired teacher whose complaint had vanished.
She thought of Rebecca Miller, the former flight attendant who had been punished for speaking up.
She thought of Priya, sitting in a car outside an airport, wondering whether a schedule change meant that her livelihood was at risk.