How to Prepare a First Factory Contact That Requests Decision-Relevant Evidence

Reader task: Plan a distinct pre-sourcing verification task for a prospective factory.
Practical artifact: A verification checklist for preparing, sending, and assessing the first contact.
Decision to support: Whether the factory has provided enough relevant, reviewable evidence to justify a next-stage sourcing review—not whether it is finally approved.

Executive introduction

A first factory contact should do more than ask whether a supplier “has quality control.” It should request a small, prioritized body of evidence that can be connected to the proposed product, relevant processes, and intended manufacturing site. The purpose is to make one bounded pre-sourcing decision: whether there is a reasonable basis for a more detailed review.

This contact is not an audit, a certification check, a product-compliance determination, or final supplier approval. It should instead distinguish assertions from documented controls and completed records. ISO’s guidance explains that documented information can support process operation or provide evidence of results, and that it may exist in different media. The request should therefore focus on information needed for the decision rather than demand an arbitrary collection of “quality documents.” See ISO’s guidance on documented information for ISO 9001:2015.

A useful response will identify who performs the work, where it is performed, which controls apply, and whether completed records show those controls being used. Product-safety questions should remain explicitly unresolved until the sourcing team has assessed the actual product against applicable information, beginning where relevant with the CPSC Business and Manufacturing resources.

Define the verification task before contacting the factory

Set one bounded decision

Frame the task as:

Verify whether this factory can provide reviewable evidence relevant to making the intended product and controlling the associated processes.

Keep the task separate from:

• Requesting prices or negotiating commercial terms.
• Approving samples.
• Conducting an audit.
• Confirming regulatory compliance.
• Verifying a certification.
• Granting final supplier approval.

Define the permitted outcomes before sending the message:

• Advance: Evidence is sufficiently relevant and reviewable to plan a follow-up.
• Clarify: Potentially useful evidence exists, but its scope, ownership, currency, status, or product connection is unclear.
• Hold: Important evidence is unavailable or cannot yet be reviewed.
• Stop: The response does not support the minimum pre-sourcing decision.

These outcomes prevent the sourcing team from treating a responsive email, polished presentation, certificate reference, or isolated record as final approval.

Describe the proposed product and process scope

Give the recipient enough information to identify relevant records:

• Product category and intended use.
• Known materials or components.
• Processes expected to be performed.
• Destination market, if established.
• Product-specific safety questions requiring later investigation.
• Whether the contact is a manufacturer, intermediary, or organization using external providers.
• Manufacturing site or sites the evidence should cover.

Do not ask for an unrestricted collection of quality documentation. ISO’s guidance emphasizes that documented information should support the operation of processes and provide confidence that processes are carried out as planned; the objective is not documentation for its own sake (ISO documented-information guidance).

Convert unknowns into decision questions

Build the evidence request around defined questions:

1. Does the evidence cover the organization and manufacturing site under consideration?
2. Does it apply to the proposed product or a relevant process?
3. Can the factory show how it reviews requirements before accepting work?
4. Can it show how relevant competence, production controls, traceability, release, and nonconforming outputs are addressed?
5. Which CPSC manufacturing information does it consider relevant to the proposed product, and why?
6. Are submitted items procedures describing intended controls, completed records showing implementation, blank forms, or unsupported statements?
7. Is each item identifiable by title, date or revision, owner, status, and scope?

Define an evidence-handling rule

Accept documented information in the medium used by the factory rather than requiring one arbitrary format. ISO’s guidance recognizes that documented information can be in different forms and media (ISO documented-information guidance).

Permit confidential customer, employee, and commercial information to be redacted. Ask that redaction not obscure:

• Document or record type.
• Relevant product or process scope.
• Site identity where needed.
• Date, revision, or record date.
• Evidence that the recorded activity occurred.
• Review, approval, authorization, or disposition fields where applicable.

Record not applicable separately from not provided. Do not treat a title, logo, certificate reference, policy statement, or file name as proof that a control is implemented for the proposed product.

Structure the first contact around evidence

Opening: state purpose and boundaries

The opening should:

• Identify the buyer and proposed product category.
• Describe the activity as a pre-sourcing evidence review.
• Explain that the response will inform whether a more detailed review is justified.
• State that the request is not an audit, order commitment, or final compliance determination.
• Include a deadline only when the sourcing team has established one.

A suitable opening is:

We are conducting a pre-sourcing evidence review for a proposed product in the category described below. The purpose is to determine whether relevant, reviewable evidence is available to support a more detailed sourcing review. This request is not an audit, order commitment, or final product-compliance determination.

Context block: give the factory a defined scope

