ASBATANKVOY handover: prepare for a discharge exception

Key takeaways

• Prepare the exception path before the discharge call becomes busy.
• Distinguish an operational observation from its proposed technical explanation.
• Keep cargo, time and expense consequences separate in the commercial review.
• Identify who obtains local records and who follows up after departure.

Begin with the agreed commercial plan

Use the actual fixture documents and authorised discharge instructions as the starting point. Identify the cargo, intended destination arrangements and any conditions still awaiting confirmation. Do not rely on the original enquiry if negotiation changed those assumptions.

Ask the contractual reviewer to identify the provisions relevant to the expected operation and possible exceptions. Check the current text rather than assuming every ASBATANKVOY edition or amended fixture uses the same mechanism.

The handover should not reproduce the whole charter. It should identify the commercial questions that operators may need to raise, the evidence to preserve and the person who can decide. A useful brief connects the agreement to the work without turning an operational summary into a substitute contract.

Define the local evidence role

FONASBA's tramp-agency training material distinguishes pre-arrival, in-port and post-departure agency work. The appointed agent's actual scope should determine which local coordination and evidence tasks it undertakes for the call.

Identify who will obtain the relevant event records and who can clarify a terminal communication. The agent may be well placed to coordinate local information, but the handover should not assume that every technical report or commercial assessment falls within its appointment.

Specify the source needed for each important question. A general update from a local contact may help the team understand prospects, while a later contractual review may require a more precise record from the person or organisation responsible for the observation.

Prepare an exception-focused handover table

The table is a preparation framework. It does not prescribe discharge procedures or determine whether time counts, a performance promise was breached or an expense is recoverable.

Record the interruption before assigning its consequence

If discharge is interrupted, identify what stopped and when. Preserve the stated reason and its source, but distinguish a contemporaneous observation from a later explanation. Different participants may describe the same period from different perspectives.

Avoid reducing the event to a single commercial label too early. A description such as terminal delay may conceal changing causes or an unresolved technical question. The reviewer needs the factual sequence before assessing the treatment under the actual agreement.

If the interruption changes character, record that development. The commercial team may need to examine different parts of the sequence separately. A continuous period on a schedule does not necessarily mean that every part has the same factual or contractual basis.

Keep technical assessment with the qualified parties

The handover can identify the records and contacts needed for a performance review, but should not tell the vessel or terminal how to conduct the operation. Technical decisions require the responsible qualified people and the applicable safety arrangements.

Likewise, a commercial concern should not be presented as a technical finding. If a party alleges that an expectation was not met, state the allegation and obtain the relevant assessment. Do not rewrite a working report to make it support the preferred commercial position.

The contractual adviser then needs the actual wording and reliable facts. The role of coordination is to connect those inputs, preserving qualifications and uncertainty. It is not to infer liability from a dashboard status or an isolated operational figure.

Fictional case: the reason for an interruption changes

A fictional tanker discharge pauses, and an early update attributes the interruption to a receiving arrangement. Later communications identify a different issue affecting the continuation of work. The voyage summary retains the original explanation for the entire period.

During handover review, the incoming operator asks whether the cause remained the same. The coordinator separates the event sequence and obtains the relevant source explanations. The commercial team can now identify which facts need technical assessment and which contractual questions remain open.

The correction does not decide who bears the delay. It prevents an early shorthand explanation from becoming the assumed basis of the whole claim review. The case shows why a useful handover must preserve developments within an exception, not merely record that an exception occurred.

Authorise additional work without obscuring the dispute

An interruption may prompt a request for an additional service, inspection or local arrangement. Identify who is requesting the work, its purpose and the person authorised to approve it. The practical need to obtain evidence should not leave responsibility for the instruction unclear.

Keep the approval of the task separate from any conclusion about who ultimately bears its cost. The actual agreement and authorised communications determine that issue. A coordinator should not promise reimbursement or accept liability merely to keep the file moving.

Where the parties need to protect their positions, obtain appropriate advice on the communication. The operational team can still organise the necessary facts and practical next steps while the commercial consequences remain under review.

Carry the unfinished work beyond departure

Before the local team disengages, identify missing documents, explanations and disputed observations. Assign a named owner to each item and state why it matters. A request tied to a specific question is more useful than a general instruction to complete the file.

The receiving commercial team should know which records are final, which are corrected and which remain contested. Preserve the source versions and the reason for any change. A later review should not have to infer the history from inconsistent attachments.

Do not treat departure as closure of every issue. The physical operation may be complete while a cargo, time or expense question remains unresolved. The handover should make those continuing responsibilities visible without assuming a particular claim outcome.

Test the brief with the receiving operator

Ask the incoming operator to walk through a realistic exception. It should be able to identify the next fact to obtain, the person qualified to assess it and the authorised commercial decision-maker.

If the answer is simply to contact everyone, the brief needs refinement. The goal is a usable route through the issue, with appropriate access to the full documents. Clear responsibility reduces repeated requests and helps preserve evidence while the event is still understood by those involved.

Common mistakes

An early explanation can remain attached to an interruption after circumstances change. Other mistakes include asking coordinators to make technical findings, approving extra work without identifying authority and leaving closing evidence tasks unowned after departure. Prepare the exception path and keep each commercial consequence distinct.

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