Can the fabricator's CWI accept their own work under AWS D1.1?

Yes. AWS D1.1 assigns the contractor primary responsibility for quality control, and the contractor's CWI has authority to accept work that meets the code's requirements. The owner's inspector is an additional oversight layer, not a replacement for contractor QC.

Does AWS D1.1 require the owner to provide an inspector?

AWS D1.1 does not mandate that the owner designate an authorized inspector. The standard assumes the owner will provide oversight if they want verification beyond the contractor's QC program. Many contracts specify this separately — often requiring a third-party CWI when the owner lacks in-house inspection capability.

Who resolves a dispute when the fabricator's CWI accepts a weld and the owner's inspector rejects it?

The engineer of record (EOR) has final technical authority under AWS D1.1. Neither inspector overrides the engineer. If the contractor and owner's inspector disagree, the dispute goes to the EOR for written disposition — accept as-is, repair to code, or repair to an engineer-approved alternative.

Can the same CWI serve as both the fabricator's QC inspector and the owner's inspector on the same project?

Generally no. The roles represent conflicting interests — the contractor has cost pressure; the owner has a safety interest in independent verification. Most quality programs and regulatory bodies prohibit dual-hat arrangements on the same project for this reason.

Inspector Authority Under AWS D1.1: Owner vs. Fabricator

AWS D1.1 splits inspection responsibility three ways: contractor QC, owner's inspector, and the engineer. Here's who has accept/reject authority and when it matters.

Inspection authority is one of the most consistently misunderstood areas in structural welding QC. Contractors assume the owner's inspector works for them once on site; owner's inspectors assume they can shut down any weld they dislike; and CWIs sometimes believe their certification grants unlimited accept/reject authority. The actual authority structure under AWS D1.1 is more layered — and getting it wrong creates exposure when a weld is later challenged.

The three-role model

AWS D1.1 implicitly structures inspection around three distinct roles:

1. Contractor's inspector — the first line of quality control

The contractor bears primary responsibility for producing conforming work. The contractor's QC program — staffed by one or more CWIs depending on project scope — controls incoming materials, procedure compliance, welder qualification currency, dimensional inspection, and NDE witnessing throughout fabrication. This is the first line of quality control, not the last.

The contractor's CWI has authority to accept work on behalf of the contractor, certifying that the weld was produced in accordance with the applicable WPS and meets AWS D1.1 acceptance criteria. They also bear the duty to reject their own work when it does not conform — before it reaches the owner's inspector.

A contractor's CWI who accepts a nonconforming weld and lets it reach the owner's inspector is in a worse position than one who caught and documented the repair internally.

2. Owner's authorized inspector — oversight, not replacement QC

The owner may designate an authorized inspector — typically a CWI retained independently — to verify that the contractor's QC program is functioning and that the delivered work meets contract requirements. This inspector has accept/reject authority over completed work within the scope the contract assigns them.

The owner's inspector does not substitute for the contractor's QC function. They audit it. Common oversight tasks include:

Reviewing WPSs, PQRs, and WPQs before work starts for code compliance — see the CWI WPS pre-production review checklist
Witnessing or reviewing NDE results
Verifying welder qualification is current against the six-month continuity rule
Auditing production weld records against the weld map

If the owner's inspector finds that the contractor accepted work which actually fails code criteria, the matter goes to the engineer for resolution — not to the contractor's project manager.

3. Engineer of record — final technical authority

AWS D1.1 reserves final technical authority for the engineer responsible for the design. The engineer can accept work that falls outside code limits when engineering analysis demonstrates the deviation is non-injurious. Conversely, the engineer can impose requirements more stringent than the code minimums where the design demands it.

No inspector on either side can override the engineer's technical judgment within the scope of the engineer's professional authority. The inspector's role is to verify conformance to the code and contract; the engineer's role is to own the technical adequacy of the structure.

What the contractor's CWI can and cannot do

Under AWS D1.1, the contractor's CWI can:

