VLCC Port Calls: Aligning Cargo, Berth and Vessel Decisions

Overview

The most useful plan identifies the next decision required from each party. It should help a crude desk understand whether a programme change affects loading, receipt, expense approval, or a downstream delivery commitment.

Key takeaways

• Separate vessel estimates from terminal requests and actual events.
• Assign a clear owner to cargo and local-service confirmations.
• Explain the commercial consequence of programme changes.
• Preserve a factual chronology for handover and later review.

Define the call before distributing updates

Start with the purpose of the call and the parcel it concerns. For a loading call, identify the crude allocation and seller readiness. For discharge, identify the receiver and intended facility. If the call is one part of a larger delivery programme, show the commitment that depends on completion.

Name the event each team is planning around. Expected arrival, a terminal's requested timing, and actual completion are different information types. An update should not lose that distinction when it moves from an operational message into the cargo desk's schedule.

The IMO Compendium distinguishes estimated, requested, and actual port-call data. See the official dataset.

Commercially, this means that an updated vessel estimate should not overwrite a terminal request as though they were the same fact. Keep both visible when they differ and identify who must resolve the resulting coordination question.

Assign authority as well as information responsibility

Build a contact map covering the owner or operator, appointed agent, terminal channel, seller or receiver, cargo desk, and commercial approver. For each party, state what information it supplies and what decisions it can make.

The appointed agent may coordinate local information and services within its mandate. It should not be assumed to control the terminal's programme, the buyer's crude allocation, or another principal's expense authority. Those distinctions need to be clear before a time-sensitive request arrives.

Similarly, a cargo planner may identify the buyer's preferred timing without being authorised to amend the freight arrangement. The chartering coordinator should route the commercial consequence to the appropriate approver rather than let a planning request become an apparent instruction by repetition.

Include an escalation contact for periods when the usual decision maker is unavailable. The fallback needs defined authority. A larger distribution list does not solve an approval gap if nobody on it can make the required decision.

Use a VLCC call decision map

The map below focuses on the interaction between a crude programme and the local call. Adapt it to the actual appointment and transaction rather than assuming every party has the same responsibilities on every voyage.

Each open issue should state the next action and expected response path. Avoid a status that merely says all parties informed. Information circulation is useful, but it does not establish that the necessary decision has been made.

Where two parties must agree, describe the handoff. For example, the terminal may propose a timing change, the owner supplies its assessment, and the cargo desk decides how to address the supply consequence. The coordinator links those steps without substituting for them.

Respond to a programme change in a controlled sequence

First establish what changed and who supplied the information. Distinguish a proposed adjustment from a confirmed event. Then identify the affected commercial commitments and the parties that need to respond.

Send a concise change summary containing the current plan, the proposed revision, and the decisions still outstanding. A forwarded chain can contain all the facts while leaving recipients uncertain about which version is current.

If the change affects a review assumption, route it back to the appropriate reviewer. A revised terminal or crude allocation may require a different assessment. The port-call coordinator should identify that dependency, not decide technical acceptability through a schedule update.

Where additional expense is proposed, preserve the request and the authorised response. Do not describe a service as approved simply because it has been discussed locally. The commercial record should show the scope to which the principal actually agreed.

Fictional case: a requested time becomes a customer promise

A fictional crude buyer coordinates a VLCC discharge. The terminal sends a requested programme, and the cargo planner copies its timing into a refinery supply report as though it were a confirmed completion forecast.

The call coordinator notices that the owner's current outlook and terminal request refer to different milestones. The coordinator circulates a clarified plan showing both information types and asks the appropriate parties to resolve the intended arrangement.

The refinery planner revises its supply communication and identifies the decision it needs before making further commitments. The agent continues local coordination, while the owner provides the vessel-related assessment through the authorised channel.

The issue is resolved through better information meaning, not by demanding more frequent messages. The same timestamp can mislead when its status and event definition disappear during internal reporting.

Keep records useful after the call

Maintain a chronology of material forecasts, requests, decisions, and actual events. Retain the source and time of the information. Do not rewrite earlier forecasts after the outcome becomes known, because the earlier record explains what the parties understood when they acted.

For commercial time or expense questions, preserve facts and route interpretation to the responsible contracting or legal team. Check the current text of the applicable agreement rather than infer rights from an isolated port report.

At completion, identify outstanding cargo records, service confirmations, and approvals. Assign them to named owners before handover. The vessel's departure does not necessarily mean the commercial record is complete.

Review the call by asking where a decision lacked an owner or where information changed meaning between teams. That produces specific improvements to the next coordination map, rather than a general instruction to communicate more.

Common mistakes

A frequent error is treating every timestamp as an equally firm promise. Another is assuming that the local agent can approve changes affecting the cargo transaction or another party's expense.

Avoid issuing a revised shared plan without identifying which earlier version it replaces. Different teams can otherwise continue acting on different programmes while believing they are aligned.

Do not add contractual conclusions to factual event records casually. Keep the evidence intact and seek the relevant review of the actual terms.

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