INDUSTRY FIELD GUIDE
Vanpool coordination records for AI matching tests
A coordinator may find a possible commute match before the operator confirms an available seat.
NAICS 488999 · All Other Support Activities for Transportation
A coordinator may find a possible commute match before the operator confirms an available seat. Census distinguishes arranging vanpools from operating them. A matchmaker can create a synthetic evaluation around the exact permissions and evidence needed before a match is considered confirmed. Census NAICS manual · FTA National Transit Database glossary
Make up two requests for the same commute window. Mark permission to be matched, a proposed seat, and separate operator confirmation where available. Withdraw one request before confirmation. Ask the model which status a coordinator may report and which request is closed. The rubric should reward preserving consent changes and refusing to infer a seat from a possible match.
Keep actual home locations, employer names, contact details, accessibility preferences, and commuting schedules out of the example. Use fictional aliases and collect no additional personal data for this task.
Describe a vanpool coordination sample
Original Fiund exercise
A possible seat match and operator confirmation depend on the request's current permission state
An original coordination fixture uses invented commute windows and role aliases. It contains no home, employer, contact, access preference or actual commuting schedule.
| Record | Source | What it records |
|---|---|---|
| VP1 | Request A | Permission to match recorded for abstract window W. Proposed seat S-A; operator confirmation explicitly names request A and S-A. |
| VP2 | Request B | Initially permission to match for W; proposed S-B. Later original withdrawal closes B before any operator confirmation. |
| VP3 | Near-match evidence | Operator confirms S-B2 for another request B2, not B. No seat confirmation or renewed permission for withdrawn B. |
Question for the model
Which match has operator confirmation, and what state should the coordinator report for B after its withdrawal?
Show the reference answer and checks
VP1 supports A's permitted match and exact operator-confirmed S-A seat in the fictional workflow. VP2 withdraws B before confirmation, so report its request closed rather than preserve an active proposed match. VP3 belongs to B2 and cannot confirm B or override its changed permission. Keep permission, proposal and operator confirmation as separate events without inferring an actual seat or collecting additional personal details.
- Treating a proposed match as a confirmed seat.
- Ignoring withdrawal or borrowing another request's near-matching seat confirmation.
Fields to preserve
- Request and permission state
- Defines whether matching remains requested.
- Proposed seat and operator target
- Supports the exact match.
- Withdrawal time and renewed-permission evidence
- Preserves changed scope.
Test another case
Add a renewed B request after withdrawal with a new ID and no operator confirmation. Require the new proposal to remain distinct from the closed original.
Use invented aliases only. Exclude locations and personal preferences; actual coordination and service decisions remain under authorized control.
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.