Retain a sanctions decision that can be reconstructed

Key takeaways

• Retain the reviewed transaction as well as the screening result.
• Distinguish contemporary evidence from information obtained later.
• Preserve the scope, conditions and authority of the decision.
• Apply a legally reviewed retention schedule rather than a universal period.
• Test whether an authorised reviewer can reconstruct the decision from the retained record.

Establish the applicable retention requirements

OFAC's recordkeeping rule update extended certain retention requirements. This illustrates why an old internal schedule should not be assumed current. Check the current text and obtain advice on the obligations applicable to the organisation, transaction and records concerned.

The commercial desk should not choose a retention period from a general article. The responsible legal and compliance teams should determine the schedule, relevant triggers and any circumstances requiring continued preservation. Other applicable obligations may also need consideration.

Translate that reviewed policy into an operational process. Staff should know which records belong in the controlled file, who manages access and who authorises disposition when appropriate. A policy that exists only as a document may not govern what actually happens to evidence in personal inboxes or temporary folders.

Preserve the transaction that was assessed

The decision should be linked to a defined proposed act. Retain the material party, vessel, cargo, route and payment information that the reviewer actually considered. A result without that context can be mistaken for approval of a different transaction later.

Identify which facts were confirmed and which were assumed or provisional. If an approval depended on a stated condition, preserve that condition with the decision rather than leaving it only in a separate email.

Do not update the old record by replacing its facts with the latest commercial information. Keep the original assessment understandable and add the later development as a distinct event. This allows a reviewer to see whether a change required a new decision.

The working operational record can show the current plan while the retained review record preserves the earlier basis. The two serve different purposes and should remain connected without being confused.

Keep the search evidence interpretable

Retain the submitted identity and relevant identifiers, the source used and the result available to the reviewer. The evidence should show what was searched, not merely that someone opened a screening tool.

A live link can help locate a source, but it may display changed information later. Preserve the evidence needed under the organisation's process to explain the result actually considered. Avoid creating an apparent historical record by taking a fresh search and labelling it as the earlier one.

Where the search produced an alert, retain its connection to the resolution. The reviewer should be able to distinguish the tool's output from the organisation's subsequent assessment. A dismissed alert should not disappear as though it never existed.

Retain reasoning without turning the file into a transcript

The record should explain the material question and why the authorised conclusion followed. It need not reproduce every incidental conversation. Focus on the evidence that changed or supported the decision and the qualifications that remain relevant.

Distinguish a factual confirmation from legal advice or a commercial instruction. A reviewer may have accepted an identity explanation while another question remained unresolved. The retained summary should not compress those different conclusions into a single cleared label.

Preserve the scope of professional advice according to the organisation's process, including appropriate restrictions on sensitive or privileged material. Operational users may need the resulting instruction and limits without access to the full analysis.

A concise reasoned summary can make the record easier to use, but it should remain traceable to its sources. Do not allow the summary to replace contradictory evidence or erase uncertainty that existed at the time.

Use a reconstruction checklist

This original checklist tests practical usefulness. It is not a regulatory record specification and does not define the applicable retention period. The organisation should align it with its reviewed obligations and systems.

A successful test lets another authorised reviewer follow the material decision without relying on the original operator's memory.

Fictional case: a live link changes the historical picture

In a fictional voyage review, the desk saves a link to a screening result and a short approval message. Later, the linked source changes. A reviewer opens the link and assumes the displayed information is what the original decision-maker saw.

The retained record does not support that assumption. The current page may be accurate now, but it does not reconstruct the earlier result. The team identifies the gap and gathers available contemporaneous evidence without presenting the new search as a historical substitute.

For subsequent reviews, the organisation changes its evidence-preservation process and tests retrieval. The decision summary is linked to the source material actually considered and to any later update requiring assessment.

The fictional case does not establish a regulatory breach. It shows how a useful live reference can be insufficient for explaining a past decision unless the relevant historical evidence is preserved appropriately.

Control corrections and later additions

A retained file may need correction when an identifier was transcribed incorrectly or a source is clarified. Record what changed and why. Preserve the distinction between correcting the record and claiming that different information was available to the original reviewer.

Later evidence can improve understanding without rewriting history. Label it as later evidence and identify whether it prompted a new assessment. This allows the principal and advisers to evaluate the actual sequence honestly.

If an earlier conclusion is revised, connect the new decision to the old one and explain the scope of the change. The operational team should know which instruction is current, while the review file retains the basis of both decisions.

Make retention work across handovers and systems

Identify where the controlled record resides and how authorised reviewers retrieve it. A file that exists only in a former employee's mailbox may be difficult to use even if it has technically been kept.

When systems change, verify that the material relationships survive: transaction to evidence, alert to resolution and decision to instruction. Migrating attachments without their context can leave a large archive that cannot explain the review.

Access should follow the roles and sensitivity of the information. Avoid duplicating identity documents broadly simply because several operational teams need to know the decision. Give them the relevant instruction while preserving the evidence in the appropriate controlled location.

Apply disposition through the reviewed schedule and any relevant preservation direction. The operator should not delete a file merely because the voyage has ended or keep it indefinitely without regard to the applicable policy.

Common mistakes

The main mistake is retaining a final status without the transaction and reasoning behind it. Another is treating a live source link as a complete historical record.

Avoid replacing old facts with new ones, removing dismissed alerts without explanation or migrating documents without their relationships. Retain a decision that can be understood and apply the appropriate legal schedule.

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