Build a schedule change detection pipeline that notifies passengers of material itinerary modifications

Steps

1. Subscribe to an airline schedule data feed or flight status API (such as FlightAware AeroAPI or an OAG schedule feed) for routes covered by active bookings in your system
2. After booking creation, store the exact flight numbers, departure and arrival times, and terminal/gate data; compare these against periodic schedule updates to detect changes
3. Define materiality thresholds: classify changes as minor (under a configurable time threshold, e.g., 30 minutes), significant (departure time shift beyond threshold or terminal change), or major (cancellation or route change)
4. On detection of a significant or major change, trigger a passenger notification via email and push with the updated itinerary, a clear explanation of what changed, and actionable options (accept change, request refund, rebook)
5. For major changes, initiate the IROPS workflow or surface agent escalation options; log the change event with a timestamp for duty-of-care and audit purposes