A pre-production meeting is the last structured chance to confirm which product version the factory will build. The buyer's job is to convert discussion into a clear decision record that shows what was verified, who agreed, and what remains unresolved. That record stops version drift, lets production proceed, and provides a single source for any later disputes. This article gives a working meeting agenda, the precise questions to ask, the items to capture as evidence, and a practical decision-record template you can use. The emphasis is on turning the meeting into a documented commitment so subsequent sourcing decisions rely on a visible record rather than memory or email fragments.

Prepare and circulate the pre-production package

Before the meeting, assemble a pre-production package that contains the master technical drawing or spec sheet, the current bill of materials, the latest lab or test reports if relevant, finished part samples or photos, and the sample approval form. Include version numbers and dates on every document. Circulating the package 48 to 72 hours before the meeting gives participants time to spot mismatches and prepare questions.

The package should also include a short meeting agenda labeled Production Readiness Review and a draft decision record template. Ask the factory to confirm receipt and to upload any factory-side quality control checklists or in-line process photos. When attendees open the meeting, everyone must be looking at the same files and the same sample version to avoid confusion.

• Master spec with version and date
• Bill of materials and component sources
• Sample approval form and photos
• Factory QC checklist and process photos
• Draft decision record template

Run a focused agenda that confirms the current version

Open the meeting by reading one sentence that states the purpose: confirm the current product version for the upcoming production run. Then walk the group through the package in a rigid order: spec, BOM, sample, test results, production process notes. Doing the same sequence every time reduces the chance that detail gets skipped.

Use the Production Readiness Review flow to confirm discrete checkpoints: dimensions and tolerances, critical materials and suppliers, labeling and packaging, functional performance, and compliance tests. After each checkpoint, ask for explicit confirmation of the document and physical sample version. Avoid open-ended phrasing; require a yes, no, or conditional answer tied to specific evidence.

• Confirm spec version and file name
• Verify BOM line items by part number and supplier
• Inspect sample photos and physical sample version
• Review test report version and scope
• Agree packaging and labeling files

Ask exact questions and collect evidence during the meeting

Turn subjective questions into verifiable ones. Instead of asking Does this sample look correct, ask Does the sample match Drawing A Rev 3 within the stated tolerances? Request the factory to point to the clause or dimension on the drawing while you record the reply. If the factory says yes, capture the time-stamped acknowledgment in the record and note which file was referenced.

Record evidence for each affirmative. Evidence can be a photo annotated with the drawing reference, a time-stamped video of a functional test, a scanned test report with lab header, or a factory sign-off on a checklist. If the evidence is a physical sample located in the factory, note the sample ID, storage location, and who inspected it. The goal is that any later reviewer can match each confirmation to a discrete artifact.

• Require a yes/no/conditional response tied to a file name
• Capture photos, videos, or test reports as supporting evidence
• Assign sample IDs and record storage location
• Timestamp and name the person who gave the confirmation

Use a decision-record template to capture commitments

A simple, consistent template turns the meeting into a decision record. The template should include meeting date and participants, the confirmed product version (file name and revision), a short checklist of confirmed checkpoints, listed evidence items, explicit unresolved items, and the approvals including digital signatures or typed names with timestamps. Keep the language factual and avoid interpreting intent.

During the meeting, fill the template live and share your screen. Read each completed line out loud and ask attendees to confirm accuracy. When all confirmed items are entered, request a formal approval: an email reply that quotes the completed record, a typed approval in the meeting chat, or a scanned signature. Save the completed record with the master spec in your document control system so that subsequent sourcing decisions reference the exact version confirmed.

• Meeting metadata: date, attendees, roles
• Confirmed product version: file name and revision
• Checkpoint checklist with evidence links
• Unresolved items with owners and deadlines
• Formal approval line with timestamp and sign-off

Handle disagreements and change requests without losing the record

Not all issues will resolve on the spot. If the factory proposes a change, document the proposed change as a formal change request within the decision record. Note who proposed it, the reason, the proposed technical wording, and an owner with a deadline for decision. Do not allow verbal changes to proceed without an added versioned spec and a recorded approval.

When opinions conflict, collect the facts that will decide the issue: reference test data, supplier capability statements, sample measurements, and cost impact estimates. If a technical specialist or external lab is required to resolve the dispute, record that need and the selection criteria. The record should show the path forward and avoid ambiguous commitments that can be interpreted differently by buyer and factory.

• Enter proposed changes as change requests with owners and due dates
• Do not accept verbal approvals; require written, versioned updates
• Document which evidence will resolve disputes and who will provide it

Turn the decision record into the next sourcing decision

Once the record is signed, use it to trigger the next sourcing step. That could be releasing the production order, ordering long-lead materials, scheduling first-article inspection, or commissioning an external test. Reference the exact file name and revision in purchase orders and material releases so procurement and the factory execute to the confirmed version.

Archive the decision record with the master spec and link it to the production batch number during manufacture. If a subsequent change is required, start a new pre-production meeting and decision record rather than appending to the original file. This practice preserves a clear chain of custody for every version and makes future sourcing decisions traceable to the recorded confirmation.

• Use the signed record to authorize production steps
• Include confirmed file and revision in purchase orders
• Archive the record and link to production batch for traceability

Schedule the pre-production meeting and circulate the pre-production package 48 hours before the session.