AQL Passed? Why the Fix Lives in Your Next Inline Check
An AQL Pass Is a Shipment Decision, Not a Fix
An ISO 2859-1 final audit approves a lot based on the units sampled. It does not prove the underlying process is stable, and it does not stop the same defect appearing in the next order.
We see this most in September, when fall deliveries and holiday replenishment leave no room for repeat problems. A passed audit closes the shipment question. Prevention is a separate piece of work — and in Qualityiris it happens where it can actually change the outcome: the next inline inspection, on the floor, while the goods are still being made.
TL;DR
An AQL pass does not erase quality risk. Qualityiris keeps the defect photos, checklist results and measurement records from every inline visit and every final audit in one workspace, so the next inline inspection can carry a corrective action plan — drafted by Iris from that evidence, reviewed and signed by the inspector, locked at submit, and verified at the following visit.
Why a Passing Audit Can Still Be a Warning
Acceptance sampling tells you whether the lot meets the threshold you chose. It does not explain why the defects happened, or whether prevention is working.
The evidence patterns worth acting on:
- The same defect recurring across lots from the same factory or line
- A heavy concentration of one minor defect, even well inside the accept number
- Repeat workmanship issues — open seams, skipped stitches, uneven hems
- Wrong labels, shade variation, poor print placement
- Inline findings that resurface in the final audit
ISO 2859-1 gives you a second signal here too. Qualityiris tracks the clause 9.3 switching rules per factory, buyer and AQL pair, so a run of borderline lots moves the recommendation from Normal to Tightened inspection. The recommendation is advisory — the inspector can override it, and the override reason prints on the buyer-facing PDF. For isolated lots we run ISO 2859-2 (LQ, Procedure A) instead, where switching does not apply.
That recommendation is not a calculation done on the spot — it reads a switching history Qualityiris preserves for each factory, buyer and AQL pair:
- The current severity (Normal, Tightened or Reduced), the running switching score, and the recent lot results behind it
- Every state change kept as a dated event: from which severity, to which severity, the reason, the lot result, and the audit that caused it
- One event per audit, so the trail cannot be double-counted or quietly rewritten, and the state itself is machine-maintained rather than hand-edited
- The history only advances when an audit is submitted, so it matches what was actually inspected and signed
So when a factory asks why it is on Tightened inspection, the answer is a dated chain of its own audits, not an opinion.
Photos matter, because a one-line summary gives a factory nothing to investigate. Every inline and audit finding in Qualityiris carries tagged images, a defect category and location, inspector comments, and the production context behind it.
Connect Inline Findings to Final Audit Patterns
Early findings often say more than the final verdict. If inline checks repeatedly show broken buttons, construction faults or stitching defects, that signal should not disappear because the final sample passed.
Measurement data deserves the same reading. A garment can stay inside tolerance while measurements drift steadily toward the limit across sizes and colours. Qualityiris anchors every measurement to the spec locked to that purchase order and stores the analysis per size and colour on the inspection, so drift shows up as a trend rather than a single out-of-tolerance cell — early enough to question grading, cutting, shrinkage or sewing before the next cut.
Because inline reports, audits, orders and specs share one order book, you can see whether a pass reflects real improvement or just a favourable sample. A lot that passed while its switching history sits on Tightened is exactly the case where an inline CAP earns its place — the history turns the factory conversation into evidence instead of opinion.
What a Qualityiris Corrective Action Plan Actually Contains
Corrective action plans in Qualityiris are inline-only, on purpose. A final audit is a terminal verdict — Accept, Reject or Hold on finished, packed goods — and it stays immutable and third-party-style. Remediation belongs to the mid-production visit, where it can still change the run.
The plan is optional and the inspector chooses it. Three choices: a Concern CAP, a Recognition Note, or no plan at all. Nothing is auto-classified from defect counts.
A Concern CAP holds:
- The root cause, written against the evidence in the report
- Action items, each with a priority (high / medium / low)
- Recheck areas for the next visit
- A suggested re-inspection date
- A status — open, in progress or closed — maintained by the QA Manager or Admin
A Recognition Note is the other half most systems ignore: two to four sentences of evidence-grounded praise citing a concrete data point, when the line genuinely performed. No platitudes.
Note what is deliberately absent: no per-item owner assignment, no due-date chasing, no factory sign-off workflow. Qualityiris is advisory by design, not a task manager parked inside someone else's factory. The plan states the finding and the recommended action; the factory is best placed to decide how to address it; verification happens at the next inspection.
"Train operators" is not a corrective action. The plan should name whether the cause sits in machine settings, fabric handling, pattern accuracy, work instructions, operator technique, inspection gaps or supplier materials — and Iris drafts exactly that from the report's own data.
Iris Drafts It. The Inspector Decides.
Iris reads the discrepancies, checklist results, measurement analysis and photos already captured in the inspection and drafts the root cause, action items, recheck areas and suggested re-inspection date. Every field lands editable. The inspector reviews, edits, replaces or discards it — their judgement is final, and they are the one who signs.
On submit the plan is locked. Mode, root cause, action items, recheck areas and recognition note freeze, and a tamper-evident snapshot is stored on the record. Only the tracking status stays editable. That immutability is the point: the buyer, the factory and the QA manager all read the same plan on the same signed PDF, and nobody edited it after the fact.
Turn Passed Audits Into Verified Process Change
A plan is not finished when someone marks it closed. It is finished when the next inline visit works through the recheck areas and the defect frequency falls and the measurements stop drifting.
One shared record — inline reports, audits, defect evidence, measurement history and the plan itself — keeps brands, factories and quality managers looking at the same facts. When a passed audit also exposes a repeat pattern, the practical response is to approve the shipment, document the risk, and verify the process change before the next production run.
Start Where the Evidence Already Is
Qualityiris connects inline checks, ISO 2859-1 AQL and ISO 2859-2 LQ audits, defect trends and measurement drift to corrective action plans an inspector signs and a buyer can trust.
Self-serve, no sales calls and no demo wall: 690 a year. 14-day free trial, no credit card. Buyer and factory accounts are included at no charge.
Further reading:ISO 2859-1 switching rules ·AQL Reality Check calculator ·Inline inspection report format ·Sample report ·All solutions
