Superyacht Maintenance Software: Managing Upkeep, Compliance and Crew Turnover

A 40-metre yacht packs into a very tight envelope almost everything you would find on a merchant ship: main propulsion, generators, hydraulics, water treatment, air conditioning, navigation electronics, stabilisers and tenders. It then adds what no cargo ship has to worry about: a teak deck that must stay flawless, a lift, a restaurant-grade galley, and an owner who will not accept a breakdown ruining a week booked twelve months in advance.

That combination is what makes yacht maintenance so hard to run on spreadsheets and ring binders. Maintenance windows are short and dictated by the owner's or the charter calendar. Crew turnover is fast: a chief engineer who signs off usually takes most of the vessel's technical memory with him. And once the yacht trades commercially, a regulatory layer lands on top — REG Yacht Code, ISM, ISPS, MLC depending on tonnage and passenger numbers — with audits that demand evidence, not recollection.

Properly deployed, superyacht maintenance software answers all three problems: it turns upkeep into a structured, dated plan; it keeps technical history independent of individuals; and it produces, at no extra effort, the evidence the flag State, the classification society and the ISM auditor expect. This article sets out how to build that system, from the equipment hierarchy through to the budget report sent to the owner or management company.

Why yacht maintenance is unlike any other

Cosmetic standards carry the same weight as functional ones

On a merchant ship, a weeping union is a monitoring point. On a yacht, it is a run mark down a lacquered bulwark, and therefore unacceptable. The maintenance scope widens to varnish, teak, polished stainless, lacquer and upholstery. None of it is safety-related, yet it consumes considerable labour and follows its own frequency logic — often weekly, sometimes daily.

A maintenance module for yachting therefore has to absorb two very different families of work: technical maintenance, driven by running hours and OEM recommendations, and presentation maintenance, driven by the calendar and assigned to deck rather than engineering. Mixing them into one unfiltered list produces an unreadable plan; splitting them across two tools produces two versions of the truth. The workable answer is one system with distinct views per department.

Seasonality compresses every intervention window

Most yachts run a sharply defined cycle: Mediterranean season from May to September, transatlantic crossing, Caribbean season from December to March, then yard period in spring. In between, only a few weeks to absorb the heavy work. Anything unplanned therefore becomes an expensive emergency, squeezed into an already saturated slot or — worse — carried out with the owner on board.

The role of a planned maintenance system is not merely to flag that a service is due. It is to project due dates onto the forward operating calendar so that jobs can be grouped into the windows that actually exist. That is what a workload forecast view delivers: seeing six months ahead which tasks will fall mid-charter, and moving them into the yard period by agreement with the chief engineer.

Crew turnover erases technical memory

This is the industry's most expensive characteristic. Tours of duty on yachts are frequently shorter than in commercial shipping, with seasonal rotations and reinforced crews in high season. When a chief engineer leaves after two seasons, he takes with him information that was never written down: which generator has a temperamental injector, which belt part number was substituted last year, which supplier in Antibes delivers within 24 hours, which valve is mislabelled on the as-built drawing.

Without a structured system, the relief rebuilds that knowledge over three to six months and pays for every lesson twice. With a complete work history attached to each item of equipment, the same relief is effective within weeks. In yachting, that is the strongest economic argument for a CMMS — well ahead of compliance.

Equipment diversity, competing stakeholders, confidentiality

A 45-metre yacht may carry several hundred registered items from dozens of manufacturers, with documentation in English, German or Italian, sometimes available only as a scanned PDF. There is no fleet standard: each vessel is effectively a prototype. Generic maintenance plans are therefore useless, and an equipment register has to be built specifically for the vessel.

Three stakeholders then want different things: the captain wants an available vessel and a crew not drowning in paperwork; the manager — management company or family office — wants budget control and supporting documents; the owner essentially wants nothing to break during his stay. One system serves all three provided each gets the right level of output: operational on board, analytical ashore, summary for the owner. Finally, information about vessel movements and owner identity has commercial value, so granular access rights are a selection criterion in their own right, not a nice-to-have.

