Handysize Port Compatibility: Check the Ship Against the Actual Berth

Key takeaways

• Obtain restrictions for the actual terminal and intended operation.
• Separate access limitations from cargo handling limitations.
• Record conditional approvals and the circumstances that could invalidate them.
• Ask the master, owner and terminal to resolve technical questions.

Define the place precisely

A port name may cover several terminals with different approaches, berths and handling systems. Begin with the exact loading and discharge locations, including any intended anchorage operation or movement between berths. If the terminal has not yet been selected, state that the compatibility review is preliminary.

Request current information from the relevant port authority, terminal and appointed local representative. Record its source and date. A restriction copied from an earlier voyage can be a useful lead, but its relevance depends on whether the berth, operation and local conditions remain the same.

Clarify who issues each approval. The agent may coordinate the submission, while the terminal reviews equipment and the relevant marine authority addresses access. A general message saying that the vessel is acceptable should be unpacked: acceptable for which purpose, on which information, and subject to which conditions?

Separate access from cargo work

Access questions concern the vessel’s route to and from the berth and the conditions under which movement is permitted. Cargo questions concern what happens after arrival. Keeping these reviews separate helps avoid a common misunderstanding: a ship may be able to enter the port without being suitable for the terminal’s handling arrangement.

Provide the requested vessel particulars to the appropriate reviewers. Ask them to identify the restrictions that control the proposed call, including relevant dimensions, draft conditions, manoeuvring arrangements and any timing constraints. The chartering team should collect and reconcile these answers rather than calculate a navigation clearance independently.

At the berth, describe the loading or discharge method. Confirm whether the operation depends on shipboard cranes, shore equipment, grabs, hoppers or other interfaces. Have the owner and terminal review the working arrangement together when either side’s equipment determines whether the cargo can move as proposed.

The BLU Code provides guidance for safe bulk loading and unloading involving masters and terminals. Its emphasis makes the ship-terminal interface a relevant review topic. IMO: BLU Code and Manual

Build a port-versus-vessel matrix

The matrix should have an action owner and evidence reference for every conditional result. “Agent checking” is a useful status temporarily, but it is not a closure record. State what answer is required and when the commercial team needs it.

Avoid forcing every issue into a yes-or-no field. Conditional acceptance may be commercially workable if the condition is understood, achievable and appropriately reflected in the shipment plan. Unrecorded conditions are much harder to manage than visible ones.

Check both ends of the voyage

It is tempting to focus on the difficult loading port and assume that the discharge end will be straightforward. Review both. A proposed cargo quantity may work at loading but require a different arrival arrangement at discharge. The resulting commercial question is whether the receiver can accept that arrangement and who bears any associated service or waiting costs.

Where the voyage includes several discharge ports, ask the owner to review the complete sequence. A ship’s condition at a later call depends on what occurred earlier. Do not treat independent terminal approvals as proof that the overall sequence has been accepted.

If a port alternative is being considered, maintain a separate matrix for it. Combining restrictions from several terminals into one conservative-looking summary can create an imaginary port configuration that represents none of the actual options.

Keep conditional approvals alive

A compatibility review is attached to a defined proposal. Changes to quantity, cargo mix, berth, equipment availability or arrival condition may require parts of the review to reopen. Establish a change trigger instead of assuming approval follows the ship indefinitely.

A practical trigger record states the assumption, responsible reviewer and event requiring reconfirmation. For example, if acceptance depends on shore equipment being available, equipment unavailability should immediately prompt an updated handling review. Commercial staff should not solve the gap by assuming the ship’s gear can substitute.

Before the fixture is finalized, distinguish closed technical matters from items still subject to review. Before arrival, ask whether any relevant local information or vessel condition has changed. These checks have different purposes: one supports the commitment, and the other supports the actual call.

Fictional case: acceptable port, unsuitable interface

A fictional receiver proposes a regional bulk terminal for a Handysize shipment. The vessel has called at the same port before, so the commercial team initially treats compatibility as settled. The earlier call, however, used another berth with different discharge equipment.

The terminal reviewer requests hatch information and a proposed equipment arrangement. That review identifies an unresolved interface between the intended shore equipment and the nominated ship. The receiver has an alternative berth, but it requires a different scheduling arrangement and additional local coordination.

The team compares the alternative berth with another vessel proposal before fixing. It records terminal-specific acceptance and keeps the earlier port call as background only. The case illustrates why familiarity with a port should accelerate the right questions, rather than remove them.

Common mistakes

One mistake is equating an owner’s willingness to call with terminal acceptance. Both perspectives matter, and neither should be silently substituted for the other. Obtain the relevant confirmations and preserve the information on which they were based.

Another is forgetting departure. A plan that discusses arrival in detail but says little about the loaded departure condition is incomplete. Ask the responsible marine reviewers to consider the full call.

Finally, avoid treating an approval as broader than its wording. A terminal may accept the ship’s particulars while cargo documentation or the final handling plan remains outstanding. Capture those distinctions in the commercial record.

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