Aggregate confirmed booking records (flights, hotels, transfers) into a traveler itinerary store keyed by traveler ID, with each segment including origin, destination, start time, end time, and confirmation reference.
Infer traveler location at any given time by querying segments where the current timestamp falls between the segment's start and end times; the traveler is at the destination of the last completed segment.
Expose a query API (GET /travelers/{id}/current-location) that returns the inferred city/country and the next confirmed segment details for use by security operations or HR.
Subscribe to a risk intelligence feed (e.g., International SOS, Crisis24) that provides location-based alerts by country or city; join these against your traveler location data to generate duty-of-care alerts.
Implement a mass notification capability that, given an affected region, returns all travelers currently in or transiting through that region and sends them a check-in prompt.
Ensure all location data is handled under your privacy policy and applicable regulations (GDPR); obtain explicit traveler consent for location tracking during onboarding.
Known gotchas
Itinerary-based location is an inference, not real-time GPS; a traveler may extend their stay, miss a flight, or travel off-itinerary — treat the data as probabilistic and design alerts accordingly.
Hotel check-out times mean a traveler may still be in a city hours after their scheduled checkout — add a same-day buffer before moving them to 'departed' status.
GDPR and similar laws require a lawful basis for processing traveler location data; legitimate interest under an employer duty-of-care framework is common but must be documented.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp