AQL inspection explained in plain English: it is a sampling-plan approach. It reviews a defined sample from a defined lot against written requirements and stated plan references. Record the lot, plan version, sampling parameter, defect definitions, requirement document, sample record, threshold reference, findings, and report scope. A sample result does not prove every unit or guarantee an outcome.<\/p>\n
AQL does not tell you what your product should be. It does not replace a specification, an approved sample reference, a supplier review, a compliance review, or a commercial decision. It gives a structured way to record a check of a defined sample when the product requirements and plan inputs have already been stated.<\/p>\n
AQL inspection is a sampling-plan approach. It reviews a defined sample from a defined lot against written requirements and stated plan references. The record should show which lot was considered, which product and document version it relates to, which sampling-plan reference was used, what defect definitions applied, what was checked, and what the report says.<\/p>\n
The words “acceptance quality limit” are often shortened to AQL in inspection discussions. Public explainers describe AQL as a way to connect a lot, a sample, and plan thresholds for a documented check. [1] [2] That description is useful, but it does not give a buyer a universal setting or decide whether a product is suitable for a particular customer or market.<\/p>\n
Do not treat AQL as a percentage of defects that a factory is allowed to make. It is also not a promise that a passed sample means every unit is free of issues. AQL sampling is based on partial information from a defined check. The record needs to show what was actually sampled and what written plan was applied.<\/p>\n
Product requirements answer one question: what is being made and checked? Sampling-plan fields answer another: how is a defined sample record being organised? Keep them separate.<\/p>\n
A product record can include the specification, product version, approved sample reference if one exists, materials, components, dimensions, appearance, functionality requirements if defined, packaging, labels, carton marks, and other customer-facing requirements. Use a product specification sheet<\/a> to keep those requirements in writing. It does not choose an AQL plan.<\/p>\n A sampling record can include the lot or batch reference, plan or table reference, plan version, sampling parameter, defect-category definitions, sample draw record, threshold reference, observation record, and report scope. These fields do not tell an inspector what a defect is. They need the product requirements and written defect definitions to make the record meaningful.<\/p>\n If an approved sample is part of the project, identify it as a product reference. The guide to using a golden sample in China production<\/a> explains how to document a reference sample. It does not define a sampling plan or establish a result for later production.<\/p>\n AQL does not define the product requirements, defect definitions, or commercial decision for a buyer. Those inputs must be written for the product and project before a sample result can be read in context.<\/p>\n AQL-related documents may use labels such as critical, major, and minor defects. The labels are only useful when the project record says what each term means for the product, its written requirements, and the scope of the check.<\/p>\nRecord defect categories in writing<\/h2>\n