Bow view of a bulk carrier at anchor

Key takeaways

  • Handover the lot schedule behind the final aggregate quantity.
  • Identify the active evidence revision and the scope of each review response.
  • Separate selected cargo from alternatives discussed but not authorized.
  • Name the people who can resolve supplier, commercial and technical questions.
  • Keep later changes traceable to the parcel that was actually agreed.

Explain how the final parcel was selected

The final shipment quantity may be the result of several supplier changes, substitutions and commercial choices. A fixture summary that gives only the total removes the history needed to understand which assumptions remain important. The operations team should receive a concise account of the selected parcel and its remaining conditions.

State which lots proceed, which alternatives were withdrawn and which decisions are still open. Explain any difference between the original procurement target and the final instruction. The aim is not to narrate every negotiation, but to preserve choices that affect what operations must monitor.

If the parcel includes a substitution accepted during negotiation, identify its evidence and review references. If a supplier contribution remains conditional, state the condition near the beginning of the handover. Do not bury it in an attachment while the summary presents the full parcel as settled.

A useful test is whether the receiving colleague can answer why each lot appears in the active schedule. If the answer depends on the negotiator's memory, the handover needs a clearer decision record.

Build the evidence map around lots, not filenames

A folder organized only by document type can make it difficult to see which cargo a file describes. Create an evidence map that links each active lot to the relevant issuer, document revision and review response. Keep the original documents accessible without forcing the colleague to infer their relationships.

IMO's solid bulk cargo framework relies on cargo information for the proposed shipment. Check the current text with the responsible specialists. IMO IMSBC information.

The map is a coordination tool, not a determination that the evidence is technically sufficient. Record who reviewed it and what question the response addressed. If a file was supplied for preliminary consideration only, preserve that limitation.

Use clear identifiers that remain stable through the shipment. A lot should not acquire a new internal name in each department without a cross-reference. Consistent identifiers help operations connect supplier updates, vessel questions and receiver instructions to the same cargo.

Distinguish active documents from historical material

Negotiation files often contain several versions of a cargo schedule and supporting documents. Retain the history, but make the active version unmistakable. A later file date does not necessarily mean the document was selected or accepted.

The handover should identify the current schedule, the evidence it relies on and the superseded versions. If a later proposal was rejected, label it as a proposal that did not proceed. Otherwise a colleague may select it simply because it appears newest in the folder.

Avoid deleting historical material that explains a decision. A withdrawn lot can be relevant to understanding a revised quantity or a supplier issue. Keep it separate from the active instruction so that history does not become accidental authority.

Where documents have similar names, add a short index with their purpose and status. The index should help the reader find the correct evidence quickly, rather than becoming another unmaintained list detached from the files.

Preserve the scope of cargo and vessel responses

A review response should remain attached to the cargo proposal it considered. Record the vessel, schedule revision, intended destinations and any stated conditions. Operations needs to know what the response supports and what change would require a further question.

Do not summarize a conditional indication as cargo accepted without qualification. Keep the condition in the active handover and identify the person coordinating closure. A short summary can still be accurate if it preserves the decision boundary.

If the owner or specialist requested additional information, include the question and the status of the reply. A document received after the review may still need to be returned to the reviewer. The handover should make that final step visible.

Commercial staff should not reinterpret technical conclusions to make the package simpler. If the wording is unclear, obtain clarification from the source. The handover's purpose is to transmit the supported position, not improve its apparent certainty.

Use a lot-level handover table

Handover fieldWhat it should identifyOperational use
Active lotStable identifier and commercial descriptionConnect updates to the correct cargo
Supplier responsibilityContact and remaining actionRoute release, quantity or delivery questions
Evidence basisIssuer, revision and linked filesLocate the information used for review
Review statusResponsible reviewer and conditionsRecognize when further response is needed
Destination instructionReceiver and authorized allocationCheck that delivery planning matches the sale
Change authorityPerson able to approve a revisionAvoid informal substitutions or reallocations
Historical alternativesWithdrawn or unselected proposalsPrevent obsolete cargo from reentering the plan

The table can be concise when each field links to reliable supporting records. The objective is not to reproduce every document inside the handover. It is to make the relationships between them clear enough for a colleague to act.

Add a short narrative for unusual cases. If one supplier's release controls the whole parcel, the table may not fully explain its significance. A paragraph describing the dependency can prevent the operational team from treating it as a routine document follow-up.

Show the authority chain for cargo changes

The supplier can report a change, but may not be authorized to alter the buyer's shipment instruction. The buyer can choose a commercial alternative, but that does not replace cargo or vessel review. The receiver can express a preference, but it may not constitute an agreed change to the parcel.

Map these decision roles explicitly. Identify who may approve a substitution, accept a shortfall, change a destination allocation or authorize additional cost. Also identify the qualified parties who review the resulting proposal.

The operations coordinator should know which actions fall within its authority, such as seeking information, and which require a principal's instruction. This prevents a practical attempt to solve a supplier problem from becoming an unauthorized commercial commitment.

Include an escalation route when the primary contact is unavailable. The route should identify an authorized alternative decision maker, not merely another person who can relay messages. A clear authority structure makes urgent changes easier to manage without bypassing necessary review.

A fictional newest file is the wrong instruction

In this fictional case, the chartering team hands over a Supramax shipment after considering several supplier substitutions. The final parcel uses the original lot from one supplier because a proposed replacement was not selected. The shared folder nevertheless contains a later cargo schedule showing the replacement.

