Skip to content
RTI

Process & workflow

How to manage a nonconformance

A nonconformance is work that doesn't meet the drawings, specification, or an approved submittal. Managing one is a defined process: document it, stop it from spreading, decide its disposition, fix it, and verify the fix — all on the record. The difference between a project that controls quality and one that argues about it later is whether nonconformances get run through that loop or quietly patched. This guide walks the loop from the moment you spot it.

For QC managers, superintendents, and engineers who've found work that doesn't meet requirements and need to resolve it cleanly.

Step by step

  1. Document the nonconformance the moment you find it

    Write it up on a nonconformance report: what the requirement is, what was found, where, and photos of the actual condition. Capture it before anything changes — the open condition is the evidence.

  2. Stop the work and contain the spread

    Tag or segregate the nonconforming work so no one covers it or builds on it, and check whether the same defect exists elsewhere in the feature. A defect found once is often being reproduced.

  3. Notify the parties who own the decision

    Loop in the engineer of record, owner's rep, or designer who has to weigh in on disposition. For a spec deviation, the designer decides what's acceptable — not the field.

  4. Agree the disposition

    Settle how it's resolved: rework to meet the requirement, repair to an approved method, use-as-is if the responsible engineer accepts it in writing, or reject and replace. Record the disposition and who authorized it.

  5. Carry out the corrective action

    Execute the fix — the rework, repair, or replacement — under the same acceptance criteria as the original work. Corrective action here means fixing this instance; addressing why it happened is root cause analysis.

  6. Re-inspect and verify against the criteria

    Inspect the corrected work against the original requirement and document that it now passes, with photos of the resolved condition. A disposition without a verified fix isn't closed.

  7. Close the report and trace it to the record

    Close the NCR with the disposition, the corrective action taken, and the re-inspection result all attached. The closed report travels with the feature into the turnover package as proof the issue was resolved.

What gets missed

  • Fixing the work quietly without writing an NCR, so there's no record the requirement was ever missed or met.
  • Letting the field decide a use-as-is disposition on a design deviation instead of getting the engineer of record's written acceptance.
  • Correcting the one spot you found and not checking whether the same defect repeats across the feature.
  • Closing the NCR on the promise of a fix rather than on a documented, photo-backed re-inspection.
  • Confusing corrective action (fixing this instance) with root cause analysis (stopping it recurring) and doing only the first.

Nonconformance vs. punch list item vs. deficiency

These get used loosely, but the process differs. A nonconformance is work that fails to meet a defined requirement and needs a formal disposition, often with the designer involved. A deficiency is a broader term for work that isn't right yet — it may be minor and closed by the crew. A punch list item is a specific incomplete or unacceptable item logged near completion for the responsible trade to finish.

The dividing line is consequence and who decides. If resolving it requires a design decision or a written acceptance of a deviation, run the full nonconformance loop. If it's a straightforward fix to meet a clear standard, a deficiency log or punch item may be enough.

Questions people ask

What's the difference between corrective action and rework?
Rework is redoing the specific nonconforming work to meet the requirement. Corrective action is the broader response to a nonconformance — which may be rework, repair, or replacement — and in a mature program also includes preventing recurrence through root cause analysis.
Who can approve a 'use-as-is' disposition?
Only the party responsible for the requirement being deviated from — typically the engineer of record or designer — and it has to be in writing. The field superintendent or QC cannot accept a design deviation on their own.

Terms worth knowing

Checklists that make this a one-tap job

Free, field-ready checklists, each with the photo every item needs before it can be submitted.

QC planConstruction quality control planRoles, definable features of work, three-phase control, nonconformance.12 items15 photosITPInspection and test plan (ITP)Activities, acceptance criteria, hold points and the record per row.11 items8 photosPunch listPunch list templateRoom-by-room closeout items with the before-and-after that closes them.15 items21 photosFinal inspectionFinal inspection checklist for constructionThe handover walk: systems, life safety, finishes and documentation.15 items25 photos
See the whole checklist library

Related guides

Reading the steps is one thing. Proving you walked them is the job.

RTI holds the submit button until every mandatory item is answered and the photos are attached, then chains the record so it can be proven untouched later.

Start freeBrowse the checklist library