One job, one record: why copies cause most freight errors

Forwarders are often told their problem is spreadsheets. It is not. A spreadsheet is a perfectly good way to hold a list. The problem is that transport keeps one, documentation keeps another, the CS desk keeps a third and accounts keeps a fourth, and all four describe the same container.

How the facts drift

The driver sends a seal number on WhatsApp; one copy gets it. The vehicle changes at the last minute; a different copy gets that. The packing list is revised; the old file stays attached to the email the next person opens. Nobody made a mistake. The copies simply stopped agreeing.

The cost of a copy is not the time it takes to make. It is the day it disagrees with the original.

One record, many hands

The alternative is a single record per job and per container that every desk updates directly, with a note of who changed what and when. The CS desk adds the seal number, transport adds the vehicle, documentation attaches the final packing list and everyone reads the same thing.

That is the idea behind Freightflow, and the first thing to test in any demo: every update, document and deadline for a shipment lands on one job record, so the question is never which version is right, only what changed.