A yacht can leave the yard with a good drawing package and still become badly documented over time. Equipment is replaced, routes change, software is updated and temporary repairs become permanent. If those changes are not reflected in the vessel's technical records, the result is usually confusion, wasted time and extra cost when somebody later has to maintain, fault-find or modify the system.
The original documentation is rarely the problem. The problem is what happens to it during the years that follow.
A yacht is constantly being changed. Equipment is replaced, cable and pipe routes are altered, control software is revised and temporary repairs sometimes remain in service far longer than expected. None of that is unusual. The problem starts when the physical or software change is completed but the associated drawings, schedules and configuration records are left behind.
In practice, documentation is also one of the easier parts of a job to remove when a budget is being squeezed. It can look like an administrative saving to someone who does not have to maintain the system afterwards. From an engineering point of view, however, the documentation update is part of the work. Leaving it out simply moves the cost into the future, usually to the point where reliable information is needed most.
A mismatch between the yacht and its records may sit unnoticed for years. It becomes obvious when something fails, a modification is planned or a refit team has to work out what is actually installed before it can move forward.
The problem shows up when the documents are needed
An outdated drawing does not necessarily cause a failure on its own. More often, it turns a straightforward job into an investigation.
A contractor may price work against the available drawings and then find, once the yacht is opened, that the installed route, equipment or available capacity is different. Before any new work can start, somebody has to trace the existing system, establish what is live, decide what can remain and work out whether the proposed design still makes sense. That takes engineering time and can hold up other trades that are waiting for access or an answer.
ONEXP described this during a 2025 assessment of an 86-metre yacht, where the installed systems no longer fully matched the available documentation. Its engineers found mixed generations of network hardware, undocumented AV equipment and accumulated control-system changes, so the first task was to establish the vessel's actual configuration. 4
OceanWeb reported a similar issue during an earlier network upgrade on a 56-metre Perini Navi, where much of the legacy cabling had little useful documentation available. 5
The direct cost may be extra labour, but on a large refit the knock-on effects can be more significant: repeated strip-out, contractor standby time, additional materials, delayed access and rework after finished areas have already been closed.
This is not an AV/IT problem
The examples above happen to come from AV/IT, but the same issue applies throughout the vessel. Electrical distribution, machinery, hydraulics, HVAC, piping, navigation equipment, automation and safety systems can all end up with technical records that no longer describe the installation accurately. A single drawing can also tell only part of the story; for example, an electrical schematic may still be broadly correct while breaker settings or protection parameters have changed, and a control drawing can show the right hardware while the software running on it is several revisions ahead of the copy held onboard.
There are also cases where keeping the documentation current is more than good engineering practice. The IMO International Safety Management Code requires companies within its scope to control documents and data relevant to the safety management system, make valid documents available and retain maintenance records. 1
Class-related modifications may also require revised drawings or technical information to be submitted for approval. DNV treats alterations as projects where documentation can form part of the approval and survey process, and its guidance for modifications to installed ballast-water treatment systems gives a practical example by calling for revised technical documentation, including an updated P&ID where applicable. 2 3
The exact requirement will depend on the yacht, flag, class and system involved, but the engineering principle is the same: when an approved or safety-relevant installation changes, the controlled information describing it needs to follow the final installation.
Drawings are only part of the technical record
On a modern yacht, some of the most important information cannot be captured properly on a conventional drawing.
A network diagram may show the switches and physical connections but still leave out the VLAN design, switch configurations, firewall policies or addressing in use. A PLC schematic can show the I/O and field wiring without identifying the program revision actually running in the controller. The same applies to HMIs, monitoring systems, lighting control, power-management systems and many other programmable platforms.
For those systems, a useful technical library needs to include the configuration information required to recover or reproduce the working system. Depending on the equipment, this may include current configuration backups, software and firmware versions, controller program’s, licence information, calibration data and other system-specific settings.
This becomes particularly important when the original contractor is no longer available. A drawing may help an engineer understand the architecture, but without the correct configuration backup it may still be impossible to restore the equipment to the state it was in before a failure.
Hidden infrastructure deserves particular attention
Cable schedules and route information are easy to neglect because most of the installation disappears from view once the yacht is complete.
A cable may pass through technical voids, deckheads and several structural divisions before reaching its destination. On larger vessels, many of those routes also pass through certified fire-rated or watertight cable-transit systems such as Roxtec. Adding or removing cables can mean opening those transits, working through an already crowded frame and rebuilding the seal correctly afterwards.
That work takes time and should be carried out by someone competent with the particular transit system. Roxtec provides installer training and supervision specifically because correct installation is important to the fire, ingress and watertight performance of the penetration, while poor installation can create leakage, rework and delay. 6
Accurate cable schedules and route information therefore have a practical value beyond simply knowing where a cable starts and finishes. During a refit they can help establish whether an existing route has spare capacity, which penetrations will need to be opened and whether the work is likely to interfere with other trades before the yacht is stripped apart.
Refit close-out is where this often goes wrong
The end of a refit is usually the worst time to start thinking about documentation. It is also the point where final drawings, configuration backups and commissioning records are most likely to be pushed aside.
By then the yacht may be close to sailing, contractors are clearing defects and the interior is being signed off. Commissioning is often still underway, and a departure date can become fixed for reasons that are not always visible to the technical team.
Commissioning, in the proper sense, is more than turning equipment on and checking that it responds. It is the process of proving that the finished installation works as intended, including its interfaces, alarms, failure behaviour and recovery where those functions are relevant. Defects should be recorded, corrected and retested, and the final settings and software should be captured before the system is accepted.
In practice, that process is sometimes compressed or never completed properly because the yacht has to leave. The vessel then goes to sea with open punch-list items, unanswered questions and documentation that reflects an earlier stage of the project rather than the installation that actually sailed.
That is a poor point at which to reconstruct the records later - in my personal experience, when wrapping up prematurely, the commissioning that should be done, never happens, as new problems arise, the old get pushed down the stack and forgotton. Also, the contractors who made the changes may have left, panels are closed and the yacht is back in operation. Information that could have been captured in minutes during the job can take hours to rediscover afterwards.
MB92 has also highlighted the growing importance of reliable data and interoperability as yacht systems become more complex and refits combine newer equipment with legacy installations. 7
Making document updates part of the job
The most effective approach is to include documentation in the scope from the beginning rather than asking for it after the technical work is finished.
Contractors should know which drawings, red-line mark-ups, cable schedules, configuration backups and other records they are expected to return. For larger projects, those deliverables can be tracked alongside the physical work so missing information is visible before the contractor demobilises or the yacht leaves the yard.
Someone onboard also needs ownership of the process. That does not mean one person has to redraw every system, but somebody should be responsible for checking that changes have been captured, the final documents match the completed work and obsolete information is either removed or clearly superseded.
The appropriate document set will vary by system and vessel. What matters is that the next engineer can understand the installation without first having to reverse-engineer the previous refit.
When the documentation cost is pushed back onto the crew
Technical crew are often in the position of recognising the problem without controlling the budget. If an owner, captain or management company decides to remove documentation from a contractor's scope, the engineer may not be able to reverse that decision. What they can do is make the consequence clear before the project closes.
The first step is to put the missing deliverables in writing. This does not need to become an argument about engineering standards. A short project note can state what has been removed from scope, what information will therefore not be delivered, and what work is being left for the vessel to complete afterwards. If an integrator was originally expected to provide updated drawings, configuration backups, cable schedules or commissioning records, those items should remain visible as outstanding rather than quietly disappearing when the quotation is reduced.
It is also worth drawing a clear line between normal onboard document maintenance and recreating a contractor's project package. Technical crew can reasonably maintain red-line mark-ups, equipment inventories, internal network information, configuration backups and change logs as part of running the vessel. That is very different from asking one engineer to reconstruct a multi-system refit after the contractors have left, particularly where proprietary software, original design files, specialist drafting or class-approved documentation is involved. In some cases the crew member may not even have the information or tools needed to reproduce the missing material accurately.
Where cost is genuinely the problem, reducing the documentation scope is usually better than removing it completely. A minimum handover might still capture the final configuration backups, the drawings or schedules that actually changed, cable identification and routing changes, equipment details, commissioning results and a list of open defects. Producing a polished drawing package later is possible; trying to reconstruct the final installed state from memory months afterwards is much harder.
If management still decides that the remaining work will fall to the crew, it should be carried as an open project item with an owner, a description of what is missing and, ideally, time allocated to complete it. This is particularly important across crew rotations. Without a written record, the next engineer may inherit incomplete documentation with no way of knowing whether it was omitted intentionally, forgotten by the contractor or assumed to have been completed by somebody onboard.
For class, statutory or safety-critical modifications, technical crew should also check whether the missing documentation is actually optional. Where flag, class, survey or the vessel's safety-management arrangements require controlled information or approval, that requirement should be raised through the appropriate management route before the project is closed. Likewise, crew should be cautious about signing or recording a package as complete when they know important deliverables or commissioning work are still outstanding; the acceptance record should reflect the condition in which the system was actually handed over.
References
1. International Safety Management (ISM) Code — Resolution A.741(18). International Maritime Organization. Sections 10 and 11 cover maintenance records and document control.
2. Approval of documentation — alterations. DNV Maritime. Guidance on technical-document approval for vessel alterations and modifications.
3. How to proceed when making modifications to installed ballast water treatment systems. DNV, 2024. Example of revised technical documentation and P&ID requirements following system modification.
4. Case Study: Refit on 86m yacht, more than just a system review. ONEXP, 20 May 2025. Example of installed systems no longer fully matching the available documentation.
5. Superyacht Network Updates: Upgrading and Futureproofing. OceanWeb, 14 November 2022. Case study involving legacy cabling and limited documentation.
6. Roxtec Installation Training. Roxtec. Guidance on correct installation of cable and pipe transits and the importance of trained installers.
7. The Intelligent Refit Era. MB92 Group, 16 July 2026. Industry research on data quality, interoperability and legacy systems in yacht refit.
Sources reviewed 14 September 2026.