Member expectations
Members expect the club to know their preferences before they arrive—wine, table, server, dietary notes—without repeating themselves every visit.
VIP preferences
Legacy families and founding members have unwritten rules—preferences live in staff memory instead of a system the whole team shares.
Private dining coordination
Three private rooms, public dining, and a member event tonight—kitchen and service staff coordinated by phone instead of one production picture.
Recurring reservations
Every Friday at 7:30, same table, same bottle—until a private function books the room and nobody flagged the conflict until the member arrived.
Exclusive events
Member galas and legacy celebrations happen once a year—prep and staffing rebuilt from scratch because last year's execution notes never reached the kitchen.
Family traditions
Anniversary dinners and holiday tables span generations—preferences and history lost when a longtime server retires.
Member communication
Event invitations, preference updates, and open requests scattered across email, texts, and the front desk—not one member record.
Labor scheduling
Intimate service requires consistent faces—schedules built for volume don't preserve the server relationships members trust.
Inventory
Member-favorite wines and seasonal ingredients—pars sized for covers, not for the member who always orders the same bottle.
Executive visibility
GM learns member satisfaction slipped from a board conversation—after three weeks of missed preference notes.
Staff consistency
New hires don't know member history—service feels impersonal until the member explains preferences the club should already know.
Seasonal programming
Summer terrace, holiday gala, spring wine series—each season needs different staffing and prep, planned from memory not member registration data.