Decide what the sample is meant to prove
Before a sample arrives, define its job. It may be intended to test product direction, visual finish, materials or components, packaging interaction, label presentation, content production needs, or a combination of these. A sample cannot answer every question at once, especially when product requirements, destination markets or packaging details are still changing.
Write down the questions you need the sample to answer. For example: Does the form align with the approved reference? Does the colour read consistently under the lighting used for launch content? Does the packaging protect the item and communicate the intended brand position? Is there a label or product-information question that needs to be resolved before a later step? The goal is not to create a generic pass-or-fail exercise. The goal is to make the review useful to the specific project.
Review against a controlled reference
A sample should be reviewed against one agreed reference set, not against a moving collection of messages, screenshots and memories. This reference may include the product brief, approved visual direction, colour reference, packaging layout, required components, known destination information and the written scope for the current stage.
When feedback is collected, separate observations from change requests. An observation records what you saw. A change request explains what should be different and why it matters. If the feedback changes the agreed scope, cost assumptions, production method, timeline or documentation needs, identify it as a material change rather than treating it as a minor comment. This protects both the creator and the production team from approving different versions of the same project.
Check the product, presentation and information together
A product sample is experienced as a whole. Review the product itself, then review the customer-facing presentation. Depending on the category and approved scope, this may include surface quality, assembly, feel, fit, function where relevant, colour, finish, scent direction where relevant, packaging construction, inserts, product information and exterior presentation.
Use category-appropriate questions rather than copying a checklist from another type of product. An intimate device, garment, body-care item and accessory may require very different reviews. If electrical, materials, labels, ingredients, safety files, destination requirements or other regulated considerations apply, identify the open question and the owner for resolving it. A sample review is not a substitute for category-specific technical or legal assessment.
Consolidate feedback before sending it
Multiple reviewers can make a sample review stronger, but only when their feedback is consolidated. Choose one person or team to collect comments, resolve contradictions and send a single version of the requested changes. This avoids a situation where one reviewer approves the finish, another requests a different finish, and neither request is clearly tied to the final decision.
Set a clear feedback date and identify whether the current sample is approved, approved with limited changes, requires another review, or is not suitable for the intended path. If you need photography or launch assets, record whether they may be created from this version or whether they must wait for an updated sample. This ensures public-facing materials do not accidentally show a version that will not be produced.
Record the approval decision in writing
The approval record should say what was reviewed, which version or sample it relates to, what is approved, what remains open, and what must happen before the next stage. It should also name the person authorised to approve the relevant decisions. A written record is especially important when packaging, labels, variants, source files or sensitive product details are involved.
Before production is considered, ask whether the brief, quote, scope, sample outcome and destination assumptions still match. If they do not, pause and update the written basis for the project. A careful approval process does not slow a good launch. It prevents avoidable rework and gives the next decision a clearer foundation.
Ready when your brief is
Turn the guide into a project conversation.
Tell us what you are considering, what is essential to your brand, and what you would like to validate next. Sensitive information can stay for the appropriate project stage.
Discuss your product direction