ASNT Level III audit support for refining inspection programmes

An audit of a refinery NDT programme is sampled downward. The auditor picks one entry in the mechanical integrity record and pulls the chain behind it: the reading, the technician, the procedure revision, the calibration, the written practice. Atlantis supplies the NDT technical authority that keeps that chain intact and represents it on technical questions during the audit itself.

Audit exposure in refining rarely comes from a missing inspection. It comes from an inspection that was performed and cannot be evidenced. A thickness reading exists in the integrity system, but the condition monitoring location it belongs to was renumbered two turnarounds ago; the technician who took it holds a certificate whose examination records were never transferred when the contractor changed; the procedure cited on the report is a revision that no longer exists in the controlled file. Nothing was done badly. The chain simply broke. The Level III scope that fixes this is narrow and specific: the written practice, procedure development and qualification, certification of personnel within that practice, independent review of data before it enters the integrity record, and answering technical questions in the audit room. It is not the inspector of record role and it is not a process safety management audit.

Source: Sources: OSHA 29 CFR 1910.119(j) mechanical integrity and 1910.119(d) process safety information; API 510, API 570 and API 653 inspection codes; API RP 578 material verification; API RP 580 and 581 risk-based inspection; ASNT SNT-TC-1A and ANSI/ASNT CP-189 for personnel qualification; ASME Section V; ISO 9712 where an employer-based scheme is not used.

Technically reviewed by Anoop Rayavarapu — ASNT NDT Level III (UT, RT, MT, PT, VT, ET) · API 653 · ISO 9001:2015 Lead Auditor
What an auditor samples in a refinery NDT programme, and the evidence that has to exist
Sampled itemEvidence requestedTypical failureWhere it is owned
Written practiceCurrent approved revision, naming the methods and levels actually in use and the edition of SNT-TC-1A it followsPractice follows one edition while certificates in the file were issued under anotherEmployer of the NDT personnel, approved by the Level III
Personnel certificationTraining hours, experience log, general, specific and practical examination records, current vision test, Level III approvalCertificate present, examination records absent, vision test lapsed mid-contractEmployer, administered by the Level III
NDT procedureApproved procedure with essential variables, demonstration where required, and the exact revision cited on the reportReport cites revision 2; only revision 3 exists in the controlled fileNDT contractor's Level III
Field dataReadings traceable to a condition monitoring location, instrument serial, calibration block and technicianReadings with no CML identity, or a CML renumbered between turnaroundsInspection contractor, accepted by the owner
CalibrationInstrument certificates and reference block traceability valid on the date of examinationBlock certificate expired between mobilisation and the readingNDT contractor
Data reviewSigned evaluation against acceptance criteria before results enter the integrity recordData loaded into the system with no independent evaluation step recordedOwner, supported by independent review
Turnaround close-outPackage closed per item with reports, dispositioned deviations and repair re-examinationRepairs done on the final night, re-examination logged after the unit was boxed upOwner's turnaround team
Ownership as shown is the common refining arrangement. The inspection record for pressure equipment under API 510, 570 and 653 remains with the owner-user and its authorised inspector, not with the NDT Level III.

Which audit are you actually facing

The word audit covers several very different events in a refinery, and preparing for the wrong one wastes the preparation. A customer or client audit of your NDT contractor samples the work performed on their equipment. A certification body audit against ISO 9001, ISO/IEC 17020 or ISO/IEC 17025 samples the management system, impartiality and demonstrated technical competence. A regulatory inspection under the OSHA process safety management standard samples the mechanical integrity element and asks what recognised and generally accepted good engineering practice the programme follows. An insurer or jurisdictional inspection asks narrower questions about specific equipment.

Each of those samples differently. A regulator asks what your written procedures say and then asks for evidence you followed them. An accreditation body asks how you know your personnel are competent and how you keep that judgement independent of commercial pressure. A client asks what you did on their unit, on which dates, and against which revision of their specification. The evidence overlaps heavily, but the narrative, the sampling logic and the room dynamics do not.

