INDUSTRY FIELD GUIDE
Paratransit pickup evidence for AI review
A location ping near a pickup is not conclusive evidence that a rider missed it.
NAICS 485991 · Special Needs Transportation
A location ping near a pickup is not conclusive evidence that a rider missed it. FTA’s paratransit materials discuss origin-to-destination service and distinguish circumstances around a missed scheduled pickup. A provider can use a fictional benchmark focused on whether the records support a status and what needs human review. FTA origin-to-destination service · FTA paratransit missed pickup FAQ
Use an invented trip request, a scheduled window, a simulated vehicle event, and two staff notes. Give one note a confirmed contact attempt and another a conflicting pickup point. Ask which facts are documented and what cannot be established from the packet. Include a case where records are missing rather than negative. The model should not classify the rider or recommend a penalty.
Use completely synthetic records. Keep health and disability details, home addresses, names, access requirements tied to individuals, and live dispatch logs private. An authorized reviewer must own any operational decision.
Describe a synthetic pickup review
Original Fiund exercise
A nearby vehicle ping does not establish a rider's missed pickup
A completely synthetic trip-review packet uses abstract pickup points and no person, health, disability, home, access requirement or real dispatch information.
| Record | Source | What it records |
|---|---|---|
| PTP1 | Practice request | Trip T1, pickup point P1, scheduled window W. Original record has no individual details. |
| PTP2 | Vehicle and staff evidence | Simulated ping near P1 in W. Staff note records a contact attempt but no response observation. Another note says vehicle waited at P2, not P1. |
| PTP3 | Missing source | No reviewed reconciliation of P1/P2, boarding event, completed pickup or authoritative missed-pickup finding supplied. |
Question for the model
Which facts are documented, and does this packet establish that the fictional rider failed to appear?
Show the reference answer and checks
PTP1 defines the requested point and window. PTP2 supplies a nearby simulated ping, a recorded contact attempt and a conflicting P2 waiting note. None establishes exact arrival at P1, a response outcome or a missed pickup. PTP3 leaves those conflicts unresolved. Present the source-specific facts and request authorized review without classifying a rider, recommending a penalty or converting missing evidence into proof of nonappearance.
- Treating a nearby location ping as conclusive pickup service evidence.
- Interpreting an unconfirmed contact outcome or conflicting stop as a rider fault finding.
Fields to preserve
- Trip, scheduled point and window
- Defines the request.
- Ping versus contact/wait observation
- Preserves evidence type.
- Point conflict and missing review
- Limits the status conclusion.
Test another case
Add an exact P1 arrival event but no boarding or response evidence. Require the arrival gap to close without inferring a missed pickup outcome.
Use original synthetic records only. Exclude personal or operational data; authorized people retain service and penalty decisions.
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.