How to Close a Pre-Production Meeting with an Evidence-Request Summary

Executive introduction

A pre-production meeting should not end with a general statement that everyone understands what happens next. It should end with a written closeout that identifies each decision, accountable owner, due point, proof requirement, reviewer, acceptance condition, and effect on the production handoff.

The practical objective is to turn every production-related decision into one of three things: an owned action, a requested item of documented information, or an open issue that blocks or qualifies the handoff. This prevents silence, politeness, or a broad “yes” from being mistaken for acceptance.

The closeout should also distinguish information maintained to support production activities—such as specifications or work instructions—from records retained as evidence that activities were completed. The ISO 9001:2015 guidance on documented information explains this distinction while allowing organizations to determine the documented information appropriate to their processes. It does not prescribe one universal document set for every product or organization.

Close the meeting around actions, ownership, and proof

Intended outcome

Use the final part of the meeting to:

• Convert each production-related decision into:
  • an owned action;
  • a requested item of documented information; or
  • an open issue that blocks or qualifies handoff.
• Create a shared written record instead of relying on verbal agreement.
• Separate information used to operate a process from records retained as evidence of completed activities.
• Identify what remains unresolved rather than presenting uncertainty as approval.
• Make the production-release effect of every open item visible.

Apply the documented-information principles described in the ISO 9001:2015 guidance, but do not imply that ISO requires this particular table or one fixed package of documents.

Communication principles for a clear closeout

Use neutral and specific language. Do not infer agreement from silence, politeness, lack of objection, or a general confirmation such as “yes” or “same as before.”

Read back every action in the same sequence:

1. What must be done?
2. Who owns it?
3. When is it due?
4. What proof must be submitted?
5. Who will review that proof?
6. Does production remain blocked until acceptance?

Ask the named owner to confirm the action and evidence request in their own words. This gives participants an opportunity to correct the owner, scope, deadline, evidence type, or handoff effect before the meeting ends.

Replace vague expressions with identifiable conditions:

• Replace “soon” with a date or defined milestone.
• Replace “standard” with the named requirement or controlled reference.
• Replace “approved” with the approving authority, accepted item, and approval status.
• Replace “same as before” with the applicable identifier or revision.
• Replace “send the report” with the required record type, product or component reference, and submission location.

Record disagreement openly. A disputed requirement, uncertain revision, or missing authority remains an open issue; it must not be converted into an approved decision merely to finish the meeting.

Use one agreed term for each recurring item—for example, “specification,” “sample,” “test record,” or “approval”—and preserve that wording in the closeout summary.

Evidence-request boundaries

Request evidence because it supports an identified control, requirement, decision, or review. Do not request files merely to create a larger document package.

Before assigning an evidence-related action, define:

• The document or record type.
• The relevant product, component, process, or requirement.
• The expected identifier, date, or revision, where applicable.
• The acceptable format or repository.
• The designated reviewer.
• The acceptance condition.
• The handoff effect while review is pending.

If a product may fall within U.S. Consumer Product Safety Commission jurisdiction, consult the CPSC Business & Manufacturing guidance as a starting point for identifying relevant information. Do not describe a test, certificate, label, regulatory document, or record as mandatory until the product, jurisdiction, and applicable legal requirements have been established.

Meeting closeout evidence summary

Step-by-step closing sequence

1. Announce the closeout

State that the remaining meeting time will be used to confirm decisions, owners, deadlines, evidence requests, and handoff effects.

Stop introducing new production topics. If a new issue must be raised, record it as an open issue with an owner and next step rather than attempting an incomplete decision.

2. Read back decisions

Identify each point as:

• accepted;
• rejected;
• conditional; or
• deferred.

Reference the applicable specification, requirement, sample, or other controlled information when available. If acceptance depends on later evidence or authorization, mark the decision as conditional rather than accepted.

3. Convert decisions into actions

Assign one accountable owner to each action. Contributors may be listed separately, but shared participation should not obscure accountability.

Give every action a calendar date or a defined handoff milestone. Avoid deadlines that depend on undefined terms such as “as soon as possible” or “before production” without a specific production gate.

4. Define proof requirements

State what documented information will demonstrate completion. Include enough detail to prevent submission of the wrong revision, an unrelated record, or evidence for a different product or component.

Confirm:

• what must be submitted;
• how it must be identified;
• where it must be submitted;
• who will review it;
• what acceptance requires; and
• whether handoff remains blocked during review.

5. Identify blockers and exceptions

Flag missing information, disputed requirements, unavailable evidence, unresolved technical points, and decisions awaiting authority.

For each issue, state whether it:

• blocks production handoff;
• permits only a conditional handoff; or
• does not block handoff.

An open item that does not block handoff still requires an owner and due point.

6. Obtain explicit confirmation

Ask each owner to confirm assigned actions and evidence requests in their own words. Record corrections before ending the meeting.

Name the person responsible for issuing the written summary and confirm the agreed distribution channel or repository.

Header information to capture

