A yacht new-build handover should not treat AV, lighting control, networking, cameras, and connectivity as loose equipment packages. For the captain, engineer, owner representative, yard, and support team, the handover is an operating file: what was installed, how it is configured, who owns each account, how it was tested, and how it can be restored after delivery.
Cave Group's marine integration work is built around Crestron control, marine audio, Starlink Maritime connectivity, UniFi networking, and vessel-scale support for superyachts and custom vessels. On an Italian new build, the best time to define the handover package is before sea trials, while the yard, integrator, network team, and owner representative can still close gaps together.
The Handover Package Should Be a File Manifest
Ask for a final file manifest, not a casual folder of exports. The manifest should name each delivered file, its date, the system it belongs to, the person or company responsible for it, and whether it reflects design intent or the installed as-built condition.
For the AV and control scope, the package should include:
- As-built rack elevations, equipment locations, cable schedules, network topology, control processor locations, touch panel and keypad locations, display locations, audio zones, camera locations, wireless access points, and communications equipment.
- A device schedule with model numbers, serial numbers, MAC addresses where relevant, installed locations, network names, firmware or software versions where available, and responsible vendor or trade.
- Current configuration backups for the control system, AV-over-IP routing, managed network, camera system, connectivity gateway, and remote-management platforms included in scope.
- A restore path that explains where backups live, who can access them, how a replacement processor or gateway would be restored, and which steps require dealer or manufacturer portal access.
- Account and platform ownership records for Crestron, network management, camera access, connectivity, media services, alarm monitoring, and any owner-facing apps.
- An interface responsibility list for every connection between AV/control and ship systems, including the owner of the API, protocol, credential, support path, and change-control process.
- A signed acceptance record, punch list, and crew training acknowledgment.
This is especially important with Crestron-led systems. Crestron's documentation for myCrestron RMS describes configuration backups, log access, downloadable backup files, deploy codes for replacement or restore scenarios, and integration reports for connected devices and functions. Its settings documentation also identifies backup and restore options, user accounts, passwords, REST API token handling, diagnostics, and privacy settings that can affect backups and monitoring. Those are not items to discover after the vessel has left the yard.
Backups Need an Owner and a Restore Path
A backup only helps if the crew and support provider know where it is, who controls it, and how it would be used under pressure. For each controlled platform, the handover record should answer four practical questions: what is backed up, where it is stored, who has permission to retrieve it, and how a replacement device would be restored.
Where Crestron Home is part of the yacht scope, the handover should document the processor, cloud registration status, backup location, latest exported reports, deploy-code process, and any limits around account access. Crestron's documentation notes that deploy codes can be generated for replacing or restoring a Crestron Home processor and that the code expires after 14 days, so a handover package should document the process rather than rely on a static old code.
The same principle applies beyond Crestron. Managed switches, Wi-Fi controllers, cameras, connectivity gateways, media servers, and monitoring tools should have current configuration exports or a documented backup method. If a platform cannot provide a useful export, that limitation belongs in the handover record.
Interface Ownership Is Not Optional
New builds often involve several teams touching the same guest experience: yard electrical, naval architecture, HVAC, security, IT, AV, lighting, communications, and owner-supplied media services. If the AV/control system talks to another system, the handover should state who owns the interface.
For each interface, document:
- The system being controlled or monitored.
- The protocol, API, driver, or contact-closure path being used.
- The credential or token owner, without exposing passwords in an uncontrolled file.
- The party authorized to change settings.
- The support contact when the interface fails.
- The acceptance test proving the interface worked at delivery.
Crestron's developer documentation lists APIs and tools for platforms including XiO Cloud, DM NVX, Crestron Home OS, 4-Series control systems, DM NAX, and other devices. That makes API responsibility a real design and handover issue: the yard and owner team should know which integrations are standard, which are custom, and which party is responsible when a manufacturer update or credential change affects operation.
Acceptance Should Match Vessel Operation
A dockside demo is useful, but it is not the whole acceptance process. The signed record should test how the yacht will actually be used by guests and crew.
For a Crestron-based marine system, acceptance should cover the owner suite, guest cabins, main salon, skylounge, crew areas, exterior decks, helm-related control points, AV zones, lighting scenes, wireless coverage areas, cameras, and internet paths included in the contracted scope. Each test should have a pass/fail result, witness, date, open item, and responsible party.
Useful acceptance questions include:
- Do touch panels, keypads, and remotes control the intended spaces and only those spaces?
- Do lighting scenes recall correctly in cabins, guest areas, and exterior zones included in scope?
- Do audio and video zones route from the specified sources to the specified displays and speakers?
- Does Wi-Fi coverage match the agreed interior and exterior areas?
- Do camera views, recording, and access permissions match the security plan?
- Does the connectivity design behave as expected when the primary internet path changes to a backup path?
- Can the captain or engineer perform agreed basic recovery steps without calling a programmer?
Open items should be ranked by operating risk. A missing label is not the same as missing configuration backups, unclear admin ownership, or an untested ship-system interface.
Crew Training Belongs in the Closeout Record
Crew training should be documented like any other delivery item. The file should identify who was trained, which systems were covered, where quick-reference material lives onboard, which accounts were transferred, and which support permissions remain with the integrator or owner representative.
Training should be role-specific. The captain and engineer need recovery paths, rack labeling, support contacts, remote-access rules, and known limitations. Interior crew need normal guest operation: room control, source selection, lighting scenes, privacy behavior, and simple resets. The owner representative needs confirmation that platform ownership, support access, and monitoring permissions match the owner's instructions.
Cave Watch should also be recorded clearly if it is part of the ongoing support plan. Cave Watch 24/7 is managed support and remote monitoring of installed systems. Cave Watch Central is alarm monitoring using Alarm.com and a UL-listed central station. Deep Sentinel is live video monitoring. Those services can be layered, but the handover should keep them distinct.
Delivery Should Not Close With Missing Control
The goal is straightforward: when the vessel leaves the Italian yard, the team running it should know what is onboard, how it is controlled, who owns each account and interface, how the system was tested, and how support is reached. That is the difference between a polished technology installation and one the crew can confidently operate after delivery.
For yacht manufacturers and project engineers, the cleanest approach is to make the AV/control handover package a contractual closeout deliverable. Define it early, review it before sea trials, and do not let delivery depend on undocumented knowledge sitting with one programmer, one laptop, or one vendor login.