How many times can a structural weld be repaired under AWS D1.1?

AWS D1.1 does not specify a numerical limit on repair attempts. However, the code requires engineer-of-record approval for repairs, and most project specifications impose a limit of two or three repair attempts before requiring engineering disposition. Each repair attempt must be re-inspected and documented.

Does each repair attempt require a new NDE inspection under AWS D1.1?

Yes — after any weld repair, the repaired area must be re-inspected by the same NDE method that identified the original discontinuity, and it must meet the same acceptance criteria. A repair that passes visual but was originally rejected by UT must pass the UT re-inspection.

When is a structural weld considered unrepirable under AWS D1.1?

AWS D1.1 does not define 'unrepirable,' but repeated repair excavations reduce base metal cross-section, create cumulative HAZ degradation, and may compromise the connection geometry. When a third or fourth repair attempt is considered, the engineer of record should evaluate whether replacement is the safer option.

What documentation is required for each weld repair under AWS D1.1?

Each repair cycle requires: the original nonconformance report identifying the defect, the repair WPS used, preheat and interpass records for the repair pass, and the re-inspection record showing acceptance or rejection. Maintain the complete repair history in the project quality file.

Weld Repair Attempt Limits Under AWS D1.1: What CWIs Must Know

AWS D1.1 doesn't set a hard cap on repair attempts, but the code and engineering practice impose real limits. Here's what CWIs and QC managers need to know.

A weld fails UT. The shop excavates and repairs. The repaired weld fails again. Now what? This scenario plays out regularly on structural projects, and many CWIs and QC managers are uncertain about the rules — specifically, how many times a weld can be repaired, what the code requires between attempts, and when engineering involvement becomes mandatory. AWS D1.1:2025 addresses repair requirements, but it does not set a simple numerical limit. Understanding what it does say — and what engineering practice adds — is essential for anyone managing weld quality on structural steel projects.

Rule library based on AWS D1.1:2025; verify against your governing edition (the AHJ or contract may specify 2020 or earlier).

What AWS D1.1 Actually Says About Repairs

AWS D1.1 permits repair of discontinuities that exceed acceptance criteria, subject to specific conditions. The repair must be performed in accordance with a qualified repair WPS, the repaired area must receive the same preheat and minimum interpass temperature as the original Weld procedure, and the re-inspection must use the same method that identified the original discontinuity and apply the same acceptance criteria.

Critically, AWS D1.1 does not specify a maximum number of repair attempts for most structural welds. The code focuses on the mechanics of each individual repair rather than limiting how many cycles are allowed. This is different from some pressure vessel codes, which explicitly cap repair attempts at two before requiring engineering disposition.

What the code does require is that repairs be authorized and documented. An unrecorded "touch-up" that is not documented as a formal repair — no nonconformance report, no repair WPS reference, no re-inspection record — is itself a nonconformance. The repair process must be formal from the first attempt.

See weld repair documentation and corrective action under AWS D1.1 for the complete documentation requirement for each repair cycle.

The Engineer-of-Record's Role in Repair Authorization

While AWS D1.1 does not set a numerical repair limit, it does require that certain repairs receive engineer-of-record (EOR) involvement. Repairs to tension-zone welds on cyclically loaded structures, repairs that reduce the effective throat below design dimensions, and repairs involving gouging that reaches base metal beyond the weld zone all require explicit EOR authorization and may require a formal disposition.

Most project specifications go further, adding a cap that AWS D1.1 alone does not impose. Owner project specifications and general conditions for structural steel fabrication commonly state that after two unsuccessful repair attempts, any further repair requires EOR written authorization with a documented repair plan. Some specifications require the EOR to review every repair above the first. CWIs working on bridge work under AWS D1.5, AISC-certified fabrication, or nuclear-adjacent structural work should always check the project-specific supplements before assuming AWS D1.1's silence on repair limits means anything goes.

Technical Limits on Repair Attempts

Even without a code-specified numerical limit, the physics of repeated repair imposes practical limits that every CWI and QC manager should understand.

Heat input accumulation. Each repair excavation and re-weld adds heat to the base metal and weld zone. For notch-toughness-qualified welds under AWS D1.1:2025 Table 6.8, repeated thermal cycling can alter the HAZ microstructure and potentially degrade the CVN impact properties of both the weld metal and the adjacent base metal. On demand-critical welds and tension-zone applications, a weld that has been repaired three times in the same area has received substantially more cumulative heat input than the original procedure qualification tested for.

