Supply Chain Action Points
Read this first — the conclusion, and the moves to make:
- By 26 June 2026, obtain the framework text and identify separately the clause that grants transit and the instruments that lift each prohibition, recording two documents with two expiry dates, because a single expiry assumption is the most common error in this file.
- By 30 June 2026, register every Iranian-origin cargo and every Iranian port call against its specific waiver or listing entry, with issuing instrument, effective date and expiry, to a target of full coverage; an announced waiver is not an entry.
- By 3 July 2026, require an independent positional record for any leg on which AIS is switched off, such as port state, agent or berthing records, so that no claim fails for want of records you chose not to keep.
- By 15 July 2026, tag every live contract that references the 60-day window with day 61 as a contract event on the compliance calendar, because a cliff that is only in the news is not managed.
- Weekly until the framework is signed, log separately which order your master is actually complying with, the IRGC closure or the U.S. position, since divergence between the two, not the closure itself, is the exposure a claim will turn on.
Shipping through the Strait of Hormuz stalled over the weekend, with only 12 ships transiting Sunday versus 21 the prior day, and 5 of 8 inbound vessels going dark (AIS off), per Windward data. Iran's IRGC declared the waterway shut on Saturday citing Israeli strikes in southern Lebanon; the U.S. military countered that 'Iran does not control the Strait of Hormuz.' Lloyd's List separately reported 15 Iran-flagged VLCCs and Suezmaxes sailed outbound from the Gulf of Oman with AIS active. U.S. Vice President JD Vance led the U.S. delegation to Bürgenstock, Switzerland for talks on a final 60-day peace framework; both sides reported 'constructive but tense' progress and established a Lebanon deconfliction mechanism. Iran secured waivers for oil exports, the lifting of port blockades, and partial frozen asset release. The MOU included free Hormuz transit for 60 days and an end to all hostilities.
The Analysis
Over the weekend the strait stopped. Windward's count is 12 transits on Sunday against 21 the day before, and five of the eight inbound vessels went dark. The IRGC declared the waterway shut on Saturday, citing Israeli strikes in southern Lebanon; the U.S. military answered that Iran does not control the Strait of Hormuz. Lloyd's List, working separately, counted 15 Iran-flagged VLCCs and Suezmaxes sailing outbound from the Gulf of Oman with their transponders on. In Bürgenstock a 60-day framework is being finalised, with free transit for 60 days, an end to hostilities, waivers for Iranian oil exports, the lifting of port blockades and a partial release of frozen assets.
Strictly speaking, the remarkable thing in that paragraph is not the volume. It is that two states have issued two incompatible statements of authority over the same water and neither of them is a court. When authority is contested, the question your master faces is not who is right. It is whose order he is obliged to obey, and what his insurer will say about it afterwards.
A dispute over who controls a strait is not a factual dispute that evidence can settle, because the two claims are made on different foundations. One is control on the water, exercised by a force that can stop a hull. The other is a legal position, that this is a strait used for international navigation whose transit passage cannot be suspended. Both can be true at once, which is the uncomfortable part. A right of transit passage is not a remedy. It tells you what the law permits; it does not tell you what happens at the boarding ladder, and it does not tell a master how to reconcile two orders that cannot both be followed.
Sixty days is a term, not a settlement. A clause granting free transit for 60 days creates a cliff at day 61 and removes the urgency to resolve anything before it. The dangerous feature is not the length. It is that the instrument granting the transit and the instruments imposing the prohibitions are not the same instruments, and nothing requires them to expire together. You can reach day 61 with a memorandum that has run out and a listing that still stands, or the reverse, and the two produce entirely different exposures for the same cargo.
The waivers deserve the same treatment, and this is where most compliance files go wrong. A waiver is not a repeal. It is discretionary, usually time-bound, and it typically binds the issuing administration without binding a bank's compliance desk, which reads entries rather than press releases. If your transaction touches Iranian oil, the question is not whether a waiver was announced. It is whether the specific entry behind your cargo was amended, by which instrument, effective when, and until when. A waiver announced but not published in an amendable form does not yet exist for documentary purposes, and a bank that cannot see it will not pay against it.
The incidence falls by role before it falls by size. Operators of Iran-flagged tonnage feel it first and most directly, because their flag is the fact that attracts the scrutiny. Non-Iranian owners with Gulf calls feel it at the next renewal, when the additional premium line and the transit notice obligation are reset by someone reading a loss record rather than a communiqué. Container importers whose carrier relays through a Gulf hub feel it as schedule slippage, which their customers will describe as unreliability. An importer with no Gulf leg and no relay feels nothing at all except, eventually, a surcharge line that nobody on their side can explain, which is the most expensive kind of exposure because it is the least arguable.
This is the point the coverage has not made, and it is why the transit counts cannot carry the weight being placed on them. Five of eight inbound vessels went dark. A dark vessel is not only a safety question; it is an evidentiary one. The voyage history that an insurer, a bank or a tribunal would use to establish where the cargo went and when does not exist, because the party that would have created it decided not to. When a claim arrives, the burden of proving that the voyage was lawful and that the casualty happened where you say it did rests on whoever holds the records, and that party has just chosen not to hold them. Then look at the asymmetry: the outbound Iranian-flagged tankers were broadcasting. Selective visibility means the visible count is a count of ships that chose to be counted. It is a sample, not a census, and treating a sample as a census is how a model acquires confidence it has not earned.
So what does 12 against 21 actually establish? An arithmetic exercise, with my assumptions flagged as mine. If five of eight inbound are dark, roughly 62% of inbound traffic is invisible. Suppose that ratio held across the board, which I cannot verify and do not claim. Then 12 visible implies something nearer 32 actual, and 21 implies nearer 56. The direction of the move survives; the level does not. Every downstream statement built on the level inherits an error of more than a factor of two, and the error runs in the direction that makes a queue look shorter than it is. Use the number to show that traffic fell. Do not use it to size what is waiting.
Run the counterfactual both ways, because the framework cuts in two directions. If you treat the 60-day clause as a settlement, you will price a route as though day 61 resembles day 1, and you will sign commitments whose conditions expire before your performance does. If you treat it as noise, you will keep paying a war-risk element that the market may reprice downward within weeks, and you will have paid it on a route that was, for a defined window, contractually open. Neither error is about prediction. Both are about which instrument you are reading.
The boundary condition, stated plainly, is this. Every conclusion above rests on the premise that the prohibitions and the permissions come from different instruments with different clocks. If it turns out that a single instrument does both, granting transit and lifting the listings in one text with one effective date and one expiry, then the cliff I described disappears and the exposure collapses into a single date you can diarise. I have seen no text that does that, and the reporting describes a memorandum plus waivers, which is two things. Until the texts are in hand, the register is the only defensible artefact, and the forecast is not.
↑ Back to the key points