A returning passenger asks for a familiar guide, but the request must remain useful context rather than become a staffing promise.
Track
Assignments
Phase
Staffing preference
Starts with
Passenger preference known
Ends with
Preference visible for staffing
Ops finds a requested-guide preference while preparing passenger context for a CIS. The preference stays visible to the guide manager while the actual booking team remains the operational commitment.
Ops records a requested guide while preparing CIS passenger context.
Past context explains why the passenger may prefer a particular guide.
The choice is limited to guides already represented in that booking context.
This is the key moment: Trailhead stores a preference separately from the booking-team assignment.
Availability and role eligibility still determine whether the request can be honored.
Only the saved booking team establishes an operational commitment.
Records the passenger's preference without presenting it as confirmed work.
Uses the preference as one input when building the actual booking team.
Passenger history and a requested-guide field
Why: Preserve useful relationship context during CIS preparation.
The preference beside the CIS staffing context
Why: Consider the request without mistaking it for a commitment.
A requested guide is a preference; the booking team is the assignment.