Vessel Maintenance Budget: How to Build It, Track It and Defend It

Every autumn the same ritual plays out in shipping companies: finance asks the technical department for next year's vessel maintenance budget, and receives a spreadsheet built in a hurry, usually last year's figures plus a flat percentage. Six months later the budget is overspent, nobody can say precisely where, and the arbitration happens under pressure: planned maintenance is deferred, orders are frozen, a survey is pushed back. Then the cycle repeats.

Yet a maintenance budget is not an accounting exercise. It is the financial expression of a technical strategy — what you deliberately choose to spend in order to avoid breakdowns, off-hire, class conditions and accidents. Built properly, it becomes the strongest instrument a superintendent or chief engineer has for being heard at board level. Built badly, it turns against its author at the first variance.

This article sets out a complete, applicable method: the structure of a technical OPEX line by line, three budgeting methods and where each one is valid, how to cost a planned maintenance system from job specifications and bills of materials, how to size a contingency provision, monthly tracking on committed / actual / budget, the cost lines that overrun most often, and finally the argument that lets you defend every line in front of a CFO. A fully worked illustrative example closes the case.

What a technical OPEX actually covers

The first cause of budget overrun is not parts inflation — it is entire cost categories forgotten at build time. A budget covering only "spares and labour" ignores roughly half the real technical spend of a vessel. Before costing anything, freeze a stable technical chart of accounts: reusable year on year, and comparable across the vessels of one fleet.

The nine lines of a vessel maintenance budget

The table below breaks the budget into nine lines with indicative allocation keys. These orders of magnitude reflect what is commonly seen on hard-working vessels in continuous service; they vary widely by segment — a superyacht, a passenger ferry and a harbour tug share neither cost structure nor operating profile. Treat them as a starting point and a sanity check, not as a truth.

Two remarks. First, "technical crew" is the most disputed line: some owners exclude it entirely from technical OPEX and book it under personnel costs, others allocate a flat share. The convention itself matters less than the fact that it is written down, stable over time and identical for every vessel in the fleet — otherwise inter-vessel benchmarking becomes fiction.

Second, drydocking. This is the line that does the most damage when it is not amortised. A major docking every five years, charged in full to the year it falls, produces one catastrophic year followed by four flattering ones and makes any form of steering impossible. The rule is simple: provision one fifth of the expected cost of the next drydocking every year, reassessed annually. That turns a shock into a running charge — and it protects you the day finance discovers the figure.

Three methods for building the budget

There are three serious ways to build a vessel maintenance budget. They are not mutually exclusive: they overlap, and best practice is to use two of them so each checks the other.

Method 1 — Corrected history

Start from the actuals of the last two or three financial years, strip out non-recurring events (a claim, a major breakdown, an exceptional docking), add known and expected events (a five-yearly survey, a major engine overhaul falling due this year), and apply a price escalation factor.

It is the fastest method and the most credible in front of a finance director, because it rests on real invoices. Its weakness is structural: it perpetuates past mistakes. If you have under-maintained for two years, corrected history enshrines that under-maintenance and locks in the next failure. It also assumes clean cost accounting, with spend allocated by vessel and by category — a condition many owners do not genuinely meet.

Use it when: the vessel has been in stable service for at least two years, the history is reliable and properly allocated, and the operating profile is not changing.

Method 2 — Costed planned maintenance system

Start from technical reality: the vessel's planned maintenance system. Cost each planned job (parts, consumables, internal hours, external hours), sum the occurrences that fall within the financial year, then add a corrective allowance calibrated on failure history.

This is the most accurate method and by far the most defensible, because every unit of currency is attached to a job, which is attached to an item of equipment, which is attached to a shipboard function. It is also the only one that lets you answer the dreaded "what happens if I cut you 15 %?" with something other than a shrug. Its limitation: it requires an up-to-date PMS and a structured equipment register. If your maintenance plan is incomplete, so is the budget derived from it.

