Hand over parsed tonnage with its unresolved questions

Overview

The handover is a transition between people and decisions, not simply an export of the parser's latest table. Its design should preserve what the outgoing reviewer knows about ambiguous messages, revisions and pending confirmation without requiring the receiving desk to reread every email.

Key takeaways

• Separate extracted candidates from reviewed and distribution-ready positions.
• Show material changes and superseded entries explicitly.
• Attach each open question to a source, owner and next action.
• Preserve conditional availability and the time context of the information.
• Obtain a clear acknowledgment of responsibility for unresolved work.

Define the state of each position

Choose workflow states that describe actual work performed. Extracted can mean that the parser produced a candidate. Reviewed can mean that a person checked the material fields against the source. Approved for distribution should mean that the relevant commercial authority and conditions have been addressed under the desk's process.

Do not use those labels interchangeably. A record can be technically well extracted while still requiring confirmation of the opening window or permission to circulate. The receiving desk needs to know which question remains, not merely see a favorable processing status.

Keep the state tied to a record version. If a new message changes the position after review, the updated fields should not automatically inherit the earlier state. The handover should identify the changed information and the review it requires.

Organize the handover by the next decision

Start with positions requiring action, then summarize material updates to reviewed entries. A chronological email dump makes the receiving desk work out priority from message order. A decision-focused view explains what must happen next and why.

For each open item, state the question in commercial terms. The source may leave uncertainty about opening place, window, vessel association or whether the message updates an existing position. Avoid a generic parse failed note when the actual uncertainty can be described precisely.

Identify the owner and expected evidence. The next step may be reviewing a source passage, asking an authorized contact for clarification or deciding how a conditional position should appear internally. The handover should not silently assign external outreach or commercial commitments beyond the receiving person's role.

Preserve the source context without overwhelming the reader

Link the record to the relevant message and passage under the appropriate access rules. Include a concise explanation of the ambiguity or change. The receiving reviewer should be able to locate the evidence without exposing unrelated commercial context to every search user.

Keep the sender's qualification where it affects meaning. A parser may normalize dates and locations, but the handover must preserve whether the position was tentative, dependent on current employment or otherwise limited. The next desk should not infer certainty from a standardized layout.

Also preserve the information's time context. State when the source was received or last reviewed through the system's established fields. Do not imply that an old position remains current merely because it appears in today's handover export.

Use an action-oriented handover table

The following table is an original design for the receiving desk. It is intended to supplement the structured record, not duplicate every vessel field.

Handle revisions as relationships, not extra rows

A later message may change an earlier position rather than introduce another vessel. Preserve that relationship. If the parser creates a new candidate, the reviewer should identify whether it supplements, corrects or replaces the existing entry.

Do not delete the prior version without explanation where the history matters. The receiving desk may need to understand why an opening window changed or why a previously circulated entry requires correction. Keep the current position clear while retaining a controlled revision trail.

Where the relationship is uncertain, hand over the uncertainty explicitly. A duplicate-looking record should not be merged solely because the names resemble each other, nor distributed as separate availability without review. The next action should address the identity and update relationship.

Fictional case: the corrected opening is handed over as a second ship

In a fictional desk workflow, an initial email provides a vessel position and a later message revises its opening window. The parser produces a candidate from each message. The outgoing reviewer notices the likely update relationship but runs out of time before resolving it.

A weak handover would export both rows with no explanation. The receiving desk might count two available positions or circulate the older window. Instead, the reviewer links the candidates and records the question: confirm that the later message replaces the earlier opening information for the same vessel.

The receiving reviewer checks the relevant source context, resolves the relationship and records the current entry's status. If the old position was already distributed, the appropriate commercial owner considers the necessary correction under the desk's process.

The case illustrates why a useful handover carries unfinished reasoning as a precise question. It does not force the next person to rediscover the relationship or rely on an unstated assumption.

Define acknowledgment and return paths

The receiving desk should acknowledge responsibility for the open queue or identify items outside its remit. A message delivered to a shared channel is not, by itself, evidence that a particular person will resolve a material exception.

Provide a route back to the outgoing reviewer or source owner for questions. The handover should contain enough context to minimize interruptions, but it should not pretend that every uncertainty can be captured in a short note. Where knowledge remains personal, identify it before the shift ends.

If an item cannot be accepted, keep it visible with a new owner or escalation. Do not allow an unassigned exception to disappear because the rest of the handover was acknowledged.

Check the handover through the receiving task

Test whether a colleague unfamiliar with the messages can identify the current position, locate the source, understand the qualification and perform the next authorized action. If the colleague must reread the entire mailbox, improve the record links and question statements.

Check the current text where confidentiality or permitted distribution is material. The handover should respect the same commercial boundaries as the source and approved output. Efficient transfer between desks should not become an excuse for unrestricted forwarding of original correspondence.

Common mistakes

One mistake is handing over a polished table without its workflow states. The receiving desk may treat every row as reviewed availability even when it is only a parser candidate.

Another is describing an exception as unclear without stating the actual question. A precise unresolved relationship gives the next reviewer a useful starting point.

A third is exporting revisions as unrelated rows. Preserve the link to the earlier entry so the desk can distinguish new tonnage from corrected information.

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

Explore Zeaclub