Regional LTL dispatch, driver messages and OS&D claims, one carrier
Summary
Seven years of pickup and delivery dispatch from one regional less-than-truckload carrier: stop lists, driver in-cab messages, dock exceptions and the overage, shortage and damage claims that follow. Dispatch notes show how planners rebuild routes around missed pickups, weather and late linehauls. Strong material for routing and exception-handling agents and for claims triage. Driver and customer identities are replaced, GPS traces are dropped and locations are kept at city level.
Collected to order. We collect it from US companies for your order. Scope, volume and timing are confirmed in writing before you sign.
Pricing on request
Request scope and pricingAt a glance
- Planned scope. Volume, sources and timing are confirmed in writing before you sign.
- Records
- 11.3Mstops, driver messages, emails and claim files
- Size
- 9 GB
- Tokens, estimated
- 1B
- Years
- 2019 to 2026
- Firms
- 1
- Owner profile
- One US regional LTL carrier, 150 to 300 staff
- Industry
- Logistics and freight
- Data type
- Field operations
- Headcount
- 150 to 300 staff
- Region
- United States
- Languages
- English, Spanish
- Formats
- JSONL, Parquet
- Updated
Sources
| System | Kind | Records |
|---|---|---|
| Dispatch and terminal system | Field operations | 5.8M stops |
| In-cab driver messaging | Team chat | 3.2M messages |
| Microsoft 365 mail | 2.3M messages | |
| Shared drives | Shared files | 41K OS&D claim files and inspection reports |
Good for
- training dispatch agents to re-plan pickup and delivery routes around exceptions
- summarizing driver in-cab messages into dispatch actions
- triaging OS&D claims and matching them to dock exception records
- evaluating models on freight class, reweigh and inspection disputes
Fields
| Field | Type | Description |
|---|---|---|
| stop_id | string | Stop id |
| terminal | string | Terminal placeholder |
| route | string | Pickup and delivery route |
| stop_type | enum | pickup or delivery |
| scheduled_window | string | Customer window, local time |
| arrived_at | timestamp | Driver arrival |
| pieces | int | Handling units picked up or delivered |
| weight_lb | int | Billed weight in pounds |
| exception_code | enum | none, closed, refused, short, over, damaged or no freight |
| driver_messages | array<string> | In-cab messages tied to the stop |
| dispatch_note | string | Dispatcher note on how the exception was handled |
Example record
{
"stop_id": "ST-24-6619082",
"terminal": "[SITE_4]",
"route": "P&D 118",
"stop_type": "pickup",
"scheduled_window": "13:00 to 16:00",
"arrived_at": "2024-02-08T15:52:00-05:00",
"pieces": 6,
"weight_lb": 2140,
"exception_code": "short",
"driver_messages": [
"BOL says 7 pallets only 6 on dock",
"shipper says 7th still being wrapped wants me to wait",
"cant wait got 4 more stops"
],
"dispatch_note": "Took 6 of 7, BOL marked 6 received. [PERSON_19] at shipper agreed to tender the 7th on a new PRO for Friday pickup. Customer service notified [COMPANY_77]."
}Licenses available
Exclusive
One buyer. Nobody else can license it during the exclusive term, usually 2 years.
Non-exclusive
Licensed to more than one buyer.
First look
One buyer gets 2 to 4 weeks to make an offer before anyone else sees the dataset.
What ships with it
- Datasheet: what it is, what it is good for, verified size, sources, years, format and limits.
- Provenance file: the owner shown by code, staff notice and consent status, exclusions, mapped to the EU AI Act Article 53 training-data summary and California AB 2013.
- Manifest with a hash for every file.
- QC report and de-identification report.
- Your own copy, with unique canary records.
How it is de-identified
Default exclusions removed, files flattened to text, identifiers found in three layers and replaced with consistent placeholders, and the result measured against a 99% bar for each identifier type in each source.