Multimodal transport: organise the connections between modes

The complete transport chain

Map the full transport chain before comparing individual legs. A useful multimodal plan identifies the collection point, transfer locations and final receiving site, with responsibilities assigned at each handover.

Cargo and handling requirements

Check that packaging and handling arrangements suit the complete journey. Cargo may face different terminal processes and equipment, so requirements should be assessed across the chain instead of only at the first loading point.

Connections and receiving

Agree what happens if one connection changes. A revised arrival at a transfer point can affect the next movement and the final delivery window, making a clear coordination contact especially valuable.

Connect the transport stages explicitly

Draw the shipment as a sequence of handovers, including the first collection and the final delivery. For each connection, identify who releases the goods, who accepts them, the location and the reference used. A confirmed main transport segment does not automatically confirm the movements or handling on either side. Write down which party arranges each operation and which information must be available before it begins.

Pay particular attention to the dependency between readiness and the next stage. Goods arriving at a transfer point are not necessarily ready for the next movement if acceptance, release or receiving instructions are still unresolved. For example, after an international main leg, the onward vehicle may need a separate collection reference and a receiving appointment. Both should be coordinated with the actual release process. Ask what happens if a connection changes and who is authorised to approve the revised sequence. The practical output is one chain of responsibilities, with confirmed and provisional steps clearly distinguished. This is more informative than comparing only the departure and arrival times of the longest segment while leaving the interfaces unspecified.

Include any agreed return movement in a separate, identifiable task. Returning an empty frame or packaging is not confirmed merely because the outward movement is booked. Assign the release, collection reference and receiving contact for that return rather than leaving it attached to an already completed delivery instruction.

Define the route as an operational task

A route becomes useful for planning when it identifies the actual points of collection and delivery, rather than only the countries involved. Include the postcode, the entrance used by freight vehicles and the contact responsible for access. If a factory gate and a loading bay have different addresses, explain which location the driver should use. A map pin can support the written instructions, but it should not replace the address and contact details.

Separate the earliest possible collection from the latest acceptable arrival. These are different constraints: goods can be ready while the receiving site is still closed. State which times are confirmed and which remain provisional, including the local time at each location. For example, if loading is possible only after a production release, identify the person who gives that release. The practical result should be a route brief that another dispatcher can understand without reconstructing the shipment from several emails. Check it with both sites before selecting the transport arrangement.

When access instructions come from a third-party warehouse, verify them with that warehouse rather than copying an old delivery note. Record when the information was confirmed. A correct customer address can still lead to the wrong gate if a previous shipment used a different receiving department.

Match the description, documents and physical shipment

Build the document set around the actual movement and ask the responsible specialists which documents are needed for that route and product. Start with a consistent goods description, package count, weights, shipper, consignee and shipment reference. The same shipment should not appear under different quantities or addresses in separate documents. Where the description is technical, include a contact who can clarify it; a broad label such as equipment is often insufficient for operational acceptance.

Separate commercial information from handling instructions while keeping the references connected. An invoice may identify ownership and value, but it does not explain how a case should be lifted or which workshop receives it. Conversely, a warehouse note does not replace documents required for the movement. If preparation is still in progress, identify the missing document and the person authorised to release it. For example, goods can be packed and ready while their release reference is not yet available. Confirm that this dependency is resolved before dispatch. Do not infer regulatory acceptance from the mere existence of a document: the proposed shipment and its data still need to be checked by the relevant parties.

Check document versions as well as their presence. If a packing list has been replaced, withdraw the previous version from the working instruction and identify the current one. Otherwise, correct documents can still create a mismatch when different participants refer to different editions of the same shipment record.

Compare proposals against the same confirmed scope

A useful comparison starts with a common set of shipment requirements. Give each proposed arrangement the same collection point, packed load, readiness information and receiving conditions. Separate essential requirements from preferences, and disclose any flexibility that can genuinely be used. This avoids comparing options that appear similar but assume different tasks. A more attractive headline offer is not a meaningful alternative if it omits an operation that the shipment requires.

Ask what is included, which assumptions remain open and what would trigger a review of the proposal. Relevant points may include loading responsibility, intermediate handling, appointment arrangements or the onward delivery task. The applicable scope should be confirmed for the actual request; do not infer a price or a fixed delivery commitment from a general service description. For example, a receiving window can be flexible even when the collection day is fixed, but that flexibility must be approved by the customer rather than invented by the organiser. Before acceptance, turn the selected proposal into one agreed instruction. Keep unresolved conditions visible so that booking does not accidentally convert an estimate into an expectation that nobody has confirmed.

Check that the proposal still refers to the current shipment when you accept it. If the cargo or required operation has changed since the enquiry, request confirmation of the revised scope. Keeping the original reference does not itself preserve the assumptions under which an earlier option was assessed.

Planning checklist

• Complete route and transfer points
• Packed cargo characteristics
• Handover responsibilities
• Connection and final delivery requirements