Handysize Handover for Several Cargo Receivers

Key takeaways

• Connect each receiver to the cargo and service it is meant to receive.
• Identify the active call sequence and its review conditions.
• Separate local coordination contacts from commercial decision makers.
• Record how a change at one destination affects later commitments.

Start with the delivery promise

The handover should explain what the shipment is intended to deliver to each receiver. Identify the cargo lot or grade, quantity basis, nominated destination and relevant receiving arrangement. The aggregate cargo total cannot establish whether the distribution matches the commercial instruction.

Use the active allocation approved by the principal. If a receiver's share or terminal remains optional, show the decision still required and who may make it. Do not present a possible allocation as settled simply because it appears in the latest planning spreadsheet.

IMO's Compendium distinguishes commercial roles including voyage charterer and commercial manager. IMO company-role definitions.

In the actual shipment, identify the people who hold the relevant authority rather than assuming it from a copied email list. An agent or local receiver contact may coordinate information without being able to amend the commercial allocation.

Preserve the sequence and its assumptions

Record the selected call order together with the vessel and terminal responses that support it. Qualified personnel determine the operational implications of the proposed cargo arrangement; the handover should transmit their conclusions within the stated scope.

If an alternative sequence was discussed but not selected, label it as historical or conditional. Operations should not have to decide which itinerary is active by comparing message dates. A later proposal can remain unapproved while an earlier instruction still governs.

Explain any condition that affects more than one receiver. A change at the first call may require later service or receiving assumptions to be reconfirmed. The handover should identify that link without inventing a fixed delay or a universal operational consequence.

Keep the actual schedule estimates separate from the commercial allocation. A receiver's timing preference is useful information, but it should not alter the call order automatically.

Build a receiver instruction map

Link the original instructions and relevant responses behind the map. The table is a guide to the active arrangement, not a replacement for contractual documents or technical plans. Where meaning or rights are uncertain, check the actual terms with appropriate advisers.

Ask the receiving operations colleague to identify which decisions remain open. An acknowledgment that the file arrived is less useful than confirmation that the colleague understands the unresolved nomination or receiver instruction.

A fictional receiver request affects the next call

In this fictional case, a Handysize shipment serves several receivers. After fixture, the first receiver asks the agent about retaining an additional portion of cargo. The agent forwards the request to operations, and a planner begins revising the local delivery sheet.

The handover map shows that the requested quantity belongs to a later receiver under the active allocation. The coordinator therefore treats the message as a proposal requiring the principal's decision, not an operational instruction. It also identifies the vessel and receiving arrangements that would need review if the change were selected.

The principal asks for the commercial consequences and decides whether to investigate the revision. Until an authorized new allocation is issued, operations retains the existing plan. The local contact receives a clear status update rather than an ambiguous suggestion that the request has been accepted.

The fictional lesson is that helpful local coordination can unintentionally change another party's delivery promise. A receiver-specific authority map exposes that connection before instructions diverge.

Define a change process that reaches every affected party

A request to change cargo allocation, terminal or sequence should identify the current instruction and the proposed difference. The coordinator should gather the affected commercial and technical responses before presenting the proposal as approved.

Once the principal makes a decision, issue a consolidated revision. Identify the receivers, providers and reviewers who need the updated information. Do not assume that copying one agent means every affected party has the new instruction.

If the change is declined, close the request clearly and retain the active plan. Otherwise a receiver may continue preparing for an alternative that the principal has not selected. The history should show the proposal and outcome without confusing either with the governing instruction.

Reconfirm service availability where the change affects its assumptions. A provider's earlier response may have been tied to a different window or cargo allocation. The coordinator should preserve the scope of the reconfirmation rather than treating it as approval of every commercial consequence.

Keep costs and claims outside the local instruction shortcut

A local request can add services or change the compared cost boundary. Identify the payer, approval authority and any unresolved allocation before issuing a new service order. Operational convenience does not establish who ultimately bears the cost.

Where contractual responsibility is disputed, record the facts and obtain appropriate review. The handover should make clear who may authorize necessary work while the allocation question is considered. Do not settle that question accidentally by using an imprecise phrase in a routine message.

Preserve the approved cost baseline and link changes to their causes. This helps later invoice reconciliation and prevents an extra receiver service from being treated as though it had always been included in freight.

Transfer the next decisions, not only the completed ones

The final handover should highlight outstanding receiver confirmations, terminal choices and review responses. Each needs a coordinator, a decision maker and a closure test. A broad note that receivers are coordinating is not enough for the next colleague to act.

Keep the active allocation accessible alongside the event register. When a schedule update arrives, operations can then see which receivers and services are affected. When a commercial request arrives, it can identify which operational assumptions need revisiting.

After delivery, reconcile the actual commercial records with the authorized allocation and documented revisions. The aim is to explain what happened using the decision trail, rather than reconstructing the plan from whichever local message was easiest to find.

Common mistakes

Providing only a cargo total loses the receiver-specific delivery promise. Include the allocation map.

Treating a local contact as a commercial authority can turn a request into an unauthorized change. Name the decision maker.

Updating one receiver's instruction without checking later calls fragments the shipment plan. Issue a coherent revision.

Assuming extra service costs follow automatically from an operational request hides the approval and allocation questions. Address them separately.

Where Zeaclub fits

Zeaclub supports agentic, AI-assisted operations with a human in control.

Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.

Explore Zeaclub

Visit the Zeaclub website