THE SHORT ANSWER
Creative direction, sample evaluation, technical acceptance and commercial release are different approvals. Record the exact version, application, decision and owner at each stage, so a positive sample response does not quietly become permission to manufacture or sell.
Why is a single approved label not enough?
A product team may approve a sensory direction while application testing, documentation or commercial terms remain open. Those are legitimate separate stages. The problem begins when a short email such as “looks good” is inherited as permission for every next step.
Define the decision in the record. State what was considered, which version it concerns and what is still outstanding. A clear approval does not need to be complicated. It needs to mean the same thing to the developer, technical team, buyer and manufacturer.
What can each stage actually establish?
Use the following table as a project-management framework. It is not a universal release procedure; the actual owners and evidence need to fit your product and organisation.
| Stage | Example decision | What it does not settle by itself |
|---|---|---|
| Brief agreed | The team accepts the current target and constraints | The final formulation |
| Direction selected | A sensory idea is worth developing | Suitability in every product base |
| Sample evaluated | Notes and a next action are recorded for a version | All technical or market requirements |
| Technical acceptance | Defined requirements have been reviewed by their owner | Unrelated markets, changes or applications |
| Commercial agreement | Supply scope and terms are agreed | Every finished-product release obligation |
How do we stop a base change disappearing into the project?
Give the new base a version and connect it to the next preparation. Record why the change was made, who made it and which previous comparisons may no longer answer the same question. Ask the relevant team what needs assessing again.
Do not erase the previous record to make the project look tidy. A useful history explains how the current decision was reached. It also prevents a sample from an old preparation being treated as the reference for a new product without anyone noticing.
What should a sample approval note contain?
Keep the note short enough to use and precise enough to be useful later. The following fields can be copied into your own project record.
- Project and product identity
- Sample, base and document versions considered
- Intended application and market
- The decision being made and its acceptance criteria
- Evidence or observations reviewed
- Decision owner and actual date
- Open actions, responsible people and next decision
How do technical documents fit into the handover?
Keep the relevant specification, SDS, batch information and other agreed documents connected to the material. Their purposes differ. An SDS supports chemical hazard and handling information; it is not itself the workplace risk assessment, as HSE explains.
A document list should show what is available, what has been reviewed and what is still required. If a product code or use changes, ask whether earlier documents still apply. Our specification, SDS and CoA guide explains the different jobs these documents do.
What is a useful next step with FÜNK?
Read our development approach and the sample-evaluation guide. Bring the decisions already made as well as the questions still open. A project can move forward with uncertainty, provided the uncertainty has an owner.
Start a project with the actual status. Creative ambition and clear records can sit comfortably together. The interesting work deserves a handover that remembers what was agreed.
Sources & further reading
General guidance for project planning. Technical requirements depend on the actual formulation, intended use and market.
