Follow-the-Sun Operations: Human Approval at the Shift Boundary

Key takeaways

• Separate receipt of a handover from acceptance of decision ownership.
• Make authority limits and escalation contacts visible on each open item.
• Preserve the approved instruction version across desks and time references.

Define what the next desk is taking over

Prepare a handover around active decisions rather than a chronological list of every message. For each item, state the current situation, required next action, responsible owner, relevant time reference and supporting documents. The receiving operator should understand why the item matters without reconstructing the whole voyage.

Distinguish monitoring from decision authority. A desk may be responsible for watching for a terminal response but not authorised to accept a commercial change. Make that distinction explicit so availability across time zones does not become an accidental expansion of authority.

Identify the scope of cover: voyages, ports, counterparties and workstreams included. A regional desk covering a port call may not be taking over claims negotiation or payment approval. The handover should name the continuing owner for those matters.

Make ownership transfer explicit

Use an acknowledgement that identifies the items the receiving desk has accepted. A generic “received, thanks” may confirm delivery without confirming that someone has reviewed the open decisions. Allow the receiver to flag missing information or an item outside their authority.

Keep the outgoing desk responsible for resolving unclear ownership through the agreed escalation route. The process should not depend on both teams assuming the other is handling an urgent issue. If an item cannot be transferred, name the duty person who remains accountable.

Record the transfer time and relevant source version. This helps explain which information the receiving desk had when it acted. If a material update arrives during the overlap period, identify whether the outgoing or incoming operator will incorporate it and notify affected participants.

Use a shift-boundary authority map

The map is a recommended operating design, not a substitute for the organisation's delegation rules. Adapt the roles to actual staffing and name substitutes for unavailable decision makers. A useful map tells the duty operator both what they can do and where the next decision belongs.

Review the map when coverage expands. Adding another time zone does not automatically provide every expertise or authority needed for every event. Match the service promise to the decisions the receiving desk can actually support.

Keep time references and deadlines intelligible

State event times and action deadlines with an explicit reference. Preserve the original local time where it matters and distinguish it from the office's display time. A handover note saying “tomorrow morning” can become misleading when read by another region.

Separate a contractual deadline, an operational target and an internal reminder. They may appear close together in a task list but have different significance. The receiving desk needs to know which source establishes each timing requirement and who reviewed it.

For uncertain deadlines, make the uncertainty visible and escalate promptly. Do not allow the scheduling tool to convert an unverified phrase into an apparently authoritative countdown. The system can organise reminders, while the responsible person confirms the underlying requirement.

Use automation to prepare, not assume acceptance

An assistant can summarise recent changes, identify unanswered messages and propose a handover draft. The outgoing operator should check the draft against the actual open work, especially where the model might confuse a discussion with an approved instruction.

The incoming operator should receive source links and the current decision status. A polished summary is insufficient if it omits a qualification or presents a proposal as agreed. The interface should make it easy to inspect the relevant message without searching through unrelated correspondence.

As an original workflow recommendation, keep automated task assignment distinct from a human's acceptance of responsibility. This is particularly important when a task is routed to a group rather than an individual. The record should show who is actively handling it, not merely which queue contains it.

Prepare escalation and interruption routes

Create an escalation directory by decision type, with named duty contacts and substitutes. Include the information needed for a useful escalation: voyage reference, proposed action, relevant source and the decision required. A concise, complete request is easier to resolve than a forwarded chain labelled urgent.

Plan for connectivity problems, unavailable reviewers and unexpected workload. The receiving desk should know how to preserve the current state and continue the approved process manually. A fallback should not silently grant broader authority because the normal application is unavailable.

After an incident, review whether the handover contained the information and authority needed. Focus on the process: missing ownership, unclear timing or inaccessible evidence. Avoid assuming that another reminder would have solved a problem caused by an undefined decision owner.

Fictional case: a revised discharge instruction between shifts

In this fictional case, the outgoing desk receives a proposed terminal change shortly before handing over a tanker voyage. The automated summary says “discharge terminal updated”, although technical and commercial responses are still pending.

The outgoing operator corrects the handover to show a proposed change and names the decision owners. The incoming desk accepts responsibility for collecting the responses and monitoring the vessel's update, while release of revised instructions remains with the authorised operator.

When approval arrives, the instruction is issued with its revision and recipients recorded. The shift transfer has kept the work moving without allowing an ambiguous summary to become an operational command.

Common mistakes

Do not equate receipt of a handover email with acceptance of every task. Another mistake is describing an unresolved proposal as a completed update. Preserve the decision status and authority owner.

Avoid relative times such as “later today” without context. Finally, do not use broad regional coverage as a substitute for specialist escalation. Continuous availability is useful only when the operator can reach the person authorised to decide the actual issue.

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

Visit the Zeaclub website