Establishing the audit type and its scope before preparing is the first hour of any engagement, because it decides what gets pulled and in what order. Where the technical questions will centre on NDT method, procedure adequacy and personnel qualification, that is the ground ASNT Level III consulting covers, and it is a different exercise from preparing the management system evidence that a lead auditor will want.

How an auditor samples: from one reading back to the written practice

Experienced auditors do not read a programme top down; they sample it bottom up. They open the equipment list, pick a vessel or a circuit, ask for the most recent inspection, and then start pulling. Which report is this? Which procedure does it cite, and by revision? Who performed it, and what qualifies them? What instrument was used, was it in calibration on that date, and against which reference block? Under whose written practice was the technician certified, and what edition does that practice follow?

Each question exposes a link, and each link must name the one below it correctly. The auditor is not looking for perfection; they are looking for whether the chain holds under a random pull. Two or three complete chains, taken from different methods and different contractors, produce a far more reliable picture than reading the quality manual cover to cover. It also means preparation that polishes the top-level documents while leaving the links untested is preparation aimed at the wrong target.

The behaviour to expect when a chain breaks is expansion. One report citing a superseded procedure revision is a finding on one report. It is also a reason to pull ten more, and if two of those break as well the finding is written against the control system rather than the document, which is a materially worse outcome with a materially larger corrective action attached.

The evidence chain, link by link

The chain in a refinery NDT programme runs in a predictable order. The written practice authorises the certification scheme. The certification record qualifies the individual for a method and a level. The procedure, approved by the Level III, defines how the examination is performed and what its essential variables are. The technique sheet or report records what was actually done on the day. The calibration record proves the instrument and reference standards were valid at that moment. The evaluation records that results were compared against the correct acceptance criteria. Only then does a number belong in the integrity record.

Most programmes hold seven of those eight links and lose one, and it is usually the evaluation step. Data arrives, gets loaded, and a corrosion rate is calculated from it without any recorded step in which a competent person judged whether the readings were valid. That gap is invisible until an auditor asks who reviewed a specific anomalous reading, and it is the reason independent NDT report validation exists as a discrete service rather than as an assumed part of data acquisition.

The other frequent break is between the field data and the asset. A thickness reading with no condition monitoring location identity is not evidence of anything, and a CML renumbered during a system migration silently destroys the trend it belonged to. Where the integrity record and the inspection data live in separate systems, that reconciliation should be a scheduled control rather than an annual discovery, which is one of the practical reasons owners consolidate on mechanical integrity software instead of spreadsheets and a document library.

Findings that recur in refining

The written practice edition mismatch leads the list. The practice cites one edition of SNT-TC-1A, while certificates were issued under another with different training hours, experience requirements or examination structure. Close behind it are missing examination papers behind valid-looking certificates, vision tests that lapsed part way through a multi-year contract, and Level III approval signatures from a Level III who is no longer employed, with no documented transfer of the certification authority.

On the data side, the recurring findings are readings with no instrument serial, calibration blocks whose certification expired mid-campaign, and procedure revisions cited on reports that no longer exist in the controlled file. Then there is the quieter one: a corrosion rate that drives a next inspection date, computed from a reading that was later found invalid and never recomputed, so the interval in the system is defensible only by accident.

Contractor transitions concentrate all of these. When an NDT contract changes hands, personnel records, procedure files and calibration histories often do not transfer cleanly, and the new contractor's written practice is not the one under which the previous four years of data were produced. Auditors are alert to that boundary and sample across it deliberately. Owners who keep their own copy of the personnel and procedure evidence, rather than relying on the contractor to hold it, come through that transition without a finding.

What the Level III signs, and what he does not

The Level III signature carries specific weight and specific limits. The Level III approves the written practice, develops and approves NDT procedures and their qualification records, administers and approves the certification of Level I and Level II personnel within that practice, performs technical evaluations, and conducts independent review of examination data. In an audit, the Level III answers technical questions: why this method, why this procedure, why this acceptance level, why this technician was qualified for this examination.

