What NCM data do customers and auditors typically want to see?

They typically want enough NCM data to answer five questions: what happened, what product was affected, how it was contained, who approved the disposition, and whether the issue was actually corrected without breaking traceability.

The required depth varies by customer, contract language, product criticality, and audit scope. A customer reviewing a supplier escape, recurring defect, or high-risk part will usually expect more detail than a routine internal audit sample. Auditors also care about whether the record is complete, controlled, and consistent across systems, not just whether a form exists.

Core NCM data usually expected

• Unique NCR or NCM record number and status

• Part number, revision, description, serial number, lot or batch, and affected quantity

• Customer, program, work order, job, operation, or routing reference

• Date discovered, where discovered, and who identified it

• Clear description of the nonconformance, including requirement versus actual condition

• Objective evidence such as inspection results, measurements, photos, test results, or operator observations where applicable

• Immediate containment actions, segregation status, and whether any suspect material remains in process or was shipped

• Disposition decision, approval history, and effective date

• MRB involvement where required by procedure or customer flowdown

• Rework, repair, use-as-is, return to supplier, or scrap details, including linked instructions or approved deviations if applicable

• Root cause and corrective action records when required by severity, recurrence, or customer request

• Verification of implementation and closure evidence

• Links to affected documents, revisions, specifications, travelers, DHR records, and change history

• Any customer notification, concession, deviation, or escape communication required by contract or procedure

What customers often focus on

Customers usually care most about product impact and decision control. They want to see exactly which parts or assemblies were affected, whether any nonconforming product moved downstream or shipped, and whether the disposition was authorized by the right roles under the right revision-controlled procedures.

For supplier-facing reviews, customers may also ask for trend data, recurrence by part family or supplier, aging of open NCRs, closure timeliness, rework versus scrap rates, and evidence that corrective action reduced repeat escapes. If a defect affects fit, form, function, reliability, airworthiness-related characteristics, or contractual requirements, expect more scrutiny and supporting evidence.

What auditors often focus on

Auditors usually test process discipline rather than just individual defect details. They often sample whether records are complete, whether dispositions match procedure, whether approvals are attributable and time-stamped, whether closed records include verification, and whether data in NCM, MES, ERP, and QMS agree.

Common audit checks include:

• Missing or inconsistent part, lot, serial, or quantity data

• Disposition used without required approval

• Rework performed without linked instructions or revision control

• Closed NCRs with no evidence of effectiveness or verification

• Nonconforming material not physically or digitally segregated

• Repeat issues with weak or generic root cause statements

• Gaps between shop floor records, ERP inventory, and quality records

• Late closure, stale open records, or manual backfilling after the fact

Trend and summary data they may request

Beyond individual records, many customers and auditors want summary views that show whether the process is under control. Typical examples include open versus closed NCRs, aging by severity, defect category trends, recurrence rates, supplier-related nonconformances, scrap and rework impact, and top causes by product line, cell, or process step.

These metrics help, but they are only credible if the underlying coding, disposition workflow, and master data are consistent. Plants often discover too late that local naming conventions, duplicate defect codes, or weak integration make trend reports hard to trust.

Brownfield reality

In many plants, NCM data is split across QMS, ERP, MES, email, spreadsheets, and scanned attachments. That does not automatically fail a customer review or audit, but it increases the risk of missing links, conflicting timestamps, stale quantities, and weak evidence trails.

A full rip-and-replace is usually not the practical answer in regulated, long-lifecycle environments. Replacement programs often stall because of qualification burden, validation effort, downtime risk, integration complexity, and the need to preserve historical traceability. In practice, many organizations improve NCM visibility by tightening field definitions, approval controls, system linkages, and record governance across existing platforms first.

Practical minimum standard

If you cannot produce a complete, time-sequenced record showing identification, containment, disposition, approvals, affected product, and closure evidence, most experienced customers and auditors will treat that as a process weakness. If you can produce that record consistently and reconcile it to adjacent systems, you are usually covering the data they expect to see.

The exact format matters less than completeness, traceability, and control.