Port call management is the coordination of a vessel’s visit to a port: preparing for arrival, arranging its berth and required services, following the work during its stay and coordinating departure. It connects the information used by the ship, agent, port, terminal and service providers so that each participant can plan and act on the latest agreed details.
A port call is the visit itself. Port call management is the work of organising that visit. Depending on the purpose of the call, activities may include cargo or passenger operations, bunkering and other vessel services. Not every call requires the same services, and not every port operates those services directly.
For a Harbour Master and the port operations team, the practical challenge is keeping the vessel’s requirements, movement plan and service readiness aligned as circumstances change.
1. What happens during a port call?
The process starts before the vessel arrives. Information is submitted, checked and used to prepare the visit. Arrival and departure movements then depend on the berth, the vessel and the resources required to support it.
The table below shows typical stages and information handoffs. It is an operational overview, not a universal allocation of responsibilities: local arrangements, the type of vessel and the purpose of the visit determine who does each part. Some activities run in parallel.
Stage | Participants typically involved | Information needed for the next step |
|---|---|---|
Prepare the visit | Ship operator or master, agent and port team | Vessel particulars, estimated arrival and departure times, visit purpose, documents and requested services. |
Review requests | Authorised port teams and relevant service providers | Checked requirements, approval status, missing information and confirmations to the requester. |
Plan the berth and movement | Berth planners, marine services coordinators and terminal where applicable | Berth location and window, vessel constraints, required pilots and tugs, and supporting resource availability. |
Carry out arrival and services | Vessel, pilots, tug crews, mooring teams and other providers as required | Assignments, changes, actual movement times and progress updates. |
Coordinate the stay and departure | Vessel and agent, terminal, port team and service providers | Progress of the visit’s activities, readiness to depart, required clearances and the departure service plan. |
Complete the operational record | Operations staff and finance teams | Confirmed services, actual activity and timestamps needed to prepare charges and review the visit. |
Departure does not necessarily close the administrative work. Service records may still need checking, and charges need to be prepared under the applicable tariffs and billing rules.
2. Who coordinates the information?
Port call management crosses organisational boundaries. The agent communicates visit requirements on behalf of the vessel or operator. Port teams coordinate the activities within their remit; terminal operators manage their own operational work; marine service providers arrange and carry out the services they deliver. Public authorities handle their respective clearance responsibilities.
Effective coordination requires agreement on who supplies each update, who makes the decision and who needs to receive the result. An amended service request, an approved request and a confirmed resource assignment are different states. Keeping that distinction visible helps the next team understand what is ready and what still needs attention.
Estimated, planned and actual times should also remain distinguishable. An estimated time of arrival (ETA) is a forecast, not proof that a berth or pilot is available. Actual movement and service times record what took place and provide a basis for operational review and billing.
3. What happens when the ETA changes?
Consider an illustrative call where a vessel’s ETA moves from 10:00 to 12:00. Recording the new time is only the starting point. The planning team needs to check whether the proposed movement still fits the berth window and the availability of the required nautical services.
A pilot may be committed to another movement or constrained by licence, vessel class or rest requirements. Tugs may be working elsewhere, with travel time and bollard pull affecting which assignments are feasible. Pilot transfers, mooring teams, line boats and applicable tidal or air-draft constraints may also affect the plan.
The revised time therefore needs to pass through the relevant planning and confirmation steps. Once a workable plan is agreed, affected teams need the updated assignments; subsequent progress updates show how the work is actually developing.
This is why berth availability and marine service readiness need to be considered together. Some ports manage only berth planning, while others coordinate both. The information exchanged with external providers remains important in either arrangement.
4. How do PMIS and Port Community Systems support the visit?
A Port Management Information System (PMIS) supports the port’s operational management of vessel visits. marineM PMIS connects vessel bookings, movement coordination, recorded services and billing. It provides the context in which the port plans and follows the work.
Berth Planner supports berth allocation and scheduling. Marine Services Planner coordinates pilots, tugs and supporting resources. Bringing berth and nautical service plans together helps planners assess whether a proposed movement can be supported. Planners can review recommendations and make manual overrides.
marineM Port Community System modules address community-facing workflows: registering vessels, submitting visit and marine service requests, following approvals, exchanging documents and receiving status updates. These requests and confirmations serve a different purpose from the port’s internal resource plan.
The system boundaries need to be clear. A PMIS does not automatically replace a terminal operating system, customs system or national maritime single window. Interfaces, record ownership and access permissions must be agreed around the systems and organisations involved.
5. How do service records connect to billing?
The planned service describes what is intended; the completed-service record describes the work carried out. Keeping that record connected to the vessel visit helps operations and finance use consistent information when preparing charges.
In marineM PMIS, recorded services and configured tariff rules support invoice preparation. The port’s agreed workflow determines how records are checked and how exceptions are handled. A service request alone should not be confused with evidence that the work was completed.
These records also help a port understand its activity. Comparing planned and actual times can highlight where a visit changed, but claims about faster turnaround or cost savings require consistent definitions and a reliable baseline.
6. How is port call management different from optimisation?
Port call management organises and follows the visit. Port call optimisation seeks to improve how its activities are coordinated, for example by reducing avoidable waiting or making better use of available resources. They are related, but an operational record alone does not establish an improvement.
Just-in-time arrival is one coordination approach. IMO’s explanation of just-in-time arrivals connects arrival planning with the availability of the berth, fairway and nautical services. It depends on more than changing the vessel’s ETA in a system.
For the improvement perspective, read our companion article on port call optimisation. For the operational starting point, map how one visit moves from its initial request through planning, execution and completed-service records, and identify who needs each update.
Explore marineM with a demonstration based on the port-call activities your team manages.