Incoming inspection: only non-conformances need a quality engineer

The question this file answersHow much of my quality team's day goes to filing batches that already met spec?

Fits: plants where quality certificates are read, retyped and filed by hand.

Typical day

What the desk looks like today

Typical, from the manufacturing playbook, where each incoming batch requires certificate review, and most batches pass. Passing and failing batches wait in one review queue, and the non-conformances needing action sit under the passes. It hurts in audit week and when a bad lot reaches the line.

What changes

What Monday looks like after

At the morning quality meeting the list on the screen is the non-conformances — with the certificate, the spec and the receipt already attached — while the passed batches are in the QMS and released. The engineers spend the day on disposition and the supplier call, not on filing.

Typical, not a measured client result. Every figure here comes from the playbook source named below.

~45–65%

less review time on incoming quality documents — SAP/Siemens (2023)

Before: every batch waits in the same review queue, and non-conformance reports sink under the passes. After: the passes go straight to the QMS; SAP/Siemens (2023) put the review-time saving at 50–65%, and disposition stays a person.

Where this number comes from

The SAP/Siemens (2023) case studies give 50–65% less review time on incoming quality documents; the manufacturing playbook uses 45–65%. The figure covers reading and filing certificates — the non-conformance report itself, once raised, is human work outside the range. Not a ppm claim.

What we install

What we put in front of the systems you already run

Your QMS stays — SAP QM, ETQ, MasterControl, Veeva or the one you run. This is the same certificate-against-spec build as our certificate-of-analysis file, with the non-conformance path made explicit:

each batch's certificate is read and compared to the specification and the PO line
in-spec batches are recorded in the QMS with the certificate attached
an out-of-spec value, a missing certificate or damage on receipt raises a draft non-conformance report and sends it to quality with the evidence.

Disposition of that lot is never automatic.

What stays human — and what this will not do

Disposition of the failed lot. The conversation with the supplier. Containment on the floor. Answers to the auditor, written as sentences.

Not a ppm claim.

What can go wrong — and what we do about it

Specifications that exist only on drawings or in heads cannot be compared automatically; where the spec is not held as values, batches stay manual until it is. The SAP/Siemens range covers reading and filing — disposition, containment and the supplier conversation are outside it, and a missed non-conformance is why borderline values go to a person rather than being passed.

What it costs to get there

The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →

Scoped in the audit — the playbook has no estimate for this exact desk.

This is about you if…

Does every incoming batch, in spec or not, wait in the same review queue?
Can your QMS receive a batch record and a draft NCR through an interface or import?

What does this mean in euros?

That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.

Get your free savings estimate 60 seconds · no sales call Or write first → Map a manufacturing process like this one — free, 60 seconds →

Not a named Aperanda client. Process file · Manufacturing.

Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.

All process files