Overview
The shared plan must preserve one coherent voyage while allowing each receiver to understand its own obligation. That requires explicit handoffs between the cargo desk, owner, agents, and terminal channels.
Key takeaways
- Give every allocation a clear receiver and milestone reference.
- Track changes at one call against the remaining programme.
- Separate customer preferences from authorised voyage instructions.
- Close local issues without losing their wider commercial consequences.
Create a customer-linked call plan
List the actual product allocations and intended calls in sequence. For each, identify the receiver, relevant facility, quantity basis, and commercial milestone that matters to the customer. Keep optional calls clearly separate from confirmed deliveries.
The plan should not expose unrelated confidential information unnecessarily. Each customer may receive only its relevant view, while the internal coordinator maintains the complete programme needed to understand dependencies.
Assign a source for every material input. The owner supplies the relevant vessel outlook, the receiver or terminal supplies its own programme, and the cargo desk owns sales allocation decisions. A combined summary should not erase those responsibilities.
Use consistent event definitions. IMO's facilitation work addresses shared meanings for maritime information exchange. See its meeting summary on data harmonisation. The practical goal is that each customer understands which event its forecast describes.
Distinguish local issues from voyage-wide changes
A receiver may request a different timing or allocation. First establish whether the request concerns only that customer's planning or requires a change to the vessel's commercial programme.
Ask the owner for the relevant assessment if the sequence or timing basis changes. The coordinator should not infer the effect on later calls or prescribe technical measures to preserve old customer dates.
The cargo desk should assess the sales consequences across the whole programme. A change that helps one customer may affect another allocation, and the authority to choose that trade-off should be clear.
Keep the original current plan in place while a proposal is evaluated, subject to the actual arrangements. Label the change as proposed until the necessary decisions and communications are complete.
Use a customer-impact responsibility map
The map below focuses on the handoffs that can fail when several receivers share one MR product programme.
| Issue raised | Initial information source | Wider question | Responsible coordination path |
|---|---|---|---|
| Customer requests later receipt | Receiver's authorised contact | Does it affect the remaining sequence? | Cargo desk with owner assessment |
| Product allocation changes | Sales or supply desk | Which records and calls change? | Commercial coordinator and document owners |
| Vessel forecast moves | Owner's authorised channel | Which customer milestone is affected? | Coordinator to relevant receiver channels |
| Terminal proposes another arrangement | Terminal channel | Is renewed review or agreement needed? | Owner and qualified reviewers |
| Optional customer confirms | Cargo sales desk | Is the option within agreed scope? | Chartering and contracting parties |
| Local expense is proposed | Appointed agent | Who can approve this scope? | Relevant commercial principal |
| One call completes | Responsible operational source | What becomes current for later deliveries? | Coordinator and next-call contacts |
The map should identify a named owner for each open action. A broad all parties copied status does not establish that the next customer has received a meaningful update or that the required decision has been made.
Where two teams share a handoff, state the sequence. For example, the owner provides a revised outlook, the cargo desk decides how to address customer commitments, and the coordinator distributes the authorised current view.
Communicate with each customer without fragmenting the plan
A customer update should identify its parcel, relevant milestone, forecast status, and material condition. Avoid forwarding the entire operational chain without explanation; it may contain information that is irrelevant or easily misinterpreted.
At the same time, do not let separate customer messages create inconsistent promises. The internal plan should be the source for each tailored update, with any customer agreement fed back into the shared record.
If a sales contact offers a timing concession, identify whether it changes the maritime programme or only the customer's commercial expectation. Those are different decisions and should not be conflated.
The coordinator should also record when a customer has not yet acknowledged a material change. Sending information is an important step, but it does not prove that the receiver's programme is aligned.
Fictional case: one customer's concession creates another's problem
A fictional distributor serves several product customers on an MR voyage. One customer asks for a later receiving opportunity, and its sales contact agrees informally without consulting the shipping coordinator.
The customer-impact map identifies that the proposed arrangement could affect later deliveries. The owner supplies the relevant updated outlook, and the cargo desk evaluates the consequences for the other customers before confirming a voyage change.
The distributor then sends consistent customer-specific updates based on the authorised plan. If the original concession cannot be accommodated as proposed, the sales team discusses another commercial response rather than leaving the vessel programme ambiguous.
The case demonstrates why customer service and voyage coordination need a defined connection. A helpful local promise can create a wider conflict when it is made outside the complete programme.
Hand over the remaining programme after each call
Do not wait until the last discharge to reconcile the record. After a call, update actual events, remaining allocations, current forecasts, and outstanding decisions. This gives the next coordinator a clear starting point.
Identify unresolved documents or commercial issues by customer and parcel. A general pending paperwork note can hide an item that affects only one receiver or a specific close-out action.
Retain material earlier forecasts and changes. The history helps explain what each customer was told and on what basis, without rewriting the record after the final outcome is known.
At completion, review where the programme fragmented. Improvements may involve a clearer customer update owner, better milestone definitions, or earlier escalation of requests that affect other deliveries.
Common mistakes
Allowing each sales contact to alter customer timing independently can create incompatible promises. Another mistake is treating a receiver request as an authorised vessel instruction.
Avoid forwarding raw updates without identifying the customer-specific consequence. Recipients need to know which event and parcel the information concerns.
Do not close a local issue without checking its effect on the remaining programme. A call-level decision can have voyage-wide commercial consequences.
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
Educational information only; not legal, financial or trading advice. Contract wording and applicable rules control. Verify current requirements and obtain qualified advice before acting.
Frequently asked questions
Should every customer receive the complete voyage plan?
Not necessarily. Provide the information relevant to its parcel and commitment while maintaining a coherent internal programme. Respect the applicable confidentiality and communication arrangements.
Who decides whether one customer's request can be accepted?
The authorised commercial parties assess the trade-off with relevant owner and receiver input. The coordinator identifies wider effects and prevents a local preference from becoming an unsupported programme change.
What should happen after one delivery completes?
Update actual events and the remaining parcel-linked plan, then communicate relevant consequences through the agreed channels. Preserve unresolved actions with named owners for the next call.
How can customer updates stay consistent?
Use one controlled internal plan as their source and feed customer decisions back into it. Tailored messages should differ in relevance, not in the underlying authorised voyage basis.