Non-Conformance Report (NCR)

Definition — what it is

A non-conformance report is a formal document that identifies work, material, or a product that does not conform to the contract documents, applicable codes, or referenced standards, and initiates a controlled process to disposition it. It exists to ensure that a discovered deviation is not simply patched over or ignored but is formally recorded, evaluated, and resolved through a documented decision — repair, rework, use-as-is with engineering acceptance, or reject — before the non-conforming work is concealed or relied upon. The NCR is the escalation instrument of a quality program: an inspection checklist detects the deviation, and the NCR governs what happens next. A non-conformance report is not a change order and not a punishment mechanism; it is a quality-control record that segregates and controls a deviation, and treating it as an admission to be avoided rather than a control to be used is how deviations end up concealed instead of dispositioned.

Also known as: NCR, Nonconformance Notice, Deficiency Report, Quality Deviation Report

Why it matters — what it protects

It prevents a known deviation from becoming a concealed one. The most dangerous non-conformance is the one that is discovered, quietly patched, and built over without a decision. The NCR forces the deviation into a controlled process where a competent authority decides whether it can be accepted, must be repaired, or must be rejected, before it disappears behind finishes or into a structural assembly.

It creates the record that determines who pays. A non-conformance almost always carries a cost — rework, engineering evaluation, delay — and the NCR is where responsibility is established. Whether the deviation traces to a subcontractor's workmanship, a supplier's defective material, a design error, or a coordination failure determines who bears the cost, and the NCR is the document that pins that down while the facts are fresh.

It protects safety and long-term performance where the stakes are highest. For structural, life-safety, and envelope elements, a deviation accepted casually can compromise the building's integrity for its entire life. The NCR routes such deviations to the engineer of record for a real evaluation rather than a field judgment, which is exactly the control that keeps a convenient use-as-is decision from becoming a latent structural risk.

It is the quality program's memory and its evidence. The pattern of NCRs — which trades, which activities, which suppliers, which recurring defects — is a direct read on where quality is failing and whether corrective actions are working. In a later dispute or warranty claim, the NCR log establishes what deviations were found, how they were resolved, and by whose authority, which is often decisive.

Lifecycle — how it moves

1. Detection

   A deviation is identified — through an inspection checklist, a test failure, a submittal mismatch, or a field observation. The moment of detection is the moment to segregate the work before it is built upon.

2. Documentation and segregation

   The NCR is raised with the specific deviation, its location, and the requirement it violates, and the non-conforming work or material is marked or held so it is not inadvertently accepted or covered. Skipping segregation lets the deviation proceed while the paperwork catches up.

3. Cause and responsibility analysis

   The origin of the deviation is investigated — workmanship, material, design, or coordination — because it drives both the disposition and who bears the cost. Recording 'defective work' without the cause forfeits the responsibility question.

4. Disposition proposal

   A disposition is proposed: repair, rework, use-as-is (accept), or reject. Use-as-is on a structural or life-safety element must route to the engineer of record, not be decided in the field.

5. Review and approval

   The disposition is reviewed and approved by the appropriate authority — the design team, engineer of record, or owner depending on the element and the disposition. A use-as-is accepted without the required engineering sign-off is a decision made by the wrong party.

6. Corrective action

   The approved disposition is executed and verified, and where the cause is systemic, a corrective action addresses the process that produced it, not just the instance. Fixing the instance without the cause guarantees recurrence.

7. Verification and closure

   The resolution is inspected and the NCR is closed with evidence. An NCR closed without verifying the corrective work is a paper closure over an unresolved deviation.

8. Trend analysis and retention

   Closed NCRs feed trend analysis and are retained for the quality record, closeout, and any later claim. The value of the log is in what it reveals across many NCRs, not just the resolution of each one.

Anatomy — the data it carries

NCR number and date

Unique identifier and detection date, anchoring the record and the segregation of the affected work.

Description of non-conformance

Precisely what does not conform, stated factually. Vague descriptions like 'poor quality' cannot be dispositioned or defended.

