PORT CALLS
Best practices
Port Log events
16 min
this guide highlights the key recommended workflows to help your shipping agency or port agent team maintain accurate, consistent, and reliable port calls data in enqlare’s ort agency operating system use system generated estimated events always work with the default estimated events (eta, etb, ets, etc ) created by the system if the event already exists as an estimate, mark it as actual instead of creating a new port log event for the same time point this ensures your data flows correctly to esof, laytime, shipments, and other integrated tools use port log events for all remaining operational activities all operational actions, other than the estimated events mentioned above, should be captured as port log events these entries document what actually happened during the vessel’s timeline, appear in the sof, and can include important details such as cargo, holds, gangs, and location to ensure accurate and complete reporting use event names for the action, and remarks for specifics event names are intentionally broad use the event name to describe the operation, and add any specific details such as “hold 2 and 5” or “in progress” in the remark field this keeps the event list clear and prevents duplicates link cargo whenever applicable when adding loading or discharging events, always link cargo and quantity this ensures your stowage plan and itinerary update correctly without additional manual steps avoid duplicate or alternative event names the port log is where you capture all operational activities and time points you can add events and comments that are visible to your company and any clients you’ve docid\ ygyr9lbxpego ssh9fq3q with you can also choose to automatically sync events from a terminal there two types of events in the port log estimated time events these are added when you enter estimates while creating the port call you can add more estimates later in the itinerary tab estimated events help you plan ahead and ensure no time points are missed when needed, you can update an estimated event to an port log event estimated events are not included in the sof port log events these events capture all operational details needed for reporting you can link cargo, quantity, hold, gang, and more port log events are included in the sof add event add events to the port log add comment add comments or notes to the port log that are visible to your team and the clients that you have shared the port call with the comments are not added to the sof import wheater events manually select or sync events added to the port estimated time points port log event tip to ensure your data (eta, etb, etc ) flows correctly to esof, laytime, shipments, and other integrated systems , always use the default estimated events created by the system mark as actual the existing estimated time points that are connected to a location, rather than creating new ones for the same event add event to add an event, click the add event button here you can choose from +100s of predefined events event select an event from the list cargo link a cargo and add the quantity for this event location choose the exact location where the event takes place missing an event if you can’t find the event you need, click missing an event to send a request to our team we will add it shortly date and time range enter the start and end date and time remark add a custom remark to provide more details for the event tip event names are designed to be general so they can be used in different situations, helping you keep your list of events short and clear if you need more specific wording — for example, loading in progress hold 2 — we recommend selecting the event loading and adding the details as a remark in progress hold 2 on the sof it will show in one line, and it will look as one use event names to describe what’s happening, and remarks to add any specific details for that event adding cargo to an event to add cargo to an event, click the add cargo button a new section will open where you can select from the cargoes added during the port call setup for each event, you can include cargo details, quantity, and additional information since each cargo is linked to a shipper or receiver, any port log entry with cargo and quantity will automatically update the stowage plan and the itinerary tab if the dropdown is empty, you’ll need to add cargoes first to do this, go to actions → edit itinerary → add cargo itinerary linked events some events in the port log are linked to automatic itinerary updates for example, adding the event end of sea passage will automatically update the vessel status to arrived to see which events trigger itinerary updates, go to tools → events and check the action column events with itinerary update listed will update the vessel status or itinerary accordingly event categories events are grouped into categories to help organize and analyze data more effectively for example, events like rain and high humidity fall under the weather delay category these categories can be used in docid\ wbosxfgfxpv1vwdfrpuy8 to highlight specific trends and are also reflected in your docid\ qenk3kba2ullgkfny0m0t to view which category an event belongs to, go to tools → events turning off events tools > events turning off events gives you full control over which options are available when adding a port log event since the same event may appear under different names (based on user preference), this feature helps you avoid duplicates and ensure consistent naming by keeping only the preferred version active, you make your statement of facts clearer and more standardized to manage this, go to tools → events, then edit and turn off the events you don’t want to use add comment to add a comment, click the add comment button comments are useful for making notes during the timeline and tracking important observations comments are not included in the sof and are only visible to users with access to the port call — including your team members and any clients you’ve shared it with import weather events importing weather events is helpful when multiple vessels are at the same terminal and experience the same weather conditions instead of entering the events for each vessel separately, you can add the weather events to the port and then either automatically sync or manually import them into the relevant port calls this way, you only add the events once, and they’re applied to all selected port calls—saving time and ensuring consistency add port events port call > ports tab to add port events, go to the port call and open the port tab select the relevant port, then choose the berth where the events occurred from there, you can add the appropriate events sync or add port events to port call to sync or manually add port events click import weather events to manually add events select the relevant events and click add to port the events will be added to the port call, and you’ll be able to edit them as needed enable automatic syncing of port events click turn on automated updates of weather events then, select the berth or terminal and choose the start date and time for syncing once enabled, all events from that berth or terminal will appear in the port log with the label port event these events can only be edited from the port page to stop syncing, open the import weather events popup and click stop updates you’ll be given two options keep events in the port log – the events remain and become fully editable remove events – the synced events are deleted from the port log