Port rankings are not cargo delivery dates

A vessel benchmark is not a delivery promise

A port can move a container ship efficiently without delivering an importer's goods to a warehouse on time. That distinction matters when a route is being selected, a supplier's delivery proposal is being assessed or a working-capital forecast is being prepared. A headline port ranking can help identify operational questions. It cannot, by itself, establish when a particular consignment will become available for use.

The World Bank's Container Port Performance Index measures vessel time in port, including waiting and time at berth. Its current publication page presents the 2025 edition and describes rankings as diagnostic tools that need context, including external disruptions. The commercial inference is straightforward: use the benchmark for the stage it observes, rather than converting it into an end-to-end delivery estimate. [1]

Build a chain of observable milestones

Oakhampton's proposed approach starts with a shipment timeline: confirmed departure, arrival at the destination port, discharge, regulatory release, availability for collection, terminal gate-out and delivery acceptance. These events should remain distinct even if one service provider reports several of them. An arrival notification answers a different question from a release notice; neither should automatically close the delivery task.

For each milestone, record the event definition, the source of evidence and the person responsible for the next action. Distinguish an estimated timestamp from an actual event. Where a forwarder reports that a shipment is cleared, establish whether that means customs release, satisfaction of other applicable controls or simply completion of a document submission. The purpose is a shared operating vocabulary, not another dashboard with ambiguous green lights.

The World Bank's warning about interpreting port rankings in context also matters when comparing alternatives. A change in vessel performance can reflect wider shipping conditions rather than terminal execution alone. Treat a ranking as a screening signal, then seek shipment evidence relevant to the service, cargo and inland route being evaluated. [1]

Separate electronic submission from usable cargo

IMO describes a Maritime Single Window as a central electronic entry point for information exchanged between ships and public authorities. Its guidance explains the FAL Convention framework for ship arrival, stay and departure reporting, including submission once and reuse of information. That is an information-exchange function; the existence of a platform should not be treated as evidence that a particular cargo has been released or collected. [2]

For a commercial shipment, Oakhampton recommends asking what evidence confirms acceptance, what remains outstanding and who receives an exception. A submitted message may still need correction or a decision. An acknowledgement should therefore retain its actual meaning in the shipment record. This is especially important when information is copied between a carrier, agent, broker and importer: a status can lose its qualification as it travels.

A practical test is to walk one recently completed shipment backwards from delivery acceptance. Identify which records established each prior milestone and where staff had to intervene. Use authorised records and remove unnecessary personal or commercially sensitive details before wider review. The exercise should expose missing hand-offs without assuming that every delay is a technology problem or that a new portal will resolve it.

Compare release evidence on a consistent basis

The WTO Trade Facilitation Agreement's Article 7.6 encourages members to measure and publish average goods-release times periodically and consistently. Its footnote allows members to determine the measurement scope and methodology according to their needs and capacity. This is encouragement to members, not a shipment-specific service guarantee or a new obligation imposed on an individual importer. [3]

Before using a published average in a commercial plan, check the measured interval and the consignments it covers. An interval beginning when a declaration is accepted cannot be assumed to include all time since a vessel arrived. Oakhampton also recommends examining variation within the available shipment history. A typical case and a delayed case answer different planning questions, particularly where a missed collection slot affects the next production or delivery window.

Keep the comparison like-for-like wherever the records allow. Separate materially different cargo requirements and routing arrangements rather than pooling them into one apparently precise figure. Where the sample is small or an event is missing, retain that limitation in the internal planning record. Do not silently substitute a port-wide vessel metric for an unavailable cargo-release measure.

Make route selection a documented operating decision

Oakhampton's commercial conclusion is to assess the full route with a small evidence pack: a defined milestone chain, relevant shipment history, unresolved release dependencies and a named owner for exceptions. A cheaper freight quote and a stronger port ranking may both be useful inputs. Neither settles the consequences of inland capacity constraints, incomplete documents or a delivery appointment that cannot be changed.

The decision is not to reject rankings or digitalisation. It is to keep each source of evidence within its proper boundary. Use vessel benchmarks to investigate port operations, release records to understand border processing and delivery records to test the final hand-off. A route becomes commercially credible when those stages connect into an executable plan, not when one stage produces an attractive score.