Capability · Dispute file

Evidence gaps listed, letter drafted in the carrier's format

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.

A file, not a finding

The output is the thing a disputes desk would have built by hand: a dated timeline with sources, the clause quoted, the arithmetic, the amount at stake, what evidence would make it stronger and who has that evidence — and the letter, ready to send.

Carrier formats

Carriers want disputes in their format: a portal form with specific fields, an email to a specific address with the invoice number in the subject, attachments in a specific order. Templates for the major carriers are maintained; your own can be added. The draft is produced in the right one.

Missing evidence

"Request the empty-return EIR from Trucker X" or "ask the terminal for the yard-hold record for 9–11 Sep" — with the contact if it is in your workspace. Disputes filed with gaps get rejected; the list is there to close them first.

Second rounds

When the carrier replies, forward the reply. The agent reads the stated ground, checks it against the booking and contract, and drafts the response — or recommends closing the dispute if the carrier is right, and records why.

What it does not do

It does not send. A person reviews and presses the button, in the portal or the mail client.

Related

D&D Pilot is in early access.

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.