In this article
Before confirming transport with Speedixa, bring the route, cargo details and handover requirements into one clear shipment brief.
Selection criteria
Build the plan around shipment requirements rather than a list of desired departure dates. Identify which orders have fixed receiving appointments and which can tolerate a different collection or delivery window.
Cargo preparation
Check opening hours at each site for the actual dates. Warehouse closures, shortened receiving periods or staff availability must be confirmed locally; do not rely on an ordinary weekly timetable.
Coordination and handover
Keep one current shipment brief. When order volume or readiness changes, update the same reference so that vehicle planning and warehouse preparation are based on the latest agreed version.
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.
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.
Turn urgency into a decision sequence
Explain the consequence of missing the requested handover and distinguish it from a preferred arrival time. The person organising transport needs to know which deadline is operationally decisive, when the shipment can actually be released and who can approve a revised solution. This allows alternatives to be compared against the same task. Avoid replacing this information with labels such as urgent or immediately, which do not identify a workable collection and delivery sequence.
Work backwards from the required handover, listing the actions that must happen first: cargo release, packing confirmation, collection access, transport acceptance and receiving readiness. Mark dependencies that another party controls. For example, a component may be available at a supplier while the maintenance team has not yet confirmed an authorised recipient. Shortening the driving or flight segment does not resolve that missing handover. Decide in advance who can approve a different collection point or receiving arrangement if the original plan changes. A useful urgent request therefore contains both the deadline and a realistic path to acceptance. The final option, its scope and its feasibility must be confirmed for the particular shipment rather than assumed from an express service name.
If only part of the shipment is operationally critical, ask the customer whether a separate release is acceptable. Identify the exact units and receiving purpose before assessing that alternative. Splitting a shipment is a decision to approve, not an automatic way to promise an earlier completion.
Keep one current instruction through the shipment
Choose one shipment reference and use it in the request, updates and receiving instructions. Allocate responsibility for confirming readiness, accepting changes and reporting the final handover. This does not require a complicated reporting system: a concise, current instruction is more useful than several attachments that contradict each other. Where information is missing, name the person expected to provide it and the point at which a decision is needed.
Treat a material change as a reason to review the plan, not simply as another message to forward. A larger package, a delayed production release or a different receiving location may affect the chosen arrangement. Describe what changed, which earlier detail it replaces and whether the change is confirmed. Ask the responsible parties to acknowledge the revised instruction. For example, when collection moves to another warehouse, updating the street address alone is insufficient if the opening hours and loading equipment also differ. At delivery, close the instruction with the agreed confirmation and record any unresolved discrepancy factually. This leaves a usable history without presenting an estimated event as a completed one.
When sharing an update, identify its source and confirmation time. A proposed change from a customer is not yet a confirmed change at the warehouse. Keep that distinction visible until the parties responsible for the affected operation have accepted the revised instruction.
Information for the enquiry
- Order priorities
- Actual site opening hours
- Confirmed cargo readiness
- Flexible and fixed delivery windows
What this means for your business
For the relevant Speedixa service, see Standard cargo delivery; send the actual route, cargo data and handling requirements so the proposed arrangement can be checked for your shipment.







