A yacht punch list that is ready for handover

01A checklist and a punch list do different jobs

A checklist describes what to inspect, such as a cabinet door’s operation or a surface finish. A punch list, also called a snag list, records the issues actually found and the work still to be completed. Keeping these purposes separate prevents a planned check from being mistaken for an observed defect.

Agree the inspection scope, the accessible areas and who records findings before going aboard. Give each issue a stable identifier so it remains recognisable in meetings and reports. A new photo normally updates the same case; a different problem needs its own entry. Avoid creating another item simply because a second person has noticed it.

02The minimum fields for an actionable item

Create one entry for each problem that can be assigned and checked independently. Use the title to make it easy to find and the description to record what you observed. A suspected cause should remain a hypothesis rather than becoming a diagnosis without supporting evidence. Agree these minimum fields across the team.

Identity and location

Issue ID, yacht, deck, area and exact position. ‘Saloon’ may not be specific enough.

Observation and evidence

A concrete description, a context photo and a close-up. Keep the location understandable even for a small defect.

Action and ownership

The requested work, assigned contractor and a named contact who can clarify the requirement.

Priority and timing

Agreed importance, planned date and any conditions affecting access or execution.

Status and checking

Work progress, closure criterion, the person checking and the final inspection result.

03Separate assignment, execution and checking

The project lead reviews findings and assigns work to the appropriate contractor. Name a contact for questions: an item assigned vaguely to everyone rarely has a clear next step. Where several trades are involved, separate their tasks or explain which part belongs to each contractor and who coordinates the handover between them.

The contractor reports the work performed and adds available evidence. The person responsible for checking then compares the result with the agreed closure criterion. In Sailify, contractor completion and internal review are separate steps. The list should make the transfer from doing the work to checking it clear.

04Make priorities, dates and visibility explicit

Agree what each priority means: an issue may prevent a test, affect a handover stage, need attention before the next visit or be scheduled separately. Priority expresses relative importance; the planned date states when the work is expected. Do not use one as a substitute for the other.

Start the pre-handover meeting with open issues, obstacles and outstanding checks. Every postponement needs a reason and a revised date to agree. Share the relevant scope with each participant. Internal discussions and updates intended for the owner should not automatically become one unrestricted conversation; decide which information each audience needs.

05Define closure before the work starts

For the cabinet in the example, ‘fixed’ does not explain the expected outcome. A more useful criterion is a flush closure and movement without contact with the lower edge. Record the inspection result and a photo where it helps document it. For work requiring specific tests, agree the method and the competent people involved before execution.

If the result does not meet the criterion, describe the remaining correction while retaining the link to the original issue. Closing an item in software records the operational workflow. On its own, it does not replace the trials, certifications or acceptance arrangements applicable to that yacht.

06A checklist for your next walk-through

Ask these questions at the end of each area before moving on. They check the quality of the information you have collected; they are not a replacement for the yacht’s technical inspection checklist.

• Can the issue be found without calling the person who logged it?
• Do the description and photos identify the same point and problem?
• Does the assigned contractor understand the requested work?
• Are the priority, planned date and obstacles clear?
• Is it clear who checks the work and what result they should see?
• Does every open item have a next step and a responsible contact?

Editorial example using demo data. Adapt the fields and criteria to your project and the agreed responsibilities.