Follow-the-sun operations: handle exceptions between desks

Key takeaways

• Transfer the unresolved decision, its consequence and its current evidence.
• Distinguish a missing fact from a missing approval or unavailable participant.
• State what the receiving desk can continue while the issue remains open.
• Preserve conflicting instructions until the responsible person clarifies them.
• Confirm ownership of the next action instead of relying on message delivery.

Describe the exception in terms of work

Start with the task that cannot proceed as expected. A receiving operator may be unable to confirm which instruction is current, obtain a necessary response or identify who can approve a proposed change. Those are different problems.

Write what is known, what is uncertain and what consequence follows from the uncertainty. A useful description might say that two source messages give different destinations and that the desk needs clarification before preparing the next operational communication.

Avoid transferring a long message chain with only “please handle” added. The next team may lack the history required to recognise the decision hidden in the correspondence. It should receive a concise explanation and access to the relevant evidence.

This article presents an original coordination framework using fictional desk scenarios. It does not prescribe navigational actions, emergency procedures or contractual rights.

Distinguish the cause of the blockage

An information gap requires a fact or source clarification. An authority gap requires a decision by the responsible person. A capability gap may require support or another team able to complete a task. Treating all three as a request for an update can waste the receiving desk's effort.

If the outgoing team has already contacted someone, record the question asked and whether a response is pending. Repeating a broad request through another channel can create competing answers without resolving the original ambiguity.

Identify any condition that makes the issue time-sensitive, using the actual business evidence. Do not invent a deadline merely to make the handover appear urgent. The receiving desk should understand both the consequence of delay and the basis for the timing.

Where a separate safety or emergency process applies, use the organisation's established route. A commercial shift handover should not become a substitute for the responsible operational response.

Use an exception transfer worksheet

The worksheet is a proposal for organising work, not a universal escalation hierarchy. Adapt roles and routes to the organisation's actual responsibilities.

Each row should lead to a specific action. A label such as urgent exception is less useful than an explanation of who must clarify what before which task can continue.

Transfer authority accurately

State the receiving team's actual scope. It may be authorised to gather information, prepare a draft or implement an already accepted instruction. Those tasks do not necessarily include deciding a new commercial position.

If delegated cover exists, identify the delegation and its limits through the approved internal process. Do not assume that the desk currently on duty can approve anything simply because the original decision-maker is unavailable.

Keep a proposed solution separate from an accepted one. The outgoing operator can explain a possible way forward, but the receiving team should recognise whether it has been reviewed or remains only a suggestion.

Record a decision in the terms given by the authorised person. An instruction to prepare a revised draft should not become an instruction to send it merely because the desk is trying to clear its queue.

Preserve conflicting evidence without freezing every task

When sources disagree, show the difference rather than replacing it with a guessed synthesis. The sequence of messages may matter, but later timing alone does not establish that a message has the necessary authority or applies to the same case.

Identify work that can continue without prejudging the open question. The desk may be able to collect supporting material, prepare alternatives or confirm receipt while the responsible person resolves the conflict. State those boundaries explicitly.

Avoid allowing provisional preparation to look like implementation. A draft based on one possible outcome should be labelled and handled according to the organisation's process so it does not become an unintended instruction.

Once clarification arrives, review the affected work. A resolved question may require updating a draft, correcting a prior summary or notifying another participant that a provisional assumption has changed.

Fictional case: two desks send different follow-ups

In a fictional operation, the outgoing desk asks a commercial manager to clarify whether a revised destination has been accepted. It then forwards the correspondence to the next desk without identifying the pending question or the existing request.

The receiving desk asks a different participant whether the vessel can accommodate the proposed destination. That participant answers the capability question, and the response is interpreted as acceptance of the commercial change. Meanwhile, the original clarification remains unanswered.

Before a communication is sent, an operator notices that the two questions were different. The desks reconstruct the exception: capability information is available, but the relevant acceptance decision is still pending. The next action returns to the authorised commercial route.

The improved handover states the exact unresolved question, the person already contacted and the work that may proceed meanwhile. The example shows why a useful response to the wrong question can still leave the actual decision unresolved.

Confirm receipt of responsibility

Ask the receiving owner to acknowledge the action they are taking, not only that they can see the message. This makes it easier to identify an issue that falls outside their role before the outgoing desk assumes it has been transferred.

If the receiver cannot accept the work, the exception needs another identified route. Do not let it become ownerless because both teams believe the other has the better contact or more relevant expertise.

Keep pending external responses connected to the current owner. A reply may arrive through the outgoing operator's channel after the transfer. The agreed process should ensure that it reaches the person now responsible for assessing and acting on it.

Preserve the evidence, but make the current position and active next step easy to find.

Close the exception after its consequence is addressed

A reply does not necessarily close an exception. Check whether it answers the actual question, carries qualifications or creates another dependency. Record the decision or fact established and the work still required.

Then confirm that affected records and participants have been updated. An instruction can be clarified while an earlier draft remains in circulation. Closing the issue should include the practical consequence of the clarification, not just the arrival of the answer.

For recurring exceptions, review the transfer design. Repeated confusion about who approves a change may indicate an unclear authority map. Repeated missing source context may indicate that the handover format is too focused on status labels.

Common mistakes

Avoid forwarding a chain without the unresolved question, assuming the on-duty desk has unlimited authority or treating a capability response as commercial acceptance. Do not let duplicate follow-ups create competing interpretations.

Another mistake is closing the exception when a message arrives without checking whether the affected task and records have been corrected.

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