A typical structural fab shop carries 15–40 active welding procedure specifications. Multiply that by revision history, supporting PQRs, welder qualification records, and NDE documentation, and you have a paper management problem that quietly grows until an AISC certification auditor or third-party inspector walks through the door.
Most shops handle WPS documentation the same way they've handled it for decades: a three-ring binder in the QC office, photocopies distributed to the floor, and an Excel spreadsheet tracking welder qualifications. This approach worked when the pace of code changes was slow, audits were infrequent, and the shop ran the same procedures year after year. None of those conditions apply as reliably today.
What Paper Systems Get Right—and Where They Break Down
Paper WPS binders are not inherently non-compliant. AWS D1.1:2025 does not specify a format for procedure documentation; it specifies what the document must contain and how it must be controlled. A paper system can satisfy those requirements.
The failure modes are operational, not code-based. Consider what happens when a WPS is revised:
- The QC manager updates the master binder.
- Copies sent to the floor last month are now superseded.
- The two welders working the night shift have the old version.
- The field crew three job sites away has the copy emailed six months ago.
Version drift is the most common WPS deficiency found in third-party audits—not missing documents, but wrong revisions in use. The document exists; it's just not the current one.
The second failure mode is welder continuity. AWS D1.1:2025 requires welders to maintain continuous use of each process to stay qualified under their WPQ; a six-month gap in any process triggers requalification. Tracking this across a multi-welder, multi-shift shop in a spreadsheet means someone is manually monitoring dates. That task gets missed. The qualification lapses. Production welds are made by a welder whose qualification has expired—another audit finding.
What Effective WPS Document Control Looks Like
Before evaluating any software, it helps to define what controlled looks like in practice:
Single source of truth. There is exactly one current version of each WPS. Every access point—floor copies, CWI tablet, inspector package—pulls from that same source. When a revision is issued, old versions are immediately superseded everywhere.
Revision log. Every change to a WPS is documented with what changed, who authorized it, and when. This is required by any reasonable quality management framework and is always on the auditor's checklist. A clean revision log demonstrates that your WPS program is actively managed, not just filed.
WPS-to-PQR linkage. Every WPS either references a PQR or identifies the prequalified basis under which it was written. When an auditor asks "what test qualified this procedure?" the answer should be one click or one page turn away, not a search through a separate binder.
Welder qualification matrix with expiration alerts. The matrix shows which welders are qualified for which processes, base metals, thicknesses, and positions. It flags welders approaching the six-month continuity threshold before they lapse, not after.
Exportable audit package. When an AISC auditor, AHJ inspector, or owner's QC representative requests documentation for a project, you should be able to produce a complete, organized packet—WPS, PQR, WPQ records, NDE reports—in minutes, not hours.