Vessel repair handover SOP: completion review to departure
A shipyard SOP for vessel repair completion and handover: outstanding-item review, testing and commissioning, QA documentation, customer and class inspection, punch-list closure, and undocking, with an owner and workload hours per step.
What the vessel repair handover sop: completion review to departure process is
Handover is where a repair project's paperwork catches up with the actual state of the vessel, and it is also where the workshop's own optimism does the most damage. A work package gets reported complete because the fitter believes it is, not because anyone with authority over the full scope has checked it against what was ordered. That is why this chart puts a review step, not a rubber stamp, immediately after "All work packages reported complete by workshops": the project manager checks the report against scope before anything moves to testing, and the decision "Any work package still open?" sends the process back through "Chase workshop to complete outstanding items" rather than letting an unfinished item ride along into commissioning, where it is far more expensive to catch.
The same reasoning repeats twice more, because a handover at a yard like FAYARD fails at three distinct moments, not one: a work package can still be open before testing even starts, a repaired system can fail its own commissioning test, and the customer or class surveyor can simply not accept what the workshop and the yard's own QA/QC already signed off. Each of those is modelled as a decision with a loop back to rework, "Return to workshop to rectify the failed system" for a failed commissioning test, "Return to workshop for major rework" for a rejected inspection, rather than a side note for someone to remember later. A surveyor's rejection is the most expensive of the three failures to reach, so the chart is deliberately drawn to let the two earlier, cheaper checks catch as much as they can before the vessel ever gets to that inspection.
The punch-list stage exists because "accepted" and "finished" are not the same thing at a repair yard: a surveyor can sign off the vessel as fit for service while a handful of minor items, a paint touch-up, a missing certificate, a loose fitting, are still open. Routing those through their own decision, "All punch-list items closed and signed off?", with a loop back through "Continue closing remaining punch-list items", keeps them from either blocking departure over trivia or getting quietly dropped once the vessel is back at sea. And the People and Workload columns on every row are not bookkeeping: Sarah Mitchell, the project manager, carries hours against outstanding-item review, inspection scheduling, punch-list compilation and the final dossier all at once, and Olivia Bennett's QA/QC hours span commissioning, the pass/fail decision and the documentation package. On a yard running more than one handover at a time, the workload BI panel is what shows a scheduler that the same project manager is already committed before a second vessel's punch-list closure gets promised for the same week.
What this flowchart covers
In this template
- Completion review: from "All work packages reported complete by workshops" through "Project manager reviews outstanding items against scope" and the decision "Any work package still open?", which loops back through "Chase workshop to complete outstanding items" until every package is genuinely closed
- Testing and commissioning: "Test and commission repaired systems" gated by "All systems test and commission successfully?", with a failed system looping back through "Return to workshop to rectify the failed system" before commissioning is retried
- QA documentation and customer/class inspection: "Compile QA documentation, test records and certificates", "Schedule customer and class inspection" and "Customer and class surveyor inspect the completed work", closed by the decision "Customer and class accept the work?", where a rejection routes all the way back through "Return to workshop for major rework"
- Punch-list closure: "Compile agreed punch-list of minor outstanding items" and "Close punch-list items and obtain customer sign-off", gated by "All punch-list items closed and signed off?", with items remaining looping back through "Continue closing remaining punch-list items"
- Final documentation and departure: "Assemble final repair dossier and warranty documentation" and "Undock or release berth, vessel departs", closing at the terminal "Repair project complete, vessel departed"
- Named People and numeric Workload on every step, spanning the "Workshops", "QA/QC", "Project Manager" and "Customer / Class" lanes, so the workload BI panel can total effort by person and by stage across the handover
When to use this template
- You're closing out a repair project at FAYARD and need a controlled, approved sequence from the workshops' completion report through to departure, not a verbal understanding of what happens next
- A previous handover let an unfinished work package ride into testing, or a punch-list item got dropped once the vessel had sailed, and you need the review and punch-list decisions to make that impossible
- You're running commissioning and inspection across several vessels' repair projects at once and need the People and Workload columns to show where the project manager or QA/QC lead is already committed before promising a customer another inspection slot
- A customer or class surveyor rejection has previously gone straight back into the workshop with no documented cause, and you need the "Not accepted" branch to force a written reason and a return through major rework rather than an informal fix
- You're inducting a new project manager or QA/QC lead and need a reference sequence from completion review through commissioning, inspection, punch-list closure and final documentation to undocking, rather than tribal knowledge of what happens next
How it works
Match the lanes to your own project organization
The sample uses Workshops, QA/QC, Project Manager and Customer / Class. If your handover process separates the workshop foreman's sign-off from a dock master's, or routes class surveys through a dedicated surveyor liaison, give each its own lane rather than folding it into an existing one: the lane is what tells a reader who owns a step at a glance.
Replace the sample People and Workload values with your own roster and hours
Swap Sarah Mitchell, Olivia Bennett, Marcus Webb and the rest for your actual project manager, QA/QC lead and workshop foremen, and set Workload to the effort each step realistically takes, not the calendar time it spans. That is what the workload BI panel totals, so placeholder hours produce a placeholder workload picture.
Write your own acceptance criteria onto the decision boxes
"All systems test and commission successfully?" and "Customer and class accept the work?" need real criteria behind them: which test standards a system must pass, and what the class surveyor is actually checking against. A decision with no stated criterion gets answered by judgement, which is exactly what the rework branches exist to catch.
Size the punch-list decision to your own tolerance for minor items
"All punch-list items closed and signed off?" assumes a punch-list of genuinely minor items agreed at inspection. If your yard's punch-lists routinely include work that should have blocked acceptance in the first place, tighten what your inspection decision treats as accepted with minor items, rather than letting it flow through to punch-list closure.
Keep final documentation as its own step, not a note on departure
"Assemble final repair dossier and warranty documentation" is the record the customer and FAYARD both rely on if a warranty question comes up later. Keeping it as a separate row before "Undock or release berth, vessel departs" means the dossier can't be skipped when a departure gets rushed.
Frequently asked questions
Why does this SOP have three separate decision points instead of one handover step?
Because a handover at a repair yard fails at three different moments, not one: a work package can still be open before testing starts, a repaired system can fail its own commissioning test, and the customer or class surveyor can decline to accept work the workshop and QA/QC already believed was done. Each decision sits at the moment its corresponding failure becomes checkable, and each branches back to rework rather than forward to a note, because catching an unfinished item at the outstanding-item review is far cheaper than catching it at the surveyor's inspection.
What do the People and Workload columns do on this chart?
Each step carries the person accountable for it and a Workload figure in hours representing the effort that step actually takes, not the elapsed time it spans. The workload BI panel reads those two columns across the chart to total effort by person and by stage, so a scheduler can see, for example, that the project manager is already carrying review, inspection-scheduling and punch-list hours on one handover before a second vessel's closeout gets added to her week.
What happens if the customer or class surveyor doesn't accept the completed work?
The decision "Customer and class accept the work?" routes a rejection back through "Return to workshop for major rework" and then back through the outstanding-item review, rather than treating the rejection as a side conversation. Only an acceptance with minor items proceeds to punch-list closure, which is what keeps a disputed repair from quietly reaching departure.
How is a punch-list item different from a failed commissioning test?
A failed commissioning test means a system didn't pass its own testing and is routed straight back to the workshop before the customer or surveyor is ever involved. A punch-list item is something the customer and class surveyor have already agreed is minor enough that it doesn't block acceptance, and it's tracked and closed separately at "All punch-list items closed and signed off?" rather than reopening the whole inspection.
Can this SOP be adapted for a repair project that has no classification society involved?
Yes. The stage structure carries over: outstanding-item review, testing and commissioning, documentation, an acceptance inspection and punch-list closure before departure. What changes is who sits in the Customer / Class lane and what the inspection decision actually checks against, so revise that step and its criteria rather than the overall sequence.