How to Give Useful Feedback on Skincare Samples

“Make it lighter” can mean several things: easier to spread, less oily, less shiny, or less noticeable after application. A useful sample review tells the chemist which of those you mean, when you noticed it, and what you want to keep.

Record the sample code and version, describe how you used it, and separate your observations from your requested changes. Then rank the revisions. That gives the next sample a clear purpose and gives your team something specific to compare when it arrives.

This guide is for product-development feedback about the experience of using a sample. Follow the developer’s instructions for evaluating it; these notes are not a safety study or a substitute for product testing.

Start with the sample and the use conditions

Put the sample code, version, date received, and reviewer name at the top of the feedback. If the label doesn’t clearly identify the version, ask before comparing it with earlier samples. Photograph the label so a handwritten code doesn’t get lost in an email thread.

Name the reference you’re comparing it with. That might be the previous lab sample or a particular retail benchmark. “The old one” isn’t enough if several versions are circulating.

Use a consistent routine when comparing samples, within the instructions supplied. Record the amount, application area, whether skin was wet or dry, and any products used before or afterward. Note when you made each observation: during spreading, just after application, or later. These details help the formulator understand what you mean without having to reconstruct the session.

Be specific about the package as well. Was the sample in a lab jar, the proposed retail tube, or a pump bottle? An observation about scooping from a jar doesn’t answer how the product will dispense from its intended pump.

Describe what happened before saying what to change

Break the experience into a few useful parts. You don’t need technical vocabulary; you need observations another person can understand.

• Texture before application: Does it hold its shape, flow, or feel stringy as you take it from the container?
• Spread: Does it move easily across the application area? Is there drag or visible residue while rubbing it in?
• Finish: Does skin look shiny or matte? Does the surface feel tacky, oily, powdery, or coated? Say when you noticed it.
• Scent and appearance: What do you notice, and what would you prefer? Keep a color or scent preference separate from a performance concern.
• Package behavior: How does it dispense? Does product collect around the opening or come out in an amount you find hard to control?

Keep the observation and the request together: “The cream spreads easily, but my fingertips still stick lightly to the application area five minutes later. Keep the spread and reduce that tacky finish.” The time here records a particular reviewer’s experience; it isn’t a standard all products must meet.

Avoid prescribing an ingredient change unless the ingredient itself is a requirement. “Reduce the oil” assumes you know what causes the finish. “Reduce the oily feel after application” gives the chemist the result you’re asking for and leaves room to choose how to approach it.

Turn “make it lighter” into a clear request

“Make it lighter but more moisturizing” combines a sensory preference with a performance goal. First explain what feels heavy. Then explain what “more moisturizing” means in your brief: a more comfortable afterfeel, a different claim, or a measured result you want the product to achieve. Ask the developer how that result would be evaluated.

An observation can be useful without diagnosing its cause. If you see pilling when layering the sample with another product, record which product, the order of application, and the timing. Report what happened before concluding that the formula or package needs a particular fix.

Example: a completed sample feedback card

The following is a fictional internal review of a moisturizer. The sample codes, conditions, and observations are invented to show how a brand might document preferences; they are not InSpec test results or an evaluation protocol.

Rank the changes before sending them

Combine the team’s comments into one revision request, with one person responsible for resolving contradictions. Preserve differences that matter: if one reviewer wants a richer finish and another wants less residue, don’t summarize both as “improve the feel.” Decide which preference best matches the product brief, or ask for a discussion before another revision.

List what must change, what would be nice to change, and what should stay. If the developer says two preferences conflict, ask it to explain the tradeoff before choosing a direction. Adding a new fragrance or changing the format should be identified as a new request, rather than hidden inside approval of the current sample.

Copy this blank feedback card

Use one card per sample version. Attach photos or short videos where they explain an observation better than words.

• Product and reviewer:
• Sample code/version; date received and reviewed:
• Reference sample or benchmark, including its identifier:
• Package used for this review:
• Use conditions: instructions followed, amount, application area, wet/dry skin, other products, and observation times.
• Observations: texture, spread, finish, scent/appearance, and dispensing behavior.
• Keep:
• Must change, in priority order:
• Optional changes:
• Questions for the developer:
• Decision: revision requested / sensory preferences accepted / further discussion needed.

Be clear about what you’re approving

Accepting a sample’s texture and finish records your preference for that version. It does not establish safety, shelf life, or support for a moisturizing or other performance claim. FDA describes cosmetic safety evaluation as drawing on relevant safety data and, where needed, additional scientifically sound testing. FDA: product testing of cosmetics

Ask the developer to separate sensory acceptance from the testing, specifications, packaging review, and other approvals still required for your project. Keep the approved sample identifier with that record so a later change doesn’t inherit an earlier approval by accident.

InSpec Solutions offers in-house skincare formulation and manufacturing. Explore our skincare manufacturing capabilities or tell us what you want to develop. Bring your current brief and the specific qualities you want to keep or change.