INDUSTRY FIELD GUIDE
Towing incident handoff records for AI evaluation
A tow operator can remove a vehicle before an authorized party confirms that a lane is clear.
NAICS 488410 · Motor Vehicle Towing
A tow operator can remove a vehicle before an authorized party confirms that a lane is clear. FHWA traffic incident management material describes separate performance events and timing. A towing company can create a synthetic dispatch exercise that asks an assistant to tell these milestones apart. FHWA traffic incident performance measures · FHWA incident information sharing
Invent two cases with a dispatch time, arrival, removal, and separate confirmation when available. On one, attach a clearance message to a different lane or incident alias. Ask the model to cite which milestones are verified and why the final status remains open for one case. Use time intervals rather than a real address.
Keep plate numbers, roadside imagery, victims’ information, law-enforcement reports, precise locations, and actual response details out of the packet. No live roadside work or recording is needed for this benchmark.
Describe a towing event sample
Original Fiund exercise
Vehicle removal and authorized lane-clearance confirmation are distinct milestones
A wholly fictional dispatch exercise uses relative minutes and abstract incident lanes. There is no vehicle, plate, roadside image, victim, location or live response.
| Record | Source | What it records |
|---|---|---|
| TSN1 | Incident A | Dispatch minute 0, arrival minute 10, removal confirmed minute 25. Separate authorized clearance at minute 30 explicitly names A/lane L1. |
| TSN2 | Incident B | Dispatch 0, arrival 12, removal confirmed 28. No B/lane L2 clearance supplied. |
| TSN3 | Attached clearance | Signed note says incident B-old/lane L3 clear at 32. No B-old-to-B or L3-to-L2 equivalence record. |
Question for the model
Which milestones and intervals are verified for A, and why does B's final clearance remain unresolved after removal?
Show the reference answer and checks
TSN1 supports A's arrival at ten minutes, removal at 25 and lane-L1 clearance at 30, leaving five minutes between removal and clearance. TSN2 supports B's arrival and removal but no L2 clearance. TSN3 names another incident and lane, so it cannot close that gap. Preserve each milestone's authority and exact target rather than equate removal with a cleared lane or use another incident's signed note.
- Treating removal as the authorized clearance event.
- Matching a clearance to a similar incident while ignoring lane identity.
Fields to preserve
- Incident and lane alias
- Defines the event scope.
- Dispatch, arrival, removal and clearance type
- Separates milestones.
- Relative time and confirming authority
- Supports intervals.
Test another case
Add B's clearance for L2 but on a different reference clock. Require occurrence to resolve while an exact removal-to-clearance interval remains uncertain.
Use original invented records. Exclude police reports and actual response details; no roadside work or operational direction is included.
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.