A newbuilding offer may answer the outline specification while changing a detail that matters to the vessel’s intended work. A different equipment selection, an unresolved drawing reference or an exclusion from the proposed delivery can be easy to overlook when the review concentrates on the overall offer.

Newbuilding bid technical clarification is the process of turning those differences into identifiable questions and recorded decisions before relying on a common technical basis. This guide is for owner and procurement teams reviewing returned bids. It follows the initial commercial-vessel newbuilding RFQ; it is not another enquiry template, a design approval or advice on interpreting a shipbuilding contract.

Freeze the specification issue behind the comparison

List the specification, general arrangement, equipment schedules and other documents actually issued to each bidder. Record their revisions and the clarification circulars that formed part of the enquiry. A response to an earlier drawing should not be compared as though it addressed a later arrangement.

Keep the offered delivery boundary visible alongside that document list. Identify whether design development, equipment supply, installation information, testing or final documentation is included, excluded or still undefined. Do not assume that a familiar vessel description gives every bidder the same understanding of those boundaries.

Where the enquiry documents contain inconsistent requirements, put the conflict back to the responsible owner or design party. The clarification register should identify the conflict, not silently choose which document takes precedence.

Separate an exception from a question or an alternative

Not every note in a shipbuilding offer has the same meaning. Classify each point so the response sought is clear.

  • Exception: the offered scope differs from an identified enquiry requirement.
  • Alternative: the bidder proposes a different technical solution for the owner to consider.
  • Clarification: information is needed to establish what either the requirement or the offer means.
  • Unresolved selection: an equipment or design choice remains open and affects the comparison.

A blank response is not evidence of compliance, and a proposed alternative is not an accepted change. Retain the bidder’s actual wording and connect it to the specification item rather than rewriting an uncertain response as an agreed position.

Trace the difference to the vessel requirement

Ask what the exception changes in relation to the intended service, arrangement or equipment function. The review may need an identified designer, equipment supplier or other technical party to explain the consequence. Purchasing staff should not have to infer technical equivalence from a brand name or a short commercial description.

Compare the offered data, not just the equipment label

For an equipment substitution, request the offered model reference, applicable data sheet and the requirement against which it is being proposed. Record missing interface or performance information as missing. A common equipment family name does not establish that the proposed item meets the vessel’s actual duty or installation conditions.

Keep technical acceptability separate from commercial treatment

An optional price can make the commercial difference visible without resolving whether the option is suitable. Record the technical decision needed and the party responsible for it separately from any price adjustment, programme assumption or purchasing instruction.

Make documentation and approval assumptions explicit

Identify which drawings, calculations, product documents or certificates the offer assumes will be provided by each party. Distinguish preparation of a document from its review or approval. Do not turn “documentation included” into a statement that a design or equipment choice is already accepted.

DNV’s public newbuilding plan-approval guidance describes a separate review process for design documentation. That distinction matters when reading a bid: an owner–bidder clarification is not itself class approval. The actual class, flag and design requirements must be established for the intended vessel; this guide does not prescribe a universal submission list.

Build a clarification register that can be closed by evidence

Use one reference for each technical issue. A useful entry connects the enquiry requirement, offered position and eventual answer without hiding the history.

  • Specification item and source-document revision.
  • Bidder’s offered wording and the type of difference.
  • The precise question or additional document requested.
  • The owner, designer, bidder or supplier responsible for the next response.
  • The technical decision, unresolved condition and supporting reference.
  • The revised specification, schedule or offer in which the outcome is recorded.

A meeting discussion can advance an issue without closing it. Keep it open until the agreed response and its consequences are traceable. If the answer changes another system or supplied item, give that dependency its own follow-up rather than closing only the original row.

Reconcile the selected position before relying on the offer

Review the clarification outcomes against the final technical documents being carried forward. Remove ambiguity between accepted changes, rejected alternatives and questions that remain unresolved. Retain superseded responses as history so that a later equipment order does not accidentally use an earlier assumption.

Gisan’s newbuilding service scope identifies vessel types and the information needed for an initial discussion. It does not establish current order acceptance, a specific design solution or a delivery programme. Share the vessel brief, the actual specification issue and the unresolved bid items through Gisan Shipyard’s technical enquiry page so those questions can be considered against a defined project.