Use it when: you have a structured CMMS and a properly described equipment base. This is the target method.

Method 3 — Fleet ratio

Apply a ratio observed on comparable units: annual maintenance cost per kilowatt of installed power, per metre of length overall, per running hour, or as a percentage of insured value. The insured-value percentage is the most widespread; on well-maintained working vessels, figures commonly fall somewhere between 2 and 5 % per year, with very large deviations depending on age and operating intensity. This method does not build a budget — it audits one, and exists to catch gross anomalies.

Use it when: you are budgeting a newly acquired vessel with no history, arbitrating between several units of a fleet, or running a quick sanity check on a budget already built.

Which method for which situation

Costing a PMS from job specifications and bills of materials

This is the technical core of the exercise, and the point at which a CMMS stops being a tracking tool and becomes a management tool. The idea is simple: if every preventive job is described by a job specification and a bill of materials, then the preventive budget is a sum, not an estimate.

From job specification to unit cost

A properly written job specification already carries most of the cost information. For each job, four components:

• Parts consumed, taken from the job's bill of materials: part numbers, quantities, last purchase price or negotiated catalogue price. This is the easiest component to make reliable, provided the item master is clean and part numbers are linked to equipment.
• Consumables and fluids: drain oil, flushing fluid, cleaning products, technical wipes, single-use gaskets. Individually trivial, collectively significant over a full year.
• Internal hours: estimated crew time, valued at an internal hourly rate. Many owners value them at zero on the grounds that the crew is paid anyway. That is an analytical error: without valuation you cannot demonstrate that outsourcing a job costs more, nor justify an additional technical rating on board.
• External hours: OEM service engineer attendance, lifting equipment hire, statutory inspection. These are the heaviest lines per occurrence and the easiest to forget when they only come round every two or three years.

From unit cost to annual budget

The second step is counting how many times each job falls within the budgeted year. For calendar-based jobs this is direct: a six-monthly job gives two occurrences. For jobs triggered by running-hour counters, you must first project the vessel's expected utilisation, then derive the due dates.

This is exactly where most budgets go wrong. A 12,000-hour overhaul on an engine running 3,000 hours a year falls every four years: budgeting it annually inflates the envelope artificially, never budgeting it guarantees the shock when it lands. Good practice applies the same amortisation logic used for drydocking: provision the corresponding fraction each year, and track that provision as a budget line in its own right.

Then add the corrective allowance. Preventive maintenance never covers everything — there will be failures. Calibrate this allowance on the corrective work orders of the last two years, adjusted for trend. A useful reference point: on a well-maintained vessel with a genuinely followed maintenance plan, corrective work commonly accounts for 25 to 40 % of intervention spend. Above 50 % the problem is no longer budgetary but organisational — a sign of maintenance still largely driven by breakdowns, a subject covered in our article on moving from corrective to condition-based maintenance.

Key takeaway — A defensible maintenance budget is built bottom-up: equipment, job, specification, bill of materials, unit cost, occurrences in the year. Every unit of currency must be traceable to a technical line and to a risk avoided. A top-down budget, obtained by applying a percentage to last year, will not survive three precise questions and will protect you from no cut whatsoever.

Contingency provision and acceptable variance

No technical budget lands exactly on target, and pretending otherwise destroys your credibility. A vessel is a complex system exposed to the sea, corrosion and fatigue: uncertainty is part of the model, so it should be budgeted explicitly rather than hidden as quiet padding spread across every line.

A contingency provision typically sits between 5 and 15 % of total technical budget. Where you set the dial depends on four factors: the age of the vessel, the quality of its maintenance history, the criticality of the operation (a ferry under a public service obligation cannot simply cancel sailings), and distance from logistics bases. A three-year-old vessel trading in coastal waters with a well-sized spares inventory justifies 5 %. A twenty-two-year-old vessel operating far from any technical base justifies 15 % — and you must be able to explain it in one sentence. That provision must remain a visible line, drawn on explicit and documented decision, not a cushion everyone dips into quietly.

