Nonconformance Report and Review Board¶
Disposition review board — instantiates Conformance Control and Corrective Feedback
Records each nonconformance and convenes an authorized board to bound the affected population and decide its disposition.
When something fails a check, two questions have to be answered by someone with authority: how far does this go and what happens to it. Nonconformance Report and Review Board is the mechanism that answers them formally. It opens a nonconformance record — the durable, traceable account of what failed, against which requirement, and on which units — and convenes a cross-functional board with the standing to bound the affected population and choose a disposition for it: use-as-is, rework, repair, downgrade, return, or scrap. Its defining role is authorized decision-making over defective output: not the pass/fail check, and not the physical repair, but the deliberate, recorded judgement of scope and fate that sits between them.
Example¶
At a medical-device plant, a routine measurement finds that a batch of catheters has an inner-diameter dimension slightly out of tolerance. An operator opens a nonconformance record: the characteristic, the requirement version, the measured values, the lot and machine. The record itself triggers the two things a lone operator can't do. First, containment — using lot traceability, the board bounds the suspect population to the units made between the last good measurement and this one, and quarantines exactly those (not the whole day's output). Second, disposition — the review board, with engineering, quality, and clinical-risk input, decides the fate: because inner diameter is clinically significant here, use-as-is is refused; the units are routed to a defined rework, and any that can't be reworked are scrapped, with the decision and its rationale recorded on the nonconformance.
The board's value is in bounding both the scope and the decision: it neither lets suspect units leak nor over-quarantines the whole line, and it makes the fate of the batch an authorized, documented call rather than an informal one at the bench.
How it works¶
- Open a durable record. Capture what failed, against which requirement version, on which traceable units — the account every later step and audit refers back to.
- Bound the affected population. Use traceability (lot, serial, time window, causal window) to define exactly which output is suspect, so containment is neither leaky nor overbroad.
- Convene the right authority. Bring cross-functional judgement — engineering, quality, and the risk owner — to decisions a single inspector shouldn't make alone.
- Choose and record the disposition. Select use-as-is, rework, repair, downgrade, return, or scrap, with the rationale attached to the record; hand execution to the rework route and any recurring pattern to corrective action.
Tuning parameters¶
- Board threshold — which nonconformances need the full board vs. a delegated quick disposition. A low threshold adds rigor and delay; a high one speeds flow but risks under-scrutinized calls.
- Containment width — how tightly the suspect population is bounded. Narrow bounds via good traceability minimize disruption but risk missing a unit; broad bounds are safe but costly.
- Disposition latitude — how freely "use-as-is" concessions may be granted. Latitude preserves value but, over-used, hides incapability and games the spec.
- Traceability depth — how finely output can be tied to time, lot, and source; deeper traceability enables tighter containment at higher record-keeping cost.
- Escalation trigger — how quickly a repeated or severe nonconformance is escalated to corrective action rather than dispositioned again.
When it helps, and when it misleads¶
Its strength is turning a scattered set of failures into a controlled, auditable record and a defensible decision — bounding the damage precisely and making the fate of defective output an accountable choice rather than a bench improvisation. It is the memory and the courtroom of the quality loop.
Its misuses are two. Use-as-is over-reach: a board that keeps granting concessions to preserve output quietly relaxes the specification and buries the signal that the process can't hold it.[n1] And disposition without learning: recording and sorting the same defect over and over — clean traceability, tidy records, and no upstream change — is inspection-as-sorting with good paperwork. Containment can also over-reach, quarantining far more than plausibly affected and causing harm beyond the defect. The disciplines: bound scope with traceability and causal windows rather than fear, cap and trend use-as-is dispositions, and route any recurrence out of the boardroom and into corrective action.
How it implements the components¶
nonconformance_record— creates and owns the durable, traceable account of what failed and how it was dispositioned; the loop's system of record.containment_and_traceability_boundary— uses traceability to bound and quarantine exactly the suspect population, containing escape without over-reach.rework_repair_and_disposition_path— decides the disposition (use-as-is, rework, repair, downgrade, return, scrap) and routes it, though it does not physically execute the repair.
It does not enforce release of conforming output or grant release waivers (Release Hold and Signoff), perform the repair and reinspection it dispositions to (Rework and Reinspection Route), or investigate root cause and prevent recurrence (Corrective and Preventive Action Cycle).
Related¶
- Instantiates: Conformance Control and Corrective Feedback — it is the record-and-disposition organ that contains failures and decides their fate.
- Consumes: Automated Conformance Check and other checks supply the failures it records.
- Sibling mechanisms: Rework and Reinspection Route · Corrective and Preventive Action Cycle · Release Hold and Signoff · Upstream Quality Feedback Packet
Editorial Notes¶
Form Classification¶
Form family: Organization, Role & Governance
Rationale: The mechanism establishes an authorized cross-functional board that owns bounded-population nonconformance dispositions and records its rationale.
Nearest alternative: Decision, Gate & Allocation — The board selects use-as-is, rework, repair, downgrade, return, or scrap, but those decisions are functions of the standing governance body.
Review outcome: Adjudicated after independent review; high confidence.
Origin Attribution¶
Primary origin: Engineering & Design
Origin pattern: Cross-disciplinary synthesis
Present-day reach: Multi-domain
Rationale: Quality engineering developed nonconformance reports, affected-lot bounding, disposition categories, corrective action, and review boards.
Related originating lineages:
- Organizational & Management Science — Formal governance practice supplied delegated decision authority, ownership, and controls against routine concession.
Review resolution: Both independent reviews agree on primary origin engineering_design; reconciliation resolves origin_mode_disagreement, domain_reach_disagreement. Formative alternate lineages retained: organizational_management. The broader reach of later applications is kept separate as domain_reach=multi_domain; origin_mode=cross_disciplinary_synthesis describes the historical relationship among lineages. Confidence is conservatively reconciled to high, and encyclopedia_synthesis=false preserves the reviewers' boundary judgment.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
[n1] A use-as-is (concession) disposition accepts nonconforming output without correction. Legitimate for genuinely inconsequential deviations, it becomes specification erosion when granted repeatedly to protect throughput — hence the practice of capping and trending concessions. ↩