Anticipation Framework & Service-Design Assessment

Prepared for: the General Manager & Director of Rooms, Brookhaven Convention Hotel · ~280-key full-service convention property, owner-operated under a major brand · illustrative scenario

1 · Executive summary

The property's service is reactive across the pre-arrival and arrival zones — the operation waits for guests to voice needs the property could have anticipated from booking patterns alone. In-stay service is mixed. Departure is anticipatory and strong.

The recommended next action is the Pre-Arrival Brief loop (Anticipation Loop #1 below) — a single, staffable change that converts approximately 60 percent of identified pre-arrival gaps into ahead-of-the-ask service, requires no new headcount, runs in 9 minutes per shift, and uses information the guest knowingly provides at booking.

The principal risk is staffing capacity to sustain anticipation loops on the worst-staffed shifts (Sunday overnight, holiday weeks). Every loop in this framework is sized to run on the property's actual labor model, not the staffed-for-peak fiction.

2 · Scope of this deliverable

What this deliverable covers: A service-design assessment of all four journey zones (pre-arrival, arrival, in-stay, departure) for the property's primary guest segments (convention attendee, conference organizer, business transient, weekend-leisure), plus an Anticipation Framework with five prioritized anticipation loops.

What it explicitly does not cover: Staff-demeanor coaching (HOS-02 Presence Architect); systematization of anticipation loops into brand-required standards (HOS-03 Excellence Discipline); recovery after service failures (HOS-05 Service Recovery Playbook); guest-data legal duties (route via Cross Suite 00 to counsel and the ADA suite for digital-accessibility dimension).

Property profile: 280 keys, full-service, owner-operated under a major brand (categorical descriptor), 14,000 sq ft of meeting space, three F&B outlets including in-house catering, dominant segments are convention attendee (40%), conference organizer (15%), business transient (25%), weekend leisure (20%). Staffing model: brand-standard for tier; minimum-staffed Sunday overnight and during holiday-week sequences.

3 · Service-design assessment — by journey zone

Pre-arrival zone · Reactive

The property holds all the information needed for substantive pre-arrival anticipation — booking source, stay purpose, prior-stay history, arrival flight number where collected, group affiliation, accessibility requests, dietary requests — but does not act on any of it ahead of arrival. The first time the property does anything with the information is at the front desk during check-in. The pre-arrival window is silent.

Anticipatory gaps: Returning guests do not see the property remembering them (loyalty signal cost). Late-arrival flights are not surfaced to the night audit before the shift starts (operational cost). Pre-collected dietary restrictions are not surfaced to F&B before the breakfast shift the guest will eat (guest cost). Group affiliations are not flagged so the property can recognize the guest as a returning conference attendee (relational cost). Accessibility requests are routinely received and then re-asked at the desk (dignity cost — the dignity standard says this is unacceptable).

Goodwill cost: high. Delivery cost: low — the information is already in the PMS. The cost is design and discipline, not data.

Arrival zone · Reactive

Check-in is transactional. The agent reads what is in front of them on screen; the guest provides what the system asks for. Returning guests are not greeted as returning unless the loyalty system surfaces it automatically. Convention attendees are not connected to their group affiliation unless they volunteer it. Late-arriving flights are not anticipated in room readiness.

Anticipatory gaps: The property treats every guest as new at check-in. The pre-arrival information that should be visible to the desk agent before the guest reaches the counter is not visible.

Goodwill cost: high (it costs more to recover from "you didn't remember me" than to remember). Delivery cost: low.

In-stay zone · Mixed

The property has strong in-stay anticipation in some pockets (the concierge team anticipates restaurant reservations and event needs well; the housekeeping team anticipates linen and amenity preferences for return guests in some cases). Other in-stay surfaces are reactive (room-service patterns are not analyzed for the long-stay guest; the second-night meal request is not anticipated; the conference-organizer's prep-day-before needs are not anticipated).

Anticipatory gaps: Long-stay guest patterns are not surfaced to the operating team. Conference-organizer pre-conference setup needs are not pre-positioned.

Departure zone · Anticipatory

The departure zone is the property's strongest. Express checkout works. Folio review is anticipatory. Bell service is pre-positioned. The departure-day breakfast accommodation for early-flight guests is in place.

Anticipatory gaps: Minor — the post-stay follow-up loop is reactive (the property responds to guest reviews; it does not initiate the post-stay loop on returning-guest cadence).

4 · The Anticipation Framework — five prioritized loops

Sequenced by goodwill cost saved per dollar of delivery cost added. The first three loops are recommended for adoption within 30 days; loops 4 and 5 require staffing review before commitment.

Anticipation Loop 1 · HIGHEST PRIORITY

Pre-Arrival Brief (15-minute pre-shift huddle for arriving guests)

Signal: The next-12-hour arrival list filtered for any of: returning guest (loyalty profile or prior-stay history), accessibility request, dietary restriction, special-occasion flag, conference affiliation, late flight, VIP designation. Decision rule: If any flag, the brief surfaces it. Owning role: Front Office Manager (compile); Front Desk + F&B + Housekeeping leads (receive); GM (review weekly). Guest-visible action: the desk agent greets a returning guest as returning, addresses the accessibility request without re-asking, surfaces the dietary preference to F&B before breakfast. Confirmation: the brief is filed; the weekly GM review samples five briefs against guest-feedback themes.

Staffability: runs in 9 minutes per shift; uses information already in the PMS; requires no new headcount; runs on the worst-staffed Sunday overnight as a 4-line printed brief left at the desk.

Anticipation Loop 2

Conference-Organizer Prep-Day Anticipation

Signal: Group-booking calendar shows a conference organizer arriving the day before their conference. Decision rule: The organizer receives a one-page pre-prep-day brief at check-in (BEO confirmation, F&B contact for last-minute changes, AV check time, room-set lead) and is greeted by the Director of Catering by name within 30 minutes of arrival. Owning role: Director of Catering. Guest-visible action: the organizer walks into a property that is visibly ready for the conference. Confirmation: post-conference debrief with the organizer captures whether the prep-day anticipation made the difference.

Staffability: applies on conference-prep-days only (~85 days/year for this property); requires one Director of Catering touchpoint, no new headcount.

Anticipation Loop 3

Returning-Guest Welcome (Loyalty Signal Recovery)

Signal: Guest checking in has prior stays at this property (PMS history, not just loyalty tier). Decision rule: The desk agent acknowledges the return verbally (named greeting, "welcome back") plus one specific touchpoint from the prior stay (room type preserved if available, restaurant the guest used, amenity preference held). The acknowledgment is sized to the prior-stay depth: 1-prior-stay = brief; 3+ prior stays = personal note in room. Owning role: Front Office Manager (training); Front Desk (delivery); GM (sample audit). Confirmation: guest-satisfaction free-text comments are sampled monthly for "returned and they remembered me" themes.

Staffability: runs on every shift; uses information already in PMS; the front office team is the only team that needs to deliver it; runs at no labor cost above current.

Anticipation Loop 4 · staffing review required

Late-Flight Arrival Pre-Position

Signal: Guest's flight (collected at booking where shared) lands within 90 minutes of midnight. Decision rule: Night audit pre-positions the room (express check-in pack at the desk, light amenity, water, late-arrival snack offer if available from F&B); the desk does not ask the tired guest the standard 6 questions, asks only "Is this room ready for you?" Owning role: Night Audit (with F&B coordination). Confirmation: sample late-flight arrivals against guest-feedback themes.

Staffability: applies on late-flight nights only; the night audit has the capacity if the late-arrival snack offer comes from a pre-positioned amenity rather than F&B kitchen activation. Stage review with the Director of F&B and Director of Rooms before committing.

Anticipation Loop 5 · staffing review required

Long-Stay Guest Pattern Recognition

Signal: Guest has been in-house 4+ nights. Decision rule: Front Office and Housekeeping each capture one observed preference (the housekeeper notes the room arrangement preference; the desk notes the breakfast pattern); on night 5, the pattern is surfaced to the guest in a discreet touchpoint that confirms the preference is being maintained ("we have you in for breakfast at 7:15 with the table by the window — please let us know if you would prefer a change"). Owning role: Director of Rooms (the integration point). Confirmation: the long-stay guest post-stay survey question on "Did we know you by the end of the stay?"

Staffability: applies to long-stay guests only (a minority of the property's mix); requires Director-of-Rooms-level integration discipline; stage review with the labor team before launch.

5 · Recommendations

Implement Anticipation Loop 1 (Pre-Arrival Brief) within 30 days. Owner: Front Office Manager (compile); GM (review weekly). Effort: 9 minutes per shift; no new headcount; uses PMS data only. Dependencies: PMS report configuration; Front Office Manager calendar discipline. Sequence: pilot 2 weeks, refine, full deployment.
Implement Anticipation Loop 3 (Returning-Guest Welcome) within 30 days. Owner: Front Office Manager. Effort: training + sampling discipline; no new headcount. Pairs with Loop 1.
Implement Anticipation Loop 2 (Conference-Organizer Prep-Day) within 60 days. Owner: Director of Catering. Pilot with the next three conference-organizer arrivals; refine; standard.
Stage-review Loops 4 and 5 before committing. Owner: Director of Rooms + Director of F&B + GM. Staffing model implications need a labor review before either loop becomes standard.
Hand the resulting anticipation loops to HOS-03 (Excellence Discipline) for systematization into standing standards. Owner: GM + Cross Suite 00. Once a loop has run for 90 days and produces the goodwill outcome, it becomes a brand-required standard, not a special initiative.
Coordinate with HOS-02 (Presence Architect) on the desk-team training that the Pre-Arrival Brief enables. Owner: GM + Cross Suite 00. The brief gives the desk agent the information; HOS-02 owns how the desk agent uses it.

6 · Open questions / required senior input

The GM decides whether the Pre-Arrival Brief runs every shift or only on guest-volume-above-threshold shifts. Recommendation: every shift, including the worst-staffed; the 9-minute investment compounds.
The Director of F&B decides whether Loop 4 (late-arrival snack offer) is in scope; this depends on F&B labor model and pre-positioning capacity.
The senior advisor decides whether Loop 5 needs HOS-03 (Excellence Discipline) involvement immediately or only after the 90-day pilot.
The Director of Rooms confirms that PMS-data access for the Pre-Arrival Brief is permitted under the brand's data-handling clauses (route via Cross Suite 00 to AIS-04 if the brand-controlled tech stack imposes any constraint).

7 · Sources & method note

Sources: 90 days of guest-feedback themes provided by the property (web reviews + brand satisfaction surveys + post-stay sentiment captured by the property), the property's PMS booking-source and stay-purpose data, the brand's service-standards manual at categorical level (cited by clause, not reproduced), the published guest-journey discipline from the firm's foundational hospitality discipline curriculum. All client-confidential sources are described categorically. No external guest, employee, or brand name appears in this brief.

Method: the assessment is based on the guest-feedback themes the property supplied (not on a site visit). A site visit would refine the staffability assessments for Loops 4 and 5. The Anticipation Framework is a structural design; the framework is staffable at the property's actual labor model.

Reviewed and signed by Vernetta Kinchen

Chief Executive Officer & Principal · Cross Suite Advisory — N M E D LLC

This brief is delivered as the firm's senior advisory analysis to the General Manager. The AI agent assembled the journey-zone assessment and drafted the five anticipation loops; my judgment shaped the sequencing, the staffability calls, and the dignity-standard framing on the accessibility-request gap. The brief does not leave the firm until I sign it. Not legal advice on guest-data or accessibility duties — route those via Cross Suite 00 to AIS-04 and the ADA suite.

How this deliverable is produced. Cross Suite Advisory's agents are built on Anthropic's Claude AI, designed and trained around the Principal's three decades of practice across executive advisory, governance, hospitality, and senior leadership development. The firm's three decades of executive hospitality practice sits inside the agents; Claude provides the reasoning engine. Every final report routes to the Principal for review and signature before it reaches a client.