VLCC Change Control When a Crude Buyer Revises Delivery

Overview

The process needs to preserve the current workable plan while the proposed alternative is assessed. This gives the cargo desk a way to pursue a change without obscuring what has actually been agreed.

Key takeaways

• Capture the requested outcome before discussing implementation.
• Assess effects on cargo, terminals, freight, timing, and records.
• Keep proposals separate from authorised instructions.
• Close the change with a shared current version and evidence trail.

Define the change in commercial terms

Begin with a short statement of the buyer's request. It might concern another receiver, a revised delivery sequence, a different allocation of crude, or a timing preference. Describe the desired outcome without adding operational instructions that the buyer has not authorised or specialists have not assessed.

Record who requested the change and who has authority to decide it. A refinery planner may identify a need while a different commercial principal controls the cargo instruction. The coordinator should not infer authority from seniority, urgency, or inclusion on a distribution list.

Identify the current plan against which the change is being assessed. Without that baseline, different recipients may compare the proposal with different versions of the voyage and provide incompatible answers.

Keep the request status explicit. Proposed, under assessment, approved commercially, and issued through the authorised channel are useful distinctions. A single changed label does not show whether the parties have reached the same stage.

Protect the boundary between commercial and safety decisions

The cargo desk can explain priorities and ask whether an alternative is commercially and operationally workable. It should not prescribe navigation, cargo-handling methods, or other technical measures to meet the revised objective.

IMO describes the ISM Code as a framework for safe ship management and operation. See the official ISM overview.

In the workflow proposed here, technical questions go to the owner and qualified parties through their established channels. Commercial approval does not replace their assessment, and an operational response does not automatically settle freight or expense terms.

This separation makes decisions faster to understand. Each party receives the question it can answer, and the coordinator can identify whether the remaining obstacle is technical assessment, receiving readiness, commercial agreement, or internal authority.

Review the change across the whole crude transaction

A revised destination may affect more than the sailing plan. It can change the receiver, terminal review, cargo allocation, documentation instructions, and timing of the buyer's downstream commitments. The change assessment should identify these relationships before the proposal is treated as simple.

Ask the owner for the relevant response to the proposed employment and ask the receiver to confirm its arrangement. Keep both tied to the same cargo description and information version.

The contracting team should assess the relevant terms and any proposed adjustment. Check the current text rather than assuming that a destination option or change right exists because a similar fixture allowed it previously.

Internal finance or approval processes may also be affected. If the original authority covered one commercial package, identify whether the revised package remains within that scope. Do not treat approval of the initial freight as unrestricted authority for subsequent changes.

Use a change-impact register

A focused register can keep a complex VLCC delivery change reviewable without becoming a substitute for the actual decisions.

The register should identify dependencies between decisions. For example, commercial terms may remain conditional on terminal acceptance. Recording that relationship prevents one completed line from making the entire change appear ready.

Each pending item needs a responsible person and next step. A broad statement that all teams are reviewing is less useful than a precise account of the missing decision.

Fictional case: a refinery request becomes an apparent instruction

A fictional crude buyer asks whether a VLCC cargo could discharge at another facility because its refinery programme has changed. The request is forwarded to several parties with the subject line revised destination, and one internal team updates its records as though the choice were final.

The change coordinator restores the request's status as a proposal and identifies the current baseline. The owner assesses the intended employment, the receiver obtains the relevant facility review, and the contracting team checks the commercial basis.

The cargo desk then receives a complete decision summary with remaining conditions. Once the authorised parties agree the revised plan, the coordinator issues the controlled update through the proper channels and identifies which earlier instructions are superseded.

The process allows the buyer to pursue the alternative while preventing an exploratory question from creating inconsistent execution records.

Close the change with a shared current position

A completed change record should state what was requested, what was agreed, which conditions remain, and when the revised commercial instruction became current. Link to the supporting owner, receiver, and approval responses.

Circulate a concise summary to the parties affected by the change. Do not assume that everyone has read the full negotiation chain. Identify the replaced version and the specific fields that changed.

Keep rejected or withdrawn alternatives in the history, but remove them from the live execution summary. Otherwise a later colleague may revive an option that was assessed and found unavailable or commercially unsuitable.

If new information arrives after approval, assess whether it changes the basis of the decision. Change control is not complete merely because an approval was once obtained; it remains relevant whenever the actual proposed employment moves beyond that scope.

Learn from the decision rather than only the outcome

After the voyage, review whether the change was clearly defined and whether the right parties decided the right questions. A difficult outcome can occur despite a sound process, while a favourable outcome can conceal an unrecorded authority gap.

Look for specific improvements. A repeated receiver ambiguity may call for a better enquiry. Slow approval may require a clearer delegation path. Conflicting instructions may require a single controlled distribution method.

The objective is to make the next change easier to evaluate, not to create a process so rigid that the cargo desk cannot respond to legitimate commercial developments.

Common mistakes

Treating a request for feasibility as a final instruction can produce conflicting plans. Another mistake is obtaining a commercial approval while leaving the revised terminal scope unassessed.

Avoid using earlier contract experience as proof of a present change right. Check the actual current wording and obtain the necessary review.

Do not close the change by sending a long email chain without a current summary. Recipients need to know what is now agreed and what earlier information it replaces.

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