Private or commercial use: two different regulatory frameworks

The strictly private yacht

A yacht in private use, with no charter activity, falls outside most international conventions applicable to merchant ships. Its obligations flow from flag State law, from classification society requirements where the vessel is classed, and above all from the terms of its hull and machinery insurance. That last point is routinely underestimated: after a major casualty, the ability to demonstrate that manufacturer-recommended maintenance was actually carried out, at the prescribed intervals, weighs heavily on how the claim is handled. A time-stamped history has no statutory value here, but it has considerable evidential value.

The commercial yacht and the REG Yacht Code

As soon as a yacht is chartered, it changes category. For vessels registered within the Red Ensign Group (United Kingdom, Isle of Man, Jersey, Guernsey, Gibraltar, Bermuda, Cayman Islands, British Virgin Islands), the reference framework is the REG Yacht Code, issued as a consolidated edition in January 2019 and updated since. It brought together two long-standing texts:

• Part A — successor to the Large Yacht Code (LY3), applying to yachts in commercial use of 24 metres and above carrying no more than 12 passengers. It covers structure, stability, machinery, fire safety, life-saving appliances and manning.
• Part B — successor to the Passenger Yacht Code (PYC), applying to yachts carrying more than 12 passengers, generally up to 36. Crossing that threshold moves the vessel into the passenger ship category, with markedly heavier requirements for subdivision, evacuation and fire safety.

Other yachting flags — Malta, Marshall Islands, Luxembourg, France — publish their own commercial yacht codes, broadly aligned with the same logic. The practical rule is unchanged: always check the text of your flag State, because thresholds and equivalences vary at the margins.

ISM, ISPS, MLC: the thresholds that change life on board

• ISM Code (SOLAS chapter IX): most flag States apply it to commercially operated yachts of 500 GT and above. The vessel then needs a documented safety management system, a company holding a Document of Compliance, a Safety Management Certificate on board and a Designated Person Ashore. Below that threshold, several flags impose a lighter regime often called "Mini-ISM". We cover the relationship between the ISM Code and CMMS in a dedicated article.
• ISPS Code (SOLAS chapter XI-2): it applies notably to ships of 500 GT and above on international voyages, which in practice captures large commercial yachts. It requires a ship security plan, a Ship Security Officer and an International Ship Security Certificate.
• MLC 2006: the Maritime Labour Convention applies to commercially operated yachts, with certification generally required above 500 GT on international voyages. It governs seafarer employment agreements, hours of rest, repatriation and living conditions.

For maintenance, the consequence is direct. The ISM Code requires the company to establish procedures ensuring the ship and its equipment are maintained in conformity with applicable rules and any additional requirements it sets, that inspections are held at appropriate intervals, that non-conformities are reported with their possible cause, that corrective action is taken and that records are kept. In plain terms: a planned, recorded maintenance programme with documented defect handling. A CMMS is not a statutory requirement, but it is the cheapest way to satisfy that expectation.

Key takeaway — The regulatory trigger is not the size of the yacht but its use. A private 50-metre may carry fewer statutory obligations than a 30-metre in charter. Three thresholds drive almost everything: 24 metres (entry into REG Yacht Code Part A for commercial use), 12 passengers (shift to Part B / Passenger Yacht Code) and 500 GT (ISM, ISPS, MLC certification depending on flag). Place your vessel on those three axes before sizing your documentary system.

Structuring maintenance: hierarchy, job procedures, checklists

Build by system, not as a flat list

The most common first-deployment mistake is entering several hundred items as a flat list. Six months later nobody can find anything and the system is abandoned. The structure that survives is hierarchical, on three levels: system → sub-system → equipment.

