The inspection log says damaged or out of tolerance, but the reviewer cannot find the drawing revision or measured result. A non conformance report needs the applicable requirement, the observed evidence and a precise statement of the failure to meet it. Add the affected product scope, immediate containment, authorized disposition and verification record so another person can follow the decision from discovery to closure.
The ISO and IAF Auditing Practices Group’s documenting guidance describes evidence, requirement and nonconformity statement as distinct parts of an audit finding. The practical workflow below adapts that evidence discipline to a manufacturing product record. It is a recommended operating structure, not a substitute for the current standard, customer requirement or quality procedure that governs your work.
Capture the observation without guessing its cause
At discovery, the inspector records the stable NCR identifier, inspection or complaint reference, product, lot and location. Preserve the observed condition, measurement units and time. Attach the original result or image through the controlled record system. The failure at this stage is an opinion without evidence: operator error or poor supplier quality names a presumed cause before the investigation supports it.
Keep sample evidence distinct from the affected population. If three inspected pieces fail, record three observed failures and the sampling context (including the population from which they were selected). Do not label every piece in the lot defective without evidence, and do not assume the rest conform because they were not inspected. The quality owner determines the appropriate containment and further inspection under the governing procedure.
Identify the exact requirement and released revision
The quality reviewer links the observation to the drawing characteristic, specification, purchase requirement or procedure that applies. Keep its document identifier, revision and effective scope. A current drawing downloaded after the event may differ from the revision used for the inspected order. Preserve that distinction before deciding whether the product, the instruction or the record failed a requirement.
For an illustrative example, assume drawing revision C requires a hole diameter from 10.00 through 10.05 mm. An inspection result for piece S17 records 10.08 mm using the specified method. The observed value is 0.03 mm above the upper limit. A report can state that precise discrepancy without asserting why it occurred or whether another piece has the same condition.
Treat missing evidence as its own question. If the required inspection record is absent, document that record-control issue against the requirement to retain it. Missing data does not establish a measured dimensional failure. Conversely, a passing measurement cannot prove that every required inspection was performed. Keep each supported finding tied to the requirement it addresses.
Bound the affected material and confirm containment
The operations owner identifies material on hand, work in process, shipped product and supplier stock that may share the relevant exposure. Use the lot traceability relationships to locate connected production and shipments, then have the quality owner confirm the scope. Similar descriptions alone cannot establish shared material, equipment or process history.
Assign each containment action an owner, deadline and completion evidence. A proposed hold is not a confirmed hold. Retain the location, quantity, status and source record showing the action took effect, with exceptions escalated under the procedure. A spreadsheet label cannot guarantee that picking or shipment is blocked in the operating system.
Suppose the illustrative lot has 100 units: 60 in storage, 25 in work in process and 15 shipped. Those mutually exclusive populations sum to 100, but the report still needs the supporting inventory, order and shipment references. If the 25 issued units also appear in a warehouse export, resolve the overlap before presenting an exposure total. Shipped units require a separate response decision by the authorized owner.
Keep suspected exposure, confirmed inspection failures and disposition quantities in separate fields. The population under containment can exceed the pieces proven defective while an investigation is open. When its scope changes, retain the earlier boundary and the evidence authorizing the change. That history explains why a hold quantity or shipment response differs from the final rejected quantity.
Requirement and evidence
Authority and affected scope
Executed action and results
Trace a finding across its approved records
Start with an inspection reference, its requirement and the affected lot or work order.
Record who can authorize each disposition
The designated disposition authority decides what happens to the affected material under the applicable procedure and customer conditions. Record the decision, rationale, quantity and approval evidence. Rework, return, scrap or an authorized concession are not interchangeable status labels. Each needs its own execution record and any required acceptance checks.
Microsoft’s nonconformance processing documentation separates approval, correction completion and closure. Use that as a documented software example of distinct steps, not as proof that a status in another system has the same meaning. Verify the permissions and evidence behind the workflow you use.
Keep the proposed correction separate from proof that it happened. If an instruction calls for rework, retain the authorized method, affected pieces, actual execution and reinspection result. A comment saying reworked cannot show which serials were processed. When only part of a lot is resolved, keep the remainder open with its own status and owner.
Link corrective action when the finding requires it
Correction addresses the observed condition; the cause investigation and corrective action address recurrence. The Auditing Practices Group’s response-review guidance calls for appropriate evidence when reviewing those parts. Follow your procedure to decide the depth of investigation and retain its rationale.
If the supplier owns the relevant process, link the supplier corrective action request to this finding. Keep the original product evidence and containment decision in the NCR while the linked request tracks the supplier’s cause analysis and verified response. Closing a supplier email thread does not, on its own, resolve the affected product population.
Assign an effectiveness check with a defined scope and acceptance rule before calling the action effective. A future review date is a plan. Preserve the actual later evidence and the owner’s decision, including a reopened investigation if recurrence appears. Avoid declaring that a single passing piece establishes permanent elimination of the cause.
Close against the evidence required by the procedure
The quality owner checks the finding, containment, disposition and verification against the closure criteria. Retain unresolved populations or linked actions under the status rules your procedure permits. Preserve corrections to the report with their author, time and reason, so the original observation and later decision remain distinguishable.
Use the quality management system evaluation if the handoff is failing because records or approvals are scattered. Test a partial disposition and a reopened correction before choosing software. The system should demonstrate the actual controlled workflow your procedure requires, including who can approve release and what remains open afterward.
How Permute connects the evidence behind an NCR
Permute is the connected-data platform we sell for analysis and custom business applications. We can combine approved SAP or NetSuite records with inspection extracts in Excel or Google Drive, reconcile lot and order identities, and preserve the source behind a finding. A missing drawing reference or uncertain lot match remains an exception for the quality team.
We apply declared scope and status definitions in repeated analyses. A quality lead can ask which open findings lack confirmed containment or disposition evidence and inspect the relevant records within their permissions. The answer can show extraction times and unresolved links rather than treating a summary status as evidence that every action finished.
Keep product release and compliance decisions with their owners
This analytical review does not certify conformity, approve a concession or release held material. Source coverage and refresh timing limit what the report can establish. Quality and engineering owners retain judgment under current procedures and requirements; any supported external action requires its own explicit permission and approval path.
Make the report understandable without its original author
A nonconformance report should let another reviewer connect the applicable requirement to the observed evidence and affected scope. Preserve the authority and execution record behind each disposition. Keep missing information distinct from measured failure, and link recurrence work without losing the original finding. Close only when the procedure’s required evidence supports the recorded decision.
Review one incomplete nonconformance handoff
Bring a disputed finding and the source records behind containment, disposition and closure.
Questions about documenting a nonconformance
Do NCR and nonconformity report mean the same thing?
Organizations use NCR for several related record names. Define the record’s purpose and approval authority in your procedure instead of relying on the abbreviation. The requirement, evidence and resulting decisions should remain traceable under any label.
Should repeated observations create separate reports?
Preserve each observed event and its scope, then follow your procedure for linking related findings or consolidating investigation. A shared cause hypothesis does not justify deleting the separate evidence. Keep the relationship visible so recurrence counts and affected quantities remain reproducible.
What if the reviewer rejects the proposed finding?
Retain the observation and the review rationale under your record-control procedure. A rejected finding should not become an approved product failure in reporting. Keep any separate inspection, containment or investigation decision tied to its actual authority and status.