INDUSTRY FIELD GUIDE
Taxi and limousine booking-change records for AI
An on-demand car and a prebooked limousine can both be reassigned.
NAICS 485310 · Taxi and Ridesharing Services
NAICS 485320 · Limousine Service
An on-demand car and a prebooked limousine can both be reassigned. A canceled assignment does not always cancel the underlying booking. New York City’s Taxi and Limousine Commission publishes trip record schemas. A service operator can build a synthetic task that preserves the distinctions among passenger request, assignment, substitution, and completion. NYC TLC trip record data
Make up one request with an accepted car and a documented substitution, and another where the booking itself was canceled. Give both a similar timestamp. Ask which service actually took place and which record supports that conclusion. Include a disputed case that shows a driver accepted but has no completion evidence. Grade the identity link and status separately.
Do not use precise pickup or drop-off points, personal identifiers, account details, accessibility needs, or driver performance records. Check platform and partner rights before sharing any operational files.
Describe a booking status exercise
Original Fiund exercise
Canceling a vehicle assignment can preserve the underlying booking
An original on-demand and prebooked-service fixture uses invented request aliases and abstract times. It contains no passenger, driver performance, location, accessibility need or payment data.
| Record | Source | What it records |
|---|---|---|
| HB1 | Booking A | Assignment A1 accepted, then explicitly canceled as a substitution. Original event assigns replacement A2 under the same booking A; completion C-A names A/A2. |
| HB2 | Booking B | Booking-level cancellation explicitly closes B, not merely its vehicle assignment. No completion event supplied. |
| HB3 | Booking C | Driver-role acceptance for assignment C1, no completion. Timestamps resemble A's but full booking and assignment IDs differ. |
Question for the model
Which booking has a documented completed service, which is canceled, and which remains accepted without completion?
Show the reference answer and checks
HB1 documents completion for A through replacement assignment A2; A1's assignment cancellation does not cancel the booking because the substitution is explicit. HB2 separately cancels booking B. HB3 supports acceptance for C/C1 without completed-service evidence. Preserve booking-level and assignment-level states rather than equate every canceled assignment with a canceled request or transfer A's completion through similar timestamps.
- Treating an assignment cancellation during substitution as booking cancellation.
- Treating driver acceptance as completed service or joining events by time alone.
Fields to preserve
- Booking and assignment ID
- Defines the two levels.
- Cancellation scope and replacement link
- Preserves substitutions.
- Accepted versus completed event
- Supports the final state.
Test another case
Add C1 cancellation with no replacement and no booking-level cancellation. Require both the canceled assignment and unresolved booking disposition to remain visible.
Use original synthetic records. Exclude precise routes, personal identifiers and platform exports; verify operator and partner rights before real reuse.
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.