The Road to Adoption: A Dated Record and a Sensible Posture

7 min read

What you'll take away Recount the framework's approval-to-deferral record as dated facts, explain what adoption would trigger and when force could follow, and set out no-regret actions for a shipowner while adoption is pending.

Everything this course has taught is approved text. This lesson is about the gap between approved and adopted: told strictly as dated facts, because in a story this political, dates are the only stable ground.

The record

April 2025: MEPC 83. The committee approved the IMO Net-Zero Framework: draft amendments to MARPOL Annex VI carrying the fuel standard, the pricing tiers, the surplus units and the Fund. Approval fixes a text and signals intent; it binds nobody. The plan was adoption at an extraordinary session that autumn, and entry into force in the course of 2027: consistent with first targets dated 2028.

October 2025: the extraordinary session. Meeting on 14–17 October with adoption on the agenda, the committee instead voted to adjourn for a year. Member-state positions had hardened, over economic impact on long-haul trades, over the governance and distribution of the Fund, and under open external pressure on delegations. DNV's note on the decision records the one-year delay and the resumed-session plan (DNV).

May 2026: MEPC 84. The committee again did not adopt. It agreed further intersessional work on the framework and its guidelines, with a resumed session expected before the end of 2026. Lloyd's Register's summary of the session records the state of play (LR MEPC 84 report).

That is the whole record: approved, then twice deferred. Treat any bolder claim, "dead", "inevitable", "delayed to 2030", as opinion until a committee session gives it a date.

Filled markers: dated facts. Hollow markers: expected, not yet decided. Apr 2025 MEPC 83 · approved May 2026 MEPC 84 · deferred again early-to-mid 2028 entry into force, if adopted Oct 2025 extraordinary session: adjourned one year late 2026 resumed session expected 16 months · tacit acceptance clock First targets in the approved text are dated 2028.
The record and the clock on one line: two deferrals so far, and sixteen months between any future adoption and entry into force. Everything right of MEPC 84 is the expected sequence rather than a decision taken which is why later adoption puts the 2028 target dates themselves in question.

What adoption would trigger

The framework amends MARPOL Annex VI, so adoption starts the tacit acceptance clock: entry into force 16 months later, unless objections from a sufficient share of parties block it: a bar that has rarely been met in MARPOL practice. Adoption at a resumed session in late 2026 would therefore mean force around early-to-mid 2028, aligning neatly with the 2028-dated first rungs of both target ladders. Every further slip in adoption pushes that arithmetic outward: later adoption dates put the 2028 targets themselves in question, one of the adjustments a resumed session would have to settle. Meanwhile the supporting machinery, LCA certification guidelines, the GFI registry, the Fund's disbursement rules, kept moving between sessions; the Global Maritime Forum's guide walks through the adoption scenarios and what remains to be built under each (GMF guide).

A sensible posture while it is pending

A shipowner cannot schedule around a decision the IMO has not made. What you can do is spend only on things that pay under every scenario:

  • Get the DCS data clean. GFI would be computed on that backbone, and FuelEU already prices the same class of data on EU trades. Bad fuel data costs money under every future.
  • Know your fleet's attained GFI. The arithmetic of lesson 3 works today. Knowing where each ship sits against both ladders turns any future adoption headline into a spreadsheet update instead of a project.
  • Buy optionality, not predictions. Biofuel-capable ships, charter clauses that allocate GHG compliance costs explicitly, supplier relationships that can document fuel pathways, all valuable with or without the framework.
  • Watch the guidelines, not the headlines. The technical work between sessions decides what compliance mechanically looks like; session-week commentary mostly does not.

And the scenario where adoption never comes is not a scenario where nothing happens. FuelEU Maritime demonstrated that a major trading bloc will regulate fuel intensity unilaterally when global rules stall; a collapsed framework makes more regional regimes likelier, not fewer, and a patchwork of them is harder to operate under than one global standard.

The honest summary a board deserves: the framework was approved in April 2025, has twice missed adoption, and carries first targets dated 2028 that compress further with every deferral. Whether it enters into force on that schedule is a political question. Whether well-to-wake fuel intensity gets priced is not: Europe already did it. Preparing for the framework is therefore not a bet on the IMO's calendar; it is the same preparation the existing regulation already demands, done early enough to be cheap.

Check yourself

1. What happened at MEPC 83 in April 2025?
2. What did the extraordinary session in October 2025 decide?
3. Under tacit acceptance, entry into force would follow adoption after how long?
4. After the MEPC 84 deferral, what is the earliest realistic entry-into-force horizon?
5. Why is DCS data hygiene a no-regret action while adoption is pending?
6. Which of these are dated facts in the framework's record?

Select all that apply.

7. Because adoption was deferred, the approved framework text lapsed and drafting must restart from zero.
8. Under tacit acceptance, how many months separate adoption from entry into force?
months