NDT Reporting Software for Multi-Method Crews: UT, RT, MT, PT in One System

Why Multi-Method Crews Are the Norm on Real Jobs

Very few turnaround or new-construction scopes call for a single NDT method in isolation. A piping tie-in package might need RT or UT on the girth welds, MT on socket welds and fillet attachments, and PT on stainless steel or non-magnetic components in the same scope, all within the same few weeks of a shutdown window. A tank floor and shell inspection under API 653 typically combines UT thickness mapping with MT or PT on critical welds and settlement survey data. A shop that can staff and coordinate a genuinely multi-method crew — rather than subcontracting out whichever method it doesn't run in-house — wins more of this combined-scope work, and keeps more of the margin on each job. But running multiple methods well on the same project surfaces a coordination problem that single-method shops never have to solve: how do UT, RT, MT, and PT records for the same asset stay connected to each other instead of living in four separate, disconnected systems.

The Silo Problem

The default state for most shops that grew into multi-method work organically is four separate template lineages — a UT template built first because thickness surveys were the original bread-and-butter work, then MT and PT templates added later, often built by whoever happened to be around when that capability was added, sometimes years apart. Each template has its own idea of how to label a weld joint, its own asset ID convention, its own file naming pattern. A project manager trying to compile one client deliverable covering all four methods for a single vessel ends up manually cross-referencing weld numbers across four exports that don't agree with each other — the exact kind of reconciliation work that eats schedule buffer on a turnaround with a fixed back-to-service date, and the kind of work that's invisible on a bid but very visible on a project's actual margin once it's done.

A Shared Asset and Weld Register Fixes the Root Cause

The fix isn't a better spreadsheet macro to reconcile the exports faster — it's giving every method the same underlying reference data from the start. When UT, RT, MT, and PT reports all pull from one shared asset register and one shared weld or component numbering system, a project manager can query "every examination result for vessel V-204, all methods" and get a complete, internally consistent answer instead of stitching four inconsistent files together by hand. This also solves a subtler problem: a weld that failed UT and gets repaired, then re-examined by MT after the repair, needs its examination history linked across both methods and both events to tell a coherent story — something four disconnected systems structurally can't do well.

Method-Specific Fields That Still Need to Coexist

A shared register doesn't mean every method uses the same fields — each method has genuinely different essential variables that a unified system needs to capture correctly, not flatten into a lowest-common-denominator "results" box.

Ultrasonic Testing

Probe angle and frequency, calibration block ID and reference reflector, DAC or TCG curve parameters, transfer correction, scan coverage, and couplant type. For thickness mapping specifically, a full grid of point readings tied to a defined grid pattern on the component.

Radiographic Testing

Source type and activity or X-ray kV setting, source-to-film distance, exposure time, IQI type and achieved sensitivity, film or digital detector identification, and a shot map linking each exposure to a specific weld location.

Magnetic Particle Testing

Magnetization method (yoke, prod, or coil), current type and amperage, field direction and coverage in two directions, and the examination medium — wet fluorescent, dry powder, or visible.

Liquid Penetrant Testing

Penetrant type and batch, dwell time for both penetrant and developer, method (visible or fluorescent), and surface preparation and cleaning method.

A platform built specifically for NDT keeps these method-specific field sets intact and correctly structured while still tying every record back to the same shared asset and weld data — the opposite of a generic form builder that either forces every method into one oversimplified template or keeps them so separate they can't be queried together. Getting this balance right is a genuine design problem, not a checkbox: too much flattening loses the essential variables an auditor needs to see; too little shared structure recreates the same four-silo problem the unified system was supposed to solve in the first place.

Personnel Certification Tracking Across Methods

A technician might hold Level II certification in UT and PT but only Level I in MT, following the qualification and experience-hour requirements typical of an ASNT SNT-TC-1A-based written practice. On a combined-method crew, a system needs to track certification level per method per technician, and ideally prevent a report from being submitted under a method the technician isn't actually currently certified for at the level the report claims. This is a real risk on multi-method crews specifically, because a technician moving fluidly between methods across a shift is more likely to have a report auto-populate the wrong default certification level than a single-method technician who only ever works one method's paperwork. Tracking this correctly through certification records tied to the reporting platform closes a gap that a generic personnel spreadsheet, disconnected from the reporting software itself, doesn't catch until an audit.

Equipment and Calibration Tracking Across a Mixed Fleet

A multi-method crew brings a correspondingly larger and more varied equipment fleet into the field — UT flaw detectors and thickness gauges, a radiography source or digital detector array, MT yokes and current sources, PT penetrant and developer batches with their own shelf-life tracking. Each has its own calibration or certification interval, and a unified system needs to track all of it in one place rather than requiring the QA manager to check four separate spreadsheets before every job to confirm nothing is about to expire mid-turnaround. This is exactly the kind of cross-functional tracking an NDT-specific ERP is built to centralize, feeding calibration status directly into whichever method's report is being generated that day.