As for acceptable year-end variance, a budget landing within plus or minus 5 % of target is a good budget. Between 5 and 10 %, the variance is normal but must be explained line by line. Beyond 10 % there is a methodological error, either in the build or in the tracking. And a systematically underspent budget is not good news: it almost always signals deferred preventive maintenance — technical debt that will be repaid later, with interest.

Monthly tracking: committed, actual, budget

A budget that is not tracked monthly is not a budget, it is a forgotten forecast. Tracking rests on three columns that must be kept strictly distinct, because confusing them is the single most widespread error in shipping companies.

The three columns

• Budget: the amount allocated to the line for the period. Frozen once approved, save for a formal revision.
• Committed: the value of orders placed, including those neither delivered nor invoiced. This is the most important column and the one most often missing. A large spares order placed in March and delivered in July is a certain cost from March onwards: ignoring it gives the illusion of a healthy budget until the summer, then a brutal surprise.
• Actual: the amount invoiced and posted. This is finance's view of the world, but it lags technical reality by two to three months.

The steering rule fits in one sentence: manage on committed, report on actual. A technical department tracking only actuals discovers its overruns a quarter late, when no room for manoeuvre is left. That is precisely the function of a CMMS purchasing module: make the commitment visible when it is made, not when the invoice arrives.

The landing curve

Every month you should produce a year-end projection, not merely a statement of position. It is obtained by adding actuals to date, committed-but-not-yet-invoiced, and estimated remaining commitments over the months left. That last term is not a simple pro rata: technical spend is not linear. A docking in October, a class survey in March and a major overhaul in June create very visible steps in the curve. The projection must therefore rest on the real schedule of outstanding jobs — something only an up-to-date CMMS can produce without three days of manual work.

A well-built landing curve reads at a glance: the theoretical budget line, the cumulative actual line, and the projection. Three lines, one chart, and a conversation with finance that lasts ten minutes instead of two hours. That is exactly the purpose of a forecasting module: projecting the workload and cost of planned work over the coming months rather than discovering it.

Drift alerts

Define thresholds before the year starts, not when the problem appears. A simple and proven scheme:

• Green: projected variance below 5 % of annual budget. Normal tracking, noted in the monthly review.
• Amber: variance between 5 and 10 %. Written analysis mandatory within the month, identification of the responsible line, corrective plan proposed.
• Red: variance above 10 %, or more than 30 % overrun on a single line. Immediate escalation to management, with two or three costed scenarios and their respective technical consequences.

The lines that overrun most often

Overruns are not evenly distributed. Four mechanisms account for most of the drift, and they are linked: the first usually triggers the other three.

Emergency purchasing

A part ordered under emergency conditions structurally costs more than one ordered in advance: loss of the negotiated price, recourse to whichever supplier is available rather than the best offer, expediting charges, no possibility of consolidating the order. On technical parts, a factor of 1.5 to 3 against the negotiated catalogue price is common.

The root cause is almost never the unforeseen event: it is an inventory badly sized or a reorder point badly set. Structured MRO inventory management, with reorder points calculated from real supplier lead times and equipment criticality, removes a large share of these emergency purchases. The carrying cost of a critical spares stock is almost always lower than the cumulative premium on the urgent orders it prevents.

Air freight of spares

This is the direct corollary of the previous point, and the most violent line in percentage terms. A modest part flown to a remote port with express customs clearance can cost more in transport than in merchandise value. Across a fleet, a few dozen urgent shipments a year add up to a figure that would have funded several complete critical spares inventories. Air freight can never be eliminated entirely, but it must be tracked as an indicator — urgent shipments per vessel per quarter — rather than buried in general overheads.

Off-hire and downtime

This is the invisible cost, the one that never appears in the technical budget although it frequently outweighs the repair itself. A day of unplanned downtime means lost revenue, possibly contractual penalties, a crew paid alongside, and sometimes commercial reputation damage.

