Newbuild Warranty Handover

A service technician has replaced a faulty component. The ship’s defect list says “done”, but the buyer still has no record that the installed system passed its follow-up checks, and a travel invoice remains disputed. Those are different outstanding questions. A useful newbuild warranty handover keeps the original defect, contractual notice, repair record and closure evidence connected without treating them as the same decision.

This guide follows defects first discovered after delivery. The newbuilding buyer’s guide covers ordering a vessel; the variation-order comparison addresses changes during construction. Here the output is a working file that the ship’s crew, buyer’s technical team and warranty coordinator can use from notification through retesting and final record completion.

1. Establish the warranty file at delivery

Give the shore coordinator and vessel team access to the executed contract, amendments, delivery protocol, relevant specifications, equipment manuals and supplier contacts. Keep the list of items already outstanding at delivery identifiable: their treatment may differ from that of defects discovered later. Record who is authorised to notify the builder, approve expenditure and sign technical closure.

Prepare a contract-specific control sheet. Have the responsible contract team verify the guarantee start and end dates, discovery and notification requirements, permitted delivery methods and recipients, repair arrangements, exclusions and any conditions affecting further cover after repair. Record the clause and amendment beside each entry. A generic “12-month warranty” heading is insufficient to establish these details.

Keep supplier support access alongside that file. Wärtsilä Online, for example, supports service-history access, equipment data and warranty-claim tracking. An OEM support ticket is useful technical evidence; it should not be assumed to fulfil the separate notice requirements of the buyer’s shipbuilding contract.

2. Give each defect a stable identity

Use one reference throughout the log, notification, attachments and service reports. Separate what the crew observed from the suspected cause. A remote pressure reading differing from a local instrument is an observation; it does not, by itself, establish which instrument or part of the installation is faulty.

Preserve original files and add later interpretations separately. Record unknowns explicitly. Equipment identity matters when sourcing replacements: Wärtsilä’s spare-parts guidance asks for equipment type, model and serial number and warns that different versions of a part may not fit the intended application.

For vessels subject to the ISM Code, maintenance procedures also require appropriate records. ISM Code section 10, reproduced by the Netherlands authorities, connects inspections, reported non-conformities and possible causes, corrective action and retained records. A warranty register can cross-reference the vessel’s maintenance system, while the vessel team continues to manage operational restrictions through its own procedures.

3. Track notice, receipt and the coverage response separately

Before a defect occurs, prepare a notification checklist for the actual agreement. It should identify the contract and defect references, discovery details, known symptoms and consequences, current evidence, immediate measures, requested attendance and contact person. Use the specified recipient and communication method; retain the transmission and receipt evidence required by that agreement. Refer to additional evidence as it becomes available rather than silently replacing the initial account.

A publicly disclosed Cadeler shipbuilding contract, based on amended NEWBUILDCON, illustrates why this needs a contract-specific check. Clause 35 connects discovery and notification with the guarantee, addresses repairs away from the building yard and replaced parts, and provides conditions for further cover. Clause 43 deals with written notices and receipt. These are provisions of that particular project, not universal deadlines or rights.

Ask the contract team to distinguish an acknowledgement of receipt from acceptance of warranty coverage, agreement to a repair method and agreement on costs. Track each response by date and reference. Forwarding a complaint to a supplier does not necessarily resolve any of those questions.

Before planned third-party repairs, establish the required notice, authority and inspection opportunity. Record arrangements for access, attendance, parts retention and costs. Urgent safety action follows the vessel’s applicable procedures; keep contemporaneous records and notify the relevant parties through the required channels.

4. Worked case: a freshwater pressure indication discrepancy

Fictional record example: a newly delivered vessel has a domestic freshwater hydrophore system. After delivery, the crew observes an intermittent difference between its remote pressure indication and a local reading. The cause is initially unknown. This example demonstrates record decisions, not a fault-finding procedure. Dates are invented, and neither the sequence nor the elapsed time establishes a contractual notice period or a standard repair duration.

Assume the buyer’s contract team has verified that the initial notice meets this project’s discovery, recipient, method and timing requirements. Also assume the responsible technical team has addressed the operating implications, and the builder subsequently confirms cover for the diagnosed defect and authorises its service subcontractor to attend. Those assumptions must be established afresh on a real vessel.

The first proposed closure fails because it does not show that the onboard indication chain meets the agreed verification requirements. Sending a replacement part or obtaining a satisfactory component check cannot fill that evidence gap. Conversely, an unpaid or disputed attendance invoice does not by itself show that the technical defect remains uncorrected.

VP014 is an invented document reference. In practice, the responsible specialists establish the measuring points, reference method, operating conditions, acceptance limits, functional checks and any observation period from the relevant equipment documentation and installation requirements. Do not assume the original local gauge is an accurate reference. If the signal also serves an alarm or control function, identify the affected functions and include the required checks. Obtain any necessary class or statutory involvement for the actual work.

5. Make closure a documented decision

The closure file should let another reviewer trace the same equipment from first report to final verification. Include the original notice and replies, diagnosis, repair scope, replacement identifiers, service report, test procedure and results, remaining restrictions and the name and authority of the person accepting technical closure. Keep any agreed monitoring action visible with its owner and completion requirement.

Record cost approval, disputed invoices and any release or settlement document separately. Have the contract team check the wording before signing a discharge. Record any further warranty cover only after its contractual basis has been confirmed; replacing a part does not establish a fresh whole-vessel guarantee.

If the symptom returns, link the new event to W-014 and preserve the earlier closure record. The new occurrence needs its own discovery evidence and contract review. This gives the buyer a usable history instead of an overwritten “closed” entry with no explanation of what changed.

What to request before handing over warranty coordination

• A contract-specific notice sheet, verified recipients and named decision-makers.
• An equipment-linked defect register with original evidence and correspondence references.
• Separate entries for receipt, coverage response, repair authority and cost agreement.
• A verification plan and recorded results supporting each technical closure.
• A separate list of unresolved costs, monitoring actions and confirmed further-cover dates.

The Chinese shipyard buying guide places warranty within the wider purchase process. For the post-delivery handover, ask for a file that explains what was reported, what was agreed, what was repaired and what evidence supports closure.