LNG Port Calls: Reconcile Scheduling and Readiness

Overview

Different teams may use the same call reference while tracking different responsibilities. The scheduler focuses on the proposed programme, the reviewer on the evidence within its scope and the cargo team on the commercial instruction. The coordinator needs a shared status view that preserves those distinctions and directs unanswered questions to the right owner.

Key takeaways

• State what a scheduling confirmation covers and which conditions remain attached.
• Keep vessel review status distinct from the commercial nomination process.
• Reconcile cargo, vessel and terminal references before issuing a consolidated update.
• Identify the decision affected by each open exception.
• Maintain a clear authority route for programme amendments.

Establish the call's common reference

Begin with the current programme identifier, nominated vessel and cargo reference. Ask the relevant parties to use those references in their responses so that messages can be matched to the same proposal.

Where the programme is still provisional, say so. A working slot discussion and an authorised nomination may appear in the same correspondence, but they should not share an unexplained status label.

The coordinator should also identify the source responsible for each type of update. A commercial scheduler may supply one kind of confirmation while another designated contact handles review questions. The actual terminal process should determine the route, rather than the coordinator assigning every matter to the most responsive person.

Record the time basis and event label used in schedule messages. If a source supplies a local time or a different reference convention, preserve that information and reconcile it through the agreed process before combining messages. Do not guess a time conversion where the underlying reference is unclear.

Separate scheduling from other call decisions

A scheduling response tells the desk something within its stated scope. Read its conditions and ask for clarification where they are ambiguous. Do not infer that it resolves unrelated cargo, vessel or commercial questions.

The commercial record should show the nomination state, relevant review state and open instructions separately. This helps management see whether the call is waiting on a scheduling answer, an evidence response or an internal decision.

A consolidated update can summarise these rows without reducing them to a single green indicator. The recipient needs to know which decision is complete and what remains to be done.

Build an exception list around decisions

An exception should identify the missing response and the decision it affects. “Awaiting terminal” is insufficient when several terminal contacts are handling different matters.

Name the responsible role and preserve the original question where precision matters. Record whether the source has acknowledged the request, asked for clarification or supplied a scoped answer. Those stages require different follow-up.

Prioritise exceptions according to the next commercial action, using information from the responsible parties. Avoid declaring a technical matter urgent simply because its title sounds important. Ask what consequence the unresolved item has for the proposed programme.

Where the consequence is unknown, make that assessment itself the next request. The commercial lead can then consider options with appropriate advice rather than acting on a coordinator's assumption.

Keep the list concise. Routine completed correspondence belongs in the evidence file. The working board should make it easy to see the matters that require attention now.

Reconcile amendments across teams

If the vessel, cargo reference or timing proposal changes, identify which responses relied on the earlier programme. Ask the relevant owners whether their confirmations remain applicable.

A revised schedule should not automatically supersede a cargo instruction or a review response. Each may require its own authorised update. The coordinator should keep the relationships visible until the programme is reconciled.

When the change is approved, issue a controlled note stating the current reference and the earlier messages it replaces. Recipients should not have to infer which of several similar updates governs their next action.

Also check internal systems used by sales, finance and operations. A current programme in the chartering file can coexist with an old customer-facing date or document request elsewhere. The coordinator should identify affected owners rather than attempting to edit every system without authority.

Fictional case: the slot is treated as complete readiness

A fictional LNG trader receives a scheduling message confirming the basis on which a proposed call is being considered. The commercial team circulates a short note saying the call is ready and turns its attention to the next shipment.

During handover, the incoming coordinator compares the scheduling response with the review register. A vessel information clarification remains open, and the cargo team has not yet issued the final commercial instruction. Neither matter was resolved by the scheduling message.

The coordinator corrects the consolidated status, assigns the outstanding requests and asks the relevant parties to explain their effect on the next decision. The commercial lead now sees a defined programme with unfinished dependencies rather than a completed call package.

Once the responses arrive, the coordinator updates the record and circulates a scoped confirmation. The team has not added a new approval layer; it has accurately represented the different decisions already present in the process.

Close the information loop during handover

The handover should identify the current call reference, material conditions and next expected update. Include the responsible contacts and the route for escalation if the usual owner is unavailable.

Ask the incoming coordinator to acknowledge the open-action list. Access to a shared folder does not show that someone has accepted responsibility for monitoring the next response.

Preserve the source of each status. A summary should let the reader locate the scheduling message or review response that supports it. This is especially important when a later change prompts a question about what had been confirmed at an earlier point.

After the call's principal events, transfer residual commercial matters explicitly. Document reconciliation and unresolved questions can remain active even when the scheduling board no longer needs daily attention. Assign their destination rather than allowing them to disappear when the call is archived.

Common mistakes

Treating a scheduling confirmation as proof of complete readiness widens its meaning beyond the evidence. Keep the related decisions separate.

Another mistake is to use a broad waiting status that does not identify the question or responder. Name the missing answer and the decision it affects.

Finally, avoid circulating a revised programme without checking the instructions and review references attached to the earlier version. Reconcile the affected workstreams before reporting the change as complete.

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