A docking plan can have the correct vessel name and still be the wrong working reference for the forthcoming attendance. An earlier issue may not reflect a later modification, an attachment may be missing, or the intended docking condition may differ from the information supplied. Revision control is therefore a technical coordination question, not simply a filename check.

This article helps owners identify questions to resolve when docking information changes. It complements the initial dry docking preparation guide; it does not calculate dock suitability, prescribe a support arrangement or authorize docking operations.

Establish which issue is being reviewed

Record the drawing number, title, revision, issue date, issuer and stated purpose. Check that the title block, transmittal and attachment list describe the same issue. A file called “latest” is not a controlled revision identifier.

Keep the previous issue available as history and identify the changes reported by the issuer. If the document has no readable revision history, record that gap and ask the responsible technical party how the current issue was established. Do not fill missing information from a similar vessel’s drawing.

  • The vessel identity and drawing reference being discussed.
  • The revision actually supplied to the yard and its transmittal reference.
  • The previous issue used for any earlier suitability discussion.
  • The stated change, source of the change and related documents.
  • The review or confirmation still required and the responsible contact.

Ask what has changed on the vessel

Distinguish a corrected drawing from a changed physical arrangement. Ask whether modifications or equipment changes affect information relevant to docking, and who has assessed their effect. An updated general arrangement does not, by itself, establish that every docking document has been updated.

Examples of questions include whether relevant hull features or appendages have changed, whether an opening or fitting is described consistently across documents, and whether reported changes have been incorporated into the drawing being circulated. These are information checks for competent review, not instructions for positioning blocks or supporting the vessel.

Where a discrepancy needs design input, identify the designer, naval architect or other responsible technical party. Do not resolve it by treating a photograph, a previous docking record or a commercial quotation as a substitute for the necessary technical decision.

Keep the intended docking condition explicit

Connect the document package to the vessel particulars and intended condition supplied for the attendance. Gisan’s docking-services page asks for dimensions, draught and displacement for the intended docking condition, together with available docking information and work scope. Suitability and the planned date range require separate confirmation.

If the condition assumed in an earlier discussion changes, flag the change rather than leaving the yard to infer it from an updated data sheet. Ask which information needs to be reviewed again. This guide provides no loading, ballast, stability or support calculation and does not define an acceptable docking condition.

Connect revisions to the requested work

The drawing review should not be detached from the repair list. Identify work affecting the underwater hull, associated equipment, access or information that the reviewing parties have asked to see. Link each relevant drawing change to the work-item reference and the party responsible for resolving its implications.

For a structural item, connect the available drawing information to the steel-renewal location and scope records. That connection helps the discussion; it does not prove that a renewal area or proposed method is accepted for docking or repair.

Separate work changes from document corrections

A correction to a label may have a different effect from a changed fitting or structural arrangement. Record the issuer’s explanation and ask the responsible reviewer to determine the consequence. Avoid marking every revision as either “administrative” or “major” without a technical basis.

Keep dependencies with the revised issue

If a revision relies on another drawing, measurement record or specialist response, include that reference in the register. Record missing attachments and unresolved questions as open inputs, not as implied acceptance.

Define who confirms the working reference

Identify who supplies the vessel information, who reviews it for the planned attendance and who communicates the confirmed working issue to the relevant parties. The owner, yard, designer and any attending survey party may have different responsibilities. Their involvement should be established for the actual vessel rather than inferred from a generic checklist.

Where formal approval or a survey decision is required, retain the actual reference and any conditions. A document being received, reviewed for planning or discussed in a meeting does not automatically make it an approved operational instruction.

Close the information loop before relying on an old assumption

Use a short revision register to show the question, current answer, affected document and unresolved action. Confirm that recipients can access the same issue and that superseded information is clearly identified. If a late change arrives, record which earlier confirmations need to be revisited.

For a Gisan enquiry, send the available drawing register, vessel particulars and specific revision questions through the technical enquiry page. The aim is to make the review basis explicit, not to establish vessel fit, an available docking slot or technical acceptance through this article.