Three arguments get fleet software approved and they do not work equally on everyone in the room. The compliance argument moves the person accountable for the vessel trading legally, and in 2026 it is unusually strong because the deadlines are dated rather than general — FuelEU vessel reports were due by 31 January, third-party verification by 31 March, compliance data uploaded by 30 April, penalties issued from 30 June, EU ETS verified emissions submitted by 31 March with allowances covering seventy percent of 2025 emissions surrendered by 30 September, and UK ETS for maritime launching 1 July. The risk argument moves the person who signs off operational exposure, because a detention or an off-hire day has a number attached that everybody recognises. The cost argument moves the finance function, and it is the weakest of the three despite being the one most papers lead with. There is also a fourth that almost nobody makes, and it is increasingly the most persuasive to an owner: banks applying the Poseidon Principles increasingly expect decision-grade data and documented compliance controls rather than headline targets, which puts record quality inside a financing conversation. This page sets out all four as arguments you can adapt rather than as advice about writing one. Start a free trial of Marine Inspection and generate the evidence each of them rests on.
Compliance
Moves: the person accountable for the vessel trading
Strongest in 2026 because the deadlines are dated. Hard to argue with a calendar.
Strong
Risk
Moves: operations and the technical function
A detention or an off-hire day carries a number everybody in the room already knows.
Strong
Cost
Moves: finance, but less than you expect
Discounted heavily where the inputs come from a supplier. Most papers lead with this.
Weakest
Financing
Moves: the owner, and almost nobody makes it
Lenders applying the Poseidon Principles expect decision-grade data and documented controls.
Underused
Most rejected papers lead with cost, which is the argument the reader is most trained to discount, and omit financing entirely. Reordering those two is frequently the whole difference between a paper that is deferred and one that is signed.
Argument One: The Calendar
The compliance argument is strong in 2026 for a reason that has nothing to do with rhetoric — the dates are published and they have already started passing. Book a Marine Inspection demo and put your fleet's position against each of these in writing.
Dated Obligations Falling in a Single Year
31 JanFuelEU Maritime vessel reports due for the first compliance period, which closed on 31 December 2025
31 MarThird-party verification of FuelEU data, and verified EU ETS emissions submitted for the 2025 compliance year
30 AprFuelEU compliance data uploaded for tracking
30 JunFuelEU penalties issued where appropriate, and Documents of Compliance distributed
1 JulUK Emissions Trading Scheme scheduled to launch for maritime
30 SepEU ETS allowances surrendered covering seventy percent of verified 2025 emissions
All yearEU ETS at full scope with all regulated emissions covered and exposure calculated on a carbon dioxide equivalent basis, a CII reduction factor of eleven percent, a FuelEU intensity requirement, SEEMP Part III revised for 2026 to 2028, and new Emission Control Areas in the Canadian Arctic and Norwegian Sea
The argument writes itself from that list. You are not asking to fund an improvement — you are asking to fund the data infrastructure that a set of dated legal obligations requires, several of which have already generated a submission this year.
And the volume has changed shape
Six years ago the reporting obligation was substantially annual fuel consumption. In 2026 it is quarterly emissions reporting, an annual carbon intensity report, fuel changeover logs, scrubber operation logs and compliance plans. Industry commentary is blunt about the consequence: 2026 demands exponentially more documentation than previous years, but volume overwhelms quality assurance, and inspectors increasingly find documentation quantity adequate and quality insufficient — forms completed but information inaccurate, inconsistent, or clearly not reflecting actual operations.
Argument Two: What Happens If You Do Not
The risk argument works best when it describes a sequence rather than an event, because a sequence explains why deferral is not free. Sign up for Marine Inspection and use this progression in the paper directly.
Stage 1
Inspection targeting rises
Published analysis puts vessels with poor compliance records facing inspection on sixty to eighty percent of port calls, against fifteen to twenty-five percent for high performers. That is not a penalty — it is a multiplier on every other exposure you carry.
Stage 2
Vetting access narrows
Major oil companies and charterers are implementing digital compliance requirements, with the reported consequence that paper-based operators lose access to premium cargoes. This is a commercial exclusion rather than a regulatory one, and it does not appear in any deficiency record.
Stage 3
Environmental penalties
EU ETS, FuelEU Maritime and regional schemes impose substantial fines for non-compliance, reported in the range of a hundred and fifty thousand to over a million dollars annually per vessel depending on exposure and trading pattern.
Stage 4
Insurance response
Clubs increase premiums or decline coverage for systematically non-compliant operators. Unlike a fine, this arrives at renewal and persists across cycles rather than clearing when the deficiency is closed.
Stage 5
Flag state pressure
Repeated deficiencies trigger enhanced flag state oversight and, at the extreme, potential certificate withdrawal. This is the end of the sequence and it is the point at which the conversation is no longer about budget.
Note what makes this useful in a paper: it is progressive. Each stage makes the next more likely, which means the honest answer to "what if we wait a year" is not "the same problem, twelve months later" — it is a position further along a sequence that gets harder to reverse at each step.
60-80%
against
15-25%
Port call inspection rates: poor compliance record versus high performer
That ratio is the most useful single number in a budget paper, because it is a multiplier rather than a cost. Every detention risk, every deficiency exposure and every hour of inspection disruption you carry is scaled by which side of it your fleet sits on — and unlike a fine, it applies to every port call for as long as the record stays where it is.
Argument Three: Cost, and Why It Is the Weakest
Most papers lead with cost savings and it is the argument the reader is most trained to discount. Understanding why makes it usable rather than counterproductive. Schedule a walkthrough and build the cost section from your own accounts rather than from anybody's percentage.
Why it gets discounted
Because a finance function has seen software savings claims before and knows they cannot be verified in advance or attributed afterwards. An imported percentage invites exactly one question, and the answer to it undermines everything else in the paper.
Why time savings fail
Hours recovered become money only if headcount falls or the time is visibly redeployed to work not currently being done. Neither is usually demonstrable, so a claimed cash saving from administrative time is discounted to nothing and damages the credibility of the harder numbers next to it.
What does work
Avoided events, priced from your own history. What your last detention cost, how many days of technical off-hire you recorded, what the last docking's change orders totalled, what you paid in expedited procurement. Every input traceable to your own accounts, and the fraction you claim is addressable stated as your own estimate rather than as a vendor's promise.
The cost section should be the shortest in the paper and the hardest to argue with. Present it after compliance and risk, keep every figure traceable to your own records, exclude efficiency savings explicitly and say why, and state the addressable fraction as a judgement you made. A short defensible number beats a large indefensible one in every approval meeting that has ever happened.
Argument Four: The One Nobody Makes
This is the newest of the four and the most likely to interest an owner, because it touches the cost of capital rather than the cost of operations. Start a free trial and check whether your lender has asked for anything of this kind yet.
The shift
Banks applying the Poseidon Principles increasingly expect decision-grade data and documented compliance controls, not just headline targets.
What that phrase means in practice
Decision-grade means data a third party would rely on for a lending decision — traceable, verifiable, consistent across vessels and time. Documented controls means being able to show the process that produced it rather than only the output.
Why it reaches the owner
Because it moves record quality out of operations and into the financing conversation, where the counterparty is a bank rather than an inspector and the consequence is terms rather than a deficiency. Compliance ratings increasingly affect access to green financing alongside charter competitiveness and port fee structures.
How to use it in a paper
One paragraph, near the front, framed as a question rather than a claim: what would we produce today if our lender asked for verifiable fleet compliance data across the last two years, and how long would it take. Owners answer that question themselves, and the answer does the work.
Matching the Argument to the Reader
The same evidence lands differently depending on who is holding it. Use this to decide what goes in the first half-page rather than what goes in the appendix. Book a walkthrough and identify which of these people actually decides in your structure.
Table 1: Which Argument for Which Reader
| Reader | What they are protecting | Lead with | Avoid |
|---|---|---|---|
| Owner or board | Capital allocation and asset value | Financing and compliance — dated obligations and lender expectations | Operational detail, which reads as a departmental request |
| Finance director | Integrity of the forecast | Avoided events priced from your own accounts, with sources named | Any percentage originating from a supplier |
| Technical director | A team already at capacity, and a previous decision | The named implementation owner and what they stop doing | Feature comparison, which sounds like criticism of the current system |
| Operations | Schedule reliability | Inspection targeting rates and off-hire exposure | Anything implying more administrative work for vessels |
| Designated person ashore | Demonstrable system effectiveness | Evidence quality, corrective action closure and audit readiness | Cost framing, which is not their accountability |
| Commercial | Charter access and vetting position | Vetting requirements and premium cargo access | Regulatory mechanics, which are somebody else's job |
| HSQE | Reporting culture and audit outcomes | Leading indicators and finding close-out with evidence | Efficiency claims, which sound like headcount reduction |
| The person who will run it | Their own time | Deployment duration and what implementation actually requires of them | Optimism about effort, which they will not believe |
The evidence for all four arguments comes from the same place: a record good enough to be shown to somebody outside your company.
Sentences That Work, and Sentences That Do Not
Approval papers turn on specific formulations more than most people expect. These are drawn from what tends to survive questioning. Start a free trial and produce the evidence that lets you write the left column honestly.
Table 2: Formulations, Compared
| Topic | What survives questioning | What does not | Why |
|---|---|---|---|
| The saving | Our last detention cost us a specific figure, from these records | Fleets typically save a large percentage | The first has a source; the second invites one question you cannot answer |
| The deadline | These obligations fall on these dates and we submit against them | Regulation is increasing and we need to prepare | A calendar is harder to defer than a trend |
| The prevention claim | This makes certain causes visible earlier; we assess the addressable share at this level | This will prevent detentions | Everyone knows the second is untrue, which contaminates the rest |
| Time savings | We exclude efficiency savings because we cannot show they convert to cash | This saves seventy percent of administrative time | Volunteering the exclusion buys credibility for what remains |
| Deferral | Twelve more months at our own historical event rate costs approximately this | We should act now | Deferral has to be given a price or it appears free |
| Ownership | This person owns it, for this many days, and stops doing this | The team will absorb it | Everyone present knows the second is not true |
| Evidence | We ran one vessel for sixty days and these are the observed results | The vendor projects these outcomes | Your own data outranks anybody's projection |
| Limits | Here is what this case does not claim | Silence on limitations | Whoever finds the first limit controls the discussion, and somebody will |
| The financing angle | What would we produce if a lender asked for two years of verifiable data | Improved data governance | A question the reader answers themselves beats a claim they have to accept |
2026 APPROVAL REALITY
Regulatory dates and mechanics vary by trade, flag and vessel, and several are subject to change. The 2026 deadlines cited reflect published guidance on FuelEU Maritime, EU ETS and UK ETS as reported during the year; applicability depends on your trading pattern, vessel size and the specific scheme, and some items remain subject to implementation guidance still being developed. Confirm your own position with your verifier, flag and legal advisers rather than relying on any summary including this one. The commercial consequence figures are industry analysis rather than audited data. Inspection targeting rates, penalty ranges and vetting access effects come from published commentary and vary considerably by region, segment and enforcement practice. This page covers the arguments; the process is separate. Who approves, whether the request is capital or operating expenditure, how to sequence a pilot and how to route the paper are set out in our business case guide, and the two are designed to be used together. Nothing here is financial, legal or accounting advice.
Frequently Asked Questions
Which argument should a budget paper lead with?
Compliance, in 2026, because the obligations carry dates rather than trends and several have already generated submissions this year — FuelEU vessel reports by 31 January, verification by 31 March, compliance data by 30 April, penalties from 30 June, EU ETS verified emissions by 31 March with seventy percent allowance surrender by 30 September, and UK ETS launching 1 July. A calendar is considerably harder to defer than a general case for improvement. Risk comes second because it has numbers everyone recognises, and cost comes third despite being what most papers open with, since it is the argument a finance function is most trained to discount.
Why is the cost argument the weakest?
Because it cannot be verified before purchase or attributed afterwards, and a finance function knows that. An imported supplier percentage invites the one question that undermines the whole paper. Time savings fare worse still — recovered hours become money only if headcount falls or the time is visibly redeployed, and where neither is demonstrable the claim is discounted to nothing while damaging the credibility of the harder numbers beside it. What works is avoided events priced from your own accounts, with the addressable fraction stated as your own judgement. Short and defensible beats large and arguable in every approval meeting.
What is the risk of not acting, stated properly?
A progression rather than an event, which is what makes it useful in a paper. Published analysis describes vessels with poor compliance records facing inspection on sixty to eighty percent of port calls against fifteen to twenty-five percent for high performers; charterers and oil majors implementing digital compliance requirements, with paper-based operators reported to lose access to premium cargoes; environmental penalties under EU ETS, FuelEU and regional schemes reported between a hundred and fifty thousand and over a million dollars annually per vessel; clubs raising premiums or declining cover for systematically non-compliant operators; and repeated deficiencies triggering enhanced flag state oversight. Each stage makes the next likelier, so deferral is not a neutral position.
What is the financing argument?
That record quality has moved into the lending conversation. Banks applying the Poseidon Principles increasingly expect decision-grade data and documented compliance controls rather than headline targets — decision-grade meaning data a third party would rely on for a lending decision, and documented controls meaning being able to show the process that produced it. Compliance ratings are also reported to affect access to green financing alongside charter competitiveness and port fee structures. The best way to use it is as a question rather than a claim: what would we produce today if our lender asked for two years of verifiable fleet compliance data, and how long would it take. Owners answer that themselves.
How has the documentation burden actually changed?
In kind as well as in volume. Six years ago the core reporting obligation was substantially annual fuel consumption; in 2026 it spans quarterly emissions reporting, an annual carbon intensity report, fuel changeover logs, scrubber operation logs and compliance plans, alongside the existing safety and certification regime. Industry commentary makes a sharper point than volume alone: 2026 demands exponentially more documentation but volume overwhelms quality assurance, and inspectors increasingly find quantity adequate and quality insufficient — forms completed with information that is inaccurate, inconsistent or clearly not reflecting actual operations. That is a capture problem rather than a paperwork problem.
Should the paper state what it is not claiming?
Yes, and it is the most reliable way to improve a case that is otherwise sound. Everyone in an approval meeting has seen a software paper that did not deliver, and a document claiming certainty is read against that memory. Whoever identifies the first limitation controls the framing, and somebody always does. Writing plainly that efficiency savings are excluded because they cannot be shown to convert to cash, that the model addresses only a stated share of past events, and that adoption is the principal risk, signals that the author was trying to be accurate rather than to win. Bounded claims also approve more easily, because they can be checked later.
1. Compliance
2. Risk
3. Financing
4. Cost
Reorder the Paper Before You Rewrite It
Most rejected budget papers contain the right material in the wrong order — cost first, where it is most easily discounted, and compliance buried on page three where a dated obligation loses its force. Lead with the calendar, follow with the progression that makes deferral expensive, add the financing question an owner will answer themselves, and put the cost case last, short, and sourced entirely from your own accounts. Then attach sixty days of observed results from one of your own vessels, which is the only evidence in the document that nobody can dispute.
