Three days after the incident, the independent audit team began reviewing Meridian Holdings' internal records.
The investigators examined customer complaints, employee communications, reservation histories, and management reports from twelve properties.
The early findings were disturbing.
At several locations, managers had classified complaints about disrespectful treatment as routine service disagreements. In some cases, customers had received apologies. In others, their complaints had been closed without meaningful investigation.
The pattern was not identical at every property.
Some managers had acted carelessly. Others appeared to have misunderstood company policy. A smaller number had repeatedly ignored concerns raised by employees.
The investigators did not assume that every allegation was true.
They compared written reports with reservation logs, security footage, witness accounts, and internal communications.
Gradually, a clearer picture emerged.
The Grand Meridian had been one of the worst-performing properties in terms of complaints involving judgments about customers' appearance.
Richard Caldwell had not invented the company's reporting weaknesses, but he had used them to avoid scrutiny.
Meanwhile, the audit uncovered an email sent by Adrian Mercer's office fourteen months earlier.
The message instructed regional managers to reduce unnecessary escalations and resolve customer concerns locally whenever possible.
On its own, the instruction was not improper.
Companies routinely establish procedures to handle ordinary complaints efficiently.
But an attachment included with the email raised questions.
It contained a proposed performance framework that evaluated managers on revenue, customer retention, and the number of complaints escalated to corporate headquarters.
A high number of escalations could reduce a manager's performance rating.
The framework did not instruct managers to mistreat customers.
However, it created an incentive to keep complaints from reaching senior leadership.
The audit team discovered that Richard had repeatedly cited the framework when explaining why he closed complaints locally.
He had also received several messages praising the Grand Meridian's low escalation rate.
Daniel read the findings in his office.
"Who designed this performance framework?" he asked.
Victoria sat across from him.
"The initial draft came from the operations strategy team. It was reviewed by Adrian's office and approved as part of the regional performance system."
"Was the potential for misuse discussed?"
"We found a message from a compliance analyst raising concerns about how the escalation metric could be interpreted."
"What happened to the concern?"
Victoria opened another file.
"The analyst recommended that serious allegations be excluded from the metric and reviewed independently. The recommendation was acknowledged but not incorporated into the final version."
Daniel looked at the date.
"Who rejected it?"
"The available records point to a decision made within Adrian's office. We are still verifying the specific approver."
Daniel leaned back.
The issue was no longer limited to an arrogant manager.
A poorly designed incentive had encouraged employees to minimize complaints rather than investigate them.
Richard had made his own choices, but the company had created conditions that made those choices easier to conceal.
"Continue the review," Daniel said. "I want the complete approval chain."
Two days later, Adrian was called to a formal interview.
At first, he remained confident.
He explained that the performance framework had been designed to improve efficiency and reduce administrative delays.
He denied instructing anyone to discriminate against customers or conceal substantiated misconduct.
The investigators agreed that no evidence currently demonstrated a direct instruction from Adrian to mistreat guests.
Then they presented the message from the compliance analyst.
Adrian read it carefully.
"I don't recall seeing this particular recommendation."
The investigator placed another document on the table.
It was an acknowledgment from Adrian's executive account confirming receipt of the analyst's concerns.
Adrian's expression changed.
"I receive hundreds of emails."
"That may be true," the investigator replied. "But your office marked this recommendation as reviewed."
Adrian adjusted his position.
"Someone on my team may have handled it."
"Who?"
"I would need to check."
The investigators continued.
They presented records showing that Adrian had personally approved the performance framework after the compliance concern was raised.
Adrian argued that the approval related to the broader program rather than the disputed metric.
But the supporting documents showed that the metric was explicitly included in the final version.
Then came the most damaging discovery.
An internal message from Adrian to a regional director stated that the company needed to avoid "unnecessary reputational exposure" from complaints that could be resolved without corporate involvement.
The message did not explicitly authorize misconduct.
Nevertheless, when read alongside the compliance warning and the performance incentives, it suggested that Adrian had prioritized reputational control over transparent reporting.
The investigators asked whether he understood that employees might interpret the message as pressure to keep complaints out of the system.
Adrian looked at the document.
"I did not intend that interpretation."
"Did you consider it possible?"
He hesitated.
"I suppose it was possible."
"Did you revise the guidance after the compliance analyst raised concerns?"
"No."
The room became silent.
For the first time, Adrian had no convincing explanation.
He had not personally ordered Richard to humiliate customers.
But he had helped approve a system that rewarded low escalation rates, failed to incorporate a warning about foreseeable misuse, and communicated priorities that could discourage transparency.
The distinction mattered.
So did the consequences.
Following the interview, Adrian was placed on temporary leave pending the completion of the investigation.
He left headquarters through a private entrance.
The news did not become public immediately, but senior executives quickly learned that the chief operating officer's authority had been suspended.
Richard heard about the development from his attorney.
"Adrian Mercer has been placed on leave?" he asked.
"Yes."
Richard stared at the wall.
He had once believed Adrian would protect him.
Now he realized that the company's problems reached far beyond his own conduct.
Yet that discovery brought him little comfort.
The audit did not erase his decisions.
It merely explained why nobody had stopped him sooner.
And when Daniel Brooks announced the findings to the board, he made one thing clear.
The company would not use systemic failures to excuse individual misconduct.
Nor would it blame one manager for problems created by senior leadership.
Everyone would be judged according to the evidence.
For the first time in years, Meridian Holdings was being forced to examine not only what its leaders had done, but also what they had allowed to happen.