Key takeaways
- Check the approach, berth and cargo interface as separate decisions.
- Submit the actual vessel configuration rather than a generic class description.
- Record the scope and conditions of every acceptance.
- Treat changes in cargo, equipment or berth as reasons to revisit affected reviews.
- Keep operational acceptance distinct from the commercial allocation of costs.
Define the operation before asking whether it fits
A compatibility question needs a defined operation. The same vessel can be considered for different cargo quantities, terminal positions, handling methods and discharge sequences. Asking whether an Ultramax is acceptable, without specifying those conditions, invites an answer too broad to support a commitment.
Begin with a short description of the intended call: nominated vessel, cargo and quantity basis, intended terminal, proposed handling method and expected sequence. Identify which details are confirmed and which remain provisional. The receiving party should not have to infer the proposal from unrelated commercial messages.
Tsuneishi publishes dimensions and cargo capacity for its TESS66 Ultramax design. Those are design particulars, not approval for a particular port call. Shipbuilder design information.
Use such material to understand the kind of information involved, then obtain the actual ship's documentation from the authorized source. A design description cannot establish a nominated vessel's current condition or the terminal's acceptance of a specific operation. The commercial coordinator's role is to connect the right evidence with the right reviewer.
Separate the approach, berth and handling questions
Organize the assessment into distinct questions so that a positive answer in one area does not conceal a gap in another. The approach review addresses the proposed movement into and out of the port. The berth review addresses the intended location alongside. The handling review addresses the exchange of cargo between vessel and shore.
The responsible nautical and technical parties determine which limits, documents and operating conditions apply. Commercial staff should not calculate an unofficial allowance and present it as clearance. They can, however, make sure that the vessel's proposed arrival and departure conditions are included in the request, and that a change is referred back to the relevant reviewer.
For the berth interface, ask whether the review covers the intended berth specifically or only the terminal more generally. A terminal can have several operational arrangements. A reply that does not identify its scope may be insufficient for the proposed nomination.
For handling, identify the equipment combination actually proposed. If shipboard gear is expected to work with a shore hopper or hired grab, the review must concern that combination rather than each item's existence in isolation. Ask the relevant specialists what information they need; do not replace their evaluation with a generic equipment checklist.
Map the cargo path to the receiving system
Compatibility does not end at the ship's side. The buyer should understand where the cargo goes after discharge and whether the receiving arrangement assumed in the proposal is available. A terminal's ability to receive a shipment is different from the receiver's commercial expectation that storage or onward transport will be ready.
Draw the cargo path in words: vessel, handling equipment, receiving point, storage or transfer, and onward movement. At each handoff, identify the provider and the confirmation needed. This is a coordination map, not an operating procedure. It helps reveal gaps between companies that each consider their own part arranged.
A receiver may have booked onward transport while the discharge contractor assumes temporary storage will be provided. Neither confirmation resolves the missing storage arrangement. Similarly, a hopper quotation may exclude positioning or support that another party assumed was included. These interface questions should be settled before the vessel's schedule is built around the proposed service.
Ask the receiver to identify the condition that would prevent cargo acceptance on arrival. It might be an unresolved commercial release, a missing contractor confirmation or a change in the destination plan. Knowing that condition gives the shipment team a meaningful trigger for revisiting the call.
Build an acceptance matrix with visible boundaries
An acceptance matrix records what each answer actually covers. It should be short enough to use during a call, while linking to the detailed documents on which the answer depends.
| Review area | Decision required | Boundary to record |
|---|---|---|
| Port movement | Proposed arrival and departure considered | Vessel condition and movement assumptions |
| Nominated berth | Intended berth considered for this vessel | Berth identity and any stated conditions |
| Cargo handling | Proposed equipment arrangement reviewed | Equipment combination and responsible operators |
| Shore reception | Cargo can enter the stated receiving system | Storage, transfer and release assumptions |
| Cargo identity | Submitted cargo information reviewed | Lot, grade and document revision |
| Commercial scope | Parties agree who arranges each service | Supply, payment and coordination responsibilities |
Use precise status terms. Submitted means the request has been sent. Acknowledged means it has been received. Reviewed means someone has considered it, possibly with conditions. Accepted should be used only within the scope of the actual response and by the authority responsible for that decision.
Do not convert a conditional reply into an unconditional dashboard status. Preserve the condition and assign its closure. If a response says acceptance depends on further information, the missing information remains part of the decision rather than a minor administrative follow-up.
Distinguish historical experience from current evidence
A previous successful call can help identify the right contacts and documents. It does not automatically answer the present question. The cargo, vessel condition, berth, equipment provider or terminal arrangement may differ from the earlier visit.
Use historical records as a comparison aid. Ask what has changed and which parts of the earlier assessment remain relevant. If the terminal is willing to rely on earlier material, record that confirmation and the present operation to which it applies. Avoid making the inference on the terminal's behalf.
This is particularly useful when commercial staff hear that a sister vessel has called before. The statement can justify investigating further, but it does not close the review. Request the nominated vessel's particulars and ask the responsible party whether additional evidence is necessary.
The same caution applies to a familiar port name. Commercial shorthand often compresses several terminals, berths or services into one location label. The compatibility record should expand that shorthand into the actual proposed destination before the team treats the matter as settled.
Keep the review valid when the shipment changes
A compatibility review is attached to a set of facts. Its usefulness depends on recognizing when those facts change. Establish a revision trigger for material changes in vessel, cargo, quantity basis, equipment arrangement, berth or call sequence.
The coordinator need not decide the technical significance alone. The process can require that changes are sent to the original reviewer, who identifies whether reconfirmation is needed. This avoids two opposite errors: ignoring a meaningful change and repeating every review without considering its scope.
Keep a change register with the old assumption, the new information, the affected decision and the person handling the response. Link the revised evidence to the original acceptance. Otherwise a later user may open an accepted document without realizing that its underlying proposal was superseded.
A change of shore contractor deserves particular attention when the original acceptance relied on a specific equipment arrangement. The substitute supplier may be commercially acceptable while still requiring a technical or operational review. Price approval and compatibility confirmation should therefore be recorded separately.
A fictional receiver change exposes the real constraint
In this fictional case, a chartering team considers an Ultramax for a cargo to a terminal used by the receiver before. The terminal provides a preliminary response based on the named vessel and the intended discharge arrangement. The commercial team marks the port as cleared.
Later, the receiver changes its storage plan and proposes direct transfer into onward transport. The ship remains the same, so the buyer initially treats the revision as a shore matter outside the compatibility review. The operations coordinator notices that the earlier response referred to the original receiving arrangement.
The coordinator sends a short change note to the terminal and owner, identifying the revised cargo path and asking which parts of the prior review remain valid. The terminal requests additional information about the new arrangement before confirming its position. Meanwhile, the buyer retains the original plan as an alternative only if its providers reconfirm availability.
The lesson is not that the revised plan was inherently unsuitable. It is that the scope of an earlier answer had changed. By preserving the condition attached to the response, the team avoids using a genuine approval as evidence for a different operation.
Resolve incompatibility through options with owners
When a review identifies a problem, translate it into an explicit decision rather than leaving a vague rejection in the file. Ask the responsible reviewer which part of the proposal cannot be accepted and whether an alternative can be considered. Do not pressure a technical party to remove a limitation for commercial convenience.
Commercial alternatives might include a different nominated vessel, another terminal, a changed cargo quantity or a revised service arrangement. Each has consequences for the sale, charter and receiving plan. The principal must decide which alternatives are authorized before the coordinator circulates them as new instructions.
Evaluate alternatives against the original shipment objective. A different berth may solve one interface while changing storage or onward transport. Hired equipment may address a handling need while adding another provider and acceptance process. The objective is a coherent revised shipment, not the isolated closure of one red flag.
After a choice is made, withdraw superseded proposals clearly. Terminals and suppliers should not be left preparing several incompatible versions because the commercial team never communicated which one survived.
Make the handover useful to the person managing arrival
The final compatibility package should contain the current proposal, the relevant confirmations, the conditions still to be met and the change triggers. Include a concise narrative explaining any unusual interface. The person managing arrival should not need to reconstruct why one contractor was selected or why a berth option was removed.
Assign ownership for reconfirmations that fall after the commercial commitment. State what evidence will close each item and what happens if the expected answer does not arrive. An unresolved dependency is manageable when it is visible and has an escalation path; it becomes dangerous when it is represented as completed.
Keep the package accessible to authorized users and avoid relying on a single individual's mailbox. Compatibility work involves several organizations, and staff changes can otherwise break the information chain just when the vessel approaches the port.
Common mistakes
Using the vessel category as proof of acceptability substitutes a label for the actual proposal. Provide vessel-specific information and identify the intended operation.
Treating berth acceptance as acceptance of every handling arrangement stretches a response beyond its scope. Maintain separate entries for movement, berth and cargo interface decisions.
Relying on a previous call without checking changes can preserve assumptions that no longer apply. Use the earlier record to guide the new review and obtain the appropriate confirmation.
Changing a shore supplier without revisiting the equipment interface can leave an accepted plan disconnected from the service actually ordered. Route the change to the responsible reviewer.
Questions to settle at the final readiness meeting
A final meeting should concentrate on differences between the accepted proposal and the current plan. Ask whether the vessel, berth, cargo and equipment arrangement still match the reviewed documents. Confirm that the receiver's cargo path remains available and that any outstanding condition has a named owner.
End with a specific record of remaining decisions. A general statement that everyone is comfortable offers little help when a later change occurs. A clear statement of the accepted arrangement and its boundaries supports a faster, more informed response.
Where Zeaclub fits
Zeaclub offers digitalised procedures across the voyage workflow.
Zeaclub provides 24/7 operating systems and worldwide coverage.
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
Does fitting the published berth dimensions establish compatibility?
No. Dimensions are one part of the assessment. The responsible parties must consider the actual vessel condition and proposed operation, including movement, berth and handling interfaces. Commercial teams should coordinate that review rather than treating one published limit as comprehensive acceptance.
Who decides whether shipboard equipment can be used?
The answer depends on the operation and the parties' responsibilities. Obtain review from the authorized vessel and terminal personnel, with any relevant equipment provider involved. Record who supplied the decision and what arrangement it covers.
Can a sister vessel's previous call be used as evidence?
It can provide useful background and help identify documents or contacts. It should not replace the nominated vessel's review unless the responsible authority explicitly confirms the extent to which earlier information can be relied upon.
What if the discharge berth is nominated later?
Keep the nomination as an open dependency, define the information needed and identify the decision deadline. A later nomination should trigger the required review. Do not describe the vessel as accepted for an unspecified berth merely because a port has been named.
Should commercial cost allocation appear in the compatibility file?
Yes, as a separate coordination layer. An arrangement can be technically acceptable while responsibility for arranging or paying for it remains unresolved. Keeping both questions visible helps prevent an accepted plan from failing because a necessary service was never ordered.