This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
Key takeaways
- Compare the final operating plan with the proposal actually assessed.
- Identify conditions attached to advice, authorisations and internal approval.
- Obtain evidence that the relevant conditions have been addressed.
- Separate a claimed authorisation from a reviewed basis for reliance.
- Give operations a clear instruction and defined escalation triggers.
Review the plan that will actually be performed
The final plan may differ from the enquiry that first entered compliance review. A vessel substitution, revised cargo description or new service participant can appear during normal commercial preparation. The pre-voyage check should identify those differences before the next dependent action is authorised.
Use a concise comparison of the assessed facts and the current instructions. The objective is not to repeat every earlier search without purpose. It is to establish whether the review still addresses the actual proposal and whether any open question has been resolved.
The operator should identify a difference without having to decide its legal significance. The responsible compliance reviewer and adviser can determine whether the change requires additional assessment. Check the current text of the applicable rules and any relevant authorisation.
Identify what the earlier decision depended on
Read the scope and conditions of the earlier assessment. A decision may have relied on a particular party structure, payment route, cargo description or proposed service. Those assumptions should be visible rather than buried in a long advice exchange.
Ask whether each material assumption remains true on the information available. If it was provisional, identify the confirmation that has since been obtained. Do not turn a provisional fact into a confirmed one merely because the voyage is approaching.
The principal should also know whether the earlier conclusion was limited to a particular jurisdiction or activity. A favourable answer to one question should not be expanded into permission for every related service or financial transaction.
Where the scope is unclear, ask the reviewer to clarify it. The pre-voyage desk should not interpret a brief approved status as broader than the underlying decision.
Review any claimed licensing basis carefully
OFAC's licensing guidance states that transactions relying on its licences must meet their applicable terms, including relevant conditions and recordkeeping or reporting requirements. That is a US-specific context. The actual basis for any proposed reliance requires qualified review under the relevant regime.
If a participant supplies an authorisation or says an activity is licensed, identify the document and the claim being made. Ask the responsible adviser to assess whether it applies to the proposed parties, activity and circumstances. The operator should not decide that question from a title or summary.
Keep the legal conclusion separate from the practical evidence needed to satisfy its conditions. A reviewer may identify what must be confirmed, while operations collects the relevant factual support. Completion should be assessed by the authorised person, not inferred from a populated checklist.
Do not assume that applying for an authorisation is equivalent to having the necessary permission. Present the actual status and obtain an instruction appropriate to it.
Translate conditions into evidence questions
A condition becomes operationally useful when the team knows what fact must be established and who can establish it. Avoid broad entries such as documentation satisfactory if the actual issue concerns a specific cargo or party detail.
The evidence request should state its scope. Ask for the relevant confirmation without inviting a counterparty to provide a sweeping legal assurance it may not be qualified to give. The compliance reviewer should assess the resulting information in context.
If a condition depends on a future event, identify how it will be monitored and what decision follows. The pre-voyage review may need to distinguish actions authorised now from later actions requiring further confirmation.
Where the evidence remains incomplete, preserve that status. An unresolved condition should not disappear from the operator's view when the planning team circulates a clean final itinerary.
Use a conditions-to-action table
| Review component | Evidence question | Instruction needed |
|---|---|---|
| Current plan | What differs from the assessed proposal? | Whether further review is required |
| Party roles | Are the actual participants confirmed? | Scope of reliance on the prior assessment |
| Cargo and route | Do current instructions match reviewed facts? | Treatment of any material change |
| Claimed authorisation | What document and legal basis are relied upon? | Qualified assessment of applicability |
| Outstanding condition | What fact remains to be established? | Who decides completion and what waits |
| Later voyage change | What would affect the decision's assumptions? | Escalation route and permitted interim work |
This original table is a commercial coordination aid. It is not an authorisation checklist for any particular sanctions programme. The actual requirements must come from the current rules, reviewed documents and appropriate advice.
Fictional case: a service addition falls outside the review
In a fictional voyage, compliance reviews a defined carriage proposal and issues a scoped internal decision. During final planning, the commercial team adds a separate service arrangement and assumes it is covered because it relates to the same cargo.
The pre-voyage comparison identifies that the added service and participant were not included in the assessed facts. The operator describes the new arrangement and the action required, then seeks the responsible review rather than extending the earlier decision.
The principal receives an updated instruction for the actual proposal. Any conditions relevant to the additional arrangement are made visible to the team coordinating it. The earlier review remains valid evidence of what was considered, without being represented as a broader approval.
The fictional case makes no claim that the added service is prohibited or requires a licence. It illustrates why the same cargo can be involved in distinct activities that need their scope assessed rather than assumed.
Keep external confirmations within their scope
A bank, insurer, agent or other participant may confirm its own position on the proposed arrangement. Preserve what that confirmation actually covers. It should not be treated as the principal's complete legal assessment or as permission on behalf of another participant.
If a confirmation is conditional, identify the condition in the working plan. A short operational summary should not remove a qualification that matters to the decision.
The principal may need to coordinate several responses before issuing an instruction. Present their relationships clearly rather than treating one positive response as resolving all remaining questions. The review should show where a dependency remains open.
If the participants' responses conflict, send the actual communications to the responsible reviewers. Do not select the most convenient answer or assume that the latest message overrides every earlier limitation.
Release an instruction that the operating team can use
The final instruction should identify the action authorised, the current proposal and any continuing conditions. Operators need to know what change requires escalation and whom to contact if it occurs.
Do not give operations an abstract statement that sanctions are cleared. A more precise instruction can preserve the decision's scope without distributing sensitive advice or unnecessary identity documents to every participant.
If the review is incomplete, state the question and the action awaiting resolution. The responsible principal should determine the interim position with appropriate advice. The operator should not fill the gap through an assumption about commercial urgency.
Retain the comparison, evidence and decision so that a later reviewer can understand why the voyage action proceeded on the basis it did.
Common mistakes
The main mistake is treating an earlier approval as permission for a changed final plan. Another is assuming that a licence title or an application establishes the right to perform the proposed activity.
Avoid losing conditions in a clean itinerary, treating another participant's confirmation as universal approval or asking operators to decide legal applicability. Test the actual plan against the reviewed scope.
Where Zeaclub fits
Zeaclub offers digitalised procedures across the voyage workflow.
Zeaclub provides 24/7 operating systems and worldwide coverage.
Explore 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
Must every earlier check be repeated before a voyage?
Use the organisation's reviewed process and assess the current facts and source information. The immediate task is to identify changes and unresolved conditions, not repeat work mechanically or assume old conclusions remain sufficient.
Does a licence cover every related voyage service?
Do not infer that. The responsible adviser should assess the actual authorisation and proposed activity, including its conditions and limits.
Can a bank's confirmation replace the principal's review?
Preserve the scope of the bank's response. It may address its own participation without resolving every question relevant to the principal's activity.
What should operations know after the review?
Provide the authorised action, conditions and triggers for renewed assessment. The team should have a clear escalation route if the actual plan changes.