Building a Compliant and Functional AWS QC47 Quality Assurance System

The AWS Accredited Test Facility (ATF) program has undergone significant modernization. With the retirement of AWS QC4, Standard for Accreditation of Test Facilities for AWS Certified Welder Program, and QC7, Standard for AWS Certified Welders, along with the introduction of AWS QC⁴⁷, Specification for AWS Certification of Welders and Accreditation of Test Facilities, ATFs are now required to meet a unified, more rigorous standard for welder performance qualification. While AWS provides formal documentation and guidance, many facilities struggle with a practical challenge: How do you build a quality assurance (QA) system that satisfies QC⁴⁷ and performs reliably during an audit?

Having authored one of the earliest AWS QC⁴⁷ quality manuals (May ²⁰²⁵) — and subsequently developed three additional QC⁴⁷-compliant programs that have all passed AWS audits — I offer the following insight into the practical “how” behind creating a robust, audit-ready QA system.

Understanding the Foundation

The first step in developing a QC⁴⁷-compliant system is a disciplined review of the governing documents. Three resources form the backbone of the ATF QA system:

• AWS QC⁴⁷ – the primary specification governing welder performance qualification under the ATF program.
• AWS B⁵.⁴, Specification for the Qualification of Welder Test Facilities — defines facility-level requirements.
• AWS Quality Assurance System Audit Checklist — the tool AWS auditors use to evaluate compliance.

To build a compliant and functional system, each of these documents must be studied carefully. In my process, I first highlight all QC⁴⁷ requirements in yellow, then highlight all B⁵.⁴ requirements (also in yellow). Next, I review the AWS audit checklist and highlight each checklist question in blue, cross referencing it to the relevant QC⁴⁷ and B⁵.⁴ clauses.

This color-coded mapping ensures that every requirement and audit question is accounted for before a single page of the quality manual is written.

Structuring the Quality Manual: Aligning with QC47 Clause 10

AWS provides a QC⁴⁷ Quality Manual Guide, but I found that a more effective approach is to structure the manual to mirror Clause ¹⁰ of QC⁴⁷ directly. This creates a one-to-one relationship between the manual and the specification, making navigation intuitive for internal users and AWS auditors.

Example Table of Contents Structure

• Clause 1 – Welder Performance Qualification Quality Manual
• ¹.¹ Scope and Policy – Corresponds to QC^{47 10}.¹
• ¹.¹.¹ References – Corresponds to QC^{47 10}.¹.¹
• ¹.¹.² Quality Manual and Related Documents – Corresponds to QC^{47 10}.¹.²
• ¹.¹.³ Quality Policy Statement – Corresponds to QC^{47 10}.¹.³

This structure allows any clause in the manual — such as ¹.¹.² — to be instantly cross referenced to the corresponding QC⁴⁷ requirement by replacing the leading “¹” with “¹⁰,” resulting in ¹⁰.¹.². This method creates clarity, consistency, and traceability throughout the system.

Note that there are a few audit questions that come from other clauses. For example, Clause ¹¹.⁴.².¹ contains a requirement to address audit nonconformance reports (NCRs) within ³⁰ days. I added this requirement to my manual under clause ¹.¹.¹¹, which corresponds to QC⁴⁷ Clause ¹⁰.¹.¹¹ – Nonconformance and Corrective Actions.

Integrating the Audit Checklist into System Development

One of the most common pitfalls in developing an ATF quality manual is treating the audit checklist as an afterthought. In reality, the checklist should be integrated into the system from the beginning.

By cross referencing checklist questions to QC⁴⁷ and B⁵.⁴ during the initial review, the quality manual can be written in a way that directly answers each audit question. This prevents the need for later revisions and ensures that the system is complete, defensible, and aligned with AWS expectations.

This approach also simplifies internal audits. When the manual is built around the checklist, auditing the system becomes a matter of verifying that each documented process is implemented exactly as written.

Conducting Internal Audits

Before AWS assigns an auditor, the facility must conduct its own internal audit. This includes the following:

• Auditing the quality manual
• Auditing the quality assurance system
• Verifying compliance with QC⁴⁷, B⁵.⁴, and the audit checklist

Because the manual is already structured around the checklist and specification, the internal audit becomes straightforward. Any gaps can be identified and corrected before AWS conducts its formal review.

This proactive approach is one of the key reasons the programs I developed have consistently passed audits with outstanding results.

Designing a System That Works for You

While compliance is essential, the quality manual and quality assurance system must also be practical. They should support the daily operations of the ATF — not hinder them. AWS audit questions may evolve over time, but a well-designed system remains stable because it is built on clear requirements, documented processes, logical structure, and practical workflows.

The goal is not simply to pass an audit. The goal is to build a system that ensures consistent, repeatable, and defensible welder performance qualification testing.

Conclusion

Developing a QC⁴⁷-compliant quality assurance system is not merely a matter of filling out forms or copying templates. It requires a structured, methodical approach grounded in the governing documents and aligned with the AWS audit process. By cross referencing QC⁴⁷, B⁵.⁴, and the audit checklist; structuring the manual around Clause ¹⁰; and conducting thorough internal audits, ATFs can build systems that are compliant and operationally effective.

This approach has been proven through multiple successful audits and provides a clear, practical pathway for any facility seeking ATF accreditation under AWS QC⁴⁷.

DARYL PETERSON (daryl.peterson@outlook.com) is an AWS SCWI with WPQ1, WPQ2, and NDEC endorsements; a weld quality consultant; and owner of Weld Quality Services LLC, Gibsonton, Fla.