Exception control

Non-conformance and corrective action: contain, decide, prevent recurrence.

A non-conformance record should protect the affected product and the decision trail before the team debates cause. PartVerity separates immediate containment, correction, authorised disposition, root-cause investigation and corrective-action effectiveness.

Decision premise

Closure question: is the product risk controlled, the disposition authorised, the cause addressed and recurrence evidence reviewed?

Control framework

Six stages from detection to evidence-based closure

The depth of investigation and action is scaled to consequence, recurrence and exposure. Correction of the detected item is not automatically corrective action on the cause.

01

Detection and record

Identify the requirement, actual condition, affected part/lot, discovery point and objective evidence without prematurely assigning blame.

Evidence route

NCR identifier, requirement, actual result, photos/data and traceability

02

Containment and exposure

Protect stock, work in progress, shipped product and related lots while the scope of the condition is established.

Evidence route

Hold locations, affected population, customer exposure and containment owner

03

Disposition authority

Define who may rework, repair, use-as-is, scrap or seek customer concession. Suppliers cannot self-approve customer-owned acceptance decisions.

Evidence route

Disposition, technical rationale, authoriser and completion record

04

Correction verification

Verify that reworked or replaced product meets the accepted requirement before release and keep the result tied to the NCR.

Evidence route

Re-inspection result and updated product status

05

Root cause and corrective action

For significant or recurring issues, address why the system allowed occurrence and escape—not only the visible defect mechanism.

Evidence route

Cause analysis, action owner, due date and implementation evidence

06

Effectiveness and lessons

Check after implementation whether the action controls recurrence and feed the learning into plans, supplier scope and future project gates.

Evidence route

Effectiveness criterion, review result and controlled-document updates

Decision evidence

Keep four decisions distinct

Blurring these decisions creates false closure. Each has a different object, owner and evidence requirement.

DecisionPurposeClosure evidence
ContainmentStop further exposure while scope is establishedAffected population identified and controlled
CorrectionEliminate the detected nonconformity on affected productRework/replacement completed and reverified
DispositionAuthorise what happens to nonconforming productNamed authority, rationale and product status
Corrective actionEliminate cause to prevent recurrenceImplemented action and effectiveness result
Preventive learningApply relevant lessons to other risks or routesUpdated controls, reviews or supplier conditions

Scope limits

False closure signals

Closing an NCR because the replacement shipment arrived.

Calling rework a root-cause corrective action.

Accepting a supplier promise without implementation evidence.

Using elapsed time instead of an effectiveness criterion.

Standards context

Use external standards to define the decision—not to decorate a claim.

Regulated-sector educational context for correction, corrective action and risk-scaled investigation; customer and sector rules govern each project.

FDA CAPA basics