Cross-section reduction. Gouge-and-repair cycles remove material. For a groove weld with a specific design throat, excavating deeply into the joint and re-welding can approach the limits of the original joint geometry. At some point — typically by the third repair attempt in the same area — the EOR must evaluate whether the repaired section still meets the design-basis cross-section requirements.

Hydrogen risk. Each repair excavation reopens the joint to atmospheric exposure, and each re-weld introduces new hydrogen from filler metal moisture and atmospheric sources. For high-strength base metals and filler metals classified at H4 or H8, this risk is managed through preheat. However, repeated heating and cooling cycles on a constrained weld zone increase residual stress, which compounds the hydrogen cracking susceptibility. See hydrogen cracking prevention and WPS documentation for the preheat and hydrogen management requirements that apply to each repair cycle.

NDE detectability limits. After two or three repair cycles, the weld zone contains a complex metallurgical history of multiple fusion events, heat-affected zones stacked on each other, and varying grain structures. In this environment, interpreting UT or RT results requires greater skill and conservatism. Geometric indications from repair geometry can mask real discontinuities. Anomalous UT signals that would otherwise be dismissed as geometry artifacts must be treated more cautiously.

The Third-Repair Trigger: When to Escalate

Engineering practice — supported by most project specifications — holds that the third repair attempt in the same weld location is the escalation trigger. By the third attempt, the following are known: the weld location has twice failed re-inspection, two rounds of excavation and re-welding have been applied, the root cause of the recurring discontinuity has not been resolved by standard repair, and continued repair attempts carry accumulating technical risk.

At this point, the appropriate response is not a third excavation without analysis. The appropriate response is:

Root cause determination. Why did two repair attempts fail? Common root causes include: design joint restraint preventing full fusion, a flawed repair WPS that does not address the original discontinuity type, inadequate preheat for the base metal thickness, or an NDE interpretation error (was the original rejection actually a real defect?).
EOR involvement. The engineer must evaluate whether the design basis is still satisfied with the current weld geometry and history, and must authorize any further repair approach in writing.
Replacement evaluation. In many cases, replacing the weld entirely — cutting the joint out and re-fitting — is more reliable than attempting a third repair. A fresh joint with the correct WPS applied to un-repaired base metal is more predictable than a third repair in a thermally fatigued zone.

See weld repair procedure qualification under AWS D1.1 for the qualification requirements that apply when a non-standard repair approach is needed.

Tension Zone and Cyclically Loaded Welds

AWS D1.1 applies more restrictive standards to repairs in the tension zone of cyclically loaded structures. The code requires that repairs in these locations be treated with particular care, that NDE coverage be complete (not sampled), and that the EOR explicitly approve the repair approach before work begins. The reasoning is structural: a weld repair in a tension zone that introduces a repair-related discontinuity — even a small one below normal acceptance criteria — can become a fatigue crack initiation site under cyclic loading.

CWIs inspecting bridge, crane runway, and seismic moment frame welds should flag every tension-zone repair for EOR review before the first arc of the repair weld is struck, not after the re-inspection result comes back.

Documentation Requirements for Each Repair Cycle

The AWS D1.1 repair process requires a complete documentation trail for each repair attempt. For each cycle, the project quality file must contain:

Nonconformance report (NCR) identifying the weld location, the NDE method and result, and the rejection basis (which acceptance criterion was exceeded)
Repair authorization — the EOR's written approval where required by code or spec
Repair WPS — the qualified repair procedure used, which may or may not be the same as the original production WPS
Preheat and interpass temperature records for the repair weld
Re-inspection record — the NDE report on the repaired weld, showing acceptance or continued rejection

If the re-inspection rejects the repair, the cycle starts again: a new NCR, a new repair authorization, a new repair WPS application, and new re-inspection records. Each cycle is documented separately. Do not amend the original NCR — open a new one. The complete repair history on a single weld location must be reconstructable from the quality file.

This documentation trail is exactly what an owner's verification inspector, an AISC auditor, or an expert witness will examine if the weld becomes a subject of dispute. A weld that was repaired three times and accepted is defensible if the documentation is complete. The same weld with missing repair records is indefensible regardless of its actual condition.

Manage your repair documentation alongside your WPS and NDE records in a single quality file. WPS Welding's audit packet tools keep your nonconformance records, repair WPS references, and NDE reports organized and exportable for owner turnover.