Perfume OEM Assumption Log: A Buyer’s Template for Open Project Conditions

Quick answer

An assumption log is a buyer-side record for information a perfume OEM project is using temporarily but has not yet confirmed. It gives each open condition a clear description, source, owner, decision point and possible impact. That lets the team continue planning without quietly turning a tentative idea into a supplier instruction, commercial commitment or product claim.

Use the log for items such as a proposed bottle reference, expected sales market, artwork language plan, target quantity range or intended launch window. It does not confirm formula feasibility, package compatibility, compliance, pricing, MOQ, lead time or production readiness. Those matters need the relevant project evidence and review.

Why an assumption needs its own record

Projects often need to move before every input is final. A buyer may be comparing two bottle shapes, waiting for a market decision or using a preliminary artwork direction to prepare a discussion. The risk appears when a provisional input is repeated in email, a meeting note or a quotation request without its status. Later readers can mistake it for an approved requirement.

An assumption log makes the temporary condition visible. It is not a list of problems and it is not a substitute for a decision log. A decision log records a choice that an authorized owner has made. An assumption log records what the team is currently working from until that choice, evidence or clarification exists.

Create one stable entry for each open condition

Give every entry a short ID and link it to the project, product configuration and records it affects. State the assumption precisely enough that another person can recognize it. “Packaging pending” is hard to act on; “working from bottle reference B-02 for the first quotation comparison” identifies what is temporary and why.

Avoid combining several conditions into one entry. A bottle reference, decoration method and carton structure may be related, but each can change independently and may need a different owner. Separate entries make it possible to close one uncertainty without accidentally closing the others.

A practical assumption-log template

Field	What to record	Why it helps
Assumption ID	A stable project reference	Lets the team discuss the same open condition across files and meetings
Current working condition	The exact temporary input being used	Prevents vague language from becoming a requirement
Source and date	Where the condition came from and when	Shows whether it is a buyer idea, supplier question or earlier record
Affected record or scope	The sample, artwork, quotation, package or market question involved	Reveals what needs review if the condition changes
Owner	Person responsible for confirming, replacing or retiring it	Gives the condition a clear next action
Needed evidence or decision	What would turn it into a confirmed input	Stops a discussion from being mistaken for proof
Review point	The next meeting, quotation round or approval gate	Keeps the condition from disappearing between updates
Outcome	Confirmed, replaced, no longer needed or still open	Preserves the history without treating an open item as approval

Keep the entry factual. A proposed condition can be useful for planning while still being unsuitable for the finished product, destination market or supplier route.

Separate an assumption from a request

An assumption tells the team what it is using while it waits for confirmation. A request asks another party for a response. A useful supplier message can include both: “For comparison only, we are currently using bottle reference B-02; please identify which details you would need to assess the proposed liquid and pack.” This does not state that B-02 is approved or compatible.

When a supplier, designer or buyer specialist responds, attach the response by reference and update the log’s outcome. Do not overwrite the original assumption with a conclusion. Keeping both makes the path from early planning to a later instruction easier to follow.

Link the log to project controls already in use

An assumption log works best when it points to the record that will eventually replace it:

the project brief for the buyer’s intended product and market;
the sample receipt log and feedback tracker for identified physical samples;
the decision log when an authorized owner makes a choice;
the change-request record if an agreed scope changes; and
the status update for the current open-item summary.

These records have different jobs. Linking them keeps a team from copying a temporary condition into multiple places and then trying to reconcile conflicting versions later.

Review assumptions before they become costly

Review the log before releasing artwork, comparing quotations, asking for samples or discussing a production instruction. Focus on entries that affect several workstreams or would make a message misleading if they changed. For each one, choose a clear outcome: confirm it with the required evidence, replace it with a new working condition, defer the related action, or remove it because it is no longer relevant.

Do not close an entry merely because time has passed or someone repeated it in a call. The closing note should identify the record or decision that resolved it, the person responsible and the date. If the team still needs specialist, technical or legal review, the entry should remain open and the relevant review should stay visible.

Example: keep a quotation comparison honest

Suppose a buyer is comparing quotations for a fragrance concept but has not finalized the bottle. The log can state that the comparison uses bottle reference B-02, that the buyer selected it only as a planning reference, and that a packaging owner must confirm the final component path before the quote is used as a purchase basis. If the supplier identifies a different component requirement, the buyer can update the log, request a revised comparison and avoid presenting the earlier figures as a final commitment.

The same pattern applies to a provisional quantity, market, artwork language or timing target. The log does not solve the question; it makes the question traceable until the correct owner and evidence resolve it.

Buyer checklist

Record every material working condition that is not yet confirmed.
Give each condition one stable ID, a source and a date.
State what record, sample, package, quotation or market question it affects.
Assign an owner and name the evidence or decision needed to resolve it.
Keep requests separate from assumptions in supplier communications.
Review high-impact entries before artwork release, sampling or commercial commitments.
Close an entry only by linking the actual decision, evidence or replacement condition.
Preserve the history so later handovers can distinguish planning inputs from approved instructions.

FAQ

Is an assumption log the same as a risk register?

No. A risk register normally records uncertain events and their possible effects. An assumption log records a current working condition that the team is relying on until it is confirmed, replaced or retired. A project may link the two records when an assumption creates a material risk.

Should an assumption be sent to a supplier?

It can be shared when it provides useful context, as long as its temporary status is explicit. A buyer should not present it as an approved specification or ask a supplier to treat it as a final production instruction.

When should an assumption become a decision-log entry?

After the authorized owner has made a decision and the relevant evidence or review supports recording it as the current project direction. The log can then link to that decision and close or replace the earlier assumption.