Record quality inspection results

Record quality inspection results in SAP — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
Record the inspection results for inspection lot INSP-772 created for PO-10432, sample size 50, 48…
Record the inspection results for inspection lot INSP-772 created for PO-10432, sample size 50, 48 pass, 2 fail, measured critical dimension average 12.02 mm within spec 11.95–12.05 mm. Mark the lot as released for consumption and update lot traceability with inspector Ana's notes: two fail units quarantined and sent to rework. Notify customer quality contact Raj and production planning.

Improve — make it easier to accept

+
Before I finalize the inspection for lot INSP-772, make it easy for QA to accept the record: show…
Before I finalize the inspection for lot INSP-772, make it easy for QA to accept the record: show the failing characteristics first, list their impact on assembly and final yield, surface historical failure rates for FG-413 and for supplier COMP-77, and flag any test that lacks documentation. Highlight the single action that would let QA release the lot immediately.

Decide — diagnose the stuck moment

+
Ana logged INSP-772 as 48 pass and 2 fail but then marked the lot released without documenting…

Inspection showed two critical failures but analyst cleared the lot without comments.

Ana logged INSP-772 as 48 pass and 2 fail but then marked the lot released without documenting containment or root cause. I cannot tell whether those two failures are isolated measurement errors or indicate a batch-level defect, and I am afraid releasing will let bad parts into assembly and trigger a customer complaint. What is the most likely interpretation and the safest next step to keep production moving but protect quality?

Become — change the pattern

+
Across several releases we see QA releasing lots with minimal notes and later assemblies show…

QA often releases lots with minimal documentation and problems appear downstream.

Across several releases we see QA releasing lots with minimal notes and later assemblies show intermittent failures traced back to those lots. This forces rework and customer escalations. What simple QA habit, entry requirement, or trigger at inspection recording would reduce downstream escapes while keeping throughput reasonable?

Next to this one

Other enterprise resource planning work people do in SAP.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.