SHELLVOY handover after loading: what remains open?

Key takeaways

• Cargo aboard does not mean every commercial question has been settled.
• Separate voyage instructions, cargo descriptions, freight inputs and document requests.
• Identify whether an outstanding item needs factual correction, commercial agreement or specialist review.
• Keep unresolved differences visible without presenting them as established claims.
• Give the next desk an action sequence tied to the actual voyage.

Start with the consequence of each open item

The useful question at loading completion is not simply whether a document has arrived. It is what the missing or disputed information prevents someone from doing. An unavailable final quantity may delay a freight calculation. An unresolved consignee instruction may affect preparation of a cargo document. A changed destination request may require a separate commercial decision. These are different problems even when they appear in the same email.

BIMCO's tanker chartering workshop includes the interaction of bills of lading, charter parties and sale contracts. That is the narrow source context here. This article offers an original handover framework; it does not prescribe a SHELLVOY clause outcome. Check the current text, including the agreed version and amendments, when identifying obligations or rights.

Build the handover around decisions that will arise next. A receiving operator should not have to reconstruct the entire fixture to discover that a document instruction remains disputed. Conversely, the operator should not interpret a prominently flagged discrepancy as an instruction to stop an otherwise authorised activity. State the actual consequence and the person responsible for deciding it.

Separate the cargo account from the document account

The cargo account describes what was reported as loaded, where the figures came from, and whether their status is preliminary or final. It should preserve material qualifications from the relevant source. Commercial staff should not silently reconcile different measurements by choosing whichever figure makes an invoice easier to issue.

The document account describes what has been requested, prepared, issued or challenged. A draft may accurately reproduce a customer's request without being authorised for issue. An issued document may later become the subject of a proposed correction. Those states should remain distinct because the action needed is different in each case.

Do not allow a filename such as “final cargo pack” to settle either account. Check the content and the issuing status of the individual records. A final operations summary can coexist with a provisional commercial quantity. A complete scan collection can still contain a document whose correction is under review.

Where a quantity difference matters to freight, identify the contractual calculation basis for review. Where it concerns cargo condition or description, route the evidence to the appropriate cargo and document specialists. One discrepancy can affect several decisions without producing the same answer for each.

Transfer the voyage instruction, not an inferred intention

After loading, messages may discuss the receiver's preference, the charterer's commercial plan and the vessel's actual instructions. The handover should identify which communication provides the operative direction and what conditions remain attached. A sales conversation is useful background but should not be promoted into an instruction merely because departure is approaching.

Describe the instruction at the level necessary for the next desk: issuing party, authorised recipient, requested action, unresolved conditions and any required response. Technical execution remains with the responsible maritime personnel. The commercial handover should make authority and scope clear without attempting to navigate or operate the vessel.

If a later message appears inconsistent with the existing plan, explain the conflict. Do not replace the earlier instruction in the handover and leave the receiving desk unaware of the change. The question may be whether a commercial variation is proposed, whether an existing option is being exercised, or whether a factual correction is needed. That classification affects who must respond.

Use a responsibility checklist built around decisions

The owner in this table is the person coordinating the decision, not necessarily the person with power to make it. Name both where they differ. An operator can gather a revised document request while the principal or specialist decides whether it can be accepted.

Set a next action for each row. “Awaiting documents” is too broad if the next desk needs to chase a named source, clarify the requested correction and avoid circulating an outdated draft. A useful next action tells the recipient what would change the item's status.

Fictional case: a correction becomes a new instruction

In a fictional tanker fixture, the loading desk receives a request to amend a cargo document's destination field. The email says the receiver is considering an alternative discharge arrangement. The document coordinator marks the requested change for review but does not agree a voyage variation.

During shift handover, the incoming desk sees the revised draft and assumes the alternative destination has been authorised. It begins preparing the commercial arrival plan around that assumption. The actual voyage instruction still names the original destination.

The problem is not solved by deciding which file is newer. The desks must recover the purpose and authority of the request. The draft records a proposed document change; it does not, by itself, establish an agreed change to the voyage.

A better handover would state that the receiver's proposal is under review, the existing instruction remains the last confirmed direction, and the responsible principal must resolve the requested variation. The document reviewer would receive the factual context, while operations would receive an explicit instruction status. The case is illustrative and does not decide any party's rights under an actual charter.

Close the loading phase without losing its unfinished work

A good handover can close a completed operational phase while carrying forward specific commercial tasks. Keeping the whole loading file labelled “open” indefinitely makes it harder to distinguish a genuine execution problem from routine account completion. Closing everything because the vessel has sailed creates the opposite problem.

Use a short completion statement followed by the exceptions. For example, identify the reported completion of loading, then list the unresolved freight input, document review and evidence request separately. Preserve who supplied the operational statement; do not convert a desk summary into an independent technical certification.

The receiving desk should acknowledge the decisions it owns. That acknowledgment confirms transfer of work, not acceptance of the underlying cargo figures, contractual positions or third-party requests. This distinction helps teams act promptly while leaving substantive questions with the people authorised to answer them.

Common mistakes

Treating departure as commercial closure leaves unfinished freight and document issues without an owner. Treating every unresolved issue as a departure restriction introduces a different unsupported conclusion. Record the actual operational consequence rather than assuming one.

Another mistake is using a revised cargo document as proof of a revised voyage instruction. Compare the purpose, authority and status of the communications. Finally, avoid an attachment-only handover: the next desk needs the outstanding decision and its commercial significance, not merely access to the same folder.

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