Chapter 2 - THE ENVELOPE MARKED PROJECT IVORY
Five years after Patricia Holt told me to find a cheaper motel, an envelope appeared on my desk with two words written across the front.
PROJECT IVORY.
Lily was eleven by then.
The Grand Regent incident had become one of those memories that no longer controlled every room it entered.
Patricia and Karla were gone.
Brian Cole was gone.
Thomas Reynolds had earned his promotion to regional vice president after spending years rebuilding complaint systems rather than defending his own reputation.
Lupita Ramirez had become executive housekeeper at the Grand Regent, then rooms director two years later.
Vance Hospitality had grown from seven hotels to eleven.
Not because I wanted an empire.
I had become suspicious of that word.
Empires depend too much on one person believing scale proves wisdom.
We had added properties carefully.
Milwaukee.
Nashville.
Boston.
Two resort-management contracts.
One airport hotel I initially hated and eventually admitted made money more reliably than several buildings I considered beautiful.
Life had become surprisingly normal.
Lily went to school.
I went to work.
Every year, we bought roses for Sarah.
Every year, Lily chose the most damaged flower.
Every year, I told one story about her mother.
The tradition had changed as Lily grew.
At six, she wanted stories about strawberries cut into hearts.
At nine, she asked about the first time I met Sarah.
At eleven, she wanted the uncomfortable stories.
“Did you ever make Mom really mad?”
“Yes.”
“How?”
“Frequently.”
“Specifics.”
Children become prosecutors with age.
I told her about forgetting Sarah’s birthday once during the first-hotel renovation.
Lily stared at me.
“You forgot Mom’s birthday?”
“I was twenty-seven.”
“That is not a defense.”
“Agreed.”
“What happened?”
“She made me sleep on the couch.”
“Good.”
Then Lily smiled.
“Mom sounds excellent.”
“She was.”
She still was in every important sense.
That Monday morning, Lily had already left for school when my assistant brought the envelope.
“No return address.”
“Mailroom scan?”
“Clean.”
I stared at it.
Five years earlier, I might have opened it casually.
Now I photographed both sides.
Old habits.
Useful ones.
Inside were twenty-three pages.
The first page carried a Vance Hospitality logo.
Current.
Official.
Below it:
PROJECT IVORY — GUEST VALUE OPTIMIZATION PILOT
My stomach tightened.
I knew the phrase.
Not the project.
Six months earlier, our board had approved a revenue-management initiative involving three hotels.
The stated purpose was ordinary.
Better forecasting.
More accurate upgrade decisions.
Improved loyalty targeting.
Reduced fraudulent chargebacks.
Smarter allocation of complimentary amenities.
Hotels already used data constantly.
Occupancy.
Booking channel.
Length of stay.
Loyalty history.
Spend.
That was normal.
But I had never heard the name Project Ivory.
I turned the page.
A scoring table.
Guests ranked from A1 through D4.
Nothing shocking yet.
Then I read the inputs.
Expected room revenue.
Food-and-beverage spending.
Prior upgrade acceptance.
Corporate-account status.
Length of booking history.
Deposit success.
Complaint frequency.
Voucher use.
Booking source.
Home postal code.
Arrival mode.
Language preference.
My hand stopped.
Language preference?
I read again.
One line:
Non-English primary preference associated with increased service time and lower ancillary-spend conversion. Weight: -3.
I stared.
Another:
Airline disruption vouchers: -4.
Another:
Third-party discount platform: -3.
Local address within 25-mile radius: -2 unless event package attached.
Repeated deposit questions: -2.
Then:
Appearance-based discretion: Manager override permitted for “brand-fit concern.”
My blood went cold.
Brand fit.
Five years earlier, Patricia had looked at my faded jacket and decided I was not a normal guest.
Now someone had apparently built software that gave the instinct a spreadsheet.
I turned another page.
Suggested service responses by score.
A1 guests:
Priority upgrades.
Early check-in.
Welcome amenity.
Manager greeting.
Late checkout flexibility.
D-level guests:
Strict deposit enforcement.
No discretionary upgrades.
Limited complimentary recovery.
Manager approval before lobby accommodation during sold-out periods.
That sentence made my jaw tighten.
Lobby accommodation.
Airline families.
Displaced travelers.
People who needed somewhere to sit.
Exactly the kind of guest Patricia once called shelter traffic.
Then I saw the pilot properties.
Grand Regent Chicago.
Vance Nashville.
Regent Boston Harbor.
My own flagship hotel.
I pressed the intercom.
“Call Melissa Chen.”
My assistant paused.
“She’s in Atlanta.”
“Video.”
Five minutes later, Melissa appeared on my screen.
She was now Vance Hospitality’s chief operating officer.
Still blunt.
Still the person most likely to tell me when I was being stupid.
Her hair was shorter.
Glasses new.
Expression irritated because it was 8:15.
“What broke?”
I held up the document.
“Project Ivory.”
Her face changed.
Only slightly.
Enough.
“You know it.”
“Yes.”
“How much?”
“More than you.”
That answer did not improve my morning.
“Explain.”
Melissa exhaled.
“Revenue-management pilot.”
“That is not what I’m holding.”
“What are you holding?”
I read the scoring variables.
She went quiet at language preference.
“Melissa.”
“I never saw that version.”
“Did you know there was a guest ranking system?”
“Yes.”
“Did the board?”
“Broadly.”
“Did I?”
“You approved predictive guest-value analytics.”
I stopped.
There.
Not forgery.
Not hidden signature.
My approval.
“Who designed this?”
“Vendor called Aurelia Guest Intelligence.”
“Internal sponsor?”
“Graham Whitlock.”
Our CFO.
He had joined two years after the Grand Regent review.
Smart.
Disciplined.
Former luxury-resort finance executive.
The board loved him.
So did investors.
“What did Graham tell operations?”
“Pilot predicts service demand and profitability.”
“Profitability is not belonging.”
“I know.”
“Do you?”
She looked at me.
“Yes.”
Good.
I continued.
“Did Lupita know?”
“No.”
“Thomas?”
“Probably partial.”
“Who sent this?”
“No idea.”
Last page.
Typed message.
YOU FIXED WHAT HAPPENED WHEN ONE RECEPTIONIST JUDGED A GUEST BY HIS JACKET.
Next line:
NOW YOUR COMPANY HAS TAUGHT A COMPUTER TO DO IT.
I sat back.
Melissa said nothing.
Then I turned over the final sheet.
There was one more sentence.
ASK WHY THE BOARD VERSION DOESN’T SHOW THE VARIABLES FRONT DESK ACTUALLY SEES.
My pulse slowed.
Sanitized reporting.
Maybe.
Maybe not.
“Preserve everything.”
Melissa nodded.
“No staff-wide alert yet.”
“Agreed.”
“Outside counsel.”
“Yes.”
“Independent data audit.”
“Yes.”
“No Graham interview until records preserved.”
She almost smiled.
“You learned.”
“I paid tuition.”
Then I said:
“Do not shut the pilot down this second.”
Melissa frowned.
“Why?”
“Because I want to know what it actually did before people change behavior because we’re watching.”
She nodded slowly.
“Read-only preservation, then suspend automated recommendations after capture.”
“Exactly.”
Then:
“Find who received D rankings.”
Her face tightened.
“Ethan.”
“What?”
“If the variables are what you say, that analysis is going to be ugly.”
“Then ugly is useful.”
I ended the call.
At 9:02, outside counsel began preservation.
At 9:18, Aurelia Guest Intelligence received notice not to delete training data, scoring logic, client communications, or override history.
At 9:41, Graham Whitlock texted me:
Hearing legal has concerns about Ivory. Call before this gets overblown.
I stared.
Overblown.
Dangerous word.
I did not call.
At 10:07, Lupita called from Chicago.
She did not know the details yet.
Only that systems were being preserved.
“Mr. Vance.”
“Ethan.”
“Something is wrong.”
Not a question.
“Yes.”
“With front desk?”
“Possibly broader.”
Silence.
Then:
“I told Thomas three months ago guests using airline vouchers were getting treated differently again.”
My chest tightened.
“You reported it?”
“Yes.”
“What happened?”
“He sent it up.”
“To whom?”
“Regional revenue team.”
“And?”
“They said the system was improving consistency.”
There.
Consistency.
The favorite word of systems that sometimes industrialize bad judgment.
“Did behavior change?”
“No.”
“Why didn’t this reach Melissa?”
“I thought it did.”
Of course.
Information softened again.
I closed my eyes.
“Lupita.”
“Yes?”
“Do you have emails?”
“Yes.”
“Keep them.”
“I always do.”
I smiled despite myself.
Then she added:
“Mr. Vance?”
“What?”
“Please don’t make this about Patricia.”
I stared.
“Why would I?”
“Because some people here already are.”
“How?”
“They’re saying we warned staff after what happened to you, and now young employees are afraid to use judgment.”
Interesting.
Excuse forming.
“It isn’t about one employee.”
“I know.”
“Good.”
Then Lupita said something I did not expect.
“There’s another problem.”
“What?”
“Last month a woman sleeping in the lobby with two children was asked to leave.”
My body stiffened.
“Guest?”
“She had a reservation for the next night.”
“Why was she there early?”
“Apartment fire.”
My stomach turned.
“Did we have rooms?”
“No.”
“Did we offer alternatives?”
“Eventually.”
“Eventually?”
“She sat outside for almost an hour first.”
Chicago.
January.
I stood.
“Names.”
“I’ll send through counsel.”
Good.
Then:
“Children okay?”
“Yes.”
That mattered first.
The meeting with Graham was scheduled for noon.
Before he arrived, counsel called.
“We pulled preliminary Project Ivory output.”
“How many guests scored?”
“Approximately forty-eight thousand across three properties.”
My stomach tightened.
“Disparities?”
“Too early.”
“Anything obvious?”
Silence.
“Say it.”
“Guests who selected Spanish as preferred language were substantially more likely to receive D-level classifications.”
I closed my eyes.
“Could be correlated with other variables?”
“Yes.”
“Do not call it discrimination yet.”
“Agreed.”
“Voucher guests?”
“Very heavily concentrated D.”
“Local addresses?”
“Also.”
“Appearance overrides?”
Pause.
“One hundred eighty-three.”
I stopped.
Managers had manually applied brand-fit concern 183 times.
“What does that mean?”
“We need notes.”
“Pull them.”
Then Graham Whitlock walked into my office carrying a laptop and the confidence of a man who believed he was about to explain a misunderstanding.
He sat.
“Ethan, I think legal is panicking over a normal revenue tool.”
I looked at him.
“Good.”
He frowned.
“What?”
“Then this should be easy.”
I slid the page across.
Language preference.
Voucher status.
Brand fit.
His face did not change.
That was almost worse.
“These are predictive variables.”
“No.”
“What?”
“They are human variables.”
He leaned back.
“Every hospitality company segments.”
“Yes.”
“Luxury hotels especially.”
“Yes.”
“So—”
“Do you believe a guest who prefers Spanish deserves less service flexibility?”
“No.”
“Then why is it negative three?”
“It correlates with ancillary spend.”
“Why should ancillary spend determine whether someone can sit in our lobby during a crisis?”
“That’s not how the model is intended to be used.”
“Then why does the operational guidance say D-level guests require manager approval for lobby accommodation?”
Silence.
There.
Graham glanced at the document.
“That may be vendor configuration.”
“You sponsored the project.”
“Yes.”
“Did you review configuration?”
“High-level.”
“Did you see board deck?”
“Of course.”
“Did the board deck include language preference?”
“No.”
“Why?”
“It wasn’t material.”
I stared.
He heard it too late.
“Not material to whom?”
Graham’s jaw tightened.
“Ethan, this is a profitability system.”
“No.”
I leaned forward.
“It became a belonging system the second staff used it to decide who gets grace.”
Silence.
Then I asked the question that would define everything after.
“Did you intentionally keep those variables out of the board deck because you knew I would reject them?”
Graham did not answer.
Not quickly enough.
And for the first time that day, I understood Project Ivory might not be a technology mistake.
It might be a governance decision.
One someone had made while assuming I would care more about margins than the people standing in our lobby.
They had not learned the lesson Patricia taught me.
Or worse—
May you like
they had learned it and decided to hide the parts they knew I would recognize.
---
Related Stories
