This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.
A licence starts with a defined prohibition
State the exact act that would otherwise be prohibited, the governing authority, the persons involved and the legal connection. Do not begin with a vague request to clear the voyage.
Check exceptions first
Review current legislation, exemptions and general licences before seeking specific authority. Record why each candidate provision does or does not cover the facts.
General and specific licences differ
OFAC describes a general licence as public authorization for a category and a specific licence as a non-public authorization to an applicant for a transaction. Both require compliance with conditions.
A pending application is not permission
Submitting a request does not authorize prohibited conduct. Separate activities that may continue lawfully from those held pending a decision.
Define the applicant
Identify the person seeking authority, its jurisdiction, role, ownership and contact. Explain why it needs the licence rather than merely observing the transaction.
Identify every restricted person
List named persons, entities owned or controlled by them, designated vessels and any government interests. Use official identifiers and explain ownership analysis.
Identify every other party
Include owner, manager, master, charterer, cargo interests, insurer, P&I club, agents, terminals, banks, suppliers, crew providers and authorities.
Anchor the vessel
Provide IMO number, current and former names, flag, registered owner, manager, location, cargo, condition and relevant designation details.
Build the voyage chronology
Set out fixture, loading, designation, route changes, current position, notices, deadlines and proposed next steps with dates and time zones.
Describe the cargo precisely
Give commodity, quantity, origin, ownership, custody, hazards, documents and destination. Distinguish verified facts from disputed assertions.
Explain the requested activity
List each service or transaction: navigation, bunkering, piloting, insurance, wages, repair, offloading, storage, sale or payment. Avoid the phrase all necessary activity.
Map every payment
Provide amount or estimate, currency, payer, banks, correspondents, beneficiary, account and ultimate benefit. Include deposits, taxes, fees, refunds and commissions.
Explain price reasonableness
Support rates with contracts, quotations, tariffs or benchmarks. An emergency should not become an unexplained transfer of value.
Identify the licensing ground
OFSI requires applicants to explain the applicable ground and satisfy its criteria. Cite the current regime rather than relying on general fairness.
Explain jurisdiction
For a UK application, describe the UK nexus. For OFAC, describe U.S. persons, currency, services, property or other relevant connections accurately.
Safety must be specific
Describe risks to life, limb, navigation, pollution, cargo and port, their probability, timing and mitigation. Attach technical evidence rather than asserting emergency.
Crew needs require detail
List people, wages, food, water, medical care, visas, travel and repatriation. Explain payment recipients and controls.
Environmental protection needs detail
Provide fuel, cargo, weather, hull, machinery and response information. State what minimum services prevent deterioration.
Cargo care may be time sensitive
Explain temperature, pressure, inerting, ventilation, stability and product degradation where relevant. Link every proposed service to the hazard.
Alternative options matter
Describe lawful ports, service providers, payment routes, cargo dispositions and why they are unavailable, unsafe or disproportionate.
Risk mitigation should be operational
Propose segregated accounts, capped payments, named vendors, direct settlement, reporting, independent verification and prohibition on substitutions.
Contracts support the narrative
Attach highlighted charter, bill, insurance, agency, supply and sale provisions. Explain rather than burying the authority in hundreds of pages.
Corporate records support identity
Include registry extracts, ownership charts, governance documents and identifiers with dates and sources.
Technical records support urgency
Use class reports, defect lists, weather forecasts, cargo manuals, master statements, photographs and port correspondence where appropriate.
Translate foreign-language evidence
OFAC's quick-reference guidance warns against untranslated documents. Provide clear translations and retain originals.
Organize attachments
Create an index tying each document to a claim. Respect portal format and size limits and use the case reference for permitted follow-up material.
Preserve the submitted version
Archive the form, attachments, timestamp, receipt and case ID. Later answers must reconcile with the original application.
One factual owner should coordinate
Legal, operations, finance and technical teams need a controlled chronology. Conflicting submissions damage credibility and slow review.
Urgency must be evidenced
OFSI says urgent applications should explain material urgency. Give deadlines, consequences and safety facts, not merely commercial inconvenience.
Review time is uncertain
OFAC says applications are case specific and may require additional information or interagency consultation. Do not promise a decision date.
Monitor through official channels
Use the portal and case ID for status. Keep a log of questions, responses and changed facts.
Update material changes promptly
New designation, port, bank, amount, cargo condition or service provider can alter the request. Do not let the authority decide an obsolete transaction.
Keep the bank informed
OFSI recommends making the bank aware where applicable. A licence does not compel a financial institution to process the payment.
Read the issued licence literally
Check named persons, acts, amounts, currencies, routes, dates, conditions, reporting and records. Commercial teams should not paraphrase its scope.
Test implementation before acting
Confirm contracts, bank instructions, invoices and operational orders match the authorization. Stop substitutions outside its terms.
Reporting survives performance
Schedule transaction reports, evidence retention and expiry review. Assign an accountable owner and preserve proof of timely submission.
Hypothetical: crew and bunker request
A designated tanker is safely anchored but running low on fuel and provisions. The application separates crew welfare, pollution prevention, bunkers, banks and capped vendor payments.
Hypothetical: new discharge port
The requested port refuses entry while review is pending. The applicant updates the authority with a screened alternative rather than relying on the old description.
Hypothetical: licence, bank refusal
Authorization is issued, but a correspondent declines under policy. The parties do not reroute secretly; they disclose a proposed replacement route and check whether amendment is needed.
Verified procedure versus forecast
The cited sources establish application procedures and evidentiary expectations. Grant, timing and conditions remain authority-specific decisions.
Forecast
Authorities will expect structured vessel, ownership, payment and safety data that can be updated without rebuilding the case. Operational licence teams will become standard in high-risk fleets.
Commercial impact
Owners face delay and care costs; charterers face cargo decisions; banks need precise routes; insurers need safe-service clarity; traders need inventory plans. A prepared file shortens avoidable information cycles.
ZeaClub view
Build the application as an executable transaction, not a legal essay. Define the prohibition, ground, parties, ship, cargo, services, money, safety, controls and deadlines. Then keep the facts current and implement only what the issued words authorize.
This article distinguishes verified source material from ZeaClub analysis, recommendations, forecasts and hypothetical scenarios.
Sources
- U.S. Treasury OFAC, Specific Licences and Interpretive GuidanceAccessed 2026-11-19
- U.S. Treasury OFAC, FAQ 75 on Specific Licence ApplicationsAccessed 2026-11-19
- U.S. Treasury OFAC, Quick-Reference Guide for Licence ApplicationsAccessed 2026-11-19
- UK OFSI, How to Apply for a Financial Sanctions LicenceAccessed 2026-11-19
- UK OFSI, Financial Sanctions General GuidanceAccessed 2026-11-19