Direct answer
A sample is useful only when its identity, revision, configuration, test conditions, deviations and approval decision are recorded. Photos alone do not create a production reference.
Sample approval record
| Section | Fields |
|---|---|
| Identity | Model, revision, serial/sample ID, firmware, date and responsible parties |
| Configuration | Driver, enclosure, battery, radio, controls, accessories, color and materials |
| Tests | Methods, conditions, results, tolerances and open issues |
| Artwork | Logo, labels, manual, packaging and revision numbers |
| Decision | Approved, approved with deviations, rejected, or data needed |
| Change rule | Which changes require notification, retest and re-approval |
Golden sample control
Seal or otherwise identify the approved sample, retain matching documents, record custody and define how production units will be compared against it.
Minimum fields in the approval record
- Sample identifier, model, hardware revision and firmware version
- Specification, bill-of-material or controlled configuration reference
- Measured results and the conditions used for each check
- Artwork, packaging, manual and accessory revisions
- Photos, labeled deviations and unresolved actions
- Approver, approval date and the rule for later changes
Keep the approved sample together with the signed records as a production reference. If hardware, firmware, enclosure, battery, accessories, labeling or packaging changes, record the change and decide in writing which checks and approvals must be repeated.
Evidence boundary: This page provides a decision framework, not a statement that a selected product has passed a test or holds a certificate. Confirm model-specific specifications, reports, samples and commercial terms in current written documents.