The argument is decisive in front of a CFO, provided it is quantified. If a day of unplanned stoppage costs the company X, a preventive line at X/3 that reduces the probability of stoppage is an investment, not a charge. This is the most effective reasoning available for defending a budget, and it requires obtaining the daily downtime cost from operations or the commercial department — a figure the technical department almost never has to hand.

Deferred preventive maintenance

This is the most insidious drift, because in the short term it produces the exact opposite of what it costs: it improves the current year's budget. Deferring preventive jobs at year end to hit the target delivers flattering apparent performance and transfers the workload — increased — to the following year.

The real cost of deferral is rarely neutral. An overhaul postponed by six months generates additional wear, sometimes damage, and converts a planned intervention into an unplanned one at the wrong time and in the wrong place. The only effective countermeasure is to track a PMS completion rate alongside budget consumption. A budget consumed at 92 % with 95 % PMS completion is a success; a budget consumed at 88 % with 70 % PMS completion is a failure dressed up as performance. ISM Code compliance also requires demonstrating that planned maintenance is actually carried out: systematic deferral is not merely expensive, it is hard to defend at audit.

Defending your budget in front of finance

A technical department and a finance department do not speak the same language. The first talks about equipment, intervals and criticality; the second talks about cash, variance and return on investment. Defending a budget consists almost entirely of performing that translation.

Tie every line to a risk avoided

The principle is easy to state and demanding to apply: no budget line should be presented as a technical cost, but as cover against an identified risk. The most effective format has four columns.

This table changes the nature of the discussion completely. Without it, the exchange is about "can you make a 10 % effort?". With it, the exchange is about "which risk are you prepared to carry?". The second question is far harder for management to brush aside, and it moves responsibility for the trade-off to where it belongs.

Prepare the cut scenarios before you are asked

Walk into the meeting with three scenarios already built: the nominal budget, a minus 10 % scenario and a minus 20 % scenario, each with the precise list of what disappears and the expected consequences. The effect is twofold: you demonstrate detailed command of your budget, and you avoid the across-the-board cut decided without you, which always lands in the wrong place.

In the minus 20 % scenario, show regulatory deadlines explicitly as non-compressible. A class survey is not negotiable, and putting that in writing protects everyone. Certificate tracking supplies the incontestable calendar that makes the argument airtight. Finally, avoid two losing postures: padding deliberately to absorb the expected cut, which works once and then destroys the credibility of your figures, and hiding behind technical language by answering "it is necessary for safety" without quantifying the risk avoided.

A fully worked example (illustrative)

The example below is entirely illustrative. It comes from no real company and is not a market benchmark: its sole purpose is to show the sequence of calculations and how to read the result. Real figures depend on age, segment, operating profile and trading area.

Working assumption: a 32-metre workboat, fifteen years old, two main engines, roughly 2,800 running hours a year, operated from a European port base, next major drydocking estimated at 250,000 in four years' time. Amounts are shown in generic currency units.

Fleet-ratio cross-check: if the insured value of the vessel is around 7 million, the budget represents roughly 4.5 % of that value. On a fifteen-year-old vessel in intensive service, the order of magnitude is coherent. Had it come out at 1.5 %, the missing line would have needed hunting down — most often the un-amortised drydocking or forgotten major running-hour milestones.

Year-end reading, still illustrative: actual 318,900, a variance of +2.0 %. Provision drawn at 82 %, including one circulating pump failure. PMS completion rate: 94 %. That triptych — small budget variance, provision used but not exceeded, preventive maintenance genuinely carried out — is the profile of a controlled budget. It is infinitely preferable to a budget held at 100 % with 70 % PMS completion.

What forecasting and purchasing modules change in practice

Everything above can be done on a spreadsheet. That is how most companies do it. The problem is not feasibility, it is the cost of keeping it current: a spreadsheet budget is right on the day it is built and wrong three months later, because jobs shift, prices move, orders accumulate and nobody has time to re-key it all.

