Cross-Property Guest Memory: Six Tests for a Prepared Return

What is cross-property guest memory?

Cross-property guest memory is the permitted reuse of relevant knowledge about the same individual at another participating location, with checks for identity, current context and the receiving team’s service capability. A familiar welcome depends on all four conditions. Copying a profile alone does not establish continuity.

This paper sets out AFG’s proposed acceptance tests for hotel groups and cruise operators. GuestMemoryOS’s public enterprise proposition describes group continuity within agreed identity, permissions and deployment scope. That proposition should be tested for the operator’s ownership and systems arrangements. It is not evidence of a completed fleet-wide deployment. [1]

Start with the person, not the room or payer

A room number changes hands. A booking organiser may travel with different companions. A shared email address may belong to a household rather than identify the person who made a request. The receiving property needs a justified match to the individual concerned.

For an acceptance exercise, create fictional profiles for two people with similar names and a party whose organiser changes between visits. Ask which evidence links the returning person to the retained knowledge. Include an unresolved case and check that the receiving team is prompted to clarify rather than confidently welcoming the wrong person.

The individual identity article explains the underlying distinction. The attribution measure turns it into a review result, retaining unresolved cases in the reported population.

Agree the sharing boundary before the first transfer

Set out which locations participate, which roles receive information and which service purposes are in scope. Map the parties responsible for operating and governing the arrangement. A common brand name by itself does not settle those responsibilities.

The service team may need the current preparation instruction without receiving the entire historical account. A manager investigating an error may require a different view. Marketing reuse requires its own applicable permissions and purpose assessment; it should not be silently inferred from permission to prepare a room.

Test access with a receiving role that is in scope and one that is outside it. Ask what happens if a location leaves the participating group or an employee changes role. Include previously exported or downloaded working material in the operational review.

NIST’s AI Risk Management Framework offers a general basis for considering trustworthiness in context. It does not determine the permissions for a hospitality group or establish compliance in a jurisdiction. [2] Use the operator’s governance review to settle the actual deployment rules.

Transfer the intent and check local feasibility

In a fictional example, Alex enjoyed a quiet breakfast on a villa terrace. A receiving city hotel has no terrace. Transferring “terrace breakfast” as a mandatory task creates a promise the hotel cannot keep. A useful brief preserves the context and prompts a suitable local option, such as a quieter table, subject to the guest’s current wishes.

Likewise, a particular room setting may depend on local equipment. Retain units and the guest’s intent, then check whether the receiving property can deliver it. Do not substitute a superficially similar amenity without considering the underlying request.

For a cruise transfer, include the receiving ship’s venues, operating times and available services in the exercise. The goal is appropriate recognition in a new environment. The cross-asset article describes the opportunity; this test examines the operational translation.

A returning guest brings a new context

Review the age and scope of retained knowledge. A business visit, a family holiday and a short transit stay may involve different priorities. Current instructions should inform preparation even where a previous preference remains part of the historical record.

The UK ICO’s accuracy guidance explains that whether information needs updating depends on its intended use. [3] AFG’s operational application is to distinguish an accurate record of a past request from an instruction suitable for this visit. That distinction supports service design; it does not substitute for jurisdiction-specific governance.

The memory lifecycle supplies review states. The receiving team should be able to see that confirmation is needed and avoid converting a tentative preference into an automatic promise.

Six transfer scenarios to include in a trial

Record the deployment version, participating locations and results for each scenario. A test in two configured locations establishes behaviour within that scope. Expansion to another brand, franchise arrangement or ship requires another explicit acceptance decision. Use the pilot study to evaluate live service outcomes after the transfer behaviour is understood.

Sources and evidence notes

[1] AFG Holdings. GuestMemoryOS enterprise group continuity.

Product and deployment proposition. Group scope and integrations require agreement with the operator. Source reviewed 25 September 2026.

[2] NIST. AI Risk Management Framework.

Official overview of the voluntary framework. General AI evaluation context, not certification. Source reviewed 25 September 2026.

[3] Information Commissioner’s Office. Principle (d): Accuracy.

Official UK guidance; sections on opinions, sources and keeping information current. Jurisdiction-specific guidance. Source reviewed 25 September 2026.

Related AFG documents

• Enterprise group continuity
• Cross-asset portability
• Individual guest identity