Two teams, one shipment, and a boundary nobody wrote down
The forwarder’s desk has done its part. The flight is confirmed, the arrival is tracked, the consignee has been told what time to expect the freight, and a ground recovery team has been engaged to collect it and run it to the plant. Everything about that reads like a clean handoff. Then the flight arrives two hours early into a terminal that will not release until the airline breaks down the pallet, and the ground team, who were told 6 AM, are two hundred miles away on another job. Nobody made a mistake. What happened is that the boundary between the two teams was assumed rather than defined, and an assumed boundary is where recoveries go to die.
This is the last piece of the forwarder recovery series, and it is the one that gets the least attention, because it does not look like a problem until it produces one. The desk thinks the ground team owns everything after arrival. The ground team thinks the desk owns everything up to release. In between sit four or five decisions that belong to whoever picks them up first.
Release timing is not arrival timing
The single most common failure at the boundary is treating the arrival time as the collection time. A flight lands, and the freight becomes available some number of hours later depending on how the airline breaks down the ULD, whether the shipment is on a transfer, whether the terminal is running its normal shift, and whether anything ahead of it in the queue is oversized or restricted. That interval is not a constant and it is not visible on a tracking screen.
The desk usually has better access to it than the ground team does, because the desk has the airline relationship and the ground team has a dispatcher looking at an ETA. So the practical rule is that release timing stays with the desk, and stays with the desk after arrival, until the freight is physically confirmed as available. Handing the ground team an arrival time and calling that a handoff moves a piece of uncertainty to the party least equipped to resolve it.
The version of this that costs the most is an early arrival. A late flight is visible to everyone and the ground team simply waits. A flight that lands two hours early produces freight that is ready before anybody expects it, a truck that is elsewhere, and a shipment that then sits in a terminal through the exact window it could have been moving in. Nothing alerts on it, because early is not an exception in any system that anyone is watching.
The piece count problem
The second unowned decision shows up at collection. A driver arrives against a delivery order for six pieces and the terminal produces five. What happens next depends entirely on who has authority, and if nobody does, the default is that the driver waits, calls a dispatcher, the dispatcher calls a desk that may be closed, and forty minutes disappear while a recovery clock runs.
The decision itself is not hard. Either the five pieces restart the line and should move now with the sixth to follow, or they do not and waiting is correct. But that is a shipper question wearing a freight costume, and it needs to have been asked before the driver is standing at the counter. A desk that owns the recovery rather than just receiving the call asks the consignee that question at booking, not at the counter, and writes the answer into the delivery order so that the driver is carrying a decision instead of a question.
One voice to the consignee
The third boundary problem is communication, and it is the one clients notice. When both the desk and the ground team have the consignee’s number, the consignee gets two versions of the same story, usually about twenty minutes apart, usually not quite matching, because one is reading a flight status and the other is reading a driver’s position. The consignee then does the reconciliation work themselves, which is precisely the work they paid a forwarder to do.
The fix is to name one voice at booking. In practice the desk should hold consignee communication end to end, and the ground team should report to the desk rather than to the customer, even when the ground team has better information. That feels slower and is not, because the alternative is a consignee making plant decisions off two conflicting inputs. Ground operations run to their own service culture and standards, which is part of what industry bodies such as the American Trucking Associations exist to formalise, and a good ground partner will not resist reporting through a single point when they are told at engagement that is how it works.
Who is allowed to decide to wait
The fourth and hardest is the wait decision. Freight is not released, and it might be twenty minutes or it might be four hours. A driver on a clock has to choose between holding at the terminal and repositioning to another job, and that choice has money on both sides of it. If the desk has not defined who decides, the driver’s dispatcher decides, and the dispatcher optimises for their fleet, which is a reasonable thing for a dispatcher to do and not what the recovery needs.
Setting this at engagement costs one sentence: the truck holds until we release it, and detention is on us from a stated hour. That converts a fleet decision into a recovery decision, and it is worth building into how an air freight recovery move is scoped rather than negotiating it at 4 in the morning with a driver who is already moving away from the airport.
Write the boundary down before you need it
Three questions define the handoff, and answering them at engagement removes almost every failure this article describes. Who confirms that the freight is physically available, and does the ground team move on that confirmation rather than on an arrival time. What is the driver authorised to do if the piece count is short, and is that written on the delivery order. And who is permitted to hold the truck, at whose cost, from what hour. None of these take long to settle and all of them are impossible to settle at speed once something has gone wrong. This is also exactly the material that a post-event review surfaces, and the boundary is the one thing a review almost always finds was never actually agreed. Define it once with a partner who works both sides of it and it stops being the part of the recovery that fails.
Set the desk-to-ground boundary with us before the next arrival.
