# Duty of care

Use [PNR_V3](/openapi/webhookeventapi/webhooks/paths/pnr_v3/post) (most preferred) or [TRIP_DETAILS_V3](/openapi/webhookeventapi/webhooks/paths/trip_details_v3/post) to monitor traveler locations and itineraries in real time,
and respond quickly when disruptions or emergencies occur.

## Event flow

The following table describes a typical duty of care workflow using the [PNR_V3](/openapi/webhookeventapi/webhooks/paths/pnr_v3/post) webhook:

| Step | Operation  | Action and next steps |
|  --- | --- | --- |
| 1 | `BOOKING_CREATED` | A traveler creates a trip.
Your system registers upcoming travel activity and begins monitoring. |
| 2 | `BOOKING_TICKETED` | The booking is confirmed and ticketed.
Your system updates the traveler's itinerary with the confirmed details. |
| 3 | `BOOKING_UPDATED` | The traveler's itinerary changes. For example, the airline has announced a 30 minute delay for departure.
Your system updates its records to reflect the new itinerary. |
| 4 | `FLIGHT_SCHEDULE_ CHANGE_PENDING`
or `FLIGHT_CANCELLED` | An airline-initiated disruption occurs (e.g., a flight segment is canceled due to bad weather).
Your system flags this change and proactively notifies the traveler. |