NDT Reporting Software for Shipyards: IACS and Class Society Format Requirements

A shipyard report has two readers, and they don't want the same thing

An NDT report written for a refinery or a fabrication shop typically has one primary audience: the client's inspection or quality engineer, who's checking it against a purchase order and a code. A shipyard NDT report has two audiences reading it for different reasons at the same time. The yard's own quality department needs it to close out a work package and release the next stage of construction. The classification society surveyor assigned to the vessel needs it to satisfy the survey requirements under whichever society's rules the ship is being built or repaired to — American Bureau of Shipping (ABS), DNV, Lloyd's Register (LR), Bureau Veritas (BV), ClassNK, or another IACS member — and that surveyor's acceptance of the report is a condition of the ship's classification, not a formality.

Get the format wrong for the surveyor, even when the underlying inspection was performed correctly, and the report gets kicked back — which on a construction schedule with steel erection sequencing tied to weld acceptance can mean idle crews waiting on paperwork rather than idle crews waiting on inspection results. This is a genuinely different failure mode than most industrial NDT work, where a report revision is an annoyance. On a build schedule, it's a critical-path problem.

Why one format doesn't fit five class societies

The International Association of Classification Societies (IACS) publishes Unified Requirements that establish a common technical floor across its member societies — UR W-series requirements touch welding and NDT expectations for hull construction, for instance — but each individual class society still issues its own rules, its own survey documentation formats, and its own expectations for how NDT results get presented and referenced back to survey items. A report format that satisfies an ABS surveyor's checklist isn't automatically formatted the way a DNV or Lloyd's Register surveyor expects to see the same information, even when the underlying technical content — a UT scan of a butt weld, evaluated against a defect acceptance table — is functionally identical.

Yards that work across multiple class societies, or repair yards that service vessels classed under whichever society the shipowner originally chose, end up needing report formats that can flex to each society's documentation conventions without changing the underlying inspection data or acceptance criteria being applied. That's a template management problem layered on top of an already complex technical one, and it's one of the clearest cases where a genuine reporting platform earns its keep over a folder of Word documents — the underlying inspection record stays consistent while the presentation layer adapts to whichever society is reviewing it.

Joint numbering off the structural drawing, not an internal scheme

One of the most consistent field-level mistakes on shipyard NDT work is treating weld joint identification the way an industrial inspection company treats it elsewhere — an internally generated ID that makes sense to the inspection crew but has no direct relationship to how the yard or the surveyor references that joint. Shipyard NDT reports need joint identification tied directly to the vessel's structural drawings and block/unit numbering — the same numbering the yard's production department, the classification surveyor, and the owner's representative are all using to track that specific weld through construction. A report that says "Weld 14" without cross-referencing it to the structural drawing's joint callout creates ambiguity that someone has to resolve manually later, usually the exact person with the least time to do it: a surveyor trying to close out a survey item before a launch date.

This gets more complicated on repair and conversion work, where the vessel's as-built drawings may not perfectly match current structure after prior repairs, and the report needs to reconcile which drawing revision the joint numbering is actually keyed to.

IACS Unified Requirements as the common floor

Even with format variation between societies, the IACS Unified Requirements give inspection companies working shipyard contracts a reasonably stable technical baseline to design a reporting system around: minimum NDT extent requirements tied to weld category and location on the hull, acceptance criteria expectations, and documentation content that has to be present regardless of which society is surveying. Building the core of a reporting template around that common floor, then layering each class society's specific presentation requirements on top — the same core-plus-variant structure that makes sense for any multi-client template library — means the technical substance of the report doesn't have to be rebuilt from scratch every time a yard picks up a contract under a different society.

Surveyor witness and hold points: what the report needs to prove happened

A meaningful share of shipyard NDT work is performed as a witnessed or hold-point examination — the classification surveyor is present, or has to be notified and given the opportunity to be present, before certain welds can be finally accepted. The report needs to capture not just the technical result but the administrative fact of the hold point: whether the surveyor witnessed the examination, waived attendance, or reviewed it after the fact, along with the surveyor's own sign-off or stamp where the society's procedures call for it. Reporting workflows that only have a field for "technician" and "reviewer" and nowhere to capture surveyor involvement are missing a field that shipyard clients will ask about specifically, because it's often the difference between a report the surveyor will accept without question and one that triggers a follow-up query.

Naval and government work: a stricter cousin of commercial class rules

Shipyards doing U.S. Navy or other government vessel work operate under a materially different — and generally stricter — documentation regime than commercial classification societies. NAVSEA technical requirements and standards like MIL-STD-2132 for NDT of ship hull welds impose specific personnel qualification, procedure, and documentation requirements that don't map one-to-one onto commercial ABS or DNV expectations, even for conceptually similar UT or MT work. A yard doing both commercial and naval work genuinely needs two distinct sets of reporting requirements running in parallel, not a single format stretched to cover both — attempting to force naval documentation into a commercial class society template (or vice versa) tends to satisfy neither reviewer fully.

Retention and repair history across a ship's life

A vessel's classification survey cycle — annual, intermediate, and special (renewal) surveys, typically on a five-year special survey cycle — means NDT records generated during original construction get referenced again years or decades later, when a surveyor doing a special survey wants to see the original hull thickness baseline to compare against current in-service readings, or when a repair yard needs to know what was found and repaired at the same location during a prior dry-docking. That means shipyard NDT reports need retention and retrieval that spans a vessel's entire service life, not just the construction or repair contract period — a very different retention horizon than most industrial inspection work, and one that argues strongly for structured, searchable digital records over paper files that may or may not survive a change of shipyard ownership or a records-room flood.