What the Level III does not do matters just as much. Atlantis is not the API inspector of record for your equipment and does not sign the inspection record that an API 510, 570 or 653 inspector owns; that role belongs to the owner-user's authorised inspector. Atlantis is not a process safety management auditor and does not sign off the mechanical integrity element. And Atlantis does not sell API 510, 570 or 653 inspector certification training, which is administered through API's own programme. What Atlantis does provide is NDT method training and certification support to SNT-TC-1A and ISO 9712 through NDT training, which is the personnel side of the same evidence chain.

There is an independence dimension as well. The person who acquired data should not be the sole authority evaluating it, and where the same organisation performs and reviews the work, the reviewer's independence has to be demonstrable in the organisational arrangement, not merely asserted. That distinction is the first thing an ISO/IEC 17020 assessor tests, and it is worth resolving before an assessor raises it.

Gap review before the audit, remediation after the finding

A gap review is run the way the auditor will run it. Pull two or three complete chains per method in use, from the integrity record back to the written practice, and record where each one breaks. Check the written practice against the certificates actually in the file. Confirm procedure revisions cited on a sample of recent reports exist and are current. Test calibration validity on the date of a sampled examination, not on today's date. Produce a register with each gap, its owner, an action and a date.

Remediation after a finding is the same technical work performed under conditions you no longer control. The extent is set by the auditor rather than by you, the deadline is theirs, the sample has usually been widened by whatever triggered the finding, and re-examination of already accepted work is frequently part of the corrective action. There is also a reporting obligation attached, which the voluntary version does not carry.

The arithmetic favours the early version by a wide margin, and the practical trigger points are known in advance: a contractor change, a written practice revision, an upcoming certification body surveillance visit, a new client audit programme, or the twelve weeks before a major turnaround. Any one of those is a sensible moment to book the review rather than to hope. Atlantis engagements here are scoped to the programme rather than sold as a fixed package, and a consultation is the starting point.

Turnaround documentation under audit conditions

A turnaround compresses a year of inspection into a fortnight, and it inverts the normal relationship between work and paperwork. Scaffolding comes down on a schedule, insulation is reinstated on a schedule, and inspection access disappears whether or not the examination was completed. The documentation is therefore written under the worst possible conditions, at the end, by people who have been working nights.

The predictable damage follows a pattern. Repairs authorised in the last forty-eight hours get executed correctly and their re-examination reports arrive after the unit is closed. Deviations get dispositioned verbally on the deck and never written up. Additional examinations ordered on discovery are performed but never linked back to the anomaly that prompted them. Six months later the package is opened by an auditor and none of that context can be reconstructed, even though every physical task was done properly.

The controls that work are all pre-agreed rather than improvised: report templates fixed before mobilisation, a nightly close-out gate where each completed item's package is checked rather than accumulated, a live deviation register with a named approver, and a repair log that will not close without its re-examination reference. Those are gating rules, which means they need to live in the system that issues and closes the work rather than in a supervisor's discipline, which is the practical case for running turnaround inspection through inspection management software.

Where Atlantis fits, and where it does not

Atlantis Inspection Services supplies NDT technical authority to refining operators and their inspection contractors. That means writing and maintaining the written practice, developing and qualifying NDT procedures, certifying personnel within the practice, performing independent review of examination data before it enters the integrity record, and attending audits to answer technical questions on method, procedure and personnel. Anoop Rayavarapu holds ASNT NDT Level III certification in multiple methods and is an API 653 Authorized Inspector, and the practice operates from Houston and Hyderabad.

The boundaries are stated deliberately and should be stated to your auditor too. Atlantis is not a process safety management auditor. Atlantis is not the API inspector of record for your pressure equipment, fixed piping or storage tanks. Atlantis does not deliver API 510, 570 or 653 inspector certification training. Confusion on any of those points creates a bigger audit problem than the one it was meant to solve, because it blurs the accountability the auditor is trying to establish.

