Non-Conformance Report (NCR)

Definition

A Non-Conformance Report — universally shortened to NCR — is the formal document that records any element of the works that fails to meet the contract specification, the approved drawings, or an accepted method statement. It is the quality system's version of a defect ticket: raised the moment the non-conformance is identified, dispositioned by the responsible engineer, closed out with evidence, and — if the QA function is doing its job — trended to reveal the systemic causes behind repeat defects.

Anatomy of a Good NCR

• Unique NCR number, date raised, and originator.
• Precise location — element, grid, level, drawing reference.
• Description of the non-conformance, referencing the specification clause breached.
• Photographs — always. An NCR without photographs is an argument waiting to happen.
• Proposed disposition — accept as-is, rework, repair to an engineered procedure, or reject and replace.
• Designer / consultant approval where the disposition affects the permanent works.
• Root cause analysis — a real one, not "operator error."
• Corrective and preventive actions, with owners and due dates.
• Closeout evidence — inspection sign-off, retest results, photographs of the completed rework.

Why It Matters

An NCR is expensive because the underlying defect is expensive. Rework, retest, delay, redesign — the costs pile up quickly. But the real reason to run a disciplined NCR system is that the log becomes the most honest quality signal on the project. A dip in monthly NCRs is either a genuine improvement or a symptom that people have stopped reporting. A cluster of NCRs against one subcontractor, one supplier, one crew or one drawing sheet is a leading indicator of a bigger failure coming.

Real-World Example

On a natural-gas processing facility in Qatar, the piping subcontractor accumulated 47 NCRs in a single month against socket weld gaps. The dispositions were being closed out one by one — grind out, reweld, retest, sign off. Nobody looked at the pattern until the QA manager plotted them on a Pareto chart. Every one of the 47 was on the night shift, the same welder, and the same welding machine. The machine was drifting out of amperage tolerance under load and nobody had picked it up because the day-shift welders were rotating machines while the night-shift welder used the same rig every night. Six hours of investigation caught what six months of individual closeouts had missed. That is what the NCR log is really for.

Disposition Categories

• Use as-is — the non-conformance is inconsequential; the designer accepts the deviation with no further action.
• Rework — bring the element back to specification through repeat work.
• Repair — the element is brought to a fit-for-purpose state through an engineered procedure that differs from the original specification (grouting, weld overlay, epoxy injection).
• Reject — the element is removed and replaced.

Any disposition other than "reject and replace" that affects the permanent works needs written designer approval. "The site engineer said it was fine" is not designer approval.

Practical Lessons Learned

• Raise NCRs early and generously. A culture that raises many small NCRs catches problems while they are still cheap. A culture that raises few NCRs is either perfect or dishonest — and perfect projects do not exist.
• Photograph before, during and after. The before-photo is proof; the after-photo is closeout evidence.
• Never accept "operator error" as root cause. Operator error is always downstream of a procedure gap, a training gap, or a supervision gap.
• Cluster analysis beats individual closeout. The Pareto chart of NCRs by subcontractor, discipline and drawing is the report the project director actually needs.
• Closeout is not signature — it is verified evidence. A signed NCR without a retest report or completion photograph is not closed; it is filed.

Expert Tips

• Colour-code NCRs on the drawing set. Open NCRs in red, dispositioned in amber, closed in green. Anyone walking a floor plate can see the exposure at a glance.
• Link NCRs to the RFI and change-order logs. Many NCRs turn into design queries or variations; the traceability saves months of dispute time.
• Publish a monthly NCR trend to the project leadership team. What gets trended gets improved.
• Tie subcontractor progress payments to the timely closeout of their own NCRs. It converts a policing exercise into their problem.
• Audit closed NCRs quarterly. Random sample, walk to the location, verify the closeout evidence matches what is on the ground.

Common Mistakes

• Raising NCRs verbally to avoid an argument, then never logging them.
• Accepting "use as-is" as a default disposition without designer approval.
• Closing NCRs on trust rather than physical verification.
• Treating the log as a policing tool against subcontractors rather than a systemic quality signal.
• No Pareto analysis — every NCR closed in isolation, no patterns detected.
• Photographs missing, so the record is unusable during a later dispute.

Key Takeaways

• An NCR is a factual record, not an accusation.
• Every NCR needs a specification clause, a photograph, a real root cause and verified closeout evidence.
• Trend the log — the patterns are worth more than any individual entry.
• "Use as-is" is a disposition, not a shortcut; it needs designer approval.
• A project with zero NCRs is a project without a working quality system.

Related Concepts

Interlocks with Quality Gate, Quality Management, RFI Management, Change Order Management and Lessons Learned. NCR templates and Pareto trend formats at PMMilestone.org.