A single-shift structural shop with one CWI can run a tight inspection program on instinct and proximity — the CWI sees most of what happens and knows every welder. Scale that to two or three shifts, five to fifteen welding stations, and a mix of processes and joint types, and the informal approach stops working. Welds happen that no one inspects before they are buried under the next pass. Fit-up deficiencies get welded over. Parameter deviations go unrecorded. When the audit arrives, the shop has production records but no inspection records to match.

A CWI surveillance plan is the document that fills this gap. It defines how inspection coverage is organized across shifts, which activities are mandatory hold points (work stops until the CWI signs off), which activities receive roving spot-checks at a defined frequency, and how the findings from each shift are handed off to the next. AWS D1.1 does not prescribe the format of this plan, but a well-constructed one is what separates shops that pass third-party audits from shops that scramble to reconstruct records after the fact.

The Two Modes of Inspection Coverage

Every activity that requires CWI attention in a structural welding program falls into one of two categories:

Hold points are non-negotiable stops. Work cannot proceed to the next step until the CWI has inspected the condition and signed or initialed the record. Common mandatory hold points under AWS D1.1 structural welding include:

  • Joint fit-up inspection (root opening, bevel angle, joint alignment, tack weld quality) before any production welding begins
  • Root pass inspection on CJP groove welds before filling — particularly for joints requiring back-gouging to sound metal before the second side is welded
  • Pre-heat and interpass temperature verification at the initiation of welding and between passes on high-restraint joints or high-strength steels
  • Final visual acceptance before the joint is submitted for NDE

Roving surveillance points are activities where continuous presence is not practical, so the surveillance plan establishes a sampling frequency. The CWI visits a defined percentage of active welding stations per shift to verify WPS compliance — electrode classifications and storage conditions, parameter settings on the machine, interpass temperature on active joints, travel speed and pass profile. The sampling strategy in the plan specifies what fraction of joints, what station rotation, and at what intervals during a shift.

The mix of hold points and surveillance coverage is what the plan defines. Stating "welds will be inspected" is not a plan. A plan states which inspections are hold points, who performs each, when they occur in the fabrication sequence, and how the results are recorded.

Building the Surveillance Plan Document

A functional surveillance plan for a multi-shift fab shop is a short, operational document — typically two to five pages — organized around the following elements:

Scope statement: Which projects, work areas, and processes does the plan cover? Welding processes (SMAW, FCAW-G, SAW), applicable code (AWS D1.1:2025), applicable joint types (groove, fillet, stud), and any supplementary owner or specification requirements that affect inspection frequency.

Personnel and coverage matrix: List each shift, the CWI or designated inspector assigned to it, and the hours of coverage. If a CWI is shared across shifts, specify which activities can proceed without CWI presence and which require CWI availability. Third-shift arrangements that rely on production supervisors for interim monitoring — where allowed by the quality control plan — should be explicitly documented. See Fab Shop Weld Quality Control Plan Under AWS D1.1 for the quality control plan framework that the surveillance plan supports.

Hold-point register: A table that maps each fabrication stage to its hold-point requirements. For example:

Stage Hold Point Required Action
Joint fit-up Yes CWI measures and signs fit-up traveler
Preheat Yes (when required by WPS) CWI records temperature measurement method and result
Root pass Yes (CJP joints only) CWI visual inspection, grinding if required, sign-off
Interpass temperature Roving CWI documents at each surveillance visit
Fill and cap passes Roving WPS parameter verification per sampling schedule
Final visual Yes CWI acceptance or rejection per AWS D1.1 Clause 8.9
NDE submission Yes CWI certifies visual acceptance before NDE proceeds

Roving inspection sampling schedule: State the minimum frequency of surveillance visits per shift (e.g., minimum of three visits per eight-hour shift, one per active welding cluster), the parameters to verify at each visit (per the WPS — amperage, voltage, travel speed, electrode classification and condition, interpass temperature where applicable), and the format for recording findings. Parameter deviation findings go on a nonconformance form; compliant checks go on the production parameter log.

