A formulation brief tells the lab what the product must achieve, which constraints matter most and how you will judge a prototype. Write it before asking for development work, so the formulator does not have to guess what “premium,” “lightweight” or “launch-ready” means to your team.

You do not need a finished formula to write a useful brief. You need a defined user, an intended use, ranked requirements, pack assumptions and a way to decide on samples. To see where the brief sits in the wider testing, production and market-access process, read the cosmetic product development roadmap.

Before you begin: collect decisions, not ingredient guesses

Gather what you already know and be honest about what is still undecided:

• Intended user, application area and conditions of use.
• Product format and the customer benefit you want to explore.
• Launch markets and draft claims.
• A sensory reference, if you have one.
• Packaging assumptions and commercial boundaries.
• One person with authority to consolidate feedback and approve the brief.

Where something is unknown, write “decision needed.” An honest gap is more useful to the lab than a confident guess, and the formulator and safety assessor will tell you what further information they need.

Step 1: Rank the product requirements

If every request carries equal weight, the lab has no basis for proposing a trade-off. Sort them first.

1. Describe the product, intended user and intended use in plain language.
2. Label each requirement must-have, preferred or open for recommendation.
3. Give each must-have an acceptance question and a decision owner.
4. Ask the lab to flag conflicts and feasibility questions before making samples.

“Dispenses cleanly through the proposed pump” is a requirement the lab can work toward. Naming an emulsifier or a mixing temperature without a technical reason takes a formulation decision out of the formulator’s hands.

Describe how the product will be used, not just who the customer is. In the EU, Article 10 of the Cosmetics Regulation (consolidated version of 18 May 2026) lists intended use and anticipated exposure among the points the safety assessment must consider. Your brief supplies that context. The safety assessor carries out the assessment.

A quick test of the ranking: if a prototype meets every must-have but misses a preference, would you continue? If nobody can answer, settle the priorities first.

Step 2: Turn sensory language into an evaluation target

“Lightweight” and “silky” mean different things to different people. A reference product makes the request concrete without asking the lab to copy someone else’s formula.

1. Identify the reference product or sample, with a code and version where available.
2. Say what you like about it: spread, residue, appearance, perceived absorption or dispensing.
3. Say what should be different.
4. Agree with the lab how and under what conditions prototypes will be evaluated.

Write down what you observed and leave the cause to the formulator. Instead of “remove the oil, it’s too heavy,” write “the sample leaves more noticeable residue than reference R01 under the agreed conditions.” The formulator can then work out why.

Sensory preference has limits. Liking one sample more than another says nothing about preservation, stability or safety. Intertek’s cosmetic stability testing page describes formula stability, final-pack compatibility and packaging functionality as separate investigations, and each needs its own scope.

The decision owner should be able to say which observations would justify asking for a revision. Avoid numeric scores unless you have agreed a scale, because they suggest more precision than an informal evaluation can deliver.

Step 3: Record markets, claims, packaging and commercial constraints

Markets, claims, pack and budget can each change the development job. Keep confirmed decisions apart from assumptions still awaiting a specialist or supplier.

1. Name the launch markets and give the actual proposed claim wording.
2. Identify the container, closure, dispenser and fill size, or mark them undecided.
3. List material restrictions or ingredient requests, each with a reason and a priority.
4. Record budget limits, requested deliverables, timing dependencies and opening-order assumptions.

Label every claim in the brief as proposed. In the EU, Article 2 of Regulation (EU) No 655/2013 ties claim wording to the common criteria and to supporting documentation in the Product Information File. Writing a phrase into the brief does not show the finished product can support it.

The cosmetic development budget and quote comparison worksheet helps keep the work you request separate from the eventual quote. The cosmetic manufacturing MOQ guide explains why formula, component and filling minimums must be checked together rather than treated as one number.

Ask the lab to point out every assumption that affects scope. Treat the launch date as a target until the dependencies behind it are understood.

Step 4: Complete one versioned formulation brief

Copy the template into your project workspace and adjust the fields to your project. Keep one current version for the lab to respond to.

Copyable cosmetic formulation brief

BRIEF ID / VERSION / DATE:
PRODUCT NAME OR WORKING REFERENCE:
BRAND DECISION OWNER:
LAB PROJECT AND TECHNICAL CONTACTS:

PRODUCT AND USE
- Format, intended user and application area:
- Intended use and relevant conditions of use:
- Initial markets:

RANKED REQUIREMENTS
- Must-have: [requirement / acceptance question / decision owner]
- Preferred: [requirement / permitted trade-off / decision owner]
- Open: [question / recommendation requested / owner to decide]

SENSORY TARGET
- Reference identity:
- Desired similarities:
- Desired differences:
- Evaluation context and questions to agree:

CLAIMS AND CONSTRAINTS
- Proposed claim wording and review owner:
- Requested ingredient or material restrictions and reasons:
- Pack, closure, dispenser and fill-size references:
- Unconfirmed packaging assumptions:

COMMERCIAL SCOPE
- Development deliverables and quote requested:
- Budget boundary or spend authorization status:
- Sample/revision scope to agree:
- Opening-order, component and filling assumptions:
- Desired timing and dependencies:

DECISIONS AND EVIDENCE
- Prototype acceptance criteria:
- Separate testing/assessment work to scope:
- Open questions / owner / decision point:
- Sample identification and feedback process:
- Changes requiring review before implementation:
- Brand approval / lab acknowledgment / unresolved conditions:

Sending a brief does not mean the lab has agreed to it. Ask for written confirmation of the scope and any exceptions, record the version both sides accept and keep open conditions visible.

Worked example: a leave-on facial moisturizer

Here is how a first-draft brief for an illustrative project might read. The references (B01, M01, P01, R01) are placeholders.

• Identity: brief B01, version 1. Working product M01, a leave-on facial moisturizer for adults. The brand product lead owns the brief, and lab contacts are still to be appointed.
• Market and use: initial EU launch, routine facial application. The formulator and safety assessor will say what further use information they need.
• Must-have M1: works with the proposed pump pack P01. Acceptance question: can the lab develop toward this pack, and what compatibility and dispensing evidence will be needed?
• Must-have M2: all feedback is tied to an identified sample and this brief version. The brand product lead decides on sensory questions, and technical decisions stay with the qualified parties.
• Preferred P1: less noticeable residue than benchmark R01. The lab may propose a texture trade-off, but the brand must agree before the target changes.
• Open O1: formulator to recommend a texture direction. No ingredients are specified.
• Proposed claim: “leaves skin feeling soft.” Needs claims review. Including it here does not approve it.
• Pack and sensory review: P01 and R01 to be supplied. Evaluation conditions to be agreed before prototypes are compared. A sensory review is not a compatibility approval.
• Commercial request: an itemized development proposal covering revision rounds, exclusions, production minimums and timing dependencies. The brief itself authorizes no spend or order.
• Acceptance and holds: a prototype moves to further work once the brand records sensory acceptance and the lab has met the agreed prototype criteria. Safety, stability, claims, pack suitability and production release are separate decisions.
• Open actions: brand supplies P01 and R01 and confirms the budget. The lab responds on feasibility and proposed evidence. Both are resolved before the related work is commissioned.

That is enough for a first inquiry. Each named unknown gives the first supplier conversation a concrete agenda, and the approved development specification comes later.

Step 5: Evaluate prototypes and request focused revisions

End every sample round with one consolidated decision and one clear next action. Conflicting informal comments should never reach the formulator as separate instructions.

1. Log the sample reference, formula version, brief version and pack configuration.
2. Evaluate against the agreed criteria, recording observations separately from preferences.
3. Mark the outcome as accepted for a stated next step, revise or rejected, with reasons.
4. Send one reconciled revision request and ask the lab to confirm the work and any scope change.

Write down exactly what an acceptance allows. “Sensory direction accepted for further development” and “approved for commercial production” are very different decisions. Record unmet criteria even when the team likes the sample overall.

A good revision request names the observation, the change wanted and its priority, for example: “Sample S02 leaves more noticeable residue than R01. Reducing residue is still preferred. Pump-pack feasibility is still a must-have.” Do not let feedback quietly rewrite the brief’s priorities.

Check that the lab knows what should change, what should stay and who will judge the next sample. Confirm how many revision rounds the agreement includes before authorizing more, because this varies by supplier.

Step 6: Control changes before moving to the next gate

Keep a record of what changed and which earlier decisions it affects. A new ingredient request, pack, target user or claim can change the job even when the product name stays the same.

1. Give each proposed change a reference and a reason.
2. List the brief fields, samples, quotes and reports it affects.
3. Ask the relevant technical, commercial and regulatory owners to assess it.
4. Approve the revised scope before implementing it, and issue a new brief version.

An earlier approval only covers what was evaluated. Switching from pump P01 to jar P02, for instance, should reopen the pack-related assumptions and evidence plan. What retesting is needed depends on the actual product and requires qualified input.

Make sure everyone works from the current brief and can find the previous decision. Keep superseded versions for context, clearly labeled so nobody mistakes them for live instructions.

Next step: ask the lab to respond to the brief

Send the ranked brief with its references and ask for a written response on feasibility, assumptions, deliverables, exclusions and open decisions. Resolve the biggest unknown before paying for the work it affects. The aim is a shared development scope, not just a more polished idea. The development roadmap shows the next evidence gate after prototype decisions.

Spotted an error or an outdated requirement? Contact Cosmetic Labs with the passage and a supporting source. Cosmetic Labs runs a directory connecting beauty brands with cosmetic labs. Publisher details are in the legal notice.