Engagement usually starts with a documented gap review scoped to the methods and contractors actually in use, delivered as a prioritised register you can act on and, if you choose, hand to the auditor as evidence of self-assessment. The service is affordable, accessible and fully customisable to the size of the programme. Request a consultation and bring your written practice, one recent NDT report and the equipment list; the first two chains usually tell the whole story.

Turnaround close-out packages: the audit that happens after the plant has already restarted

A refinery turnaround audit has a characteristic that other audits do not: by the time it happens, the unit is usually back in service. That timing changes what the audit can and cannot do. It cannot re-inspect anything — the vessel is closed, insulated, and running. It can only test whether the documentation package generated during the turnaround window supports the decisions that were made, which means the close-out package is being asked to do all the evidentiary work that direct re-examination would otherwise do.

The recurring gap is disposition trail rather than raw data. Turnaround inspection generates a large volume of readings under significant schedule pressure, and the readings themselves are usually retained. What frequently is not retained, or is retained inconsistently, is the disposition reasoning for each anomaly — who reviewed a below-minimum reading, what fitness-for-service basis was applied, and who signed the accept-as-is decision before the vessel was closed. An auditor reconstructing the turnaround after the fact needs that chain intact for every anomaly, not just the ones that made it into the final summary report.

Where Atlantis is engaged for turnaround audit support, the useful work is usually completed before the audit happens: reviewing the close-out package against the anomaly log while records and the people who wrote them are still accessible, rather than after the plant has moved on and the turnaround team has dispersed to the next site.

How does an auditor sample a refinery NDT programme?

The auditor rarely starts at the top. They pick one item from the equipment list, ask for its last inspection, then work backwards from the report to the procedure, the personnel certification, the instrument calibration and the written practice, checking that each link names the one below it correctly. Two or three complete chains tell them more about programme health than a hundred documents read in isolation, and a single break in one chain triggers a widened sample.

Which document fails audit most often?

The written practice, and it fails in a specific way. The practice on the shelf references one edition of SNT-TC-1A while the certificates in the file were issued under a different edition with different experience and examination requirements. Nobody notices because both documents look correct on their own. A certificate is only valid inside the practice it was issued under, so an edition mismatch puts every certification in the file into question at once.

What does the Level III sign, and what does he not sign?

The Level III signs the written practice, NDT procedures and their qualification records, personnel certifications issued within that practice, and technical evaluations or independent data reviews carried out under it. The Level III does not sign the inspection record of an API 510, 570 or 653 inspector, does not act as the owner-user, and does not sign off the mechanical integrity element of a process safety management programme. Keeping those signatures separate is what makes each of them defensible.

How does a gap review differ from remediation after a finding?

A gap review is voluntary, sampled, and produces a prioritised list with owners and dates before anyone external is looking. Remediation after a finding is compulsory, scoped by the auditor rather than by you, usually carries a deadline measured in weeks, and frequently requires re-examination of work already accepted. The technical content can be identical. The cost is not, because remediation happens under an extent that has already been widened by the finding that triggered it.

Why do turnaround packages attract audit findings?

Because a turnaround compresses months of inspection into days, and the documentation is written last. Repairs authorised on the final night get executed, but the re-examination report lands after the unit is boxed up, the deviation is dispositioned verbally, and the package closes with a gap nobody can reconstruct six months later. Auditors know the pattern and sample turnaround close-out packages preferentially for exactly that reason.

What is Atlantis responsible for in an audit?

Atlantis provides NDT technical authority: written practice, procedure development and qualification, personnel certification within the practice, independent review of inspection data, and representation on technical questions during an audit. Atlantis is not a process safety management auditor, is not the API inspector of record for your equipment, and does not sell API 510, 570 or 653 inspector certification training. Those roles belong to the owner-user and to API respectively, and the separation is deliberate.

Request a consultation