Vessel repair handover process map

What is in this map

19 steps across 4 swimlanes and 5 phases, with 4 decision points.

Swimlanes (who does the work)

Workshops, QA/QC, Project Manager and Customer / Class

Phases (left to right)

Completion review, Testing, Customer inspection, Punch-list closure and Departure

Why map this process

The map draws two very different rejection outcomes as separate branches: accepted with minor items, the punch-list path, and not accepted, major rework back to the start. Conflating them would either send every minor snag list through a full project restart, or let a genuinely unacceptable repair proceed on a punch-list that was never meant to carry that weight. Most handovers land on the first branch, and the map is built around that being the normal case, not an exception.

The final repair dossier is explicitly a compilation, not a single document — test records, class endorsements, as-built drawings and every change order from the project, filed together. That note is doing real work: it tells whoever adapts this map that the dossier's completeness depends on every other map in this cluster, inspections and change orders alike, having actually produced the records it needs to gather here.

Every step in the map

This is the spreadsheet behind the diagram. The numbers in “Goes to” are row numbers, which is exactly what the editor’s “Line to” column holds — so you can read the flow here and retype any part of it.

The decision points

Every branch in the map, with the label on each outgoing line. These are the questions the process has to be able to answer.

• 3. Any work package still **open**?

  Owned by Project Manager · Completion review

  • All closed → step 5
  • Items open → step 4

• 6. All systems test and commission successfully?

  Owned by QA/QC · Testing

  • Pass → step 8
  • Fail → step 7

• 11. Customer and class **accept** the work?

  Owned by Customer / Class · Customer inspection

  • Accepted, minor items → step 13
  • Not accepted → step 12

• 15. All *punch-list* items closed and signed off?

  Owned by Project Manager · Punch-list closure

  • Closed → step 17
  • Items remain → step 16

Notes on specific steps

These notes travel with the map. In the editor they live in the Notes column and appear when you open a box.

17. Assemble **final repair dossier** and warranty documentation

Test records, class endorsements, as-built drawings and every change order from this job go in as one dossier, the reference the customer and FAYARD both pull from if a warranty question comes up.

Making it yours

The 'any work package still open' decision loops all the way back to the project manager's own review, not to the specific open package — that is deliberate, because the review is a wholesale gate across every workshop's output, and a partial pass would let one department's incomplete work slip through while others' get reviewed. When you adapt the punch-list loop, keep it as repeated closure rather than a fixed number of rounds: real punch-lists close item by item over days, not in one pass, and the loop is what lets the chart represent that without inventing an arbitrary round count.

What to watch out for

• Do not merge the major-rework branch with the punch-list branch. They return to completely different points — major rework goes all the way back to workshop review, punch-list items get tracked and closed without reopening the whole project. Treating a customer's rejection as automatically minor is how a yard ends up calling major rework 'a few punch-list items'.
• The commissioning-failure loop returns to testing, not to the workshops that did the original repair. A system that fails commissioning needs to be re-tested after rectification, and routing straight back to a workshop repair step without the retest gate would let a second attempt ship without verification either.
• The final dossier is easy to treat as paperwork that happens automatically once the vessel departs. It does not — it has to be compiled and checked before departure, because a warranty dispute six months later is exactly the moment a yard discovers a test record was never actually filed.

Frequently asked questions