LR2 Port Calls: Coordinating Product and Receipt Readiness

Overview

For products business, a schedule update can be commercially incomplete even when the vessel timing is clear. The coordinator needs to connect the cargo and receiving workstreams without confusing them with technical operating authority.

Key takeaways

• Track vessel, product, and receiving readiness independently.
• Give document and quality questions named decision owners.
• Distinguish forecasts from requested and confirmed programmes.
• Explain how each change affects the customer's next action.

Define the cargo purpose of the call

Identify the product parcel, seller or receiver, intended facility, and commercial milestone the call must support. If several allocations are involved, show which customer belongs to each part of the programme.

At loading, the relevant questions include product availability, current specification information, and the terminal's intended programme. At discharge, the receiver's readiness and document process may be central. The coordinator should identify the actual dependencies rather than use one generic cargo ready label.

Ask the customer which event it needs for planning. Expected vessel arrival may not be the same as product available for distribution. The receiving party should define the relevant milestone and supply the information within its responsibility.

Keep the purpose concise in the shared call plan. It gives every participant context for the updates and makes it easier to recognise when a change affects a commercial commitment rather than merely a local detail.

Map the product and vessel information channels

Name the owner or operator contact, appointed agent, terminal channel, cargo specialist, seller or receiver representative, and commercial approver. State what each supplies and what each can decide.

A product-quality clarification should go to the authorised cargo source and relevant reviewer. The local agent may coordinate communication but should not be expected to determine technical suitability or interpret a specification independently.

Similarly, the vessel's current outlook should come through the owner's authorised channel. The cargo desk can communicate timing priorities, but should not create technical instructions to make an internal sales schedule fit.

The contact map should include an escalation route when a decision is urgent. A fallback contact needs defined authority; simply copying more people does not establish who can approve a changed programme or additional expense.

Preserve the meaning of every milestone

The shared plan should distinguish a vessel estimate, a terminal request, a proposed receiving arrangement, and an actual event. These can all be current information while describing different things.

IMO's port-call datasets distinguish such event statuses. See the official data model.

When the information moves into a customer report, preserve that meaning. A terminal's requested time should not become a confirmed availability promise merely because the sales team needs a date.

Record the source and update time for each material input. A newly circulated call plan can contain an older product or receiving assumption. The document date alone does not show whether every workstream has been refreshed.

Use a product-readiness responsibility map

The map below highlights the decisions that can fall between maritime coordination and product-commercial teams during an LR2 call.

The coordinator should identify the next action for each open item. A broad statement that documents are in progress does not explain whether a draft is being prepared, an issuer must correct a record, or a receiver is deciding a substantive question.

Keep the map aligned with the current parcel. If the product reference or receiver allocation changes, identify which workstreams need renewed information rather than assuming the old readiness status remains valid.

Manage programme changes as linked decisions

When the terminal or receiver proposes a change, establish its status and scope. Is it a new timing preference, another facility, or a revised product allocation? Those changes can affect different parties and should not be grouped under a generic schedule update.

Ask the owner for the relevant assessment and the cargo desk for the commercial consequence. If quality or acceptance assumptions change, route the issue to the proper reviewer. The coordinator should connect the decisions without answering specialist questions itself.

Communicate the current plan, proposed change, and outstanding confirmations in one concise summary. A long forwarded chain can contain all the evidence while leaving recipients uncertain about the actual action requested.

Once the required decisions are made, identify the superseded version and circulate the current basis. If the proposal is withdrawn, close it explicitly so it does not remain an apparent alternative in execution records.

Fictional case: product paperwork and vessel readiness diverge

A fictional products buyer receives a favourable LR2 arrival update and tells its distribution team that the cargo programme is settled. The receiving facility, however, is still clarifying a specification reference with the cargo source.

The call coordinator's responsibility map shows the distinction between vessel outlook and the unresolved product workstream. The buyer updates its customer communication to reflect the actual status and assigns the clarification to the authorised specialist.

The owner continues providing vessel information, and the terminal maintains its own programme through the appropriate channel. Once the clarification is resolved, the coordinator reconciles the relevant milestones rather than simply reusing the earlier customer promise.

The case illustrates why readiness should be specific. A ship can be progressing as expected while another decision remains important to the commercial receipt plan.

Close the call with an accurate commercial handover

Retain factual event reports, product and document decisions, and relevant expense approvals. Keep actual events separate from forecasts so a later reviewer can understand both the outcome and the information available during the call.

Where time or expense treatment is disputed, preserve the evidence and check the current text of the applicable agreement through the responsible review process. The port-call summary should not invent a legal conclusion from an isolated timestamp or message.

At completion, identify remaining records and actions. The next team should know whether it is waiting for an issued document, a correction, or a commercial decision, and who is responsible for obtaining it.

Use the post-call review to improve the earliest weak handoff. If product questions surfaced late, involve the cargo source earlier. If customer promises used the wrong milestone, improve definitions before the next voyage begins.

Common mistakes

Treating vessel readiness as proof that every product and receiving condition is complete can mislead customers. Another mistake is asking an agent to decide a quality question outside its mandate.

Avoid circulating forecasts without their source and status. Recipients need to distinguish an estimate from a requested or confirmed programme.

Do not close the call administratively while unresolved documentation actions have no owner. A completed cargo operation can still leave a commercial handover incomplete.

Where Zeaclub fits

Zeaclub offers digitalised procedures across the voyage workflow.

Zeaclub provides 24/7 operating systems and worldwide coverage.

Explore Zeaclub

Learn about Zeaclub