Reading inspection reports without guesswork: part 8
Reports do not end with verdicts; they end with homework. The remarks section lists what must be reworked, sorted, waived, or re-checked before the goods move, and buyers who skip it inherit those tasks as surprises. This guide shows how to convert remarks into a disposition list with owners and dates. Read it as the operational companion to verdict arithmetic: the numbers tell you what happened, and the remarks tell you what happens next.
Key takeaways
- Confirm the verdict covers the full presented lot, because sampling results cannot speak for goods produced after the inspector left.
- Sampling standards define how sample sizes and acceptance numbers relate to lot size, so check the report names its basis before trusting its verdict[1].
- Quality records must be traceable and retrievable, which means remarks, photos, and waivers filed together rather than scattered across inboxes[2].
- Turn every remark into a disposition line with an owner and a date: rework, sort, waive by deviation, or hold for re-inspection.
- Re-inspection needs its own stated sample and scope, since re-checking a handful of cartons never re-verdicts a whole lot.
The eighth part of this series addresses the moment after the verdict: turning report remarks into actions. Many buyers read the pass or fail line, file the PDF, and move on, leaving the remarks section, the most operational part of the document, unread. Remarks contain the rework list, the sorting instructions, and the conditions for re-inspection. A report whose remarks are ignored is a diagnosis without a prescription.
Records discipline explains why remarks deserve equal weight with numbers. Quality management practice treats records as the evidence that procedures were followed and decisions were traceable[1]. In inspection reporting, the numbers show what was found and the remarks show what should happen next. Both belong in the file, and both belong in the buyer response.
This article covers coverage checks, class disputes, remark-driven dispositions, and the filing habit that keeps reports retrievable. It assumes the verdict arithmetic from earlier parts is already verified; here the question is what to do on Monday morning with a report that arrived on Friday evening.
Verify coverage before acting on the verdict
Open the report at the lot description, not the verdict. Confirm the presented quantity, the inspected quantity, and whether any balance was produced after the visit. A verdict on eighty percent of a lot is a verdict on eighty percent, and the remaining twenty percent needs its own decision: separate inspection, documented risk acceptance, or production hold. Buyers who act on verdicts without checking coverage routinely accept goods nobody examined. See the inspection scope
Then confirm the sampling basis is stated and sane. The report should name the standard or procedure, the inspection level, the resulting sample size, and the acceptance numbers applied. Sampling methodology exists precisely so that sample verdicts can represent lots under defined rules[1]. A report that hides its basis asks for trust; a report that states it invites verification. Prefer the second kind, and require it in your inspection instructions.
See the inspection scope agreed before the visit and compare it with what the report actually covered. Scope drift happens quietly: the factory presents a partial lot, the inspector samples what is there, and the verdict reads as if the whole order was judged. The comparison takes three minutes and prevents the most common report misreading in import quality control.
Turn remarks into a disposition list
Read the remarks section line by line and convert each remark into a task with an owner and a due date. A remark about seam puckering becomes a rework instruction with a quantity and a re-check method. A remark about mixed carton marks becomes a sorting task with a responsible party. Remarks without owners age into disputes; remarks with owners age into closed files.
Handle class disputes through the specification, not through argument. When a supplier contests a major-defect call, open the product specification to the defect definitions both sides approved. If the definition supports the call, the rework stands; if the specification is silent, record a deviation decision and update the specification for the next order. Either outcome beats a week of email debate about what a reasonable person would accept.
Record all of this where the next person can find it. Documented information needs control: identification, retrievability, and protection against loss[2]. Practically, that means one folder per shipment holding the report, photos, tally sheets, deviation approvals, and the disposition list with completion dates. A buyer who inherits that folder mid-season should understand the shipment in fifteen minutes.
Disposition worksheet
| Remark or finding | Disposition decision | Owner and re-check |
|---|---|---|
| Defects within acceptance numbers | Accept with routine monitoring | Buyer files report; no re-check needed |
| Excess major defects in sample | Rework or sort defined quantity | Supplier reworks; inspector re-samples |
| Critical defect found | Hold lot pending root cause | Supplier investigates; buyer approves restart |
| Approved deviation requested | Waive by written deviation or reject | Buyer signs; specification updated |
| Partial lot inspected | Decide balance coverage separately | Buyer schedules or risk-accepts in writing |
File the completed table with the report; an unwritten disposition is a forgotten one.
Re-inspection rules that hold up
- Name the re-inspection scopeState whether the re-check covers the full lot or only reworked cartons, with its own sample size drawn the same way as the original. A vague re-check proves only that somebody visited twice.
- Segregate reworked goodsReworked goods must be identifiable: segregated, marked, and listed by carton. Inspectors cannot verify rework inside a mixed stack, and suppliers cannot prove it either.
- Require root cause for criticalsCritical findings restart the logic, not just the sample. Require the root cause, the corrective action, and evidence it was applied before scheduling the return visit.
- Close every lineClose each disposition line with a date and evidence reference when done. The shipment file is finished only when every remark points to an outcome.
The filing habit pays off the first time a customer complaint references a shipment from two seasons ago. With coverage verified, remarks dispositioned, and evidence filed together, the answer takes minutes and rests on documents. Without that habit, the same question takes weeks and rests on memory.
Sources
- Wikipedia: Acceptance sampling —— Overview of acceptance sampling including AQL concepts used in product inspection.
- Wikipedia: ISO 9000 —— Overview of the ISO 9000 family of quality management standards.
Frequently asked questions
How do I know what the verdict actually covers?
Compare the inspected quantity against the lot the factory presented, and check whether the report covers the full lot or a stated part. Sampling arithmetic only supports verdicts on goods the inspector actually saw. Anything produced after the visit needs its own coverage decision.
What if my supplier disputes the defect classes?
Define them in the product specification before the next inspection: which flaws are critical, which are major, and what the acceptance numbers are. Without written class definitions, every inspector draws the line somewhere slightly different. The specification is the contract; the report is its execution.
Where should an approved deviation live?
File it with the report and cross-reference both directions: the report notes the deviation reference, and the deviation record notes the report number. Unlinked waivers get lost; linked waivers get audited cleanly. The next person opening either file should find the other in seconds.
Should I redo the inspector arithmetic myself?
Yes, and good reports invite it. Reproduce the verdict from the sample size and class counts in two minutes. If your arithmetic agrees, file with confidence; if it disagrees, you have a precise question instead of a vague worry. Checkable reports are a feature, not an insult.