Has WPS authoring really changed?

The code requirements are largely the same. What changed is the audit environment, the welder workforce, and the pace of code-edition updates. Shops using Word and Excel are paying a tax in audit findings and authoring time that didn't exist 15 years ago.

Don't most shops still use Word?

Yes — the majority of small and mid-size shops still use Word for WPS authoring. But the leading certified shops have moved to dedicated software, and AISC audit data shows the gap in finding rates widening.

What's the typical migration timeline?

30-WPS migration: 4-8 weeks calendar with 60-120 hours of engineering time. Most shops phase it: new WPSs in the new tool, legacy WPSs frozen until they expire or need revision.

Why fab shops are leaving Word and Excel for WPS software

Word and Excel did the job for decades. Three forces are pushing fab shops to dedicated WPS software now — and they're not going away.

Word and Excel-based WPS libraries are still the majority across US fab shops. They produce code-compliant WPSs. They're free (or close to it). They're familiar.

Three forces are pushing shops away from them. None of the three are reversing.

Force 1 — tighter audit environments

Third-party audits got tighter in the last decade. AISC certification programs added rigor. AWS QC1 inspector training emphasizes systematic checks. AHJs in major US cities are pushing more code-compliance verification onto fabricators.

What this means for Word/Excel libraries:

The kinds of findings that used to be "noted" are now formal deficiencies
Revision-control gaps that were tolerated are now finding-generators
Edition-citation drift gets caught earlier
Welder-to-WPS traceability is actively tested

A Word library that produced 3 audit findings in 2015 might produce 8 in 2025 — same library, stricter auditor. Software-based libraries with built-in rule validation maintain low finding counts.

Force 2 — welder workforce demographics

The US welder workforce is aging out. The American Welding Society has estimated tens of thousands of welder positions per year going unfilled. New welders coming in have:

Less code-knowledge depth than the retiring generation
More tablet/phone familiarity than paper-binder workflow
Less tolerance for shop floors with broken information systems

A paper WPS binder on the shop floor, last updated when the previous QC manager retired in 2019, doesn't engage a 24-year-old welder. A clean floor terminal with the current revision, searchable by joint type and process, does.

Welder retention is a real factor in WPS tool choice now.

Force 3 — accelerating code-edition releases

AWS D1.1 used to update on a slower cadence. The 2010 → 2015 → 2020 → 2025 sequence is now about every 5 years. Other codes (D1.6 stainless, D1.5 bridge) are on similar tempos.

Each new edition requires:

Bulk-update of table citations across the library
Verification of essential-variable changes (Table 6.6 row 4 dropping A5.36, etc.)
Re-verification of preheat calculations against updated Table 5.8
Re-signing of every touched WPS

For a Word library with 30 WPSs, an edition migration is 60–100 hours of careful manual work. For a software library, it's a few hours of rule-engine review and an export.

Over a 20-year shop lifetime with four code-edition migrations, that's 240–400 hours of manual work versus a fraction of that in the software case.

The combined impact

A shop running Word/Excel today is paying:

Higher audit-finding rates (force 1)
Slower onboarding and lower retention of younger welders (force 2)
Larger periodic migration burdens (force 3)

Each force compounds. A shop with a 10-year-old Word library, an aging CWI nearing retirement, and a 2025-edition migration coming up has all three forces hitting at once.

What software solves

Modern WPS software addresses all three:

Force 1: built-in rule engine catches deficiencies before they reach auditors. Edition citations, table cross-references, preheat minimums, filler matching — all validated automatically.
Force 2: floor terminals with current revision, search by process or material, mobile-friendly. Engages younger welders.
Force 3: code-table updates ship server-side; library migrates automatically when essential variables don't change, with clear flags when they do.

What it doesn't solve

Software is not a substitute for:

A qualified CWI's judgment on novel procedures
A welding engineer's design of new welds
A QC discipline of revision control on the shop floor
The PQR investment for qualified-by-test work

Software amplifies good practices. It doesn't replace them.

Migration calculus for a typical shop

Annual software cost: $3,000–$8,000 for a mid-size shop
Audit-finding reduction: typically 60–80% from baseline
Authoring time reduction: typically 70–90%
Migration effort: 60–120 engineering hours over 4–8 weeks
Payback period: typically less than 12 months

Shops that started on software have a competitive advantage in audit results, retention, and authoring throughput. Shops still on Word and Excel are paying a hidden tax that's growing every year.