Site leadership and quality · Audit

Preparing a crew’s records for an owner QA audit

Have four sets of records complete and cross-referenced: personnel (qualifications, continuity, training), weld traceability (maps, logs, materials), examinations and tests, and nonconformances with their closure. Auditors usually pick a few welds and trace them in both directions, so prepare by doing the same trace yourself before they arrive.

What the audit samples

Records an owner QA audit commonly reviews (the audit plan decides)
AreaRecordsTypical question
PersonnelWelder and operator qualifications, continuity records, inspector qualifications, site trainingWas this welder qualified for this weld on this date?
ProceduresWPS and PQR, weld schedules, owner-approved proceduresWhich procedure covers this joint, and is it approved?
TraceabilityWeld maps, weld logs, heat numbers, material certificatesShow me the material certificate for this weld.
Examination and testVisual and borescope records, test recordsWhere is the borescope image for weld 47?
NonconformanceNCR register, dispositions, closure evidenceHow was this NCR closed, and who approved it?
CalibrationOxygen analysers, gauges, orbital equipment as requiredWas the analyser calibrated when this weld was made?

Preparing in the week before

  1. Read the audit plan or ask the owner which areas and systems will be covered.
  2. Pick five to ten welds at random and trace each from the map to the log, welder qualification, material certificate, examination record and image.
  3. Fix gaps honestly: record late entries as late with the date, do not back-date.
  4. Check the NCR register: each one either closed with evidence or open with a plan.
  5. Make sure the people who keep the records will be available to answer questions.
  6. Brief the foreman and crew that auditors may ask them about procedures at the workface.

On the day, have one person, usually the QA/QC lead, collect every document request in a list with the time it was asked and answered. It keeps the audit orderly and shows the auditor that requests are tracked rather than lost.

Where the owner and code decide

The owner’s audit scope comes from their quality requirements and contract rights; the code sets the records that must exist. Your QA manager decides how findings are answered and by when. If an auditor asks for something your contract does not require, record the request and agree it through your QA manager rather than improvising.

After the audit

Answer each finding through your QA manager, with the cause, the correction and what will stop it recurring, and track it to closure like any other corrective action. Share findings that relate to the crew’s work with the foreman and crew, explained in a language they understand. If a finding questions a welder’s qualification or a weld’s acceptance, treat it through your normal NCR and qualification processes, not as a one-off fix for the auditor.

Keeping it from being a crisis

The audit is easy when records are kept daily (weld maps and logs) and borescope images are filed by weld number (borescope records). New crews need particular attention to qualification and continuity evidence (qualification continuity), since their records start on your site.

Frequently asked questions

Should crew members attend the audit?

Only if the auditor asks to talk to them, usually at the workface. Make sure they know they can answer honestly and refer questions on records to QA/QC.

What if we find a missing record before the audit?

Raise it through your own process, correct what can be corrected and be open about it. A gap you found and are fixing is usually viewed better than one the auditor finds.

Do welders’ Korean certificates need to be in the audit file?

Keep them as background if your QA manager wants them. The auditor will mainly look for the qualifications made under your own procedures.

Have a fab scope that needs these trades?

Requests are in preview: you can fill in the request form, but it does not submit yet. Email WELDK with your roles, site country and start window.