Requirement violated

The specific specification section, code provision, drawing, or standard the work fails to meet. The basis that makes it a non-conformance rather than an opinion.

Location and quantity

Exactly where and how much work or material is affected, which bounds the disposition and the cost.

Responsible party / cause

The trade, supplier, or origin — workmanship, material, design, coordination. Drives both the disposition and who pays.

Photographs and test data

Evidence of the deviation, especially for work about to be concealed, often the only durable proof of the condition.

Segregation / hold status

Whether the affected work is held or marked so it is not accepted or covered pending disposition.

Proposed disposition

Repair, rework, use-as-is, or reject, with the rationale. Use-as-is on critical elements must escalate rather than resolve in the field.

Disposition authority and approval

Who approved the disposition and when — the design team, engineer of record, or owner — which must match the element's criticality.

Corrective action

The action taken to resolve the instance and, where systemic, to address the cause so it does not recur.

Verification and closure

The re-inspection or test confirming resolution, and who verified it, before the NCR is closed.

Cost and schedule impact

The rework, evaluation, and delay cost, and any schedule effect, tied to the responsible party.

Linked records

The inspection checklist that detected it, related submittals, RFIs, change events, and any backcharge to the responsible party.

Failure modes — how it breaks

Deviation patched without an NCR

A defect is found and quietly corrected or covered without ever raising a formal record. If the correction was inadequate or the deviation was structural, there is no documentation, no disposition authority, and no evidence, and the problem resurfaces as a failure or a warranty claim with no trail.

Field use-as-is on a critical element

A structural or life-safety deviation is accepted as use-as-is by the field team for schedule convenience, without the engineer of record's evaluation. A decision that required professional engineering judgment is made by someone not qualified to make it, creating a latent risk and liability.

Cause never determined

The NCR records the deviation but never establishes whether it was workmanship, material, design, or coordination. The responsibility question is left open, the party who caused it is never backcharged, and the same cause produces the next NCR.

Instance fixed, systemic cause ignored

The specific non-conforming work is corrected but the process that produced it is untouched. The same defect recurs across the project because the corrective action addressed the symptom and not the cause.

Closed without verification

The NCR is marked closed once a disposition is decided, but no one re-inspects or tests to confirm the resolution was actually executed correctly. The record shows resolved; the work may not be.

NCR used as punishment, so reporting is suppressed

When NCRs are treated as blame documents rather than quality controls, field teams stop raising them and start hiding deviations. The program loses its visibility into quality precisely because it made the record adversarial.

Cost and responsibility divorced from the record

The NCR is resolved but the rework cost is never tied to the responsible party or converted into a backcharge. The cost surfaces later as an unexplained variance, long after the leverage to recover it from the responsible sub has passed.

Metrics — how it is measured

NCR volume and rate

NCRs per period and per work element or trade. Reveals where quality is failing and whether it is improving over time.

Disposition mix

Distribution across repair, rework, use-as-is, and reject. A high use-as-is share can signal either genuine minor deviations or a program accepting too much.

Time to disposition and closure

Days from detection to approved disposition and to verified closure. Long cycles mean non-conforming work is holding up the schedule.

Repeat-cause frequency

How often the same root cause recurs. A direct measure of whether corrective actions are addressing causes or just instances.

Responsible-party attribution rate

Share of NCRs with a determined cause and responsible party. Measures whether the cost-recovery question is being answered.

Cost of non-conformance

Aggregate rework, evaluation, and delay cost captured through NCRs, and the share recovered via backcharge. Ties quality failures to margin.

Verified-closure rate

Share of NCRs closed with documented verification rather than a paper closure. Measures whether resolution is real.

The AI shift — what actually changes

Conversational

The NCR log becomes a quality-intelligence resource. You ask which recurring causes drive the most non-conformances, which supplier or trade generates the highest NCR rate, which open NCRs are holding up scheduled work, or how much unrecovered rework cost sits in closed NCRs without a backcharge, cited to the records.

