Port drayage dispatch, terminal appointments and per diem disputes, 10 firms

Summary

Container drayage records from 10 trucking firms serving West Coast and Gulf ports: dispatch boards, terminal appointment attempts, chassis swaps, street turns and the email disputes over demurrage and per diem. The data shows how small dispatch teams juggle free time, terminal holds and driver hours. Useful for planning agents and for evaluating reasoning about who owes what when a container sits. Steamship line, cargo owner, driver and container identifiers are replaced.

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 pricing

At a glance

  • Planned scope. Volume, sources and timing are confirmed in writing before you sign.
Records
8.7Mcontainer moves, emails and documents
Size
21.4 GB
Tokens, estimated
2.1B
Years
2016 to 2025
Firms
10
Owner profile
10 US port drayage trucking firms, 15 to 120 staff each plus contracted drivers, West Coast and Gulf Coast ports
Industry
Logistics and freight
Data type
Logistics and supply chain
Headcount
15 to 120 staff per firm
Region
United States (West Coast, Gulf Coast)
Languages
English, Spanish
Formats
JSONL, Parquet
Updated

Sources

SystemKindRecords
Drayage dispatch systemField operations2.1M container moves
Google Workspace mailEmail6.3M messages
Shared drivesShared files310K interchange receipts, delivery orders and PODs as text

Good for

  • training dispatch agents to plan container moves around last free day, appointments and driver hours
  • evaluating reasoning on demurrage and per diem liability from dated event chains
  • extracting holds, free time and appointment data from terminal and customer email
  • drafting dispute letters with the supporting timeline

Fields

FieldTypeDescription
move_idstringMove id in the dispatch system
firm_codestringPool member code
containerstringContainer number placeholder
size_typeenum20GP, 40GP, 40HC, 45HC or 40RF
terminalstringTerminal placeholder
move_typeenumimport, export, empty return or street turn
last_free_daystringTerminal last free day, YYYY-MM-DD
eventsarray<string>Dated events from discharge to empty return
demurrage_daysintDays charged past last free day
per_diem_daysintChargeable equipment days after free time
dispute_thread_idstringLinked dispute email thread

Example record

{
  "move_id": "MV-2023-0571183",
  "firm_code": "DRY-03",
  "container": "[CONTAINER_41]",
  "size_type": "40HC",
  "terminal": "[SITE_11]",
  "move_type": "import",
  "last_free_day": "2023-03-09",
  "events": [
    "03/06 discharged, customs hold",
    "03/08 hold released 16:40, no appointments left for 03/09",
    "03/10 appointment 06:00, out-gated 07:12 on pool chassis",
    "03/10 delivered to [COMPANY_58], live unload refused, dropped",
    "03/17 empty return rejected, terminal not receiving this line's empties",
    "03/21 empty returned"
  ],
  "demurrage_days": 1,
  "per_diem_days": 7,
  "dispute_thread_id": "TH-640218"
}
One record, de-identified. Placeholders such as [PERSON_12] and [COMPANY_4] stay the same across the whole dataset, so threads still read correctly.

Licenses available

  • 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.

The full method

Request scope and pricing

We confirm scope, volume and timing in writing before you sign. Samples go out under evaluation terms after a short buyer check, once the first records are in.

Dataset: NK-35093

Organization type
What would you like?
Intended use
License interest

We use these details to reply to you and handle your request. See our Privacy Notice.