Nonconformance Reports (NCRs): Catching Quality Problems Before They Cost You

What an NCR is

A Nonconformance Report (NCR) is a formal record that some part of the work does not conform to the requirements — the specifications, the approved drawings, the applicable code, or the accepted standard. It documents what is wrong, where, how it was discovered, and what the project decides to do about it.

The key word is documented. Quality problems happen on every job. The question is whether they get raised, decided, and recorded — or whether a crew quietly patches it, hides it, or builds on top of it and hopes nobody notices. An NCR forces the issue into daylight where a qualified person makes a deliberate call. That record is also your protection: if a defect surfaces later, the NCR shows it was caught, evaluated, and resolved on purpose, not missed.

When to raise one

An NCR is warranted any time installed or in-progress work deviates from a requirement in a way that matters. Common triggers include:

• •Work that fails an inspection or test — a concrete cylinder break below the specified strength, a weld that fails NDE, a pressure test that does not hold.
• •Installation that does not match the approved drawings or specs — wrong material, wrong dimension, missing component, out-of-tolerance placement.
• •Material delivered or installed that does not match the submittal or has no traceable documentation.
• •Work performed out of an agreed sequence or without a required hold-point inspection, so conformance can no longer be verified the normal way.

The disposition options

Once a nonconformance is documented, a qualified party — often the engineer of record, the owner's rep, or the QA manager depending on the contract — decides the disposition. There are four standard outcomes, and choosing among them is an engineering judgment, not a field shortcut:

• •Use-as-is (accept): the deviation is reviewed and determined not to affect form, fit, function, or code compliance, so it is accepted as built. This requires sign-off from the authority responsible for the requirement — a crew cannot use-as-is its own mistake.
• •Rework: the work is brought fully back into conformance, so the end result meets the original requirement as if the defect never happened — for example, removing and reinstalling a misplaced item correctly.
• •Repair: the work is corrected to an acceptable condition that may not fully restore the original specification but is engineered and approved as fit for purpose — for example, an approved weld repair procedure rather than full replacement.
• •Reject / scrap: the work or material cannot be made acceptable and must be removed and replaced. The most expensive outcome, and the one good early detection is meant to prevent.

Root cause and corrective action

Fixing the defect is only half the job. If you rework a bad weld but never ask why it was bad, you will rework the next one too. The disposition handles the specific instance; the corrective action handles the cause so it does not recur. That is what separates a quality system from a list of patched mistakes.

Root-cause analysis asks why the nonconformance happened — not the surface symptom, but the underlying reason. Was the welder unqualified for that procedure? Was the WPS not on the wall? Was the drawing revision out of date in the field? Was the inspection skipped? A useful technique is to keep asking "why" until you reach a cause you can actually act on. The corrective action then targets that cause: requalify the welder, post the current procedure, control drawing revisions, enforce the hold point. A well-closed NCR names the root cause and the corrective action, not just the fix.

The cost of rework and how NCRs feed a quality system

Rework is one of the largest hidden costs on a construction project. The visible cost is tearing out and redoing the work, but the real bill is bigger: schedule delay, follow-on trades that have to wait or come back, wasted material, and the damage to your relationship with the owner. Catching a nonconformance during construction is dramatically cheaper than discovering it at closeout or during a warranty claim, when access is gone and the cost multiplies.

Beyond any single defect, NCRs are data. A stack of NCRs is a map of where your quality is breaking down — a recurring sub, a particular detail, a chronic submittal gap. Reviewed as a set, they tell you where to put inspection effort, which corrective actions are working, and which problems keep coming back. In Field PM, NCRs live in the QA/QC module alongside inspection logs, hold points, and punch lists, so each report carries its photos, its disposition, and its corrective action, and you can see patterns across the job instead of treating every defect as a one-off. That is how a pile of paperwork becomes an actual quality program.