Nautical charts and navigation instruments laid out for study

Key takeaways

  • Map each undertaking to its issuer and recipient.
  • Distinguish an incoming LOI from an outgoing promise by the principal.
  • Identify differences in requested acts, conditions and response obligations.
  • Keep the operational instruction separate from the exchange of undertakings.
  • Obtain advice before describing the chain as fully matched.

Understand the intermediary's position

Steamship Mutual's LOI risk discussion describes undertakings passed through a charter chain and the difficulties that arose when they were called upon. Check the current text of each relevant LOI and obtain advice on the principal's actual position rather than assuming that a chain transfers every exposure automatically.

An intermediary may receive one undertaking while issuing another. Those are separate commercial relationships. The handover should identify both because the principal's outgoing promise may need to be performed before it obtains a response under the incoming one.

The document desk should therefore avoid a single status such as LOI in place. That label does not show which side of the transaction is complete or what the principal has promised. It can also hide a missing approval at another link.

Begin with a simple map of the relevant parties and documents. The map should describe the actual relationships under review.

Map undertakings without merging them

For each LOI, record the issuer, addressee, requested act and transaction references. Identify whether the document is proposed, signed, under review or accepted through the relevant process. Preserve the scope of the decision supporting that status.

Use separate entries for incoming and outgoing documents even where their wording appears similar. A difference in party identity or requested act may matter to the principal's position. The review should examine the actual text with appropriate advice.

The map should also identify the source of the operational request. The person relaying a message may not be the party giving the undertaking. Keeping those roles distinct helps the receiving desk know whom to approach for clarification or instruction.

Do not turn the map into an unsupported legal conclusion. It shows the documents and communications available to the principal. Whether they provide matching protection is a question for the relevant advisers and commercial decision-makers.

Compare the commitments that matter operationally

The principal needs to know whether the undertakings address the same contemplated act and whether material conditions differ. Present the differences clearly without drafting a legal interpretation yourself.

If the outgoing undertaking refers to a broader request than the incoming one, identify the practical discrepancy. The principal may need revised wording, different support or a different decision about proceeding, subject to its contractual position and advice.

Also identify the kinds of response contemplated if a claim or demand arises. The reviewer should understand whether the documents address funds, security or other assistance, but should assess the exact obligations from the actual wording. A general summary that the issuer will cover losses may omit an important operational question.

The handover should preserve uncertainty about those commitments. Do not describe the principal as protected merely because documents exist on both sides of the chain.

Use a chain handover matrix

Link or taskInformation to transferQuestion to resolve
Incoming undertakingIssuer, wording and review statusWhat support is the principal being offered?
Outgoing undertakingRecipient, wording and approvalWhat has the principal promised?
Requested actExact operation and transaction referencesDo the documents address the same proposal?
Material differencesConditions and scoped comparisonWhich differences require legal or commercial approval?
Operational directionAuthorised principal's instructionWhat may the implementing party actually do?
Later demandContact and escalation responsibilityWho coordinates the principal's response?

This original matrix organises the handover. It is not a statement that one document answers another, nor a prescribed enforcement process. The actual undertakings and applicable advice govern the relevant obligations.

A concise matrix can expose a missing decision quickly. It should be supported by the documents and material communications rather than replace them with abbreviated descriptions that conceal qualifications.

Fictional case: the outgoing promise is already sent

In a fictional charter chain, an intermediary prepares an incoming LOI for review while a separate team sends an outgoing undertaking to another participant. The shared voyage record states that LOI arrangements are being finalised, without showing the different stages.

At shift change, the incoming operator assumes that neither side creates an immediate task. A review reveals that the principal has already communicated an outgoing promise while the incoming document remains subject to a material clarification.

The desk escalates the actual position to the principal and advisers. It identifies the outstanding incoming issue, the outgoing document and the operational request being considered. The principal gives an instruction based on that position rather than on an assumed matched arrangement.

The fictional case does not determine whether either undertaking is enforceable or what remedy is available. It shows why a single collective status can conceal an imbalance that the principal needs to assess promptly.

Prepare for a response obligation without predicting a claim

A good handover identifies who will coordinate matters if a demand arrives under the undertaking. This is a practical responsibility assignment, not a prediction that a claim will occur or an instruction to pay without review.

The responsible team should know where to find the relevant document, what action was authorised and what evidence records the operation. It should also know which principal and advisers must receive a substantive demand promptly through the appropriate channels.

Do not assume that passing a demand to the next party in the chain completes the principal's own response. The actual outgoing and incoming obligations require review. The handover should keep those decisions visible rather than treat forwarding as a substitute for assessment.

Where a commercial or financial response may be needed, identify the internal authority path. The operator should not have to discover who can make that decision while handling an urgent external request.

Keep the operation within the authorised scope

The party implementing the requested act needs an operational instruction from the appropriate principal. Receiving a collection of LOIs is not a clear direction about what action has been approved.

State the authorised act, relevant transaction and any conditions. If the plan changes, identify which undertakings or approvals may need review before the instruction is extended. Similarity with an earlier operation should not replace that review.

After implementation, preserve an accurate account of what occurred. Do not describe the operation in language chosen solely to match the preferred interpretation of the LOI. The factual record should remain reliable for later assessment.

The incoming desk should inherit both the current operational position and any continuing document question. Completion of the physical task should not automatically close unresolved commercial review across the chain.

Close the handover with a defined next action

For each unresolved item, identify the decision needed and the person responsible. The next action might be obtaining an issuer clarification, reviewing a difference in scope or confirming the principal's instruction. A generic request to monitor the chain is insufficient.

When an item is resolved, update its own status. Avoid marking the entire chain complete merely because one participant has returned a signed document. The handover should reflect the actual state at each relevant link.

Common mistakes

The main mistake is treating several LOIs as one collective protection. Another is using a shared status that hides an outgoing promise while an incoming undertaking remains unresolved.

Avoid assuming that forwarding a demand completes the principal's response, that similar wording produces matching obligations or that document receipt authorises the operation. Map each commitment and decision separately.

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

Educational information only; not legal, financial or trading advice. Contract wording and applicable rules control. Verify current requirements and obtain qualified advice before acting.

Frequently asked questions

Does an incoming LOI automatically protect an outgoing undertaking?

Do not assume that result. Compare the actual documents, requested acts and conditions with appropriate advice. The principal needs to understand any difference in its position.

Why track each document's status separately?

The undertakings may be at different stages. A signed outgoing document and an unresolved incoming proposal create a different commercial position from a fully reviewed arrangement.

Is forwarding a demand to another party enough?

It is one communication step. The principal's own response obligations need review under the actual undertaking, and the handover should identify who coordinates that assessment.

What should the implementing operator receive?

Provide the authorised operational instruction and its conditions. The operator should not infer permission or legal protection from a bundle of undertakings passed through the chain.

Primary sources