Provide:

• Proposed product and intended use.
• Known materials, components, and processes.
• Intended destination market, if known.
• Expected manufacturing site, if known.
• Specific uncertainties the response should resolve.

Ask the recipient to correct inaccurate assumptions before supplying evidence. If the recipient is an intermediary, ask it to distinguish its own information from information owned by or applicable to the manufacturing site.

Evidence request: ask for a small, prioritized set

Priority 1: identity and scope

Request:

• Legal or operating name used by the manufacturing organization.
• Address of the site expected to perform the work.
• Contact person’s production or quality function.
• Processes performed at that site.
• Processes expected to be handled by external providers.
• A statement identifying which submitted documents and records apply to that site.

Priority 2: controlled documented information

Ask for relevant extracts or examples showing how the factory addresses:

• Review of product or customer requirements.
• Personnel competence for relevant work.
• Control of externally provided processes, products, or services where applicable.
• Production or service provision.
• Identification and traceability where applicable.
• Product inspection, verification, and release.
• Control and disposition of nonconforming outputs.
• Corrective action or improvement where applicable.

ISO’s guidance distinguishes documented information maintained to support process operation from documented information retained as evidence that activities occurred. Ask for both an explanation of the intended control and a completed record demonstrating implementation where available (ISO documented-information guidance).

Priority 3: one completed example record

Request one redacted, completed example connected to the relevant product category or process, such as:

• Requirements-review record.
• External-provider evaluation record.
• Production or process record.
• Traceability record, if applicable.
• Inspection, verification, or release record.
• Nonconforming-output and disposition record.
• Corrective-action record.

One example does not establish continuing effectiveness. Its purpose is to determine whether the evidence is structured, attributable, connected to the proposed scope, and suitable for deeper review.

Priority 4: product-safety and CPSC relevance

Ask the factory to:

• Identify which CPSC manufacturing information it considers relevant to the proposed product.
• Explain the basis for that selection.
• Identify corresponding manufacturing controls or records it can provide.
• Mark questions as unresolved rather than make unsupported compliance claims.

The sourcing team must determine product-specific obligations separately. The CPSC Business and Manufacturing page is a starting point for products within the CPSC’s scope, but a general factory statement is not a substitute for identifying requirements applicable to the actual product.

Response format: make evidence comparable

Ask the factory to provide an evidence index containing:

• File or document title.
• Document type.
• Relevant site.
• Relevant product or process.
• Date, revision, or record date.
• Document owner or issuing function.
• Classification as a procedure, blank form, completed record, or other material.
• Confidentiality or redaction note.
• Brief explanation of how the item answers the request.

Close: explain what happens next

State that the response will be reviewed for:

• Relevance to the proposed product, process, and site.
• Identifiable document or record status.
• Connection between stated controls and completed evidence.
• Unresolved product-safety questions.
• Contradictions or missing information.
• Need for clarification or a more systematic follow-up.

Do not promise approval based only on the first response.

Practical verification checklist

A. Prepare the task

Check	Verification action	Evidence or output to retain	Status
☐	Write the single decision the contact must support.	Task statement with advance, clarify, hold, and stop outcomes.	Not started / Complete
☐	Define the proposed product, use, materials, processes, and destination market where known.	Scope note attached to the contact plan.	Not started / Complete
☐	Identify assumptions the factory must confirm or correct.	Assumptions list.	Not started / Complete
☐	Separate this verification from pricing, audit, sample approval, and final compliance decisions.	Written boundary statement.	Not started / Complete
☐	Identify the manufacturing site the evidence should cover.	Site question included in the message.	Not started / Complete
☐	Review the CPSC manufacturing source for potentially relevant questions.	Product-safety question list with unresolved items marked.	Not started / Complete

B. Build the evidence request

Check	Decision question	Requested evidence	Review cue
☐	Who will manufacture the product, and where?	Organization name, site address, contact function, and site-process description.	Do later items refer to the same organization and site?
☐	Which operations are performed internally?	Process list or description for the proposed work.	Is the product-process connection explicit?
☐	Which operations use external providers?	Description of external processes and relevant control information.	Are outsourced activities identified clearly?
☐	How are requirements reviewed?	Relevant procedure or extract and a redacted completed review record.	Does the record show what was reviewed and the resulting decision?
☐	How is competence addressed?	Relevant criteria or controlled information and a redacted example record.	Is it tied to a relevant role or process?
☐	How is production controlled?	Relevant production-control information and a completed example.	Is it connected to an identifiable process or product scope?
☐	How is identification or traceability handled where applicable?	Relevant method and redacted example.	Can the factory explain when and why it applies?
☐	How is release authorized?	Release criteria or procedure and a completed release example.	Is authorization or disposition visible?
☐	How are nonconforming outputs controlled?	Relevant control information and a completed disposition record.	Does it show identification and disposition, rather than only a blank form?
☐	How are problems followed up?	Corrective-action information and a completed example where available.	Does it distinguish the issue, action, and follow-up?
☐	What CPSC manufacturing information may be relevant?	Factory’s selection, reasoning, and linked controls or records.	Are unsupported assurances separated from reviewable evidence?

