Quick answer
A perfume OEM project handover should give the next buyer-side owner one reliable view of the current product configuration, the records that support it, the decisions already made and the questions that still need action. It is not a production release, quotation acceptance or substitute for project-specific review. Its purpose is to prevent an earlier file, sample or chat message from being mistaken for the current instruction when responsibilities change.
Create the handover before a buyer changes roles, adds a procurement colleague, moves from development to launch planning or asks a new agency to manage artwork. Keep it short enough to use, but link every important statement to a named record and revision.
Start with one clear project identity
The person receiving a handover should not have to reconstruct the project from subject lines and file names. Begin with a one-page summary that names the exact configuration being discussed. A broad label such as “50 ml perfume project” can cover several fragrance directions, bottle options and artwork files.
| Record | What the handover should identify |
|---|---|
| Working product name | The buyer’s current SKU or project name and the intended product format |
| Configuration reference | Fragrance or formula reference where applicable, fill size, component set and pack-out reference |
| Current stage | Briefing, sample feedback, packaging review, quotation alignment or another named stage |
| Buyer-side owner | The person who consolidates the current instruction and the people who provide specialist input |
| Supplier-side contact | The current contact and the document or message that contains the latest shared instruction |
| Intended market and channel | The destination and route to market being considered, without treating this as a completed review |
Use the same project name and references in the brief, sample record, packaging register and quotation discussion. When a name changes, note the former name so older records remain traceable.
Separate the current instruction from project history
A handover needs history, but the new owner first needs to know what is current. Put a short “current instruction” section at the top, then list superseded items separately. This prevents an old sample comment or early bottle rendering from being followed by accident.
For every important record, state its purpose. For example, a file may be an inspiration reference, a request for quotation, a sample-feedback record or a buyer instruction for a named next step. Avoid a single status such as “approved” when different people could read it as creative preference, artwork review or production authorization.
| Status | Meaning in a handover |
|---|---|
| Current reference | The record the team should use for the stated purpose now |
| Submitted for review | A record sent for a named review; no outcome should be inferred yet |
| Decision recorded | A buyer decision tied to a specific version and purpose |
| Superseded | An earlier record retained for traceability but not for current instructions |
| Open action | A question, owner and next action that still need follow-up |
This simple language is more useful than trying to make the handover look fully complete. An honest open action is safer than an unlabelled assumption.
Make samples and feedback easy to trace
Sample discussions become hard to follow when comments refer only to “the latest one.” Record the sample code or label, date received, the evaluation method used and the feedback document that applies to it. If the project has several fragrance directions or packaging samples, keep their references separate.
The handover should tell the next owner whether a comment was an observation, a requested change or a final buyer-side decision for a stated purpose. It should also identify who consolidated the feedback. This gives the supplier one clear route for the next response and helps the buyer avoid reviving an older request after the team changes.
Do not describe a concept sample as a blanket approval for a different formula, pack or stage. When an item changes, add the new reference and note which earlier decisions may need to be revisited.
Bring packaging and artwork records into the same view
Packaging work often runs in parallel with fragrance development. The handover should name the bottle, pump, cap, decoration, label, carton, insert and pack-out references that belong to the configuration being discussed. Link to the current artwork or proof revision rather than attaching unnamed files.
| File or item | Revision | Purpose | Current owner | Handover note |
|---|---|---|---|---|
| Product brief | Named revision | Defines the buyer’s intended product scope | Buyer project owner | Link the current copy and any open choices |
| Sample feedback | Named sample and date | Records observations and requested changes | Feedback owner | State whether a consolidated response was sent |
| Packaging register | Named revision | Connects components, decoration and pack-out references | Packaging or design owner | Mark current versus replaced components |
| Artwork or proof | Named revision | Identifies the file under discussion | Design owner | State the review purpose and any open content inputs |
| Commercial record | Quotation number and date | States the commercial scope discussed | Procurement owner | Do not extend its scope by assumption |
File names such as “final” or “latest” do not give a new owner enough context. A stable reference, revision and purpose do.
Carry forward open actions without hiding them
The handover should include a short open-action list. Each item needs one owner, the information or decision required, and the next communication point. Keep commercial, technical, artwork and destination-market questions distinct so the recipient can route them to the right person.
Examples of useful open-action wording include “buyer to provide the current barcode reference for artwork review” or “confirm whether the revised component reference is included in the current quotation discussion.” These phrases explain what is needed without making a claim about availability, timing, documentation or market readiness.
If an earlier decision depends on an item that is still open, state that dependency. That is especially helpful when a project changes its component reference, artwork version, destination or quantity basis. A new owner can then see what must be checked again instead of assuming an old conclusion carries forward.
Use the handover as a controlled communication reset
After preparing the record, the outgoing owner should review it with the incoming owner and identify the single buyer-side contact who will send consolidated instructions. Share the current record with the supplier when it helps clarify which references and actions are current. The goal is not to resend every historical file; it is to establish one usable baseline for the next conversation.
Before the first new instruction is sent, check that it names the project configuration, refers to the relevant sample or file revision, separates open questions from decisions and identifies the recipient expected to respond. This gives both teams a cleaner starting point than forwarding a long chain of messages.
A practical handover checklist
- Name the current product configuration, including the project or SKU reference.
- Identify the current buyer-side owner and any specialist contributors.
- Link the current brief, sample record, packaging register, artwork revision and commercial record.
- Label each record by purpose and mark replaced versions as superseded.
- State the current instruction separately from background history.
- Record feedback against the exact sample or file reviewed.
- List each open action with an owner, required input and next communication point.
- Check which earlier decisions may need a new review after a change.
- Give the supplier one consolidated buyer-side contact for the next instruction.
Related reading
- Use the custom perfume manufacturer brief to establish the first project record.
- Structure fragrance comments with the perfume sample revision feedback guide.
- Keep physical and artwork records aligned with private-label perfume packaging version control.
- Track important questions and outcomes in a perfume OEM decision log.
FAQ
Is a project handover the same as a production release?
No. A handover communicates the current project record and open actions. A production release should be a separate, project-specific instruction tied to the exact configuration and required reviews.
What should happen to older files?
Keep them traceable, but label them as superseded or background material when they are no longer the current reference. The new owner should be able to find the current record first.
Who should send instructions after a handover?
Name one buyer-side owner to consolidate comments and issue the current instruction. Other team members can contribute specialist input, but the supplier should not have to choose between conflicting messages.