When should a concession be raised instead of closing an NCR with rework?

A concession should be raised when you intend to accept or ship a known nonconformance without fully bringing the item back to all specified requirements through approved rework. If the part can be restored to conforming condition by defined rework, and that rework can be verified and documented, then you normally close the NCR with rework, not concession. The boundary matters because a concession is an acceptance decision for remaining nonconformance, not a synonym for disposition paperwork.

Practical rule

Use rework to return the item to the original approved requirement. Use a concession when the item will remain nonconforming in some respect but is being proposed for acceptance based on risk review and approval. In many regulated environments, a repair can also trigger concession or deviation workflows if the repair changes the design intent, performance basis, inspection method, or approved process path. Local procedure and customer terms decide that line, so do not assume your internal NCR form is enough.

When concession is usually appropriate

• The part, assembly, or document record will not fully meet drawing, specification, or process requirements after disposition.
• A repair is proposed instead of rework, meaning the item is made usable but not restored exactly to original requirements.
• The customer, design authority, or MRB process requires formal use-as-is or repair acceptance.
• The nonconformance affects fit, form, function, life, reliability, maintainability, interchangeability, or contractual configuration in a way that needs explicit approval.
• The product has already moved downstream or been delivered, and acceptance of the condition must be formally recorded and authorized.
• The requirement cannot be objectively re-verified after correction, or evidence of full restoration is weak.

When concession is usually not appropriate

• The issue can be corrected by approved rework that returns the item to the original requirement.
• Inspection or test can confirm the item now fully conforms.
• The change is only administrative, such as a correctable documentation error, and your procedure allows controlled record correction without accepting product nonconformance.
• The team is using concession to avoid scrap, schedule pressure, or repeated rework approvals without a real technical basis for acceptance.

Common mistake

The common mistake is treating concession as a convenient way to close difficult NCRs. That is risky. It can hide recurring process failures, bypass proper design authority review, and weaken traceability. In regulated operations, auditors and customers usually look hard at repeated use-as-is or repair dispositions because they often signal process capability, planning, supplier, or training problems that should be escalated through CAPA or RCCA.

What decides the boundary in practice

The answer is not purely definitional. It depends on your quality procedure, MRB authority, customer flowdown, product criticality, and sometimes program-specific clauses. Aerospace and similarly controlled sectors often require stricter approval paths for concession than for straightforward rework. Some customers reserve concession approval to themselves or to the design authority. Others allow internal approval only within narrow limits.

You also need clean configuration and traceability data. In brownfield plants, NCR, MES, ERP, PLM, and QMS records often do not align cleanly. That creates a real failure mode: the shop closes an NCR as rework in MES, while QMS or customer paperwork treats the same event as repair or concession. That mismatch causes evidence gaps later. If your systems are fragmented, manual reconciliation and change control are usually still necessary.

Questions to ask before choosing concession

• After disposition, will the item fully meet the original requirement?
• Is the proposed action rework, or is it really a repair or use-as-is decision?
• Who has authority to approve that decision under contract and procedure?
• Does the condition affect safety, performance, life limit, certification basis, or interchangeability?
• Can the final state be objectively verified and traced in the product record?
• Does this event indicate a recurring issue that also needs CAPA or supplier action?

Bottom line

Raise a concession when the product will be accepted with a known remaining departure from requirement, or when a repair or use-as-is decision needs formal approval beyond normal rework closure. Close the NCR with rework only when approved rework restores full conformity and that conformity is verified. If the distinction is unclear, treat it as an authority and traceability question, not just a paperwork choice.