INDUSTRY FIELD GUIDE
Travel agency ticketing and itinerary status records for AI
Travel records can include a priced itinerary, an issued ticket and a later refund event.
NAICS 561510 · Travel Agencies
Travel records can include a priced itinerary, an issued ticket and a later refund event. DOT’s buying and refund guidance explains several points where ticket status and the selling party matter. A travel agency can build a staged evidence exercise around those distinctions. DOT buying a ticket · DOT refunds
Invent two itineraries with the same departure time. Mark one as quoted and issue a dummy ticket against the second. Then add a refund request that has no settlement evidence. Ask what the agency can document about issuance and refund status. Include the ticket reference and status event in the answer key instead of treating the itinerary date as proof.
Use fabricated booking references and original screen mockups. Exclude real passenger names, itinerary histories, passports, payment tokens and booking-system exports.
Describe a fictional ticket status sample
Original Fiund exercise
A priced itinerary, issued ticket and refund request describe different states
Two imaginary itineraries use invalid booking references and original mock screens. No passenger, passport, payment token, actual ticket or booking-system export appears.
| Record | Source | What it records |
|---|---|---|
| TA1 | Itinerary A | Departure slot T, priced quote Q-A. Status QUOTED; no issued-ticket event. |
| TA2 | Itinerary B | Same departure slot T, distinct booking B. Original dummy ticket event I-B explicitly links to B and is labeled ISSUED. |
| TA3 | Refund record | Request R-B asks for a refund of I-B. No approval, settlement or completed refund event supplied; draft summary calls both itineraries ticketed and B refunded. |
Question for the model
Which itinerary has documented ticket issuance, and what refund state is supported for B?
Show the reference answer and checks
TA2 explicitly supports issuance for itinerary B through I-B. TA1 remains a priced quote even though its departure slot matches B's. TA3 records a refund request for I-B without approval or settlement evidence, so B's completed refund is unverified. Correct the draft's two status errors and keep quote, ticket and refund events distinct. The fixture does not determine refund entitlement or perform a booking or payment action.
- Treating a priced itinerary as an issued ticket.
- Inferring a completed refund from a request or merging bookings by departure time.
Fields to preserve
- Itinerary and invalid booking ID
- Defines the record.
- Quote versus issued-ticket event
- Separates stages.
- Refund target and settlement evidence
- Limits the outcome claim.
Test another case
Add an issued ticket for A but a refund approval only for B. Require issuance and refund states to update independently without inventing settlement.
Use original mockups and nonvalid references. Exclude passengers, histories, passports and payment credentials.
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.