C. Check document usability

For each submitted item, verify:

• It has an identifiable title or description.
• It is labeled as a procedure, blank form, completed record, or other material.
• The relevant organization and site are clear.
• The relevant product, process, or function is clear.
• A date, revision, or record date is visible where appropriate.
• Ownership, issuance, review, approval, or authorization is identifiable where appropriate.
• Redaction does not remove fields needed for the decision.
• The factory explains why the item is relevant.
• Any translated summary can be connected to the underlying document.
• Missing information is recorded as unavailable, unclear, or not applicable.

D. Compare statements with records

• For each important statement, identify whether the factory supplied a narrative, maintained procedure, blank form, completed record, or combination.
• Check whether a completed record appears to implement the control described in the corresponding procedure.
• Note contradictions in organization name, site, product scope, process, revision, or date.
• Flag generic materials that do not explain their relevance to the proposed product.
• Do not conclude that a single sample proves consistent implementation.
• Record follow-up questions without rewriting or correcting the factory’s evidence.

E. Log the review outcome

Status	Use when	Next action
Advance	Evidence is relevant, identifiable, and sufficient to plan a deeper review.	Define the next verification activity.
Clarify	Evidence may be relevant, but its scope, ownership, status, or meaning is unclear.	Send focused questions tied to specific files or omissions.
Hold	Decision-critical evidence is unavailable or cannot be reviewed.	Pause progression and state what must be supplied or resolved.
Stop	The response does not support the minimum pre-sourcing decision.	Close the task and retain the evidence log and rationale.

F. Prepare follow-up systematically

Use ISO 19011 only as guidance when planning a more systematic management-system audit or audit program. Its scope includes guidance on audit-program management, conducting management-system audits, and evaluating auditor competence (ISO 19011).

Before escalating, define:

• Review or audit objectives.
• Scope and criteria.
• Evidence to be sampled.
• Responsibilities and required competence.
• Review method.
• Reporting and follow-up.
• Limitations caused by remote access, redaction, language, or unavailable records.

Do not describe the first email exchange as a completed audit.

Image credit

Title: A store filled with lots of different types of clothing
Use in this guide: Contextual illustration of finished goods. It is not evidence of a factory, manufacturing process, or supplier capability.
Credit: wang xuesong
Source: Unsplash
License: Unsplash License

Sources

• ISO — Guidance on the requirements for documented information of ISO 9001:2015:
  https://www.iso.org/files/live/sites/isoorg/files/standards/docs/en/iso_9001_2015_guidance_documented_information.pdf
  Used to distinguish maintained documented information from retained evidence, recognize different media, and focus requests on information relevant to process operation and results.

• ISO 19011 — Guidelines for auditing management systems:
  https://www.iso.org/standard/19011
  Used to frame a later, systematic audit activity rather than characterize the first contact as an audit.

• U.S. Consumer Product Safety Commission — Business and Manufacturing:
  https://www.cpsc.gov/Business–Manufacturing
  Used as a starting point for investigating product-safety and manufacturing questions for products within the CPSC’s scope.

Scope and limits

What this task can establish

• Whether the factory responds with evidence relevant to a defined product, process, and site.
• Whether submitted materials are identifiable and reviewable.
• Whether the response distinguishes procedures, blank forms, completed records, and assertions.
• Whether important gaps can be converted into focused follow-up questions.
• Whether there is a reasonable basis to invest in a deeper sourcing review.

What this task cannot establish

• That the factory consistently follows every documented process.
• That submitted documents are authentic solely because they appear complete.
• That one sample record represents all production.
• That a management system conforms to a standard.
• That a factory or product holds a certification.
• That the proposed product complies with all applicable laws or CPSC requirements.
• That the factory should receive final approval.
• That an email evidence request is equivalent to an audit under ISO 19011.

Final next move

Complete the checklist before sending the contact. When the response arrives, index every item against the original decision questions and assign advance, clarify, hold, or stop with a written reason.

If the outcome is advance, define one separate next-stage verification task, such as a focused records review or a planned management-system audit. Do not treat the first contact as final factory approval.