INDUSTRY FIELD GUIDE
Passenger charter itinerary revisions for AI testing
A client may confirm receipt of a proposed itinerary before the operator accepts the revision.
NAICS 481211 · Nonscheduled Chartered Passenger Air Transportation
A client may confirm receipt of a proposed itinerary before the operator accepts the revision. FAA’s charter-type services materials distinguish this part of aviation operations. An operator can use a simulated conversation and record set to test whether an assistant can summarize the currently confirmed plan. FAA charter-type services
Prepare two itinerary versions with different departure windows. Record a passenger acknowledgment, an operator confirmation of only one change, and a later draft that was never confirmed. Ask which window is currently supported and which details need an operator response. Label who issued each record and whether it was a request, acknowledgment, or confirmation. Keep live dispatch decisions outside the task.
Use invented passengers and aircraft identifiers. Remove actual airport access arrangements, aircraft assignments, flight plans, and payments. If a booking intermediary owns part of the correspondence, clear reuse separately.
Describe a charter itinerary evaluation
Original Fiund exercise
Client receipt of a revised itinerary does not confirm every operator change
An original charter-document fixture uses invented roles and departure windows. It contains no passenger identity, aircraft assignment, airport access, flight plan or payment.
| Record | Source | What it records |
|---|---|---|
| CFI1 | Confirmed plan V1 | Departure window W1 and generic service label S1. Operator confirmation explicitly references V1. |
| CFI2 | Proposed V2 and responses | V2 requests W2 and service label S2. Client acknowledges receiving V2. Operator confirms only S2 and explicitly leaves W2 pending; W1 retained meanwhile. |
| CFI3 | Later draft V3 | Proposes W3, unsigned and unconfirmed. No additional operator event supplied. |
Question for the model
Which departure window and service-label change are currently supported, and what remains pending?
Show the reference answer and checks
CFI2 explicitly confirms only S2 while retaining CFI1's W1 pending a response on W2. The client's receipt acknowledgment is not operator acceptance of the requested window. CFI3's W3 remains an unconfirmed draft and does not replace either state. Report the partially confirmed plan with W2 unresolved rather than treat an entire revised itinerary as accepted from one party's acknowledgment or a narrow confirmation.
- Treating client receipt as operator acceptance of an itinerary.
- Extending partial confirmation to all requested fields or selecting an unsigned latest draft.
Fields to preserve
- Itinerary version and issuing role
- Defines source authority.
- Requested versus confirmed field
- Preserves partial acceptance.
- Retained window and pending response
- Makes the current documentary plan explicit.
Test another case
Add operator acceptance of W2 effective after the review cutoff. Require the earlier summary to retain W1 and mention the future change separately only when available.
Use original synthetic correspondence. Exclude actual dispatch and aircraft information; intermediary-controlled messages need independent reuse permission.
Discuss a contribution
Describe the sources you control, the task they could support and what has already been checked. Use the existing-data assessment for an archive or the collection brief for a new recording project. The contributor agreement defines Fiund’s licensing authority and compensation. A guide or fictional exercise does not establish an accepted collection or a sale.