How a UK forwarder is turning complete requests into CargoWise jobs with one confirm

Creating a shipment meant three passes. Someone checked the request had what was needed to start, then chased the gaps with the customer, often one email at a time. Then they keyed the job into CargoWise screen by screen, and later went back to fix the record when billing or customs found something missing.

For urgent shipments, including aircraft parts that ground a plane until they arrive, every one of those passes is time the freight isn't moving.

Dispatch checks each request against a minimum-field matrix the operations team signs off, per shipment type and region. If anything is missing, it drafts one email listing all of it, and a person reviews and sends it. Nothing reaches a customer on its own.

If the request is complete, Dispatch builds the job through CargoWise's structured import and puts it in front of an operator, who checks it, corrects anything and confirms once. The service level comes from the purchase order rules, and the original email and attachments are filed to the job.

Once the job exists, Dispatch checks it against everything that job type requires and sends any gaps to a queue with the reason attached. When someone corrects an agreed reference, such as an air waybill or PO number, it updates everywhere it's meant to instead of drifting.

Connectivity to the forwarder's CargoWise test environment is live, and the job templates are being agreed with operations. Nothing touches production until acceptance testing is signed off, and the numbers go on this page after that.