Generative

Drafting shifts from a blank form to a structured draft: from the inspection finding and photos, a model assembles an NCR with a factual deviation description, the specific requirement violated identified from the specifications, the location and quantity bounded, and candidate causes proposed for investigation, which the quality manager verifies and completes.

Orchestrated

The NCR stops being an isolated record. It is raised automatically from a failed inspection, holds the affected schedule activity until disposition, routes use-as-is on critical elements to the engineer of record rather than the field, links to the submittals and RFIs that bear on the deviation, and connects the resolved cost to a backcharge against the responsible party so quality, schedule, and cost stay joined.

Autonomous

The routine motion runs continuously: NCRs are drafted from failed inspections and segregation is flagged, affected work is held in the schedule until dispositioned, disposition and closure aging is monitored and escalated, recurring causes are surfaced across the portfolio, and unrecovered rework costs are flagged for backcharge, while the disposition decision, any use-as-is acceptance, the engineering evaluation, and closure verification remain firmly human.

Prompts — put it to work

Tool-agnostic and copy-ready. Adapt the specifics — thresholds, contract windows, cost codes — to your own project before you run them.

Conversational — Understanding what the NCR log is telling you about quality.

Analyze our non-conformance log for this project. Tell me the three most frequent root causes and which trades and suppliers they trace to; which recurring causes have had a corrective action that clearly did not work because the same cause keeps reappearing; which open NCRs are currently holding a scheduled activity; and how much rework cost sits in closed NCRs where a responsible party was identified but no backcharge was ever issued. Present it as a quality-and-cost picture, not a list, and tell me plainly where the biggest unaddressed problem is.

What good output looks like: A cause-and-cost analysis identifying the dominant recurring causes, failed corrective actions, schedule-blocking NCRs, and unrecovered costs, with the single biggest unaddressed problem named and cited.

Follow-ups:

• For the top recurring cause, what corrective action would actually address it?
• Draft the backcharge documentation for the unrecovered rework costs.
• Which suppliers should we flag in prequalification based on this NCR history?

Generative — Raising a rigorous NCR from an inspection finding.

Draft a non-conformance report from the following inspection finding and photos. Finding: at the level 2 masonry wall, the specified horizontal joint reinforcement spacing was not maintained, with reinforcement observed at roughly 24 inches on center where the specification requires 16 inches. Write a factual description of the deviation, identify the specific specification section and any code provision it violates, bound the location and quantity affected, and propose candidate causes to investigate — workmanship, missing material, or a coordination gap. List the disposition options with a note that any use-as-is on this structural element must route to the engineer of record. Flag exactly what evidence and measurements I should capture before the wall is furred or covered.

What good output looks like: A factual, requirement-referenced NCR with bounded location and quantity, disposition options with the critical-element escalation noted, and a pre-concealment evidence checklist, with the disposition itself left to the proper authority.

Follow-ups:

• What information does the engineer of record need to evaluate a use-as-is disposition?
• Draft the hold notice to stop covering this wall until disposition.
• If the cause is the mason's workmanship, draft the backcharge basis.

Orchestrated — Making a non-conformance drive schedule, engineering, and cost correctly.

NCR 031 documents a structural weld deviation on an installed beam connection. Connect it to everything it should govern: place a hold on the erection activities that build on this connection until disposition; route the use-as-is question to the engineer of record with the weld inspection data and the specification reference, because this is a structural element the field cannot accept on its own; check whether the approved shop drawings and the welder's certification match what was performed; and, once the cause is determined, connect the rework or evaluation cost to a backcharge against the responsible party. Return an action summary tying each step to the record it affects and flagging what cannot proceed until the engineer responds.

What good output looks like: An action summary that holds the dependent schedule, routes the structural disposition to the engineer of record, checks the installation against the approved drawings and certifications, and prepares the cost recovery, with the acceptance decision reserved for the engineer.

Follow-ups:

• Draft the transmittal of the weld data to the engineer of record.
• Which downstream erection activities are blocked, and what is the schedule exposure?
• If use-as-is is denied, what is the rework sequence and cost?

Autonomous — Standing policy for running the non-conformance process.

Operate our non-conformance process continuously under these rules. Draft an NCR from every failed inspection and test with the deviation, the requirement violated, and the location and quantity, and flag the affected work to be held and segregated. Hold the dependent schedule activities until a human disposition is recorded. Route any proposed use-as-is on a structural, life-safety, or envelope element to the engineer of record — never accept one yourself. Monitor disposition and closure aging and escalate stalled NCRs. Surface recurring causes across the portfolio and flag corrective actions that have not stopped recurrence. Connect resolved costs to a backcharge against the identified responsible party for human approval. Never decide a disposition, never accept a use-as-is, never perform the engineering evaluation, and never close an NCR without recorded verification; route all of those to the appropriate human authority with your reasoning and the supporting records.

What good output looks like: A process that drafts, segregates, and holds work while routing dispositions to the right authority, where acceptance, engineering evaluation, and closure verification always stay human, fully audited.

Follow-ups:

• Show me this week's open NCRs holding scheduled work and every stalled disposition.
• Which recurring causes should the quality review escalate to leadership?

Get the full Construction AI Prompt Catalog — every prompt in the library in one document.

Maturity — locate yourself honestly

0. Level 0 — Informal patching

   Deviations are corrected or covered without formal records. Causes and costs are untracked, and structural deviations may be accepted in the field with no engineering review.

1. Level 1 — NCRs logged

   Non-conformances are documented with descriptions, dispositions, and closures, but cause analysis, verification, and cost attribution are inconsistent.

2. Level 2 — Controlled and linked

   NCRs segregate work, route critical dispositions to the engineer of record, verify closure, link to inspections and backcharges, and feed trend analysis.

3. Level 3 — Assisted

   NCRs are drafted from failed inspections, dependent work is flagged to hold, recurring causes are surfaced, and unrecovered costs are flagged for human review.

4. Level 4 — Operated

   Drafting, segregation, schedule holds, aging escalation, and cost linkage run within guardrails, while disposition, use-as-is acceptance, engineering evaluation, and closure verification stay human.

Common questions

What are the disposition options for a non-conformance?

Generally four: repair, which restores the work to an acceptable condition though not necessarily the original specification; rework, which brings it fully back into conformance; use-as-is or accept, in which the deviation is accepted without correction, usually requiring engineering or owner approval; and reject, which removes and replaces the non-conforming work. The right choice depends on the criticality of the element and the nature of the deviation, and use-as-is on a structural or life-safety element must be evaluated by the engineer of record, not decided in the field.

Is an NCR the same as a change order?

No, and conflating them causes real problems. An NCR documents that work or material fails to meet the existing contract requirements, and its resolution — repair, rework, or replacement — is generally the responsibility of the party that caused the deviation, at their cost. A change order modifies the contract requirements themselves and adjusts the contract price and time accordingly. A non-conformance is a failure to meet the current contract; a change is an alteration of it, and the cost responsibility is completely different.

Why not just fix a defect quietly instead of raising an NCR?

Because a quiet fix leaves no record of the deviation, no disposition by the proper authority, and no evidence that the correction was adequate, which is exactly what a later failure or warranty claim needs. For a minor cosmetic issue corrected immediately the informal route may be defensible, but for anything structural, concealed, or contested, patching without an NCR means the most serious deviations are the ones with the least documentation. It also forfeits the ability to establish cause and recover cost from the responsible party.

Why do the same non-conformances keep recurring?

Almost always because the corrective action addressed the specific instance but not the systemic cause. Fixing the one bad weld does nothing to change the welding procedure, the welder's qualification, or the inspection timing that allowed it, so the next bad weld is inevitable. Effective NCR programs distinguish correction of the instance from corrective action on the cause, and they track repeat-cause frequency precisely to expose the cases where only the symptom was ever treated.