A proven breakdown for a yacht: Propulsion (main engines, shaft lines, propellers, gearboxes); Electrical generation (generators, switchboards, converters, battery banks, shore power); Fluids and hull (fuel, lube oil, sea water, bilges, steering gear, bow thrusters); Hotel services (air conditioning, watermaker, black and grey water, laundry, galley, lift); Deck machinery (windlasses, davits, passerelle, swim platform, stabilisers); Navigation and communications (radars, ECDIS, autopilot, GMDSS, VSAT); Safety (fire detection and fixed firefighting, liferafts, lifejackets, EPIRB, SART); Tenders and toys (tenders, jet skis, dive compressor).

Each item then carries make, model, serial number, commissioning date, physical location, criticality, documentation and associated counters. That level of detail is what makes an equipment register usable rather than decorative.

Standardise job procedures

A job procedure is the standard method for a recurring task: what to do, in what order, with which tools, which parts, which safety precautions and what estimated duration. Standardising delivers three immediate effects: the job is done the same way whoever performs it, the parts requirement is known in advance and therefore orderable, and the relief has a written instruction rather than a verbal handover.

A useful procedure always includes the trigger (running hours, calendar interval or observed condition), the consumables list with exact part numbers, the safety points — electrical isolation, valve lock-out, PPE — and the readings to record. That last item matters: capturing exhaust temperature per cylinder or differential pressure across a filter gradually converts preventive maintenance into condition-based maintenance. Our four-step method for building a preventive maintenance plan sets out that process.

Seasonal recommissioning and lay-up checklists

These are the two most profitable documents on board. Recommissioning covers waking the vessel up: refilling systems, purging and testing generators, levels and anodes, testing bilge pumps and alarms, checking life-saving appliances and their expiry dates, testing fire detection and fixed extinguishing, starting air conditioning and watermaker, alongside then sea trials, tender checks.

The lay-up checklist covers the reverse: protecting fresh water and sea water systems, engine preservation, battery trickle charging, ventilation and dehumidification of interior spaces, textile storage, membrane rinsing and preservation, electrical isolation. Every line must generate a time-stamped record with the name of the person who completed it. Generated automatically each year, these two sequences turn the spring campaign into a repeatable process.

Engine hours, generators and counters

On a yacht the gap between calendar time and running time is enormous. A main engine may run only a few hundred hours a year while a generator accumulates several thousand, because it feeds the air conditioning alongside. Triggering everything on the calendar therefore over-maintains propulsion and under-maintains electrical generation.

Good practice is to record counters daily — engine and generator hours, fresh water production, consumption — and let the system raise tasks on threshold. A counters module fed by the engineering watch also gives an accurate read on consumption per generator, useful when arbitrating between shore power and on-board generation.

Typical maintenance plan by system across one season

A reference framework for a 30 to 50-metre yacht on a Mediterranean cycle. Intervals are indicative and must always be checked against manufacturers' manuals and flag State and class requirements.

This skeleton is only worth something once translated into dated jobs, assigned to a person and linked to a specific item of equipment. That is precisely what a CMMS does: convert a table into a stream of work orders whose completion rate can be measured.

Bringing a new chief engineer up to speed in weeks

When a chief engineer joins a yacht he does not know, he needs four things: what is on board, what has recently been done, what is outstanding, and where the spares are. A properly maintained system answers all four in one sitting. The equipment register defines the scope. The history reveals the vessel's real behaviour — which item has been reworked three times in two years, which failure recurs after every ocean crossing. The open job list defines urgency. Stock levels define room for manoeuvre.

None of this is automatic: it assumes previous entries carried useful content. A line reading "repaired" transmits nothing. A line reading "leak at port sea water pump discharge union, O-ring replaced with part number X, torque reset to Y, recheck in 100 hours" transmits competence. Data entry quality is the real success factor of a yachting deployment. An effective handover then fits into four weeks:

