Several repair items may need the same underwater hull area, opening or access route during a docking period. Treating each item as an independent line can hide conflicts: an area may be ready for examination while another activity changes its condition, or equipment may be closed up before the relevant review is complete. A useful programme makes those interfaces visible.

Here, “underwater hull work” means work on normally submerged hull areas made accessible during a docking period. This is not an in-water diving procedure, a universal repair sequence or an instruction for hot work, lifting, isolation or enclosed-space entry. It is an owner-side method for discussing dependencies with the parties responsible for the work.

Group the work by area and shared access

Keep the approved work-item numbers, then identify which activities share a physical area or access arrangement. A location-based view can reveal a dependency that is not obvious in a discipline-based quotation.

For each relevant area, connect the requested inspection, repair, equipment work and surface treatment to their actual references. Avoid assigning a single completion status to the whole area when different work items have different review or reinstatement requirements.

  • Which items need the same area to remain accessible?
  • Which item changes the condition another party intends to inspect?
  • Which opening or removal arrangement serves more than one task?
  • Which activity depends on an owner, specialist or survey decision?
  • What must be recorded before access or the physical arrangement changes?

Describe dependencies instead of imposing a generic sequence

The work programme should reflect the actual vessel condition, repair method, applicable procedures and responsible technical decisions. A generic statement such as “inspection, steel work, then coating” does not explain every equipment interface or the inspection stages needed within a particular repair.

Ask the responsible parties to state what makes an activity ready to start and what evidence permits the next activity to proceed. Record those conditions against the work item. This is more useful than copying a standard sequence that has not been reviewed for the vessel.

The initial dry docking planning guide covers enquiry inputs. The focus here is the relationship between activities after the work package has been defined, not another vessel-data checklist or a docking cost estimate.

Make inspection and decision points visible

Where a technical party identifies a required examination or review stage, show it in the programme and agree how readiness will be communicated. Do not assume that a later photograph can replace an examination that was required while the work remained accessible.

Keep repair completion, inspection completion and formal survey close-out as separate states. The class survey coordination guide explains why a work record and a class or statutory decision are not interchangeable. The applicable inspection stages must come from the actual repair and responsible parties.

Record the consequence of a new finding

If a finding changes the repair boundary, identify the affected area and dependent tasks before updating the programme. Connect the finding to the technical response, owner’s authorization where relevant and revised work reference. Do not silently extend the original item or assume the next activity can continue unchanged.

Connect structural, equipment and coating interfaces

Where structural repair and equipment work share an area, ask how their access and completion boundaries fit together. Record responsibility for adjacent components, protection, reinstatement and the evidence requested. Do not infer that a trade’s item includes every shared task.

For surface treatment, the selected system, specification and applicable technical instructions govern preparation, application conditions and subsequent work. Ask who confirms the relevant requirements and how later activities will avoid compromising completed work. This article sets no cleanliness grade, coating thickness, curing period or environmental threshold.

Gisan’s surface-preparation and coating scope and docking-services scope provide the service context. They do not define a project-specific sequence or guarantee compatibility between independently proposed methods.

Review parallel activities through the responsible safety arrangements

Two tasks occupying different work-item lines are not automatically suitable to run together. Ask the responsible yard and vessel teams to review proposed overlaps under their applicable risk-assessment, permit and control arrangements. Record the resulting constraints in the planning discussion.

Keep the coordination register separate from the safety authorization itself. A programme entry, meeting note or commercial instruction is not a permit to begin work. Specialist procedures and competent supervision remain necessary where the activity requires them.

Use an area release record at handover

Before treating an area as complete, reconcile the relevant work items, examination records, reinstatement status and open actions. Identify which party confirms each item and what remains outstanding. A single “area released” note should not obscure an unresolved technical decision.

Share the work list, marked locations and known dependency questions through Gisan Shipyard’s technical enquiry page. A clear interface discussion supports a vessel-specific programme; it does not promise a docking duration, an operational release or a particular inspection outcome.