Records and documentation flow: Define which forms are used, where they are stored (digital or physical), and how they are transferred between shifts. A shift handoff log signed by the outgoing and incoming CWI (or inspector) is the mechanism for continuity. See CWI Inspection Report Documentation Under AWS D1.1 for the underlying record format requirements.

Shift Handoff: The Most Overlooked Element

The shift handoff is where multi-shift inspection programs most commonly break down. The outgoing CWI signs off the shift and leaves. The incoming CWI starts fresh, not knowing which joints are mid-sequence, which joints received roving parameter checks and which did not, and whether any open nonconformances are waiting for disposition.

A formal shift handoff log addresses this by requiring both inspectors to review and acknowledge:

  • Open hold points: Any joint that reached a hold-point stage but did not yet receive CWI sign-off. These are the highest priority for the incoming shift.
  • Active joints in progress: Which joint numbers are in what pass sequence, with the current interpass temperature range noted. The incoming CWI needs to confirm temperature before the first weld of the shift.
  • Open nonconformances: Any rejected conditions documented during the outgoing shift, their status (unrepaired, repaired-pending-reinspection, or resolved), and who is responsible for disposition.
  • WPS changes in effect: Any temporary parameter adjustments, approved deviations, or special instructions from the responsible engineer that affect the incoming shift's work.

The handoff log does not need to be long — a half-page summary with signatures from both inspectors covers the requirement. What it must not be is verbal. A verbal handoff leaves no record, and when a deficiency is discovered three days later, there is no documentation of what was known at each shift transition.

Sampling Strategy for NDE Submission Packages

Alongside the visual inspection surveillance, the CWI builds the NDE submission package — the documentation that accompanies welds sent for UT, RT, MT, or PT. The surveillance plan should specify how the CWI constructs this package:

  • Which joints require 100% NDE (demand-critical, owner-specified, or where visual inspection found indications)
  • Which joints receive spot NDE at the minimum code rate
  • The sequence: visual acceptance must precede NDE submission under AWS D1.1, so the surveillance plan should establish a queue — joints cannot enter the NDE queue without a visual acceptance entry on the inspection record

For spot UT sampling under AWS D1.1, the minimum sampling rates and selection criteria are code-specified. The surveillance plan notes the applicable rate and the CWI's authority to increase it when visual inspection findings suggest elevated risk in a joint category.

For reference on NDE sampling requirements, see NDE Sampling Rates: AWS D1.1 Spot vs. Full Coverage, and on method selection, see NDE Method Selection for Structural Welds.

Connecting the Surveillance Plan to the WPS Library

The surveillance plan is most useful when it references the WPS library directly. For each process and joint type in the scope, the plan should state which WPS governs and which parameters are to be verified during roving checks. This prevents the common scenario where a roving inspection checks amperage and voltage but not electrode classification — and misses that a welder has switched to an unqualified electrode mid-shift.

At each surveillance visit, the CWI should verify, at minimum:

  1. The WPS number posted at the welding station matches the joint being welded
  2. The electrode, wire, or flux in use matches the classification on the WPS
  3. The machine settings are within the WPS parameter ranges (amperage, voltage, wire feed speed where applicable)
  4. Preheat and interpass temperature are in range (measured, not assumed)
  5. The travel speed and bead profile are within the WPS requirements

These five checks, documented on the roving parameter log with the joint number, welder ID, and time, constitute the core of an effective surveillance record. See Production Welding Parameter Log Documentation for the format detail.

Keeping the Plan Current

A surveillance plan written at the start of a project and never revisited loses value as the project evolves. If a new process is added, if a new CWI is assigned, or if owner specifications impose additional inspection requirements mid-project, the plan should be revised and reissued. The revision history is part of the document control record and may be requested during audit.

For shops managing WPS libraries, welder continuity, and production inspection records across shifts and projects, a centralized system reduces the coordination burden — wpswelding.com provides a shared WPS and welder qualification database that multiple shift supervisors and CWIs can access without maintaining separate paper libraries.


Rule library based on AWS D1.1:2025; verify against your governing edition. The AHJ or contract may specify 2020 or an earlier edition with different table numbering.