The operations colleague initially opens the newest schedule. Before circulating it, the colleague checks the lot-level handover table and sees that the active evidence map refers to the original lot. The mismatch prompts a focused question to chartering.

The negotiator confirms that the later schedule was an unselected proposal. The team labels it accordingly and issues a clear active index. The vessel and terminal continue receiving information about the cargo actually chosen, while the alternative remains available as historical context only.

The fictional lesson is that file chronology cannot establish decision authority. A traceable active parcel prevents a rejected proposal from becoming the operating plan through an innocent document-selection error.

Reconcile the cargo handover with the commercial baseline

The final lot schedule should match the quantities and assumptions used in the approved shipment estimate. If the cost model includes a different parcel or supplier delivery boundary, identify the discrepancy before operations begins ordering services around it.

This does not require operations to resolve every commercial allocation. The handover should state the agreed service boundary and any unresolved cost question, with the authorized person responsible for it. The team needs to know which services may be instructed and where further approval is required.

If a supplier's contribution changed during negotiation, explain whether that affected assembly, holding or destination services. A final aggregate quantity can remain similar while the supporting service package changes materially. Preserve the connection between the cargo decision and the budget revision.

Expected recoveries should also remain distinct from operational instructions. A service may need arranging while its ultimate allocation is still under review. State the known facts and refer interpretation of rights or liabilities to the authorized commercial or legal team.

Transfer open conditions as explicit actions

An open condition should describe the missing decision or evidence, the active lot affected and the next action. Cargo documents pending is too broad if the real issue is a particular issuer's response to a reviewer question. Specific wording allows the receiving colleague to continue the task immediately.

Assign a coordinator and identify the decision maker whose answer closes the item. Record the expected information point and the consequence if it does not arrive. The consequence may be escalation or investigation of an authorized alternative, rather than automatic continuation of the original plan.

Ask the receiving colleague to acknowledge these actions. Receipt of the handover package alone does not show that someone has accepted responsibility for monitoring the unresolved supplier release or revised cargo evidence.

When an item closes, retain the response and update the active record. Do not simply remove the condition. Its closure may explain why the team later issued an instruction or why a subsequent change requires review again.

Keep the same traceability during execution

The handover structure should continue as the shipment develops. New supplier information should be linked to the relevant lot and assessed against the active schedule. If it changes the proposal, issue a controlled revision rather than silently replacing the original field.

Maintain a change record showing the old assumption, new information, affected decisions and resulting authority. This gives the principal a concise way to review a proposed adjustment and gives operations a clear instruction once it is approved.

The factual record should remain separate from conclusions about responsibility. Record when a supplier reported a change, what evidence followed and which instruction was issued. Appropriate reviewers can later assess commercial consequences using the actual agreements and chronology.

Do not let informal messages bypass the shared record. A useful conversation can resolve a question, but the resulting instruction still needs to be captured so that other authorized participants are working from the same parcel.

Review the handover by asking operational questions

A handover review is more effective when it tests practical questions. Which supplier can confirm the outstanding release? Which cargo schedule did the owner consider? Who may accept a replacement lot? Which receiver instruction governs the destination allocation?

If the receiving colleague cannot answer these quickly, improve the index or narrative. More attachments may not help if the relationships remain unclear. The goal is a navigable decision record, not a larger archive.

After the shipment, ask which questions operations had to return to chartering to answer. Repeated questions reveal where the handover omitted essential context. Use those findings to improve the next active parcel record while retaining only controls that support real decisions.

Common mistakes

Handing over only the final total removes the lot-level logic behind it. Include the active schedule and evidence map.

Treating the newest file as the approved instruction confuses chronology with selection. Label proposals and superseded material clearly.

Summarizing a conditional response as complete acceptance hides the remaining dependency. Preserve its scope and closure owner.

Allowing a supplier update to change the commercial parcel automatically bypasses authority and review. Route the change through the defined decision process.

The final handover question

Ask the receiving colleague to describe the active parcel and name the most important unresolved condition without consulting the negotiator. Then ask which document and contact support that answer. This reveals whether the handover is usable in practice.

A clear response means the colleague can continue coordination with the right context. An unclear response identifies a specific gap to fix before the shipment depends on a decision that only the original negotiator understands.

Where Zeaclub fits

Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.

Zeaclub offers digitalised procedures across the voyage workflow.

Explore Zeaclub

Explore Zeaclub

Educational information only; not legal, financial or trading advice. Contract wording and applicable rules control. Verify current requirements and obtain qualified advice before acting.

Frequently asked questions

Why is an aggregate quantity insufficient for handover?

It does not identify the lots, supporting evidence or supplier conditions behind the parcel. Operations needs those relationships to recognize changes and route questions correctly. The total remains useful, but it should be connected to the active lot schedule.

Should obsolete cargo proposals be deleted?

Retain relevant history, but separate it clearly from the active instruction. An unselected proposal may explain a decision without being suitable for execution. Labels and an index help prevent accidental reuse.

Who decides whether a supplier substitution can proceed?

The authorized commercial principal selects the business response, while the responsible specialists assess the revised cargo and vessel proposal. The coordinator gathers information and connects those decisions; it should not infer either approval from the other.

What should an open-condition entry contain?

Identify the affected lot, missing answer, coordinator, responsible decision maker and next action. Explain what closes the item and what happens if the expected response does not arrive. This makes the condition actionable across handovers.

How can the handover remain concise?

Use an active summary, a lot-level table and links to supporting evidence. Preserve material conditions and authority while avoiding duplicate document copies or a chronological retelling of every negotiation message.

Primary sources