Quality Nonconformance

Quality & Non-Conformance Management

Overview

Use this skill to review, structure, or improve nonconformance handling in regulated manufacturing environments where product disposition, investigation quality, CAPA escalation, supplier controls, and closure evidence matter.

This skill is designed for analysis and review work, not for issuing legal or regulatory sign-off. It helps the operator:

• distinguish immediate containment from deeper investigation
• decide whether an issue should remain an NCR/nonconformance or escalate to CAPA
• assess whether supplier escalation is required
• judge whether a closure package is evidence-based or too weak to accept
• preserve provenance and decision rationale before merge, handoff, or audit preparation

The workflow is intentionally risk-based. It should be applied only after identifying the governing quality framework for the record under review.

When to Use This Skill

Use this skill when the task involves one or more of the following:

• reviewing a nonconforming product event, deviation, NCR, or MRB packet
• deciding whether a case needs containment only, formal investigation, CAPA escalation, supplier action, or reopening
• checking whether root-cause claims are supported by objective evidence
• evaluating whether repeated defects indicate a broader process, validation, measurement, or supplier-control problem
• assessing closure quality for CAPA, SCAR, rework, concession, or deviation records
• preparing a review packet for quality leadership, audit response, or cross-functional handoff

Do not use this skill as a substitute for:

• legal advice
• formal regulatory reporting decisions that require authorized personnel
• product release authority
• changing approved procedures without controlled change management

Before using detailed criteria, identify the applicable regime, for example:

• FDA medical device / QMSR-harmonized device context
• pharma or biopharma quality system using ICH / GxP expectations
• aerospace, automotive, or internal QMS controls
• internal quality review with no direct regulated submission impact

If the governing framework is unknown, stop and ask for it before prescribing record content or closure standards.

Operating Table

Workflow

1) Establish the review frame

Start by collecting the minimum context needed to make a safe judgment:

• product or process affected
• lot, batch, serial, or unit scope
• where affected material is now located
• whether any product was released or distributed
• detection point: incoming, in-process, final release, complaint, service, audit, or stability/monitoring
• applicable quality system or regulatory context
• assigned record owner and disposition authority

If any of these are missing, call out the gap before concluding anything.

2) Control the nonconformance before investigating cause

Treat containment and disposition as a distinct stage.

Check whether the record shows:

• identification of affected material or records
• segregation or administrative control where practical
• hold status and access restriction
• preliminary scope assessment
• documented disposition path or hold-for-investigation status
• rework or reinspection requirements if applicable
• authorized approval for the chosen disposition under local procedure

Common disposition paths include:

• use as is
• rework
• repair
• return to supplier
• scrap
• concession or deviation
• hold for investigation

Do not accept a packet that explains root cause in detail but cannot clearly show what happened to the affected product.

If product has already shipped, add review of traceability, customer impact, field status, and whether separate reporting or market action processes must be considered by authorized personnel.

3) Triage risk and decide investigation depth

Scale the investigation to risk rather than applying the same depth everywhere.

Review at least these factors:

• severity of potential impact
• occurrence or recurrence pattern
• detectability and control weakness
• distribution status
• complaint, adverse event, or reportability linkage
• multi-lot, multi-line, or multi-site scope
• confidence in the available data

Also test for bias:

• blaming operator error before checking system factors
• blaming the supplier before checking incoming controls and specifications
• accepting the first plausible cause without ranking evidence
• closing because action was completed, not because effectiveness was demonstrated

Document why the chosen level of investigation is proportionate.

4) Investigate cause using evidence, not just narrative

A good investigation distinguishes:

• symptom: what failed
• containment: how exposure was controlled
• direct cause: what immediately produced the event
• root cause: why the system allowed it
• contributing factors: conditions that increased likelihood or reduced detection

Minimum evidence checks:

• compare actual records, not recollections alone
• review recent trend data and prior similar events
• check change history, maintenance, calibration, setup, tooling, and environment where relevant
• review inspection method adequacy and measurement-system confidence
• for supplier events, review specifications, quality agreements, inspection plans, and supplier change visibility
• for repeated process defects, review process validation or continued process verification evidence instead of defaulting to retraining

Be cautious with conclusions such as "operator error," "supplier issue," or "isolated incident" unless corroborated by records.

5) Decide NCR only vs CAPA escalation

Not every NCR requires CAPA, but some should not remain local.

Typical escalation triggers include:

• recurrence after prior correction
• high-severity or patient/customer safety impact
• distributed product or complaint linkage
• evidence of broader process or system failure
• validation failure or loss of validated state
• repeated supplier escapes or ineffective SCAR history
• multi-lot or multi-line impact
• poor detectability suggesting controls are weak
• prior closure later shown to be ineffective

If one or more of these are present, require a clear rationale if the issue is not escalated.

Use references/review-criteria.md when you need a compact decision aid during live review.