D&D Pilot reads the carrier invoice, the bill of lading, the gate and terminal events, your contract's free-time clauses and the email thread, then builds the timeline, checks the invoice against the clause, lists what evidence is missing and drafts the dispute letter. Your team decides; the agent does the reading.
Illustrative output. Names and figures are examples.
Carrier and terminal invoices as PDF, portal export or scanned statement; B/L and booking; EIRs; terminal and depot events as EDI, export or screenshot; the email thread. No TMS integration required.
Discharge, availability, holds, gate-out, empty return, invoice — assembled from all documents into a single dated sequence with the source and confidence of each event.
Free time, clock start, combined or separate D&D, rate tiers, container-type bands, exclusions — read from the governing contract (not the public tariff) and recomputed day by day.
Each shipment produces a dispute file: timeline, clause check, computed vs invoiced, the evidence still missing (and from whom), and a letter draft in the carrier's preferred dispute format.
Rate a 200-line statement in minutes and rank what is worth disputing; track every dispute from filed to credited; report recovery by carrier and cause for the shipper and for the next contract negotiation.
A dispute file reads 5–15 documents and an email thread per shipment. Teams handling 10–50 disputed shipments a day run roughly 20–100 million tokens a month. Day-count maths is deterministic code; the model is spent on reading documents and drafting.
We are onboarding a small number of design partners with real documents and real deadlines. Tell us what you work on and we will set up a workspace with your material.