LNG Programme Changes: Reconcile Trading and Shipping

Overview

A sales amendment may alter the destination or delivery proposition while the chartering team still uses an earlier employment estimate. A scheduling update may reach operations without reaching the team preparing the commercial calculation. The coordinator needs a change record that connects these workstreams and identifies the decisions each one must make.

Key takeaways

• Give the proposed change one reference across trading, chartering and receiving teams.
• Identify the current authorised state separately from the amendment under review.
• Track effects on commercial terms, programme estimates and specialist responses.
• Keep model revisions distinct from authority to implement the change.
• Close the change only after affected instructions and assumptions are reconciled.

Capture the business purpose and the proposed amendment

Record who requested the change, what outcome is sought and which elements of the current programme would be amended. A request to improve a sales result is a business objective; a new destination or timing proposal is one possible way to pursue it.

Keeping that distinction visible allows the team to explore alternatives without assuming that the first suggestion is already the authorised solution. It also helps reviewers focus on the actual proposal they are being asked to assess.

Attach the current programme reference and label the new one as proposed. Recipients should not have to infer from message order whether the amendment has been approved.

Identify the commercial authority needed to proceed. Where agreement terms govern the change, check the current text and obtain the relevant review. The coordinator should not treat an updated internal model as evidence that a counterparty has accepted an amendment.

Map the affected workstreams

Ask each team to identify the decisions and assumptions that depend on the changed element. Trading may need to reconsider the sale proposition. Chartering may need revised employment or cost information. Receiving contacts may need a new scoped review or scheduling response.

The map should include completed decisions that might need confirmation of continued applicability. A change process focused only on open tasks can miss a previously closed response whose basis has now changed.

The coordinator should seek the responsible parties' assessment of technical effects. The map organises the questions; it does not answer them through commercial inference.

Freeze the comparison basis during review

When the teams assess alternatives, use a common scenario identifier and record its assumptions. If one team changes a key input, notify the other affected teams rather than allowing the models to drift independently.

A useful comparison separates the base programme from the proposed amendment. Show what changes and what remains the same under each team's view. This makes it easier to identify costs or values counted twice, omitted or attached to different scenarios.

Do not overwrite the base case before the decision is made. Management may need to compare the alternative with the current authorised programme or return to it if the amendment does not proceed.

Label model outputs by status. A preliminary estimate can support screening while remaining inadequate for a final commitment. A calculation marked reviewed may still depend on commercial terms that have not been agreed. Preserve both facts.

Keep review completion separate from implementation authority

A specialist may confirm its position on the proposed programme while commercial negotiations remain open. Conversely, the commercial parties may reach a conditional understanding before the relevant technical or receiving response is complete.

Record each decision with its scope and conditions. Do not let the completion of one workstream close the entire change automatically.

If management needs to act before every item is resolved, the decision note should state the unresolved dependencies and the authorised direction. The coordinator records that direction rather than inventing a general rule that all changes must either stop completely or proceed immediately.

Where a response contains ambiguous wording, ask for clarification through the proper route. A short acknowledgment should not be stretched into consent to the financial, scheduling or technical consequences of the amendment.

Fictional case: three versions of one cargo

A fictional LNG trader proposes changing the receiving destination. Trading updates its sales model using the new buyer's indication. Chartering keeps the original employment duration while awaiting a revised estimate. Operations receives a tentative scheduling message for the alternative and updates its call tracker.

At the decision meeting, the three teams appear to support the change, but their figures and statuses describe different versions. The coordinator assigns one scenario reference and asks each team to identify its current assumptions and open questions.

The reconciliation reveals an unconfirmed receiving condition and an employment estimate that still belongs to the base programme. Management pauses the final commercial decision while those specific inputs are obtained, preserving the original option within its known limits.

After the responses arrive, the teams update the same scenario and issue a consolidated decision note. The change is assessed as a complete proposition rather than a collection of locally current files.

Release the approved version deliberately

Once the authorised decision is made, issue a change note identifying the current programme, supporting response references and instructions superseded. State which recipients need to act and which need awareness only.

Check that customer-facing information, vessel instructions, receiving references and internal commercial models all identify the approved proposition. The coordinator can assign updates to their owners without assuming authority to edit every system directly.

Preserve any conditions that remain attached to the decision. A concise closure note should not erase the limitations that management accepted or the follow-up work still required.

If the change is rejected or withdrawn, record the reason accurately and confirm the status of the base programme. Do not assume that all earlier options remain available simply because the amendment did not proceed.

Learn from mismatched versions

After closure, review where the workstreams diverged. If the problem was an unshared scenario revision, improve the notification trigger. If a cost assumption lacked an owner, assign one earlier in the next change review.

Avoid responding to every incident with a larger generic checklist. A specific correction to the observed failure is more likely to improve coordination than adding fields that no one uses.

Retain the base and revised records with their decision trail. They explain what the business knew and authorised at each stage, which supports a fair review of both successful and disappointing outcomes.

Common mistakes

Updating each team's file independently can leave the business with several different propositions under one cargo name. Use a common scenario reference.

Another mistake is to treat a reviewed spreadsheet as authority to implement a change. Model validation and commercial agreement are different decisions.

Finally, avoid closing the amendment when the main instruction is sent while related customer or receiving records still show the old programme. Reconcile the affected records and assign residual work.

Where Zeaclub fits

Zeaclub offers digitalised procedures across the voyage workflow.

Zeaclub provides 24/7 operating systems and worldwide coverage.

Explore Zeaclub

Learn about Zeaclub