Can another company use this PQR for its WPS?

Separate responsibility, record identity and technical coverage

The specific company situations described in 6.2.1.1

AWS D1.1/D1.1M:2025 Clause 6.2.1.1 identifies these limited cases: a company that voluntarily changes its name may use the new company name on the WPS while retaining the PQR record under the former company name; and consolidation into a parent company is addressed by the same narrow company-identity provision. Keep the original PQR identity and evidence traceable when the WPS shows the new company name.

Do not expand this wording into a blanket permission for an acquired business, affiliate, subcontractor, licensee, new legal entity, buyer of assets, or unrelated company to adopt another organization’s PQR. If the business history does not clearly match the stated case, the record cannot be treated as transferable by assumption. Preserve the factual question for the responsible code authority or Engineer as applicable to the project.

Clause 6.2.1.2’s treatment of qualification performed to another standard is a separate subject, with its own responsibility decision. It should not be used to bypass the company identity question in 6.2.1.1.

A practical identity and traceability check

1. Copy the exact manufacturer/contractor name shown on the original PQR and qualification test records.
2. Obtain the corporate evidence for any name change or parent consolidation, including effective dates and the relationship between the named entities.
3. Match that evidence to the specific Clause 6.2.1.1 language; do not infer a qualifying event from common ownership or a similar trade name.
4. Preserve the PQR under its original identity and link it to the new WPS identity with a traceability note. Never edit the original test record to replace its author.
5. Separately verify the PQR’s code edition, test reports and technical coverage for the proposed weld, materials and production variables.
6. Review contract-specific submission, review and approval requirements. Do not describe a customer or Engineer’s acceptance as AWS certification.

Bounded examples

Voluntary name change: A documented organization changes its name and retains the original PQR files. The clause’s stated name-change case may allow the WPS to carry the new name while the PQR remains under the former name. The WPS still needs a complete traceability link, and the PQR must independently support the proposed production conditions.

Unrelated subcontractor: A subcontractor receives a copy of a fabricator’s PQR and a permission letter. That alone does not establish that the subcontractor performed qualification or falls within the named company-change exception. Do not prepare a WPS as though qualification responsibility transferred without a basis in the governing code and project determination.

Documents to assemble before a WPS request

• Original PQR and all revisions, with the manufacturer/contractor identity intact.
• Supporting test reports and qualification record showing who performed and documented the qualification.
• Corporate name-change or parent-consolidation evidence when relying on the narrow exception.
• Proposed WPS scope, material and joint information, process variables, project code edition and contract review requirements.

WPS preparation can check record identity and technical support from submitted evidence. It cannot issue a corporate legal opinion, create missing qualification responsibility, certify AWS compliance, or compel project acceptance. If the facts do not establish the narrow case, the qualification responsibility question remains unresolved.

Code basis and related guides

Basis: AWS D1.1/D1.1M:2025 base edition plus the registered July 28, 2026 base-edition errata; AMD1 is not included. The governing contract edition controls each project. Confirm all applicable table notes and project requirements against the controlled code text.