INDUSTRY FIELD GUIDE
Event ticket reservation, transfer and price records for AI
A ticket agency can test whether a model keeps the displayed price, reservation status and transfer events distinct.
NAICS 561599 · All Other Travel Arrangement and Reservation Services
A ticket agency can test whether a model keeps the displayed price, reservation status and transfer events distinct. The FTC’s unfair or deceptive fees guidance covers live-event tickets. That guidance provides context for building fictional price displays while keeping the exercise focused on data interpretation. FTC fees rule FAQs
Invent a reservation with a stated total and a later transfer invitation. Provide an acceptance event for one ticket and only the invitation for a second. Include a price document that belongs to a different reservation. Ask which transfers completed and which price evidence attaches to each reservation. Leave refund status unresolved unless a matching record establishes it.
Use original interface mockups and inert references. Exclude scannable tickets, real customer data and partner pricing systems. Secure rights for any third-party event art.
Describe a mock ticketing records sample
Original Fiund exercise
A transfer invitation and its acceptance apply to individual tickets
An original ticket-agency mockup uses inert references and no event art, scannable code, customer or transaction. Prices are invented document fields.
| Record | Source | What it records |
|---|---|---|
| TK1 | Reservation R1 | Two dummy tickets A and B; stated total 80 practice units. Original price card explicitly names R1. |
| TK2 | Transfer events | Invitations sent for A and B. Acceptance event explicitly references R1/A only; no B acceptance supplied. |
| TK3 | Other price and refund note | Price card for R2 shows total 70. Refund request names R1/B but no approval, settlement or completed refund event. |
Question for the model
Which transfer is documented as accepted, which price belongs to R1, and what refund state can be reported?
Show the reference answer and checks
TK2 supports acceptance of R1/A's transfer and only an invitation for R1/B. TK1 provides R1's stated 80-unit total; TK3's 70 belongs to R2 and cannot replace it. TK3 records a B refund request without settlement evidence, so the refund remains requested rather than completed. Keep ticket-level transfers, reservation-level price and refund workflow separate without making a legal entitlement or actual payment conclusion.
- Treating all invitations as accepted because one ticket has an acceptance.
- Using another reservation's price or promoting a refund request to completed reimbursement.
Fields to preserve
- Reservation and ticket reference
- Defines event scope.
- Stated price source
- Preserves the matching total.
- Invitation, acceptance and refund event type
- Separates stages.
Test another case
Add an acceptance for R2/B. Require R1/B to remain pending despite the same local ticket letter.
Use original interfaces and nonfunctional references. Exclude real tickets, customer data and partner pricing systems; clear third-party artwork separately.
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.