The first photograph Lily placed on our refrigerator after returning home was not one of the Chicago skyline. It was her drawing of Daniel's upside-down pancake rabbit. She secured it with a small magnet shaped like a strawberry, stepped backward, and announced that he could see it from wherever he was.
I stood beside her in our kitchen, holding the shortened rose we had managed to bring back from Chicago. Several petals had loosened during the flight, but the flower had survived. I placed it in a narrow vase on the windowsill above the sink, where Daniel used to leave his coffee cup after breakfast.
The house felt both familiar and strangely quiet after four days in a busy hotel. Lily disappeared into her bedroom to reunite Rabbit with the other stuffed animals. I unpacked our suitcase, started a load of laundry, and found myself enjoying the ordinary sounds of home.
By Wednesday morning, the investigation was waiting for me again.
Elaine had scheduled a secure meeting with David and two members of our internal compliance team. The purpose was to review the missing audit documents from the Grand Regent. I joined from my office at headquarters, where Daniel's original handwritten hospitality statement remained framed behind my desk.
The compliance manager, Andrew Chen, began by explaining what the records showed. Robert's office had submitted monthly certifications indicating that guest complaints were reviewed for recurring patterns and appropriate escalation. Those certifications were logged in the management system.
The supporting audit files, however, were inconsistent.
Some months contained detailed worksheets. Others had only short summaries. In the periods surrounding Denise Walker's and Marcus Bell's complaints, several worksheets were absent from the expected folder.
Andrew had examined the access history.
"The files weren't all deleted," he said. "Some appear never to have been uploaded into that location."
"Can we determine whether they existed elsewhere?" I asked.
"We're checking archived email attachments and local storage backups."
David leaned forward.
"Does the certification require a completed worksheet?"
"Yes. The policy says the monthly review must be documented."
I looked at the dates on the screen. Robert had certified completion of reviews that could not yet be verified through supporting records.
That was a procedural failure. Whether it was a deliberate misrepresentation remained unresolved.
I asked Andrew to explain the difference between the certification itself and the underlying work.
"A manager can conduct a review and fail to store the documentation correctly," he said. "That's poor recordkeeping. But if the manager certifies a review that never happened, that's a more serious issue."
"Can we establish which occurred?"
"Not yet."
I thanked him for making the distinction clear.
We reviewed the available complaint summaries. Denise Walker's case had been marked resolved after a partial refund. Marcus Bell's had been closed following a credit toward a future stay. Both records contained brief notes stating that employees had been reminded of service expectations.
There was no documentation showing what those reminders involved, who delivered them, or whether follow-up occurred.
Elaine pointed out that Patrick's performance evaluations did not mention either complaint.
"That doesn't necessarily mean there was no coaching," she said. "But the required documentation is missing."
I asked whether Robert had been questioned directly about the audits.
"He'll receive the records today and have an opportunity to explain them."
"Good."
After the meeting, I walked to the window overlooking downtown Denver. Our headquarters occupied two floors of a renovated office building. Daniel and I had rented our first workspace in a converted storage room above a hardware store. When the business expanded, he had insisted that we retain the original folding table, even after we could afford proper conference furniture.
The table now stood in a small meeting room down the hall.
I sometimes used it when difficult decisions reminded me how the company began.
That afternoon, David and I sat at that table to review the broader implications of the Grand Regent investigation. We spread the current performance evaluation templates between us and examined the sections relating to guest service.
The language was generous. Employees were expected to demonstrate initiative, compassion, professionalism, and good judgment.
But the scoring system placed heavier numerical weight on productivity and efficiency.
A housekeeper who spent extra time helping a guest could receive a positive comment for service while losing measurable points for falling behind schedule.
A receptionist who closed a difficult interaction quickly might meet efficiency expectations even if the guest left dissatisfied.
The contradiction was subtle enough to escape casual review.
Once I saw it, I could not ignore it.
"How long have we used this weighting?" I asked.
David checked the revision history.
"About eighteen months."
The timing overlapped with Robert's appointment, but the framework had been developed at corporate headquarters for multiple properties.
I had approved it.
David had approved it.
The operations team had recommended it.
No one person had created the problem.
I studied the form and remembered the meeting where we discussed labor costs. The company had expanded rapidly, and several properties were struggling with inconsistent staffing expenses. We wanted clearer expectations and more reliable comparisons.
The objectives were legitimate.
But we had failed to test how employees would respond when different expectations competed.
"An employee shouldn't have to choose between helping someone and protecting their performance score," I said.
David nodded.
"We need a way to account for service interruptions."
"Not just a box they can check afterward. A real process that supervisors understand."
We began outlining a revised approach. Guest assistance would be documented as part of service performance rather than automatically treated as lost productivity. Supervisors would be required to consider the circumstances behind missed targets. Employees would have a way to challenge evaluations that ignored legitimate guest needs.
I also wanted to review how complaints affected management bonuses.
David warned that the incentive structure involved complex calculations across properties.
"I know," I said. "But complexity isn't an excuse to leave it untouched."
By late afternoon, Elaine called with an update from Chicago.
Robert had been given the audit records and asked to explain the missing documentation. He maintained that monthly complaint reviews had occurred but acknowledged that some worksheets might not have been properly retained.
When questioned about Denise and Marcus, he said the matters had been delegated to the front-office manager after compensation was authorized.
Elaine asked why he certified the monthly reviews without verifying the underlying documentation.
Robert said he relied on department managers to complete their responsibilities.
I listened carefully.
Delegation was necessary in an organization of that size. A general manager could not personally handle every complaint or examine every reservation.
But certification carried responsibility. Signing a review meant more than assuming someone else had completed it.
"Has anyone confirmed whether the front-office manager conducted those reviews?" I asked.
"Not yet. We're interviewing him tomorrow."
I asked Elaine to continue.
Robert's explanation might establish negligence rather than deliberate concealment. Either way, repeated failures to verify serious complaints could justify corrective action.
After the call, I went home earlier than usual.
Lily was at the kitchen table with my mother, carefully shaping cookie dough into uneven circles. Flour covered her cheeks, and Rabbit sat nearby wearing a paper apron.
My mother looked up as I entered.
"You look tired."
"I am."
She handed me a damp cloth.
"Then wash your hands and help us."
For the next half hour, I measured chocolate chips, rolled dough, and listened to Lily explain why Rabbit needed his own cookie. My mother pretended not to notice when Lily added extra chocolate to one batch.
The ordinary domestic chaos helped me think clearly.
Later, after Lily went to bed, my mother stayed for tea.
She asked how the investigation was progressing. I explained that we had found significant failures in complaint documentation and employee evaluations, but that some questions about intent remained unresolved.
My mother listened, then asked whether I was disappointed in Robert.
"Yes."
"Because he may have acted badly?"
"Because he was trusted to notice problems before they reached this point."
She considered my answer.
"And are you disappointed in yourself?"
I looked down at my cup.
"More than I expected."
She did not immediately respond.
I explained that the company had grown so quickly after Daniel died that I had depended heavily on reports and executive summaries. I had traveled, reviewed numbers, approved plans, and trusted managers to translate our values into daily practice.
Most of the time, that trust had been justified.
But the Grand Regent showed how much could go wrong between a boardroom decision and an employee standing in front of a guest.
My mother reached across the table and rested her hand over mine.
"Daniel trusted people too," she said. "He just made a habit of checking how the work felt to the people doing it."
I remembered him spending an entire afternoon helping housekeepers after an unexpected staffing shortage at our first hotel. He had returned home with sore shoulders and a new appreciation for how unrealistic some of our cleaning schedules were.
The next morning, he changed them.
He had never considered that a contradiction between values and procedures should be resolved through a better speech. He changed the procedure.
I went to bed thinking about that distinction.
On Thursday, Elaine's team interviewed the former front-office manager responsible for the complaint records. The man had left the Grand Regent several months earlier for another property outside our company.
His account added another layer to the investigation.
He acknowledged that complaint reviews were sometimes shortened during busy periods. He said Robert emphasized keeping guest satisfaction scores high and avoiding unnecessary escalations.
But he denied receiving instructions to conceal allegations of discrimination.
When asked why Denise Walker's complaint had not been forwarded, he said he believed the partial refund resolved the situation.
Elaine asked whether he had reviewed the allegation about selective treatment.
He admitted he had not examined that portion of the statement carefully.
The explanation aligned with Robert's account in one respect: the system had treated compensation as closure.
Yet the former manager also said Robert personally reviewed the monthly complaint summaries before certification.
That detail contradicted Robert's suggestion that he relied entirely on department managers.
Elaine arranged a follow-up interview.
I asked her to give Robert the opportunity to respond to the discrepancy and review any relevant emails or meeting notes.
By Friday afternoon, Andrew had recovered archived correspondence showing that Robert received monthly complaint summaries with flagged cases highlighted for review.
Denise Walker's case appeared in one of those summaries.
Marcus Bell's appeared in another.
The emails did not prove Robert read every word. They did, however, establish that the information had been sent directly to him before he certified the reviews.
One message from the former front-office manager asked whether a complaint involving Patrick should be referred to corporate human resources.
Robert's response was brief.
He instructed the manager to resolve the guest's concerns locally and avoid unnecessary escalation unless additional evidence emerged.
I read the sentence several times.
It did not explicitly direct anyone to conceal misconduct.
But it showed Robert making a decision about escalation after a complaint had already raised concerns serious enough to trigger company policy.
Elaine said the next step was to determine whether Robert understood that requirement at the time.
I knew the answer might not change the fact that he had failed to follow it.
But it could affect how we evaluated his responsibility.
That evening, I received a message from David containing a photograph of the Grand Regent's lobby. It showed the gold crest behind reception and the words Daniel and I had chosen years earlier.
He had taken the picture during his visit.
Beneath it, he wrote that the hotel's employees were asking whether the company intended to change its service expectations.
I replied that we did.
Then I added something else.
The changes could not stop at Chicago.
We needed to examine the same procedures across every property we owned.
I closed my laptop and looked at Daniel's photograph on the bookshelf.
For years, I had thought preserving his legacy meant keeping the company successful.
Now I understood that success could conceal drift if nobody examined what the numbers required people to do.
Robert's missing audits had exposed a failure of management.
The broader review was exposing a failure of oversight.
And the responsibility for correcting that second failure belonged to me.
Click here to continue reading: PART 11: When the Investigation Reached Its Findings, I Had to Decide Whether Correcting the Hotel Meant Removing the People Who Had Failed It
The Night My Exhausted Daughter and I Arrived at Our Hotel and Discovered How Quickly Strangers Could Decide We Did Not Belong
Part 10 of 15
