What evidence should be attached to an NCR?

Attach enough objective, traceable evidence to show what the nonconformance is, what product or process is affected, when and where it was found, and why the proposed containment, disposition, or corrective action is supportable. An NCR should not become a dumping ground for every related file. The evidence package should be complete enough for quality, engineering, MRB, customer, or auditor review without relying on tribal knowledge.

The exact evidence depends on the product, customer requirements, internal QMS procedure, regulatory context, and whether the issue is handled only as a nonconformance, escalated to MRB, or linked to CAPA or RCCA. In regulated manufacturing, the minimum standard is usually traceability, objectivity, and controlled records rather than volume.

Common evidence attached to an NCR

• Clear description of the defect or deviation: what requirement was not met, using the applicable drawing, specification, work instruction, inspection plan, routing step, or purchase order requirement.
• Identification of affected product: part number, revision, serial number, lot or batch, work order, traveler, operation number, supplier lot, and quantity affected or suspected.
• Inspection or test results: measured values, pass/fail results, gage or equipment identifiers, inspection method, sampling basis, and acceptance criteria.
• Visual evidence: photos or videos when they help explain the issue, ideally with scale, orientation, date, and reference to the affected feature or location.
• Process context: operator station, machine, tool, fixture, program, environmental condition, setup record, maintenance status, or process parameter data when relevant.
• Material and certification records: certificate of conformance, material certs, receiving inspection records, supplier documentation, shelf-life data, or traceability records when the issue may involve material or supplied product.
• Controlled document references: drawing revision, specification revision, work instruction version, inspection plan, FAI reference, or PLM record used at the time of manufacture or inspection.
• Containment evidence: hold tags, quarantine records, inventory locations, suspect population definition, stop-ship actions, or system holds in MES, ERP, or inventory systems.
• Disposition support: engineering evaluation, use-as-is rationale, repair or rework instructions, scrap authorization, concession or deviation reference, and required approvals.
• Correction and verification evidence: reinspection results, rework completion records, updated traveler steps, test reruns, or verification that affected inventory was cleared or segregated.

What should usually not be attached

Do not attach uncontrolled copies of drawings, procedures, or specifications unless your document control process allows it and the revision is clear. In many environments, it is safer to reference the controlled PLM, MES, QMS, or document control record rather than duplicate a file that may become stale.

Avoid screenshots with no timestamp, user, source system, or revision context. They may be useful as supporting evidence, but they are weak if they cannot be tied back to a controlled record or audit trail.

Do not attach export-controlled, customer-restricted, proprietary, or sensitive technical data unless the NCR system and all recipients are authorized for that data. This is a common failure mode when quality workflows cross suppliers, customer portals, email, and internal QMS tools.

Brownfield system considerations

In many plants, NCR evidence is spread across MES, ERP, PLM, QMS, inspection software, maintenance systems, supplier portals, and shared drives. Full replacement of these systems is usually unrealistic in regulated environments because of qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, and long equipment lifecycles.

A practical NCR process often uses controlled links, record IDs, and system references rather than trying to move every artifact into one platform. That only works if permissions, retention rules, audit trails, and record ownership are defined. Broken links, orphaned files, and undocumented manual exports are common audit and investigation problems.

Quality of evidence matters more than quantity

Good NCR evidence is specific, dated, attributable, legible, and tied to the requirement. Weak evidence leaves reviewers guessing about the affected population, product revision, measurement method, or approval basis.

Typical failure modes include missing serial or lot traceability, unclear defect photos, measurements without acceptance criteria, undocumented disposition rationale, uncontrolled rework instructions, and corrective actions that are not connected to verified evidence. These gaps do not automatically mean a compliance failure, but they make the NCR harder to defend and harder to learn from.