LOI disputes when the intended recipient changes

Key takeaways

• Identify the recipient and capacity described in the actual request.
• Distinguish a contact change from a change in the intended delivery arrangement.
• Preserve the relationship between the undertaking and the operational instruction.
• Seek advice on disputed scope before relying on an assumed equivalence.
• Make any agreed change explicit in the authorised instruction.

Define the recipient question precisely

Steamship Mutual's LOI risk discussion describes a dispute in which the recipient's agency role mattered to the undertaking. That outcome depended on the facts and wording. Check the current text and obtain advice on the actual arrangement rather than extending another case's result to a new request.

The commercial desk should identify what has changed. A new operational contact may represent the same intended party, while a new company name may indicate a different proposed recipient or capacity. The reviewer needs evidence of the relationship rather than an assumption based on a familiar email chain.

Ask the requester to describe the intended action clearly. Who is to receive or handle the cargo, in what capacity and under whose instruction? The answer should be specific enough for the carrier and advisers to assess the request without reconstructing it from logistics shorthand.

The preparer should not decide entitlement to the cargo. Its task is to make the factual and documentary question clear and preserve the actual instructions for the authorised decision-makers.

Compare the request with the undertaking

Place the relevant operational request beside the LOI under review. Identify the recipient, place and action described in each. A difference may be an innocent clarification, but it still needs to be understood before the carrier relies on the undertaking for the proposed act.

Do not resolve the mismatch by editing the operational summary alone. If the intended arrangement has changed, the principal and advisers need to consider whether the undertaking, instruction or both require attention. The document desk should not supply its own interpretation through a revised label.

The review should also consider the capacity in which the named participant acts. A service provider's involvement does not automatically explain whom it represents or what authority it has. Obtain the relevant confirmation rather than inferring the relationship from its presence at the operation.

Where several intermediaries relay the request, preserve the original instruction and any subsequent qualification. A compressed final message can conceal a change introduced earlier in the chain.

Separate the factual dispute from the legal question

The parties may disagree about who a participant represents, what action occurred or what the LOI covers. These issues require different evidence and review. Identify which one is actually unresolved.

A factual question about a participant's role may require confirmation from the responsible party and relevant supporting records. A question about the legal effect of the wording needs advice. A commercial proposal to change the recipient requires the principal's decision and any further agreement necessary.

Do not treat a confident operational explanation as a legal conclusion. Equally, do not ask the adviser to decide a factual relationship without presenting the available evidence and its limitations. The quality of the review depends on keeping those inputs distinct.

If the facts remain uncertain, explain the competing accounts and the action currently proposed. The principal should understand what is unknown before deciding how to proceed with advice.

Use a recipient-scope issue table

This original table supports preparation for the carrier and advisers. It does not define delivery, agency or entitlement as a matter of law. Those questions depend on the relevant facts, documents and applicable legal framework.

Use the table to narrow the dispute. A request for a clearer company identity may resolve a factual mismatch; it will not necessarily resolve a contested interpretation of the undertaking.

Fictional case: the new recipient is called a contact update

In a fictional cargo operation, the accepted working plan identifies a recipient in an LOI. Before the intended action occurs, a new message names another company and describes the change as an update to the local contact details.

The operator notices that the company identity has changed, not merely the contact person. The requester says the new company is involved in the same commercial arrangement but does not explain its capacity. The undertaking still names the original party.

The desk pauses the assumption that the change is administrative and presents the discrepancy to the principal. The relevant relationship is clarified and the proposed action is reviewed against the LOI with advice. Any resulting instruction states the reviewed scope rather than relying on the phrase contact update.

The fictional case does not decide whether either company is entitled to receive the cargo. It illustrates why a change introduced through casual operational language can require a substantive scope decision.

Assess proposed solutions without assuming protection

The requester may offer a revised LOI, additional confirmation or a different operational arrangement. Each proposal should be reviewed on its own substance. More paperwork is not necessarily a complete answer if it leaves the requested act or recipient unclear.

Identify what the proposed solution is intended to resolve. A confirmation of identity may answer one factual question while leaving the legal scope unchanged. A revised undertaking may require a fresh issuer or authority review. A different operation may raise new practical or contractual questions.

The principal should receive a concise explanation of those consequences. Do not describe a proposal as acceptable simply because it is customary in the requester's business. The carrier's actual decision must address the arrangement it is being asked to implement.

Where the parties reach a commercial resolution, clarify its scope through the appropriate review. Preserve any issues that remain open rather than reporting a practical agreement as a general admission about the earlier dispute.

Give operations a reviewed instruction

The final instruction should identify the authorised action and the relevant party with enough clarity for the operator to implement it within its role. It should preserve any condition or limitation that forms part of the decision.

Operations should not be expected to infer the legal result from an LOI attachment and several inconsistent messages. The principal should provide the operational direction, supported by the reviewed documents and advice.

If a further change is requested at the point of execution, identify it promptly and return the affected question for review. Do not extend an earlier instruction merely because changing the plan again would be inconvenient.

Retain the request, clarification, undertaking and instruction as a connected record. That record explains the basis of the action without turning the preparer's summary into a substitute for the underlying evidence.

Common mistakes

The main mistake is treating a changed company as a changed contact person. Another is assuming that a service provider's presence establishes its capacity or the scope of the undertaking.

Avoid merging factual clarification with legal interpretation, relying on forwarded shorthand or assuming that a revised LOI resolves every issue. Review the recipient, act and protection together.

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