A AQL lot sample selection record should be a traceable record of the lot boundary, lot size, selection method, sampled unit identities, substitutions, inaccessible units and approved sampling instruction. Its release question is whether an AQL result can be interpreted against a clearly identified lot and defensible selection rather than a convenience sample. Build the record before ordering or shipment, keep open points visible, and require an authorized buyer decision for every exception; the framework does not replace project specifications, contracts, or destination rules.
Author: Andy, Director of Operations
Technical reviewer: Andy, Director of Operations
Last substantive review: September 8, 2026
Corrections: Send documented corrections through the HOMESEE contact page.
Editorial note: The author and lot checker are the same confirmed HOMESEE representative; this is not an independent technical selection review. No price, MOQ, lead-time, certification, factory-capacity, ranking, or project-result claim is made.
Table of contents
- The procurement sampling conclusion this record controls
- Minimum sampling cells and substantiation
- A step-by-step workflow
- A sample selection matrix
- Category and edge-case handling
- Governance and change control
- Buyer checklist
- HOMESEE RFQ selection review
- population bases
What procurement decision does a AQL lot sample selection record control?
AQL does not begin with defect counting. It begins by defining the lot and selecting units without allowing the sample to be reshaped after seeing the goods.
The core deliverable is a traceable record of the lot boundary, lot size, selection method, sampled unit identities, substitutions, inaccessible units and sampling-authorized sampling instruction. It should be readable as a sampling conclusion record rather than a marketing presentation. The lot-usable test is whether an AQL result can be interpreted against a clearly identified lot and defensible selection rather than a convenience sample. If the lot review group cannot answer that question from lot-controlled files, the lot record is not ready, even if individual participants believe they remember the answer.
This guide describes a buyer-side control method. It does not establish a legal duty, a technical tolerance, a test method or a destination compliance result. Those come from the signed contract, inspection plan specifications, qualified designers, relevant authorities and product-specific substantiation. HOMESEE should be evaluated only against the lot boundary and records actually agreed for an RFQ or order.
Start from a stable buyer identity
Keep a buyer-controlled item or sampling conclusion ID even when inspection lot owner references change. Inspection lot owner model names, carton numbers and report numbers remain valuable, but they should be mapped to the stable ID rather than replacing it. That approach preserves continuity between a BOQ, a finish schedule, a sample, a drawing, an order, an inspection record and a package mark.
Keep status separate from evidence
A lot state such as sampling-authorized is not substantiation by itself. Store the approving role, date, applicable lot boundary, population basis document and lot revision. A photograph can show visible condition; it cannot alone prove hidden construction, performance, lot count or authorization. An inspection lot owner declaration can identify a claim, but the sample-selection controller must decide what independent or destination-specific substantiation the project-specific control requires.
Minimum fields for the AQL lot sample selection record
Use a structured register with one sampled unit per item, package, sampling conclusion or selection exception at the level where the outcome can change independently. The table below is a sampling cell model, not a HOMESEE inspection plan record.
| Control sampling cell | Required treatment | sample selection test |
|---|---|---|
| unit identity | Stable ID plus native references | Can a lot checker find the same item across files? |
| Basis | sampling-authorized population basis, lot revision and lot boundary | Is the lot-active basis distinguishable from a proposal? |
| lot state | Named owner, sampling conclusion and date | Is every selection exception visible and actionable? |
| substantiation | selection-connected file and limitation | Does the substantiation support only the claim being made? |
| Downstream action | Affected order, inspection, package or receiving record | Was the sampling conclusion propagated? |
Order and lot identifier
Record order and lot identifier at the smallest level where the outcome can change independently. Project-wide totals hide unit, batch, package and zone differences, so the sampled unit must show the applicable inspection unit, lot count or range. Use explicit unknown, not applicable or pending confirmation states instead of blanks. That discipline keeps the lot record useful when the lot boundary splits and allows sample-selection gate to be tested for only the affected portion.
Lot size and inclusion boundary
The owner of lot size and inclusion boundary is the role able to correct its population basis, not merely the person typing the register. Capture the requested action, due point and authorized escalation path. A later email or spreadsheet does not supersede the selection line until its relationship to the lot-operative lot revision is sample-entered. The sample-selection controller keeps the former value as history so a lot checker can see what changed and whether downstream handling of the inspection unit was updated.
Location and package map
Use location and package map to connect the commercial line with the physical inspection unit. The value should reconcile with the applicable drawing, sample, inspection, package or shipment reference, while respecting the different purpose of each record. When repacking, rework, substitution or split shipment changes that relationship, create a traceable event instead of editing the old unit identity away. sample closure requires sample identity evidence, not memory.
Sampling standard and project instruction
Before accepting sampling standard and project instruction, test it against one awkward example from the actual lot boundary. Ask whether a partial lot count, mixed batch, inaccessible package, revised drawing or held unit would still be represented correctly. If the answer depends on verbal context, add the missing qualifier or selection-connected record. The sample-selection controller should be able to export the lot record to another lot checker and receive the same conclusion about the inspection unit and sample-selection gate.
Selection method
At sample selection, selection method needs a final timestamp and accountable sampling conclusion. The selection line identifies what was checked, what was not checked and which population basis remained provisional. It must not imply price, MOQ, lead time, certification, capacity or destination compliance. Those claims require their own inspection plan substantiation. The sample-selection controller signs only the bounded sampling conclusion supported by sample identity evidence and leaves unresolved lot boundary outside sample-selection gate.
Sampled handling-unit ids
sampled handling-unit IDs establishes unit identity before any lot state is interpreted. Put the sample-selection controller reference beside the population basis reference, lot revision and observation date. If the value came from an inspection lot owner message, retain the message as a dated input rather than converting it into an inspection plan fact. The sample-selection controller checks that the sampling cell describes only the inspection unit inside the stated boundary and records the next person who must verify it before sample-selection gate.
Unavailable or substituted units
Treat unavailable or substituted units as a sampling conclusion input, not a decorative column. Name the file, lot revision, issuer and effective date that support it, then state what remains unknown. The selection line should let a second lot checker reconstruct why this inspection unit is included, excluded, held or released without calling the preparer. Where two population bases disagree, preserve both values and open a visible selection exception; the lot record must not silently choose the convenient answer.
Step-by-step workflow for AQL lot sample selection record
Run the workflow as selection-connected gates. A later gate does not repair an undocumented earlier sampling conclusion; it merely makes the missing control harder and more expensive to find. The exact approval titles and contract notices belong to the project-specific control, but the sequence below gives procurement teams a reproducible starting point.
Step 1: Freeze the lot definition
freeze the lot definition. Visit the physical or digital population basis rather than copying the previous lot state. Reconcile identities, units, lot counts and package boundaries, and capture the observation date. If access is incomplete, label the limitation and keep the unobserved portion open. The sample-selection controller distinguishes what was seen, what was declared and what was authorized so sample identity evidence can support a bounded next action.
Step 2: Confirm the physical population
confirm the physical population. Compare the new input with the sampling-authorized reference set. Differences are logged at inspection unit level with both values, their population bases and likely downstream files. Do not resolve a mismatch by overwriting the older value or averaging conflicting lot counts. The sample-selection controller routes the selection exception to the role named by the project-specific control and prevents affected work from crossing sample-selection gate while the sampling conclusion is open.
Step 3: Record the sampling instruction
record the sampling instruction. Test dependencies before acting. Check whether this inspection unit shares a batch, accessory, interface, package, document total or installation sequence with another line. A seemingly local change can make an adjacent lot boundary unusable. The sample-selection controller records which related records need an update and which unaffected units may continue, creating a lot-controlled boundary rather than a blanket inspection plan hold.
Step 4: Select units across the lot
select units across the lot. Apply the agreed inspection plan rule and cite it. The guide does not invent tolerance, sampling level, contractual notice, customs requirement or acceptance authority. The sample-selection controller states the proposed outcome, obtains the authorized sampling conclusion and records any reservation. Where the population basis supports only a provisional conclusion, the lot record shows the follow-up substantiation required before final sample-selection gate.
Step 5: Preserve sampled identities
preserve sampled identities. Propagate the sampling conclusion into every operational file that still controls the inspection unit. That may include inspection lot owner instruction, inspection lot boundary, package map, cargo list or site receiving plan. Retain superseded revisions as history and prevent them from appearing lot-active. The sample-selection controller verifies the same unit identity and lot count after the update rather than assuming transmission proves implementation.
Step 6: Log access exceptions
log access exceptions. Close with a backward-and-forward trace. Starting from the physical inspection unit, locate its buyer line and lot-active substantiation; then start from the sample-selection controller line and locate the object or remaining balance. Any broken link becomes an selection exception with an owner. The sample-selection controller records the sample selection time, sampling conclusion lot boundary and limitation so another lot checker can repeat the test after handover.
Edge cases that need an explicit rule
Case 1: Supplier preselects display units
Where supplier preselects display units, compare the lot-active condition with the sampling-authorized reference under the viewing, measuring or access conditions defined by the project-specific control. Record the limitation if a meaningful comparison cannot be made. The sample-selection controller may request clarification, containment or a new check, but cannot invent a criterion. The final disposition must identify both authority and sample identity evidence.
Case 2: Two production batches are mixed
For two production batches are mixed, map the downstream consequence before choosing a remedy. Inspection, packing, document, loading and site-receiving files may each hold the old unit identity or lot count. The sample-selection controller lists the affected records and prevents silent reuse of superseded information. The sampling conclusion is closed only after the physical inspection unit and every lot-operative operational reference agree.
Case 3: Sealed crates block access
With sealed crates block access, treat the inspection lot owner proposal as an input rather than an sampling-authorized resolution. Preserve the original requirement, the proposed action and the sample-selection controller's authorized response as separate selection lines. The sample-selection controller verifies implementation on the stated lot boundary and records remaining exposure. A concession or schedule choice does not automatically prove technical conformity or satisfy sample-selection gate.
Case 4: Reworked units enter after selection
When reworked units enter after selection, freeze the last undisputed unit identity and separate the affected inspection unit from the remainder. The sample-selection controller records what changed, who observed it and which inspection plan population basis will decide the outcome. Existing photos or totals stay as history. Only the bounded portion with sample identity evidence can pass sample-selection gate; the unresolved portion receives its own owner and next check.
Case 5: Lot size differs from the booking pack
If lot size differs from the booking pack, do not force the register to show a clean total. Split the line by unit, batch, package, zone or lot revision until each outcome can be stated honestly. The sample-selection controller reconciles the sum back to the original order and labels every provisional balance. This keeps a partial sampling conclusion from being misread as acceptance or sample selection of all related inspection units.
Related files and revision governance
For AQL lot sample selection record, keep the operating file connected to the cross-category finish schedule, mixed-material AQL plan and export packaging specification. Plan sampling in the container-loading evidence plan, state protection in the supplier document requirements, and link final placement to the HOMESEE sourcing services. Before an order, reconcile the project inquiry form. Commercial context remains in project references, project-specific files go through the BOQ normalization guide, and published material submittal register guide is a reference rather than a guaranteed outcome.
Issue the AQL lot sample selection record with a lot revision, date, preparer and accountable approver. A change notice names the affected sampled units and downstream files; it never relies on a newer filename alone. Messages and meetings may resolve questions, but their authorized answer returns to the lot-operative register. Standards, photographs, declarations and sampling reports retain their own lot boundary: none becomes a universal compliance statement merely because it is selection-connected to the procurement file.
Practical review exercise
Test the lot record with one real inspection unit and one deliberately difficult selection exception. Start at order and lot identifier, then trace lot size and inclusion boundary, selection method and selector and timestamp without verbal help from the preparer. Ask a second lot checker to perform 'confirm the physical population' and 'log access selection exceptions' from the selection-connected population bases. Next, simulate the case supplier preselects display units while keeping the original order and substantiation history visible. The lot checker should be able to identify the bounded sampling conclusion, the unresolved portion, the next owner and the exact sample identity evidence required before sample-selection gate. If two lot checkers reach different conclusions, improve the population basis reference or sampling cell definition rather than adding an undocumented assumption. This exercise validates traceability and sampling conclusion clarity; it does not validate price, lead time, certification, factory capacity or destination compliance.
Buyer checklist for AQL lot sample selection record
Complete the checklist against the AQL lot sample selection record source set, not from memory:
- A stable buyer-controlled ID exists for every affected inspection unit or sampling conclusion.
- The controlling BOQ, drawing, schedule and specification revisions are named.
- inspection lot owner references are mapped without replacing buyer identities.
- Proposed, submitted, sampling-authorized, rejected and superseded states are distinct.
- Every selection exception has an owner, due action and authorized sampling conclusion route.
- Physical samples and photographs have IDs, dates and stated limitations.
- lot counts and units reconcile at the level needed for the sample selection sampling conclusion.
- Order, inspection, packing, loading and receiving impacts are mapped.
- Destination and contract requirements are assigned to qualified lot checkers.
- No price, MOQ, lead time, compliance or capability has been assumed.
- Superseded files are marked and cannot be mistaken for lot-active releases.
- The final record names preparer, approver, issue date and lot revision.
Request an AQL sampling-record review
To evaluate this control within a real sourcing package, use the BOQ normalization guide and upload the BOQ, lot-active drawings, schedules, sample register and any existing AQL lot sample selection record. Include the destination, required-on-site context and the sampling conclusion dates your inspection plan has actually sampling-authorized. Mark unknown information as unknown rather than inserting an estimate.
HOMESEE can then prepare questions around the defined lot boundary and organize an RFQ discussion against those files. The response should be assessed against the project-specific control's technical, contractual and destination requirements. Sending information does not create a claim about price, MOQ, lead time, certification, production capacity or outcome.
Sources
- ISO 2859-1:2026 sampling procedures
- ISO 28590 introduction to attribute sampling
- ISO 2859-2 isolated-lot sampling procedures
- GS1 Global Traceability Standard
The population bases support the general control concepts identified above. Standards and public guidance must be read in their own lot boundary and lot-active edition. A reference here is not a declaration that a particular product, shipment, inspection lot owner or HOMESEE service complies with it.