The Forecast module from Smart Sailors targets exactly this point. It projects upcoming maintenance due dates from the real plan, calendar intervals and counter readings, and shows where the workload falls in the months ahead. That is the raw material of the landing curve, produced automatically instead of being rebuilt by hand every month.

The Purchasing module supplies the missing column: committed spend. As soon as a requisition is approved and converted into an order, the amount becomes visible in budget tracking — before delivery and long before the invoice. It is precisely this gap between commitment and invoicing that explains most overruns discovered too late.

Both modules rest on the other building blocks: the equipment register that carries the bills of materials, the inventory module that supplies real consumption values, and the dashboard that aggregates indicators at fleet level. The mobile application works offline, which ensures consumption and time spent are recorded on board at the moment of the job rather than reconstructed from memory at the next port call — an essential condition for unit costs to be realistic the following year. Details of the twelve modules and the pricing are available online.

FAQ

What percentage of vessel value should be spent on maintenance?

There is no universal rule. On well-maintained working vessels, annual maintenance budgets commonly fall between 2 and 5 % of insured value, with wide deviations depending on age, operating intensity and segment. Use this ratio as a sanity check on a bottom-up budget, never as a build method. A budget calculated as a percentage is attached to no real job and will not survive serious scrutiny.

Should drydocking be included in the annual maintenance budget?

Yes, but amortised. Charging a major docking in full to the year it falls makes steering impossible and produces a budget crisis every four or five years. Sound practice is to provision a fraction of the estimated cost of the next docking each year, reassess that estimate annually against the class calendar and the actual condition of the vessel, and track the provision as a budget line in its own right.

How do you budget a newly acquired vessel with no history?

Combine two approaches. First, cost the maker's maintenance schedule or the plan reconstructed during the pre-purchase survey: that is your technical base. Then cross-check the result against a fleet ratio drawn from units comparable in age and use. Increase the contingency provision in the first year — 12 to 15 % is reasonable — because you know neither the vessel's weak points nor the quality of its past upkeep. From year two, real history takes over.

What is the difference between committed and actual, and why does it matter so much?

Committed covers orders placed, even if not delivered or invoiced. Actual covers invoices posted. Between the two there are often two to three months on technical parts, more on yard work. Managing on actuals alone is like driving by the mirror: you find the overrun once it is already spent and irreversible. Tracking committed spend is the only way to keep room for manoeuvre.

How should you answer a demand for a 15 % budget cut?

Never respond with a blanket refusal or a blanket acceptance. Present the precise list of what would disappear, line by line, with the associated risk and its likely consequence. Isolate what is non-compressible — class surveys, statutory certificates, safety — and explicitly propose the remaining trade-offs. The decision belongs to management; your role is to make it informed and documented. A written trade-off protects you as much as it protects the company.

Is a systematically underspent budget a good performance?

Rarely. Regular underspend almost always signals deferred preventive maintenance, a maintenance plan oversized against reality, or jobs recorded as done without being done. Always read budget consumption together with PMS completion rate: it is the only pair of indicators that distinguishes a genuine saving from technical debt in the making.

Conclusion

A vessel maintenance budget is neither an accounting constraint nor a drafting exercise. It is the quantified expression of your technical strategy, and the only document that lets you talk to finance on equal terms. Its strength rests on three pillars: a complete and stable cost structure, a bottom-up build from the real maintenance plan, and monthly tracking that separates committed from actual.

The rest is discipline: a contingency provision governed rather than raided, alert thresholds defined before the year rather than during it, a PMS completion rate tracked alongside budget consumption, and every line tied to a risk avoided.

If you would like to see how the Forecast, Purchasing, Maintenance and Inventory modules fit together to deliver this kind of control across your fleet, book a demonstration or trial the platform for 30 days. Our team, made up of seafarers, can start from your existing maintenance plan and show you what your costed budget would look like.