Off-hire handover when vessel service resumes

Key takeaways

• Describe the reported capability and its source without broadening the confirmation.
• Identify the next operational instruction independently of the hire dispute.
• Preserve the factual sequence around resumption for contractual review.
• Keep provisional estimates separate from approved account treatment.
• Assign unfinished factual and commercial questions to named roles.

Resumption creates several different decisions

Steamship Mutual's off-hire guidance discusses the relationship between the applicable clause and the end of an off-hire period. Check the current text and obtain advice before treating any operational update as the decisive contractual endpoint.

The handover should answer several practical questions. What has the vessel reported about its capability? What service is now instructed? What evidence remains necessary for the hire assessment? Has the principal authorised any account action? A short message that the vessel is “back” can leave all of these unclear.

Operational recovery and commercial close-out often proceed on different information. The next desk may need to coordinate employment while the earlier event remains under review. It should not have to wait for a final account conclusion merely to understand the current operational instruction.

Equally, commercial staff should not treat the need to resume routine coordination as a reason to close the hire issue without review. Carry the unresolved question forward explicitly and keep it separate from the live operational task.

Transfer capability within the source's scope

A technical message can be precise about a completed task while saying little about the next employment. A vessel report may confirm readiness for a specified operation with qualifications. Preserve those distinctions instead of rewriting all positive updates as unrestricted availability.

The outgoing desk should identify who provided the confirmation, what it covers and whether any further confirmation is expected. It should not issue its own engineering judgement or remove limitations because they complicate a commercial summary.

The incoming desk then knows which factual statements it can relay within its authority. If the next instruction requires a capability outside the confirmation's scope, route the question to the responsible operational or technical personnel. Do not use the hire discussion to answer a technical question.

This protects the usefulness of the handover. A carefully scoped confirmation tells the next desk what is known and what remains open; a broad optimistic phrase gives it less actionable information.

Separate the live operation from the disputed interval

Prepare a live-operation section describing the current instruction, expected coordination and immediate contacts. Prepare a separate commercial section describing the proposed off-hire boundaries and the status of their review. The sections can refer to the same event without merging their decisions.

For example, the current instruction may concern a movement while the account review concerns whether an earlier interruption ended before that movement. Operations should preserve relevant facts, but it should not alter the historical chronology simply to align it with the new instruction.

If the service requirement changes during the recovery sequence, make that change visible. The incoming reviewer should not assume that the same operational context continued throughout. Ask for clarification where the transition is uncertain.

The handover should also identify any external communication already made about hire. An internally provisional endpoint and a position formally sent to the counterparty have different consequences for the next desk's communication. Report what was actually communicated rather than summarising both as “our view”.

Use a role-based close-out checklist

Adapt the roles to the actual organisation. One person may perform several functions, but the decisions still need to be distinguished. A small team benefits from clear decision boundaries even when a formal departmental handover is unnecessary.

The checklist should identify the next substantive action for each unresolved question. “Monitor” is insufficient if the actual need is a technical clarification, a contractual review or an instruction before an account is issued.

Fictional case: a positive update closes the wrong task

In a fictional operation, the outgoing desk receives confirmation that a specified repair task has been completed. It changes the voyage record to “resumed” and marks the commercial incident closed. The incoming desk assumes that both capability and hire treatment have been settled.

A subsequent review finds that the technical message addressed the repair task, while a separate operational confirmation was still expected. The hire account also contained a provisional boundary that had never been approved. The single status label concealed different unfinished decisions.

The team corrects the handover. It records the completed technical task accurately, identifies the confirmation needed for the next instructed service and restores the commercial review as an open item. The account preparer receives a clear instruction to retain the provisional status pending the authorised decision.

The fictional case does not prescribe a technical resumption process or determine an off-hire endpoint. It demonstrates why a shared status label should not collapse distinct operational and commercial questions.

Preserve the account position during the transition

The incoming desk should know whether the account contains an estimate, a proposed claim, an agreed adjustment or an implemented transaction. These are different states. A figure can remain unchanged while its decision status changes materially.

Identify the basis of any provisional estimate and the outstanding fact that could change it. The next desk can then update the assessment when that fact arrives without inventing a new methodology or assuming that the old estimate was final.

If a payment decision is approaching, escalate the actual decision required. Do not ask the incoming operator to determine entitlement merely because that person holds the newest vessel update. The appropriate reviewer and principal should receive the current evidence in time to act within their roles.

A disagreement with the counterparty should remain visible even where the internal position is settled. Internal approval authorises the organisation's action; it does not establish external agreement.

Close the incident by resolving its components

Operational coordination can return to its normal pattern while document collection, account review or settlement remains open. Close each component when its own purpose has been fulfilled. This gives the team a more reliable picture than keeping everything open or closing everything together.

Before closing the commercial component, confirm that the final treatment is traceable to an authorised decision and that finance has the relevant instruction. Preserve any defined settlement scope and unresolved matters outside it.

For future improvement, note what made the transition difficult. The useful lesson may concern a missing capability qualification or an ambiguous account status, rather than a general demand for more messages. Change the handover field that would have made the decision clearer.

Common mistakes

The main mistake is using a single “resumed” label for technical completion, operational capability and commercial closure. Another is allowing the latest operational message to become an account instruction without review.

Avoid dropping qualifications, hiding a changed service requirement or treating internal approval as counterparty agreement. Transfer each unfinished decision with its factual basis and responsible role.

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