Add these fields above the closeout table:

Control field	Entry
Meeting title and date
Product or project identifier
Production stage covered
Participants and represented functions
Source requirements or specifications reviewed
Closeout-summary owner
Summary issue date and revision
Agreed location for submitted evidence
Production-release authority, if defined

These are recommended control fields for this artifact. They are not presented as a universal list required by ISO or CPSC.

Practical artifact: closeout table

Complete one row for every decision, action, or unresolved issue. Do not combine unrelated actions merely because they share an owner.

ID	Decision, action, or open issue	Accountable owner	Due date or milestone	Evidence requested	Identification or format expectations	Reviewer and acceptance condition	Handoff effect	Status
01							Blocked / Conditional / Not blocked	Open / Submitted / Accepted / Rejected
02							Blocked / Conditional / Not blocked	Open / Submitted / Accepted / Rejected
03							Blocked / Conditional / Not blocked	Open / Submitted / Accepted / Rejected
04							Blocked / Conditional / Not blocked	Open / Submitted / Accepted / Rejected
05							Blocked / Conditional / Not blocked	Open / Submitted / Accepted / Rejected

Evidence-request writing pattern

Use the same sentence structure for every request:

[Owner] will complete [action] by [date or milestone] and submit [identified evidence] through [agreed location or method]. [Reviewer] will accept it when [defined condition] is met. Until then, the handoff is [blocked, conditional, or not blocked].

This pattern links responsibility, timing, evidence, review, acceptance, and handoff status in one readback.

Final verbal checklist

• Every decision has been classified as accepted, rejected, conditional, or deferred.
• Every action has one accountable owner.
• Every action has a date or defined milestone.
• Every evidence request is linked to an action, decision, control, or requirement.
• Expected evidence is described precisely enough to review.
• Relevant identifiers, dates, and revisions are recorded where applicable.
• The submission location or method is confirmed.
• The reviewer and acceptance condition are recorded.
• Production blockers are visible.
• Open issues have owners and escalation paths.
• Participants have had an opportunity to correct the readback.
• The summary owner and distribution method are confirmed.

Follow-up and verification

Track submission and acceptance as separate events. Receipt means that an item was delivered; it does not establish that the evidence is correct, relevant, complete, or accepted.

Record rejected evidence with the reason for rejection and the correction required. Do not overwrite the status in a way that hides the earlier review result. Preserve superseded versions when necessary for traceability, subject to the organization’s documented-information controls. The ISO 9001:2015 documented-information guidance provides the relevant general framework without prescribing a single retention method for every organization.

Escalate overdue blockers instead of silently changing their due dates or handoff status. The summary can later support verification or audit activity by showing what was agreed, what evidence was requested, and how acceptance was determined. When reviewing whether agreed processes and controls were followed, apply an evidence-oriented and systematic approach consistent with the audit guidance described by ISO 19011. This use does not turn the meeting summary itself into an audit report.

Scope and limits

• This article addresses the communication and documentation closeout of a pre-production meeting.
• It does not determine which laws, CPSC rules, tests, certificates, labels, or records apply to a particular product.
• It does not establish product conformity, authorize production, or replace technical, legal, regulatory, or quality review.
• The ISO 9001:2015 documented-information guidance allows organizations to determine the documented information needed for their processes and quality management systems; it does not prescribe one universal meeting-closeout form.
• ISO 19011 provides guidance for auditing management systems. It does not make this summary an audit report or create certification status.
• CPSC applicability must be checked against the product, jurisdiction, and applicable requirements using resources such as the CPSC Business & Manufacturing guidance.
• The communication method should not rely on assumptions about nationality or culture. Apply the same explicit readback, ownership, and evidence-confirmation process to all participants.

Image credit

Selected image: “Elderly men playing mahjong and smoking in a social gathering”
Photographer: 志坚 平井
Source: Unsplash
License: Unsplash License

Editorial limitation: This image depicts a social gathering, not a pre-production meeting, factory, supplier assessment, audit, or compliance activity. Use it only as a general visual for interpersonal communication. Do not present it as evidence of a sourcing practice or production process.

Sources

• ISO 9001:2015 — Guidance on the requirements for documented information

  • Basis for distinguishing documented information used to support process operation from records retained as evidence of results.
  • Basis for avoiding an unnecessarily prescriptive or universal document set.

• ISO 19011 — Guidelines for auditing management systems

  • Basis for structured, evidence-oriented review and follow-up.
  • Used as audit guidance, not as a certification claim.

• U.S. Consumer Product Safety Commission — Business & Manufacturing

  • Starting point for identifying CPSC information relevant to manufacturers and businesses.
  • Product-specific applicability must be established separately.

Final next move

Copy the closeout table into the meeting record and complete one row for every decision, action, and unresolved issue. Read every row back to the named owners. Do not mark the pre-production handoff complete until every blocker has an accountable owner, a due date or milestone, a defined proof requirement, a reviewer, and an acceptance condition.