Inspections and Non-Conformances

Where quality matters, receipts and production output are inspected before the stock is treated as good.

Where to find it

Architect Panel → ERP - Operations:

• Inspections — what was checked, by whom, and the result
• Non-Conformances — what failed, the disposition and the follow-up

Inspections

An inspection records a check against a receipt, a lot or a production output — what was checked, who checked it, when, and the outcome. Recording the inspector and the time is what makes the record evidence rather than an assertion.

Non-conformances

When something fails, a non-conformance captures it: what was wrong, how much is affected, and what is to be done — use as is, rework, return to supplier, scrap. The disposition matters as much as the failure, because it is what determines the stock movement that follows.

Tie it to lots

Record the lot on the inspection and on the non-conformance. That is what connects a quality failure to genealogy, so you can answer which outputs used the affected batch and where they went. An NCR without a lot tells you something went wrong but not what to do about it.

Use it for supplier performance

Non-conformances aggregated by supplier are the most honest supplier quality metric you will have, because they are recorded at the point of failure rather than compiled at review time. Analytics can report on them like anything else.

Keep the process light

An inspection regime nobody completes is worse than none, because it produces a record that looks like assurance and is not. Inspect what genuinely carries risk, and make recording it quick.