Accept completed welds that meet the WPS and code acceptance criteria
Issue weld repair instructions consistent with the WPS
Reject nonconforming work and document it in the correction log
Release finished work to the owner's inspector for final acceptance review
Sign off hold points in the inspection sequence

The contractor's CWI cannot unilaterally:

Accept deviations from code requirements — that requires written EOR authorization
Override a rejection by the owner's inspector without engineering support
Sign a WPS that has not been properly qualified — see who is authorized to sign a WPS under AWS D1.1
Certify NDE results outside their own certification scope (a CWI certifying Level II UT results requires the relevant ASNT or SNT-TC-1A certification, not just CWI)

What the owner's inspector can and cannot do

The owner's authorized inspector can:

Examine any weld, any joint, and any stage of the work in progress
Review NDE reports and require re-inspection when reports are incomplete or ambiguous
Hold completed work pending owner acceptance
Reject work that does not meet the governing code or contract criteria

The owner's inspector cannot unilaterally:

Require welding to be performed in a manner not specified by the WPS or code without EOR direction
Arbitrarily delay production without a documented technical basis for the hold
Substitute their personal preference for a code-compliant judgment call by the contractor
Override a written EOR disposition on a specific weld

An owner's inspector who repeatedly imposes requirements beyond what the code specifies — without EOR backing — is exceeding the scope of inspection authority. Good inspectors know where the code ends and personal preference begins.

When disputes arise

The typical pattern: the contractor's CWI accepts a weld; the owner's inspector rejects it on a specific code basis. Resolution:

Both parties document their technical positions in writing — weld number, location, basis for rejection, basis for acceptance.
The matter goes to the engineer of record for review.
The engineer issues a written disposition: accept as-is; repair to code per a specified procedure; or repair to an engineer-approved alternative that deviates from the code's standard remedy.
Both parties implement the disposition, and the record is filed.

Disputes that bypass the engineer and go to project managers on both sides typically resolve slower and produce more litigation exposure than taking the technical path. Engineers make a technical record; project managers make a business decision that may be revisited years later.

Third-party inspectors and code authorities

On some projects an additional party enters the picture:

AISC certification auditors — these assess whether the shop's quality management system is functioning correctly against the AISC Certification Standard. They do not have accept/reject authority over individual welds. They evaluate the system, not the weld.

Building department or AHJ inspectors — have authority defined by the applicable building code and local ordinance, which may overlap with AWS D1.1 or impose additional requirements. Their accept/reject authority derives from the adopted code, not from AWS D1.1 itself.

Independent third-party CWIs hired by the owner — have whatever authority the contract assigns them. This should be explicitly defined in the contract before the inspector arrives on site. Vague scope language ("full inspection authority") creates disputes; specific scope language ("authority to witness NDE and review weld records; accept/reject authority on welds covered by Section 5 of the contract") prevents them.

Documentation that supports the authority chain

The contractor's weld records need to be structured so that every accept/reject decision is traceable. The minimum supporting documentation:

A written QC plan that designates the contractor's responsible welding inspector with CWI certification on file
Weld maps identifying each weld, the applicable WPS, and the welder's ID stamp — see welder ID stamp and production traceability
A hold-point log showing which inspections occurred, by whom, and the result (accept/reject/repair)
NDE reports referenced to weld map numbers, not just to drawing numbers

Without this chain, the owner's inspector has no audit trail to work from, and the contractor's CWI accept decisions are undocumented — a significant liability when a connection is challenged in a post-construction review.

Rule library based on AWS D1.1:2025; verify against your governing edition.

Practical setup

For new projects, establish the inspection authority in writing before work starts: who is the contractor's responsible CWI, who is the owner's authorized inspector, and what is the EOR's process for receiving and resolving hold-point disputes. A one-page project inspection plan attached to the kickoff package eliminates most authority disputes before the first arc is struck.

For audit-ready QC documentation that ties weld maps, hold-point logs, and NDE reports into a single exportable packet, see the audit-packet export feature.