Reporting systems that tie records to a persistent vessel/hull identifier — rather than an internal job number that means nothing once the contract closes — make it possible to actually answer the question a surveyor asks fifteen years later: what did the original construction NDT show at this exact frame and joint number, and has anything changed since.

Dry-docking and repair work: reconciling historical records across owners

Repair yards face a specific version of this problem that new-construction yards don't: a vessel arriving for dry-docking or repair carries an inspection history that was generated by a different yard, possibly under a different classification society at the time, possibly using joint numbering conventions that don't match the vessel's current structural drawings if the ship has been modified or re-classed since original construction. A repair yard's NDT reports need to reference the correct current structural drawing and joint numbering, while ideally still being able to note where a joint corresponds to a prior repair or an original construction defect that was accepted under a now-superseded criteria set. Getting this wrong — reporting a repair weld under a joint number that doesn't match what the current classification society survey record expects — creates exactly the kind of ambiguity that turns a routine repair survey into a drawn-out documentation dispute with the surveyor.

This is also where owner-supplied history matters: a shipowner switching repair yards, or a vessel changing class society, should be able to hand over prior NDT records in a form the new yard can actually use, rather than a stack of PDFs in an unfamiliar format that takes days to reconcile against current drawings before the first new scan can even be properly referenced.

Sequencing NDT against coating and outfitting schedules

Shipyard NDT doesn't happen in isolation from the rest of the build or repair schedule, and the report needs to reflect where in that sequence the examination occurred — because acceptance often has downstream consequences tied to timing. A weld accepted by NDT before coating application is a very different documentation situation from one where coating has already been applied and needs to be removed for access, and reports need to clearly note surface condition and coating status at the time of examination, since a surveyor reviewing the record later may need to understand whether a repair (if one was needed) required coating rework as a consequence. Yards running tight outfitting schedules also need NDT reports finalized fast enough that they don't become the blocking item holding up the next trade's access to the same area — which is as much a reporting turnaround problem as it is a scheduling one, and another reason status visibility for the yard's production planners matters as much as the final technical content.

Multi-society yards: the reality of a mixed order book

A yard's own order book rarely sits neatly under one classification society for long. A commercial yard might have an ABS-classed tanker on one berth and a DNV-classed bulk carrier on the next, each with their own surveyor visiting on their own schedule, and the inspection company servicing both needs to be able to switch between report formats correctly without the risk of a technician grabbing the wrong template under time pressure and generating a DNV-format report for an ABS-surveyed vessel. This is a genuine, recurring field error in yards without disciplined template management — usually caught by the surveyor rather than internally, which is the worse place to catch it. Reporting systems that tie the correct template to the specific vessel and its classification society automatically, based on the job record rather than relying on a technician's memory of which format goes with which ship, remove this specific and entirely avoidable failure mode.

Photographic and visual documentation standards vary by society too

Beyond the data fields themselves, class societies differ in what they expect from photographic documentation accompanying an NDT report — some surveyors expect reference photographs showing the weld location relative to a structural feature for every examined joint, others are satisfied with photographs only for joints with recorded indications. Getting this wrong in either direction creates friction: too little photographic documentation triggers a surveyor query, too much becomes an unwieldy report that's harder for the surveyor to review efficiently during a site visit with a full day of other survey items still ahead of them. Building the photographic documentation requirement into the class-specific template, rather than leaving it to individual technician judgment on-site, keeps this consistent across a yard's full crew roster.

Handling non-destructive re-examination after repair

When an initial examination finds a rejectable indication and a repair is made, the report needs to document both the original finding and the subsequent re-examination as clearly linked records — the same joint, before and after repair, with the repair itself referenced by whatever weld repair procedure and traveler documentation the yard uses internally. Class societies generally expect to see this linkage explicitly, not as two disconnected reports that happen to reference the same joint number with no stated relationship between them. A reporting system that structurally links a re-examination record back to the original finding it's clearing — rather than treating each examination as an independent event — makes this relationship obvious to a surveyor reviewing the sequence later, without requiring them to piece it together from separate documents.

What to build for before the next class society contract lands

Yards and inspection companies serving shipyard clients are best served by building their reporting structure around the IACS common floor first, then adding class-society-specific presentation variants as contracts require them — rather than building a bespoke format for the first society they work with and trying to retrofit it later. Pairing that structure with disciplined joint numbering tied to structural drawings, explicit surveyor witness fields, and long-horizon retention tied to a persistent vessel identifier covers the specific ways shipyard reporting diverges from standard industrial NDT work — and keeps a hull weld report doing its actual job: satisfying the yard's production schedule and the surveyor's classification requirements at the same time, without a second round of paperwork.

Atlantis NDT Products & Services

Atlantis NDT pairs field expertise with software: NDT inspection management software — Atlantis ERP, a digital twin platform for asset integrity, and NDT reporting software. Build your team with NDT training & certification (ASNT SNT-TC-1A) and ASNT certification pathways, or bring in ASNT Level III consulting. Affordable, accessible, fully customizable — book a free consultation.