When a product version is not explicit, every meeting becomes a guessing game. Suppliers, factory technicians, and buyers may each mean different samples, drawings, or BOM revisions when they say the same name. The buyer job is to convert a meeting into a visible, actionable record that matches one approved reference. This article shows a practical method: prepare the meeting with the approved reference attached, run comparisons during the discussion, write decisions that point back to that reference, and use a product change log to make the next sourcing decision transparent.

Define the product version before the meeting

A product version can be an approved physical sample, a labeled engineering drawing, a BOM revision number, a SKU with linked photos, or a change log entry. The ambiguity that kills pre-production meetings comes when attendees assume different references. Start by naming exactly which reference will govern the meeting and send it with the invite.

Before you open the discussion, confirm the reference ID, who approved it, and when. That single sentence sets the frame for every technical question, cost tradeoff, and capacity decision. If the meeting touches multiple versions, split agenda items by reference so each decision maps to one version.

• Attach a photo of the approved sample with scale and label
• Include the BOM revision and drawing file names
• Link the product change log entry or sample approval ID

Prepare a reference-linked agenda and documents

Create an agenda that lists items as comparisons against the approved reference. Each line should name the component, the suspected issue, and the reference clause or sample to check. A clear agenda keeps the meeting short and prevents side conversations about unspecified versions.

Send the agenda and all referenced documents at least 24 hours before the meeting so participants can check measurements, tolerances, and tooling notes. When suppliers receive the exact reference, they can prepare counter-evidence such as sample photos, dimension checks, or proposed tooling drawings that cite the same reference.

• Agenda line example: "Handle height vs approved sample ID #A23; supplier proposes +2 mm"
• Documents to include: approved sample photos, spec sheet, BOM, tooling notes, PCL entry

Run the meeting as a series of reference comparisons

Open the meeting by reading the approved version ID aloud and confirming everyone sees the same file or photo. For each agenda item, ask the supplier to state their current version reference and then compare differences point by point. Require statements in the form: "Supplier version X differs from Reference Y by…"

Use precise questions that force measurable answers. Ask for exact dimensions, material IDs, color codes, and sample photos with a ruler. If there is a proposed change, capture whether the change is a suggestion, accepted pending sample, or rejected. That distinction determines whether a follow-up pre-production sample is required.

• Sample questions: "Which reference are you using?", "What is the measured difference in mm?", "Who must approve this change?"

Record decisions so every note links back to the approved reference

Meeting minutes fail when they say "approve change" without stating which reference is being changed. Use a template where each decision row contains the reference ID, the clause or component, the decision made, the owner, and a deadline for the next sample or action. That template creates a one-to-one link between discussion and the approved product version.

Make the record accessible and immutable. Save minutes in a central folder and attach any supplier photos or test results to the same entry. If a change requires a new sample, note the sample ID, expected delivery, and acceptance criteria in the same row. This reduces back-and-forth and protects the buyer when production capacity and tooling timelines hinge on one version.

• Decision template fields: Reference ID, Component, Measured difference, Decision (accept/sampling/reject), Action owner, Deadline, Sample ID

Update the product change log and manage disagreements

When the meeting produces a change, record it in the product change log with its source meeting, the exact language of the decision, and the next approval step. The log becomes the historical chain that links the approved reference to later revisions. A single, maintained log prevents parallel versions from circulating in email threads and chat apps.

If parties disagree, require objective proof before accepting a new version. Ask the supplier for dated photos, measurements, or a sample shipment marked with the supplier version ID. If the disagreement affects compliance, performance, or manufacturing cost, the buyer can escalate to a technical reviewer or QA for a measured test rather than a verbal compromise.

• Log entry should include: Meeting ID, Decision text, Supporting files, Request for new sample or test, Approver name and date

Turn the meeting record into the next sourcing decision

Decisions in pre-production must feed the next sourcing action: approve a pre-production sample, change tooling orders, adjust capacity commitments, or hold the PO. Use the version-linked minutes to decide. For example, if the record shows a change accepted pending sample, do not release tooling or bulk production until that sample is approved against the same reference ID.

Keep a short checklist that converts the record into the procurement step you need. Confirm the approved reference ID, the final decision row, the presence of an approved sample ID if required, and the sign-off by the authorized buyer. When those boxes are checked, the sourcing team can proceed with a clear audit trail and fewer surprises.

• Sourcing checklist: Confirm reference ID; Confirm latest PCL entry; Check for approved sample ID; Verify sign-off and deadline

Attach the approved reference to your next pre-production meeting invite and add a reference-linked agenda line as the first item.