A truck leaves your gate at 14:00. Nobody at the customer's dock knows it is coming. At 16:10 it pulls up, the gate guard cannot find the plate on any list, nobody has booked a forklift, and the purchase order number on the delivery note matches nothing the receiver can see. Forty-five minutes go on phone calls with a driver who has already lost his place in the queue.
None of that was the driver's fault, and none of it needed to happen at the door. Every item was knowable at 14:00.
This article is about one small habit: a short message to the receiver when the truck leaves, listing what is coming and what they need to have ready. Warehouse practice calls the electronic version an advance shipping notice. You do not need a system to do it. A message in the chat app your teams already use is enough.
Where this fits
Most delivery trouble is made before the truck moves. The failed delivery article shows a Thai road courier where about three failures in four were paperwork, and where drivers and receiving staff named causes such as a receiving person who did not know the job, a missing tax invoice or purchase order, and a vehicle not registered in advance to enter the factory. A departure message is a cheap way to catch those while there is still time. It sits between the booking and the arrival, in the part of the day that transport control is meant to watch.
What the message says
One message, the same fields every time, so the receiver learns where to look.
- Truck. Plate and driver name, and the driver's mobile number.
- Times. The time it left, and the expected arrival time (ETA).
- Load. Number of pallets or pieces, and the document numbers that travel with it: purchase order, delivery note, tax invoice.
- Seal number, if the truck is sealed. The receiver compares it with the number on the truck at the door. A mismatch tells them the doors may have opened on the way.
- What the receiver must have ready. Gate registration for this plate, a forklift or unloading crew, a named person to sign, a bay if bays are allocated.
That is five lines. If it takes a dispatcher more than a minute, the form is too long.
When to send it, and when to send it again
- Send it when the truck leaves, not when the load is planned. Departure is the first moment the plate, the pallet count and the ETA are all true.
- Send a second message when the ETA moves by more than the slack in the delivery window. If the window is 10:00 to 11:00 and the new ETA is 11:20, the receiver needs to hear it at 09:30, not at 11:20. How to read that slack is in the delivery windows article and in the transport control article linked above.
- Ask for a reply only when something is wrong. "No reply means we expect you" keeps the receiver's work to a glance. A reply of "no forklift until 15:00" is exactly the information you wanted early.
Who sends it
The shipper's dispatcher, not the driver. A driver on the road should not be typing, and the dispatcher is the person who already holds the booking, the loading time and the paperwork. Copy the carrier's dispatcher so both sides see the same ETA.
The receiving side needs one named person who reads it. Without that, the message goes to a group chat that nobody owns.
What it is for, and what it is not
It does three jobs:
- It removes surprises at the gate that can be fixed with a phone call: unregistered plate, no unloading help, wrong person to sign.
- It lets the receiver check goods against what was sent rather than line by line against the order. This is the faster method the textbook describes for receiving, and it only works if the receiver has the sender's list before the truck arrives.
- It gives you a dated record of what you told the customer and when, which helps if there is later an argument about a late arrival or a refused load.
It does not replace the booking, the delivery window or the delivery note. It does not guarantee the receiver will act on it. And it should not be used to change the terms: if a delivery is going to miss its window, a message is a courtesy, not a waiver.
What it saves, as an illustration
The numbers below are invented to show the method. Use your own counts.
Say a customer's dock receives 8 trucks a day, and 1 truck in 10 arrives with a problem the receiver could have fixed in advance. Each such truck loses 45 minutes at the door.
- Problem trucks a day: 8 Γ 0.1 = 0.8
- Over 26 working days: 0.8 Γ 26 = 20.8 trucks
- Lost time: 20.8 Γ 45 = 936 minutes, or 15.6 hours a month of trucks standing at that one dock
If the message lets the receiver fix half of those before arrival, that is about 7.8 hours a month back, on one customer. Waiting hours are paid for somewhere. See what happens when trucks queue at a dock for what a queue at the dock does and how to fix it.
What to do on Monday
- Write the five lines as a template and save it where dispatchers can paste it.
- Pick your three customers with the most waiting at their gate, and ask each for one named person to receive the message.
- Send it for every departure to those three for a month.
- Count, for those trips, the minutes from arrival at the gate to the first pallet off. Compare with the month before, if you have it.
- Add a line to each customer's master data: the gate registration rule, and who reads the message.
Where the evidence stops
No Thai study of departure notices to consignees, or of how much they cut waiting at a receiving dock, was found. The method comes from a logistics textbook on receiving and dispatch. The Thai paperwork failure pattern is from the road courier study covered in the failed delivery article. The 1-in-10 problem rate and the 45-minute loss are illustrations only, and a message does not fix a receiver who lacks the people or equipment to unload.