• Days 1-3 — walk the vessel with the equipment list open on mobile, verify tag numbers, correct discrepancies on the spot.
• Days 4-10 — read twelve months of history system by system, identify the three items consuming the most labour.
• Week 3 — joint physical inventory of critical spares and update of reorder levels.
• Week 4 — review the six-month forward plan with the captain, decide which jobs move to the yard period, review certificates falling due.

One final point, and a decisive one: OEM manuals, wiring diagrams, system drawings and contractor reports must be attached directly to the relevant equipment, not dropped into a shared folder whose logic depends on whoever created it. If an engineer has to ask someone where a document is, the documentary structure has failed.

Spares on board and procurement in port

Space on a yacht is contested between guest comfort and technical needs, so stocking "just in case" is impossible. The method is to rank parts on two axes: the consequence of unavailability (voyage stopped, guest comfort degraded, mere inconvenience) and the real lead time in the cruising areas. Only high-consequence, long-lead items justify shipboard stock: injectors, a spare turbocharger, watermaker membranes, belts and pump impellers, critical circuit boards, hydraulic hoses in common lengths.

A spare parts module with reorder levels and precise locations avoids yachting's twin failure modes: running out of a 30-euro part that stops a cruise, and accumulating obsolete references in forgotten lockers. Our article on MRO stock management details the classification method.

Yacht procurement has one distinctive feature: the vessel moves. An order placed in Palma may need to be delivered in Bonifacio four days later. Every order must therefore be tied not only to a supplier but to an expected delivery place and date. The role of a purchasing module is to preserve the link between the technical need, the order, the supplier and the goods received. Finally, every part issued from stock must be charged to the equipment it was fitted to: that discipline costs seconds and delivers both a true cost per item and direct evidence for the auditor or the underwriter.

Budget, reporting and owner accountability

A yacht's annual operating budget commonly represents a significant percentage of its value, and maintenance and works are among the most volatile lines within it. Managing that budget invoice by invoice tells you nothing useful. Managing it by system exposes drift immediately: when air conditioning consumes three times its forecast budget across two consecutive seasons, the question is no longer whether to pay the invoice but whether to replace the plant.

A CMMS that links labour, parts and contractor services to equipment produces that view with no extra work. A dashboard then aggregates by system, by period and by vessel for fleets under a single management company — the main lever described in our article on reducing vessel maintenance costs.

The monthly report management expects fits on one page and answers five questions: which jobs were planned and which were completed; which defects were raised and where their treatment stands; what has been spent against budget; which certificates fall due within 90 days; which points need an owner decision. Producing that by hand takes half a day a month; extracting it from a system fed continuously takes minutes. The same logic applies to the yard period: a refit work list should build all year through deferred defects and survey observations. Flagging a defect as "for yard period" builds that list automatically, with history and photographs — a decisive advantage when negotiating shipyard quotations.

Offline mobile: an adoption requirement, not a luxury

Network coverage on board is unpredictable: remote anchorage, steel-enclosed engine room, ocean passage. If the tool demands a permanent connection, the crew reverts to paper and duplicate entry kills the project within weeks. An offline-capable mobile application, syncing automatically once connectivity returns, allows work to be recorded where it is done. Three uses justify that capability on their own: taking counter readings during the watch, photographing a defect at the moment of discovery, and signing off a safety checklist during rounds. In all three, the delay between action and record is the main source of lost information.

Compliance: ship and crew certificates

A commercial yacht above 500 GT may carry around twenty statutory and class certificates, each with an issue date, an intermediate survey window and an expiry date: safety construction and safety equipment, load line, oil pollution prevention, sewage pollution prevention, air pollution prevention, anti-fouling systems, Safety Management Certificate, International Ship Security Certificate, Maritime Labour Certificate, radio licence, tonnage certificate.

Crew documents add another layer: STCW certificates of competency and revalidations, medical certificates, basic safety training, specialist certificates (GMDSS, advanced firefighting, survival craft and rescue boats) and flag State endorsements. On a high-turnover yacht, the probability that an individual certificate expires mid-season is high, and an expiry discovered the day before a charter is an immediate operational problem.

