A lock pre-shipment release record should answer more than whether the cartons are closed. The buyer and supplier still need to know which approved configuration was built, which lots and quantities are in the shipment, which inspection and packaging evidence applies, whether any hold remains open, and who is authorized to release the identified shipment.
This lock pre-shipment release record is a buyer-side tool for procurement, quality, operations, and logistics teams handling cabinet, drawer, mailbox, locker, furniture, and enclosure lock orders. It joins existing evidence into one dated decision. It does not set product tolerances, sampling levels, test methods, shipping terms, or WELLHW capabilities. The contract, approved specifications, quality plan, and authorized owners determine those requirements.
Define the Release Unit Before Reviewing Evidence
A purchase order may contain several part revisions, finishes, keying groups, production lots, or destinations. A release decision should therefore identify the exact units it covers. If the evidence differs across lots or cartons, split the review into separately identifiable release units rather than using one blanket approval.
| Boundary question | Record | Why the answer matters |
|---|---|---|
| What is being shipped? | Buyer part and supplier reference, approved revision, variant, and purchase-order line | Prevents a passing report for one configuration from covering another |
| Which physical units? | Lot or batch IDs, finished quantity, carton or pallet IDs, and location | Makes the release traceable to identifiable stock |
| Where is it going? | Shipment or destination reference and any buyer-specific labeling rule | Allows packaging and document checks against the intended order |
| What is excluded? | Held, rejected, reworked, replaced, or awaiting-review quantities | Stops unresolved material from inheriting an approval |
The lock lot traceability record provides the links among inputs, production, inspection, packaging, and shipments. This release record uses those links to decide whether a specific shipment may move. A traceable lot is not automatically a released lot.
Build an Evidence Map, Not a Stack of Unchecked Files
Documented information can support the operation of a quality process and preserve the evidence behind its decisions, as explained in ISO’s summary of ISO 10013:2021. For a shipment decision, the buyer’s required records should match the same order and release unit; the mere presence of a file is insufficient. The evidence map below is an editorial tool, not a statement that ISO prescribes this exact form.
| Evidence group | Match and review | If missing or inconsistent |
|---|---|---|
| Approved baseline | Purchase-order line, drawing or specification revision, approved sample or change reference, and applicable variant | Hold the affected release unit until the governing requirement is identified |
| Product acceptance | Required inspection or test record IDs, results, coverage, dates, and authorized acceptance against the approved criteria | Request the missing evidence or route a nonconformance; do not infer a pass from silence |
| Open quality events | Hold, nonconformance, deviation, rework, replacement, and corrective-action references with affected boundaries | Keep affected units excluded until an authorized disposition and any required reinspection are recorded |
| Packaging and identification | Approved pack and label reference, actual carton count, unit count, part and lot labels, and required protection evidence | Correct or review the mismatch before shipment |
| Traceability and shipment | Lot-to-carton mapping, packing list, shipment reference, and any project-required document set | Reconcile identities and quantities before signing the release |
Use the first article inspection record for initial production evidence and the packaging approval record for the agreed pack configuration. Neither record alone approves every later shipment. The release review must verify that the relevant evidence applies to the actual units now leaving the site.
Reconcile Quantities Before Signing
Write down the quantity path for each release unit: completed, inspected or otherwise covered by the approved acceptance plan, accepted, held, rejected, reworked and reaccepted, allocated to cartons, and proposed for shipment. The figures need not all be equal, but every difference needs an explanation and a physical or system location.
For example, if a record shows 500 completed units, 20 held for review, and 480 proposed for shipment, the release reviewer should be able to find the hold reference and verify that the 20 held units are absent from the 480-unit carton allocation. The numbers here illustrate reconciliation only; they are not a sampling plan, acceptance level, or WELLHW production example.
For each carton or pallet group, confirm that the packing list, label, and lot mapping agree with the approved release quantity. Where the contract requires key-group, accessory, or spare-part information, use a controlled reference and authorized channel. Do not copy key codes, bitting, or access hierarchies into a broadly shared shipping worksheet.
Use a Release Decision With a Clear Boundary
| Status | Meaning | Next action |
|---|---|---|
| Ready for review | Evidence is assembled but not yet approved | Check identity, coverage, quantities, open events, and authority |
| Hold | A requirement, result, identity, or quantity remains unresolved | Identify affected stock and the owner of the missing decision |
| Partially released | Only a named subset meets all release conditions | State exact lots, cartons, quantities, and excluded stock |
| Released | The named shipment unit and required evidence have been approved by the authorized role | Transfer the approved identity and documents to logistics |
| Release withdrawn | New evidence invalidated a prior decision before or after dispatch | Freeze further movement and use the contract’s escalation and notification path |
“Partial release” is useful only if the released subset can be physically and digitally distinguished from held stock. A deviation request is not an automatic release. If a proposed shipment departs from an approved requirement, use the lock order deviation request and obtain the authority required by the order before the affected units move. If a quality issue needs cause analysis and recurrence prevention, link the separate supplier corrective-action record.
Copyable Lock Pre-Shipment Release Record
Adapt this record to the buyer’s quality system. Each blank should either contain a value, a controlled reference, or a documented “not applicable” decision with its reason. Avoid a single unchecked “all OK” box.
1. Record control
Release record ID / revision / date: ____
Buyer / supplier / program: ____
Record owner and authorized release role: ____
Governing purchase order, quality plan, and contract references: ____
2. Release-unit identity
PO line / buyer part / supplier part / approved revision: ____
Variant, finish, and controlled key-group reference where applicable: ____
Lot or batch IDs / production or storage location: ____
Destination / shipment reference: ____
3. Quantity reconciliation
Completed quantity: ____
Accepted and allocated quantity: ____
Held / rejected / reworked / replaced quantity and record IDs: ____
Carton or pallet IDs and unit counts: ____
Proposed release quantity and explanation of differences: ____
4. Evidence index
Approved baseline and sample/change references: ____
Inspection or test record IDs, results, coverage, and reviewer: ____
Packaging and label approval plus actual verification: ____
Lot-to-carton map / packing list / required certificates or documents: ____
Open quality events and their affected boundaries: ____
5. Exceptions and action
Missing or conflicting evidence: ____
Material on hold and its location: ____
Required correction, review, deviation, or notification: ____
Action owner / due date / completion evidence: ____
6. Decision and transfer
Status: ready for review / hold / partially released / released / withdrawn
Exact released lots, cartons, and quantity: ____
Exact exclusions and restrictions: ____
Authorized reviewer / decision / date and time: ____
Logistics handoff acknowledgment and document set: ____
Post-release issue or withdrawal reference, if any: ____
Audit From the Carton Back to the Decision
Before dispatch, select a carton from the proposed shipment and trace its label to the packing list, lot, product acceptance evidence, approved revision, and release decision. Then start with the release record and verify that each named carton exists, carries the matching identity, and is absent from any active hold. This two-direction check tests whether the paperwork corresponds to the physical shipment.
Watch for a release signed before the final inspection result; a packaging approval used for a different label revision; a lot report that covers only some cartons; a quantity adjustment with no stock movement; or a deviation whose approval applies to a different batch. Record each mismatch and route it to its owner. Do not silently edit an old acceptance result to make the release package appear complete.
What to Send for a Supplier Discussion
Send the non-confidential purchase-order line, approved part and revision references, planned lots and quantities, required inspection and packaging document list, carton or pallet plan, open hold references, and the role authorized to release the shipment. Ask the supplier to identify gaps and the evidence needed to close them. For a project review, contact WELLHW with that non-sensitive summary; exchange controlled drawings and security-sensitive key records through the agreed authorized channel.
Source and Scope Note
ISO, “Release of ISO 10013:2021, Quality management systems – Guidance for documented information”, February 17, 2021; accessed October 13, 2026. It supports the narrow point that documented information helps organizations operate and preserve evidence of processes. The release-unit map, evidence matrix, status model, quantity path, copyable record, and two-direction audit are original editorial tools. They are adaptable buyer-side suggestions, not a claim that WELLHW uses a particular system or that one format satisfies every contract or standard.