Crew Scheduling Gets More Complex, Not Less

Scheduling a multi-method crew across a turnaround means matching the right certification level to the right task on the right day, often shifting technicians between methods as the scope of work changes hour to hour — UT in the morning on a piping spool, MT in the afternoon on a repair weld once fabrication finishes it. A scheduling system disconnected from certification records risks assigning a technician to a task they're not currently certified for, simply because the person building the schedule didn't have real-time visibility into who holds what certification at what level. Integrating scheduling with the same certification and reporting data eliminates this class of error at the planning stage rather than catching it after the fact in a completed report.

A Realistic Combined-Scope Turnaround

Consider a Gulf Coast refinery unit turnaround with a piping tie-in package: sixty girth welds requiring RT, forty socket welds requiring MT, and a batch of stainless steel instrument connections requiring PT, all on a three-week schedule with a hard back-to-service date. A crew of eight technicians rotates across all three methods depending on daily fabrication progress. By the final week, the client's inspection engineer wants one consolidated report package covering every weld in the tie-in scope, organized by isometric drawing number, not by which method examined it. A shop running four disconnected systems spends the final days of the turnaround — exactly when schedule pressure is highest — manually assembling that package. A shop running a unified system with a shared asset and weld register generates it directly from data that was already structured correctly from the moment each technician submitted their report in the field.

The difference compounds further on the repair side. Several of the RT-examined girth welds in this scenario come back with rejectable indications requiring rework and re-examination. In a disconnected system, tracking which welds are in repair status, which have been re-shot, and which are cleared for final sign-off means someone maintaining a separate spreadsheet cross-referencing weld numbers against report file names — itself a source of the exact transposition errors structured systems are meant to eliminate. In a unified system, the weld's status updates against its single record in the shared register: repair initiated, re-examination scheduled, final disposition recorded, all visible to the project manager and the client's inspection engineer without anyone having to reconcile anything by hand.

What to Look for in a Unified Multi-Method System

• One shared asset and weld register that every method's reports reference, not four separate numbering conventions.
• Method-specific templates that capture each method's actual essential variables correctly, not a flattened generic form.
• Per-method certification tracking that can block a report from going out under a certification level the technician doesn't currently hold.
• Calibration and equipment tracking spanning the full mixed fleet, not siloed by method.
• Scheduling that has real-time visibility into certification status when assigning technicians to tasks.
• Report aggregation by asset, weld, or drawing number across all methods, generated directly from structured field data rather than assembled by hand at the end of a job.

Client-Side Data Expectations Are Rising

Owner-operators running mature risk-based inspection programs increasingly want structured digital data feeding directly into their own asset integrity systems, not a folder of method-specific PDFs they have to re-key by hand. A refinery inspection department managing thousands of components under an RBI program built around API 580/581 methodology needs UT thickness trend data, MT/PT weld examination history, and RT records to all reference the same component IDs the client's own system uses — which is only possible if the inspecting shop's internal data structure was built coherently across methods in the first place. A shop that can hand a client clean, structured, cross-method data that plugs directly into their existing systems has a real edge over one that hands back four inconsistent PDF exports and expects the client's engineers to reconcile them. This is also where multi-method reporting data connects naturally to a broader digital twin or asset integrity initiative on the client side — the inspection data is only as useful to that larger system as the structure it arrives in.

Cross-Training and the Certification Ladder

Shops building multi-method crews are usually also running an internal cross-training pipeline — a technician who came up through UT taking on MT or PT certification hours to become more valuable across a wider scope of work. A reporting and certification system that tracks hours, experience, and qualification progress per method in one place makes it far easier to see who's close to qualifying for the next level in a second or third method, and to staff upcoming turnarounds accordingly. Without that visibility, cross-training tends to happen informally and inconsistently, and a shop can find itself short-staffed in a specific method on a bid deadline simply because nobody had a clear picture of where each technician's qualification hours actually stood. Structured NDT training and certification tracking, tied to the same platform that generates the reports, turns this from a guessing game into a plannable pipeline.

Coordination Is the Actual Product

A multi-method crew's real competitive advantage isn't just having four certifications under one roof — it's being able to deliver a coherent, cross-method inspection record that a client's engineering team can actually use without doing the reconciliation work themselves. Reporting software that treats UT, RT, MT, and PT as one connected system rather than four separate products is what makes that advantage real instead of aspirational, and it's the difference between winning combined-scope work once and winning it repeatedly because the client's inspection department specifically trusts how the shop's data comes back to them. For a shop deciding whether to bid on its next combined-method scope, the reporting infrastructure question is worth answering before the bid goes out, not after the crew is already mobilized and discovering the gaps between methods in real time under schedule pressure.

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.