The answer is two registers: a ship certificate register with advance alerts at 90, 60 and 30 days, and a crew certificate register linked to the rotation plan, so that before each crew change you can confirm the complement still meets the Minimum Safe Manning Document. For yachts carrying passengers, passenger lists and their transmission to port authorities follow IMO FAL Form 6.

Rolling out a CMMS without breaking the season

The best moment to start is lay-up, when the crew has time and the vessel is accessible. Six simple rules:

• Narrow scope first. Start with machinery and safety; deck and interior follow.
• Survey on site. Photograph nameplates item by item rather than copying an obsolete shipyard list.
• Counters before tasks. Daily hour readings from day one: that is the data that will trigger everything else.
• Twenty procedures, not two hundred. An over-ambitious plan at launch produces a poor completion rate and discredits the tool.
• One data owner on board. The chief engineer or chief officer, with a monthly review with the shore superintendent.
• Three indicators in year one. Preventive completion rate, defects open more than 30 days, stock-outs that delayed a job.

FAQ

Does a private yacht really need maintenance software?

No regulation imposes it on a strictly private yacht. The value lies elsewhere: preserving asset value, holding a complete history at resale, demonstrating to underwriters that recommended servicing was carried out, and above all limiting failures during the owner's use. On 24 to 40-metre vessels with small crews, the main gain remains continuity of technical memory between successive chief engineers.

When does the ISM Code apply to a yacht?

The ISM Code concerns commercially operated yachts; most flag States apply it from 500 GT, and several impose a lighter "Mini-ISM" arrangement below that threshold. A strictly private yacht is not subject to it. Because the detail varies with the flag State and the number of passengers carried, checking the applicable text with the flag Administration and the classification society remains essential.

What is the difference between REG Yacht Code Part A and Part B?

Part A, derived from the Large Yacht Code (LY3), applies to commercial yachts of 24 metres and above carrying no more than 12 passengers. Part B, derived from the Passenger Yacht Code, applies above 12 passengers, generally up to 36. Crossing that threshold brings the yacht into the passenger ship category, with reinforced requirements for subdivision, evacuation and fire safety, and a material impact on both design and operating cost.

How do you manage maintenance when the crew changes every season?

By making information independent of individuals: a complete equipment register with documentation attached, a work history written with genuine technical detail, written procedures for recurring jobs, and an accurate spares inventory with locations. A structured four-week handover then lets a relief become self-sufficient far faster than a 48-hour verbal takeover allows.

Does the application work without a connection at sea?

Yes. The Smart Sailors mobile application is designed to work offline: consulting equipment and its documentation, recording jobs, taking counter readings and photographing defects all remain possible in the engine room or offshore. Synchronisation happens automatically as soon as a link is available, with no action from the crew.

How long does it take to deploy a CMMS on a yacht?

On a 30 to 50-metre vessel, allow two to four weeks for the equipment survey and documentation loading, then a full season to stabilise procedures and intervals. Starting during lay-up is considerably more comfortable: the crew has the time needed for initial data entry and the vessel is physically accessible.

Conclusion

Yacht maintenance is not a miniature version of merchant ship maintenance. It is a different exercise, where availability is absolute, intervention windows are narrow, technical memory is volatile and finish quality is non-negotiable. Structuring the work around a clear hierarchy, standardised procedures, counters read daily and a genuinely populated history delivers three measurable benefits: fewer failures during owner use, far faster crew handovers, and a compliance file that is ready on audit day rather than reconstructed the night before.

Smart Sailors is maritime maintenance software built by seafarers, deployed on more than 400 vessels, with an offline mobile application and twelve modules covering maintenance, equipment, spares, purchasing, certificates and crew. Review our pricing or book a demonstration tailored to your yacht. The trial is free for 30 days and our team supports the migration of your existing data.