Now he looked at them differently.
He opened the supporting records.
A complaint entered on Monday.
A manager's response recorded on Tuesday.
A closure date entered on Tuesday afternoon.
No confirmation from the guest.
Another complaint reclassified from staff conduct to general service.
Another report marked resolved after compensation was offered.
The records did not establish misconduct by themselves. Each entry required context. A guest might accept a refund without needing further contact. A complaint might be correctly reclassified after investigation. A case might be closed because the guest stopped responding.
But the pattern deserved scrutiny.
Adrian opened a blank document and began typing.
Questions for independent review:
-
What criteria govern the classification of guest complaints?
-
Who can change a complaint's category or closure status?
-
Does the system require confirmation from the guest before closure?
-
How do managers' performance evaluations depend on complaint volume?
-
Are employees rewarded for resolving problems or for reducing the number of recorded problems?
-
How are allegations involving discriminatory treatment escalated?
-
What records are preserved when a complaint is reclassified?
-
Can a manager alter a record involving their own conduct or department?
-
How frequently are closure decisions audited independently?
He paused, then added one final question.
- What happens to an employee who refuses to close a complaint they believe remains unresolved?
That question bothered him most.
Systems were built from rules, but they were maintained by people. If the system rewarded employees for suppressing problems, even good employees could become part of the problem without consciously deciding to do harm.
Adrian saved the document.
At 9:16 p.m., his phone vibrated with a message from Miriam Shaw.
The independent team has received your request. Preservation notices are being issued tonight. Please do not contact hotel employees directly about the incident. We will arrange interviews through the formal process.
He replied:
Agreed. Please include the reservation audit trail, payment authorization, lobby security footage, and all internal communications relating to my check-in.
A minute later, another message arrived.
Will do. One additional point: our preliminary review identified differences between complaint closure statistics and the underlying case histories. We are examining whether those differences reflect legitimate reclassification or inappropriate reporting practices.
Adrian read the message twice.
He looked around the suite.
The room was beautiful.
The service, once the immediate confrontation had ended, had been efficient. A staff member had delivered a fresh bottle of water without being asked. The thermostat worked. The curtains closed smoothly. The city beyond the glass appeared almost unreal.
A guest who experienced only the room might have left a glowing review.
A guest who encountered only Emily might have described the staff as professional.
A guest who met Victoria at the wrong moment might have left feeling humiliated.
All three experiences could occur inside the same hotel.
The challenge was to understand what connected them.
Adrian closed his laptop and walked to the window again.
He had entered the Aurelia Grand intending to test the company's hospitality.
Instead, the hotel had given him a reason to question the integrity of its records.
Tomorrow's signing was no longer a simple financial event.
It was a decision about whether Northstar could trust the company it was preparing to own.
And before Adrian could answer that question, he would need to know whether Aurelia Hospitality had been measuring its failures honestly.
The Woman Who Kept the Records
At 7:12 the following morning, Rachel Bennett sat in a small coffee shop on West Forty-Seventh Street, watching the steam rise from a cup she had barely touched.
She had chosen the table at the back because it was quieter there.
She had also chosen it because she could see the entrance.
For six years, Rachel had worked at the Aurelia Grand, first as a guest-relations coordinator and later as a senior case specialist. She had left the hotel eight months earlier, after a disagreement with management that she had described to friends as a professional difference.
That description had been easier than the truth.
Rachel had not left because she disliked hospitality. She had left because she no longer trusted the way her employer defined a resolved problem.
Her work had once been simple in principle.
A guest experienced a problem. Rachel recorded it, investigated it, and helped find a solution. If the problem involved another department, she contacted that department. If the complaint concerned staff conduct, she escalated it. If the guest remained dissatisfied, the case stayed open until someone determined what else could reasonably be done.
The process was not perfect.
Some guests were unreasonable. Some complaints were based on misunderstandings. Some problems could not be solved to everyone's satisfaction.
But the system had been designed to preserve the distinction between an unhappy guest and an unresolved failure.
Then the performance targets changed.
Corporate leadership introduced a new reporting dashboard intended to improve efficiency across Aurelia's properties. The dashboard measured response times, complaint closure rates, guest satisfaction, and the percentage of cases resolved within twenty-four hours.
At first, Rachel welcomed the changes.
The old system was cumbersome. Some complaints sat untouched for days because nobody knew which department owned them. A faster process could help guests receive answers sooner.
But the new dashboard did more than measure speed.