Beyond Credentials: What Welding Inspectors Should and Shouldn’t Do

In this trade, confidence can get mistaken for competence. You see it when someone tries to win the discussion by quoting clause numbers rather than applying the requirements to the work in front of them. That is not how I approach inspection. I am not an engineer, and I do not use the code book as a debating tool. My responsibility is to verify conformance to the governing code, contract documents, and approved procedures. I’m a welder first, so as a CWI, I level with welders but within the limits of the applicable requirements and acceptance criteria. 

Here is the part that many new inspectors learn after certification. The wallet card does not teach you how to run a job in the field. It does not teach you how to write reports that hold up to review, how to document engineering dispositions, or how to handle a request to sign off outside your qualification. Those skills come from structured training, supervision, and repetition in real production conditions.

The Crucial Role of Mentorship

New Certified Welding Inspectors (CWIs) often have strong test preparation but limited exposure to production documentation, inspection hold points, and the day-to-day decisions that must be supported in writing. Without a mentor, a new inspector can miss requirements, misapply acceptance criteria, or create weak records. Any of those can compromise the project and the inspector’s credibility.

Early in my career, experienced inspectors corrected my reports and my process before those mistakes became formal nonconformances or audit findings. That supervision mattered. My advice is direct. Find a mentor, and do not wait for a problem to force the relationship. If you are a senior CWI (SCWI), be intentional about mentoring because it reduces risk for the entire organization.

AWS B5.1 vs. QC1

A recurring technical mistake I see is confusion between AWS B5.1, Specification for the Qualification of Welding Inspectors, and QC1, Specification for AWS Certification of Welding Inspectors. The documents reference each other, so the mix-up is common.

• B5.1 addresses roles, responsibilities, and minimum competencies. I use it as a framework for training plans, task assignment, and qualification matrices. It is not a certification document. It describes what a person should be trained to do and under what level of oversight.
• QC1 governs AWS certification for Certified Associate Welding Inspectors (CAWIs), CWIs, and SCWIs. It defines eligibility, renewal, and the rules for representing your credential. I treat QC1 as a boundary document. It clarifies what the certification does and does not authorize in terms of scope and representation.

B5.1 supports employer training and task assignment across Associate Welding Inspector (AWI), Welding Inspector (WI), and Senior WI (SWI) role descriptions. QC1 defines your certification status. When the two are blended, an inspector can assume they are “certified to do” a task that requires employer authorization, additional training, supervision, or separate certification under a written practice.

B5.1 as a Practical Training Blueprint

If you manage an inspection program or if you are trying to standardize practice in a small shop, B5.1 is a useful blueprint. Auditors ask how employees and inspectors are trained and how competence is verified. B5.1 gives a baseline for knowledge, skills, and tasks by role. When you align internal expectations with a published AWS framework, you improve consistency and defensibility.

Some organizations resist “following a book,” preferring internal practices or informal expectations. Audits do not reward that mindset. Using a publicly available, widely understood standard removes ambiguity and gives both the organization and the auditor a common reference point.

Another advantage is access. B5.1 is available at no cost. That matters because it lowers the barrier for building a formal training plan, a task qualification record, and a documented progression model.

B5.1 also reflects an operational reality. A person’s demonstrated skill can outpace their title. If the organization determines a person has the capability, it can assign higher-level tasks. For example, some CWI job descriptions now include bolting, coatings, and sometimes even concrete inspection. As a CWI, I have even been asked to perform bolting inspection.

B5.1 makes it clear that the employer remains the final decision-maker. Qualification to the standard does not automatically make a person suitable for every assignment, and it does not limit the employer’s authority to assign work. In practice, that means inspectors may be asked to take on responsibilities outside their primary discipline, and it becomes important to recognize when you may be out of your depth and need help or 
clarification.

Ethics in Action: What CWIs Must Not Do

When people ask me what a CWI “is allowed” to do, I usually flip it around. The career-saving question is, what should I not do?

1. Don’t act like an engineer. A CWI should not change welding procedure specifications (WPSs) or procedure qualification records (PQRs) without qualification. Their role is to verify compliance, not to redesign the process. Substituting filler metals, tweaking essential variables without qualification, or approving procedures outside their qualified range crosses a bright ethical line.

Do not assume authority you do not have. Only the engineer of record, or other designated authority, can make design decisions and code interpretations that change requirements. If I need a disposition, I get clarification and make sure it’s documented.

2. Do not perform nondestructive testing (NDT) that you are not certified to perform. A CWI credential does not qualify a person for penetrant testing, magnetic particle testing, ultrasonic testing, radiographic testing, or other NDT methods unless the individual meets the method requirements under the applicable standard and the employer’s written practice. When a job requires NDT, I verify technician qualification records and that the procedure and equipment meet the project requirements.

3. Do not ignore documentation. Inspection decisions must be traceable. I keep procedures, inspection reports, correspondence, photographs, and approvals organized. If a dispute arises years later, the record is what supports what was inspected, what was accepted or rejected, and why. If it isn’t documented, it didn’t happen. Paperwork is part of the job.

Verify before You Call Nonconformance

Passing a CWI exam on one code does not translate to technical competence across all codes. Moving from API work to AWS D1.1, Structural Welding Code — Steel, or into aerospace requirements such as D17.1, Specification for Fusion Welding for Aerospace Applications, requires deliberate study. These differences are not limited to the codes themselves — they extend to how procedures are written, qualified, and applied. Some codes provide detailed acceptance criteria. Others defer key decisions to engineering judgment, which increases the need for formal interpretations and written dispositions. A professional response is to pause, review the governing requirements, and then respond based on documented criteria.

That principle applies directly in the field, where the governing procedure is the immediate standard for acceptance. On a pipeline job, I once evaluated an in-service sleeve weld and saw a visible tempering (annealing) pass intended to slow cooling. My first reaction was that it was unacceptable. The qualified procedure allowed it. A welder told me to read the procedure, so I did. The takeaway is simple. The procedure controls, and the inspector must verify compliance with the approved procedure before calling a condition nonconforming.

Culture, Confidence, and Saying “No”

Inspection work requires technical confidence and procedural discipline. You have to be willing to stop work when acceptance criteria are not met. You also have to be willing to say “I do not know” when you need time to verify requirements. The inspectors who perform well over time are the ones who build training plans, seek competent review early, and maintain documentation that supports every acceptance decision.

A Career Worth the Discipline

The value of being a CWI is not quoting clause numbers. The value lies in the consistent application of acceptance criteria, documented decision-making, and disciplined control of scope. Use B5.1 to build training programs and task authorization, and use QC1 to define certification boundaries and representation rules. Decline work that requires qualifications you do not have. When you need to verify a requirement, stop and review the governing documents. Then document the basis for acceptance or rejection.

Those habits protect the inspector, and they improve quality outcomes for the entire project team.

This article is adapted from a presentation given by DAVID VIAR (viar18@att.net) at the Inspection Expo & Conference held February 3–4, 2026, in Austin, Tex.