A WPS is a regulated document. Its value depends entirely on the qualifications of the person who signed it. Anyone can write a WPS. The question is: who can sign it.

What AWS D1.1 actually says

AWS D1.1:2025 requires that the WPS be "prepared and signed by qualified personnel" but doesn't define a single role title. In practice, the code defers to:

  1. The contract. If the contract specifies "CWI-signed WPS" or "PE-stamped WPS," that governs.
  2. The AHJ. Local jurisdictions and building officials can impose stricter rules.
  3. The certification body. AISC, AWS QC1, ASME, API — each imposes its own signatory rules.

The most common combinations: a CWI signs, or a welding engineer signs, or both.

Who counts as a "qualified" signer

The roles typically accepted in US fab shops:

  • Certified Welding Inspector (CWI) — AWS QC1 certification, current and in good standing
  • Senior Certified Welding Inspector (SCWI) — same body, higher tier
  • Certified Welding Engineer (CWEng) — AWS QC10
  • Professional Engineer (PE) in metallurgical, welding, mechanical, or structural engineering
  • Foreign-equivalent inspector under AWS B5.1 — IWI, IWE, IWS in countries with reciprocal arrangements

Some certifications add a "responsible welding engineer" role that is documented at the company level and is the named signer for the entire WPS library.

Who can't sign

  • Welders, regardless of experience or stamp number — welders sign WPQs, not WPSs
  • Foremen, supervisors, and shop managers without CWI or engineering credentials
  • QC clerks who handle paperwork but aren't certified
  • The owner / operator, unless they personally hold a qualifying credential

What "signed" actually means

A signature on a WPS is an affirmation that the signer:

  1. Has reviewed the document against the cited code edition
  2. Believes it produces sound welds within the listed parameter ranges
  3. Accepts professional responsibility if it doesn't

That's why "qualifications" matter — the signer is on the hook.

Digital signatures

Digital signatures are acceptable under AWS D1.1 as long as the system:

  • Authenticates the signer's identity
  • Timestamps the signature
  • Hashes the document so post-signature edits are detectable
  • Produces an audit trail

DocuSign, Adobe Sign, and purpose-built WPS software all meet these requirements. Some AHJs still want a wet signature on the controlled hard copy in the QC binder — check the contract.

The audit consequence

The most common signature-related audit finding: the signer's CWI certification lapsed. The certification is current at sign time, but by the time the auditor checks (six months later, the certification is expired). Best practice: re-sign at every revision, and pull a fresh AWS QC1 verification at the same time.