Editorial note

This article provides general information, not legal, regulatory or financial advice. Requirements depend on the applicable contract, authority and jurisdiction.

Nautical charts and navigation instruments laid out for study

A project label does not describe the whole transaction

A commercial request headed Sakhalin-2 can contain several different jobs. A broker might be asked about a crude shipment, an adviser about a project service, and a finance team about a payment. Treating that heading as the answer to every sanctions question makes the proposal less reliable. The useful starting point is the actual work requested, the product involved and the parties performing it.

The November publication records an existing license, not a fresh November opening. GL55F's crude-maritime provision concerns Sakhalin-2 byproduct solely for Japan, through 12:01 a.m. Eastern standard time on December 18, 2026. Separate paragraphs address specified project-related banking and petroleum-service prohibitions, with retained exclusions. OFAC's published license text supplies those distinctions.

For a US service company, the immediate commercial question is therefore narrower than whether it can work on Russian energy. It is whether the particular requested service has a sufficiently defined factual basis for a qualified sanctions review. Pricing an unidentified bundle before resolving that question can create a quotation that the company cannot responsibly perform.

Separate the cargo proposition from the service proposition

A shipper may describe its cargo by broad commodity category, while a service request describes the activity. Neither description necessarily establishes the other. A statement that oil comes from a named region does not by itself identify a named project's output. Equally, an association with a project does not establish that every shipment contains the particular product described in a permission.

The review should begin with information the commercial team can reasonably request: the contracting entity, the precise service, the declared product, its documented project connection, and the intended consignee and destination. The purpose is to obtain an accurate transaction description for review, not to redesign a transaction to fit a preferred answer. Missing origin evidence should remain a missing fact rather than becoming an assumption in the price sheet.

OFAC's petroleum-services FAQ also discusses a broader services prohibition and identifies project-specific authorizations within that framework. It does not present the existence of an energy project as a general exemption. FAQ1216 provides that background.

This matters when a request combines work for several projects. A customer relationship may be longstanding and commercially valuable, yet the new work can differ from the previously reviewed assignment. The sensible unit of analysis is the proposed transaction. Customer familiarity helps communication; it does not supply missing facts about an additional cargo or service.

Mixed proposals need separate commercial decisions

Consider an expressly fictional service firm reviewing three proposed jobs. Job A involves a specifically identified project cargo and destination supported by documents. Job B uses only a broad regional origin description. Job C concerns a different product and a separate service package. Assume no job has yet received legal clearance. A commercial manager should not group all three under one favorable project headline.

The next action can differ without declaring any job lawful or unlawful. Job A may be ready for detailed review. Job B may require better origin information before a meaningful assessment. Job C may need a different scope analysis entirely. This distinction prevents both overstatement and unnecessary rejection: incomplete evidence is different from an adverse determination, and an unrelated service is different from a duplicate of the reviewed work.

Suppose the hypothetical firm expects contributions of $80,000, $60,000 and $40,000 from the respective jobs, before common overhead and any review expense. The commercial pipeline totals $180,000. If only Job A is sufficiently documented to enter the next approval stage, the firm should not describe $180,000 as executable business. Even the $80,000 remains conditional until the required decisions are complete. The example measures internal pipeline quality, not sanctions exposure or the probability of obtaining permission.

A practical forecast can distinguish identified opportunity, adequately described work and approved commitment. That makes staffing decisions more defensible. Reserving the same scarce specialist team against all three jobs may block an unrelated assignment without creating a corresponding executable revenue opportunity.

A destination assumption can change the offered service

Destination should be treated as a commercial fact requiring support, not a casual line in an introductory email. A buyer may want optionality for ordinary market reasons, but optionality can be material to the scope of a project-specific authorization. The commercial team should bring any such difference to the reviewer before presenting a firm service commitment.

That does not require publishing a customer's confidential documents or circulating sensitive information unnecessarily. It requires an agreed factual statement of what the company is being asked to do and a controlled route for material changes. If the customer later changes that statement, the earlier approval should not be represented as a review of the changed proposal.

The same principle applies to a customer who asks for one price covering an immediate job and several possible later assignments. A quotation can distinguish the defined assignment from future work requiring separate agreement. Commercial simplicity is useful only when the promised scope is intelligible. A single attractive price is not an improvement if it obscures which work the seller is prepared to undertake.

The service company's decision remains its own

A customer's assurance, a bank's willingness to discuss payment, and a supplier's commercial interest answer different questions. None should be presented as a substitute for the service provider's assessment of its own role. The actual entities and activities matter more than a general claim that other participants are comfortable with the project.

Timing also belongs in the decision. A proposal stretching beyond the reviewed authorization period should not assume that a future extension will arrive. The company can identify the dependency without speculating about policy. Before commitment, the responsible reviewer should check the then-current official text, any replacement or amendment, and other applicable restrictions. This article's research date does not turn its historical account into continuing transaction clearance.

A proposed Zeaclub workflow could help a buyer distinguish the project name, product description, requested service and unresolved commercial assumptions in an inquiry. Such organization would support a qualified human review; it would not determine eligibility or provide authorization. Bring a clearly described service requirement to Zeaclub when exploring counterparties, and keep the permission decision tied to the actual transaction rather than a familiar energy headline.

Sources