How to Turn a Factory Walkthrough into an Evidence Request List

Executive introduction

A factory walkthrough should produce more than photographs, general impressions, and verbal assurances. Its practical purpose during pre-sourcing research is to identify relevant manufacturing claims, observe how work is performed, and request records or demonstrations that can support—or fail to support—those claims.

The walkthrough should therefore be planned as a distinct verification task. Before the visit, define the products, processes, requirements, records, and factory claims to examine. During the visit, convert each relevant observation into a specific evidence request. Afterward, maintain a dated log showing what was observed, what was requested, how the evidence was checked, and which questions remain unresolved.

This approach draws on ISO 19011 auditing guidance for organizing objectives, scope, criteria, evidence collection, findings, and reporting. Product-safety-oriented requests can be framed using the U.S. Consumer Product Safety Commission’s manufacturing best practices. If a defined inspection lot will be assessed through attribute sampling, the activity requires established inputs and acceptance criteria rather than an informal choice of convenient samples; see ISO 2859-1.

Plan a Distinct Factory Checks Verification Task

Define the task before the walkthrough

Set the task parameters in writing:

• Decision stage: Pre-sourcing research.
• Task purpose: Verify whether observed factory practices and available records support the supplier’s relevant manufacturing and product-safety claims.
• Required output: A dated evidence request log showing what was observed, what evidence was requested, how it will be checked, and what remains unresolved.

Keep this task distinct from:

• Supplier discovery or commercial comparison.
• Product specification development.
• Contract negotiation.
• Formal certification.
• Finished-lot inspection or product acceptance.

Prepare these inputs before scheduling the route:

• Product description and intended use.
• Applicable product requirements and acceptance criteria.
• Factory claims requiring verification.
• Proposed production steps and inspection points.
• Known safety-critical materials, components, or processes.
• Names or roles of people responsible for answering evidence requests.
• Any access, confidentiality, photography, or copying restrictions.

Without defined requirements, the team may collect documents without knowing whether they are relevant. A certificate on a wall, a blank inspection form, or a tidy production area may provide context, but none independently demonstrates that a control is current, applicable, and consistently implemented.

Set verification criteria

Use ISO 19011 as guidance for organizing the verification activity:

• Define the objectives, scope, and criteria.
• Identify the functions, processes, locations, and records to examine.
• Gather verifiable evidence instead of relying on unsupported statements.
• Record findings and unresolved questions consistently.

Use the CPSC manufacturing best-practice guidance to frame requests concerning:

• Product-safety planning.
• Design and manufacturing controls.
• Supplier and material controls.
• Testing, traceability, and record retention.
• Responses to defects or other product-safety issues.

Use ISO 2859-1 only when a defined lot will be assessed by sampling for inspection by attributes. Identify the lot and inspection characteristic, establish the sampling-plan inputs and acceptance criteria in advance, and document any deviation. Do not select convenient samples informally during the walkthrough and describe the result as a defined acceptance-sampling decision.

Prepare a controlled walkthrough route

Arrange the route around the flow of information and material:

1. Document-control or production-planning area.
2. Incoming-material receipt and storage.
3. Material identification and release.
4. Production and assembly steps.
5. In-process inspection and testing.
6. Nonconforming-product controls.
7. Finished-product inspection and release.
8. Packing, labeling, storage, and traceability.
9. Record-retention and issue-response functions.

At every stop, use three prompts:

1. Show the process.
2. Show the instruction or criterion governing it.
3. Show a completed record demonstrating that it is used.

Use production-area observations as prompts for specific evidence requests, not as standalone proof of process control.

Convert Walkthrough Observations into Evidence Requests

Apply the observation-to-evidence method

For each relevant observation, record seven elements:

1. Claim: What the factory says it controls or performs.
2. Observation: What is visible or demonstrated, stated neutrally.
3. Risk or decision relevance: Why it matters to the sourcing decision.
4. Evidence request: The specific document, record, sample, or demonstration needed.
5. Verification method: Review, comparison, trace-back, trace-forward, demonstration, or defined sampling.
6. Result: Supported, partly supported, not supported, or not yet verified.
7. Follow-up: Missing item, clarification, corrective action, or decision escalation.

For example, if containers of an incoming component display lot identifiers, do not conclude that full traceability exists. Record the identifiers observed, request the governing traceability procedure and records for a defined receipt, and test whether that receipt can be connected to storage status and subsequent production use.

Write evidence requests that can be answered

An effective request names the control being examined and defines the relevant product, process, period, receipt, or lot. It should normally request both:

• The current governing document, such as an instruction, specification, or procedure.
• A completed record showing that the document was implemented.

Ask for identifiers, dates, approval status, revision status, and applicable product or lot references where relevant. State whether a redacted copy, on-screen review, photograph, or recorded document reference is acceptable. Assign a response owner and follow-up date.

Avoid vague wording such as:

• “Send quality documents.”
• “Prove the factory is good.”
• “Show some inspection reports.”

Prefer a testable request:

Provide the current incoming-inspection instruction for the relevant component and completed inspection records for a defined recent receipt selected for review. The records should show the receipt identifier, inspection date, result, status, and approval or review evidence where applicable.

The request is bounded, connects a governing document to implementation, and identifies what will be checked.

Triangulate rather than relying on one form of evidence

A single record rarely answers every relevant question. Triangulate by comparing different evidence forms:

• Compare the operator’s explanation with the current work instruction.
• Compare the instruction with a completed record.
• Compare material identification with receiving and production records.
• Trace a selected finished unit or lot backward through production and incoming materials where records permit.
• Trace a selected incoming material forward to production use where records permit.
• Check whether records include actual conforming and nonconforming outcomes, rather than only blank templates.
• Treat photographs and visual orderliness as context, not proof that a control operates consistently.

Where sources conflict, record the conflict precisely. For example, note that the instruction available at a workstation carries a different revision from the version identified as current. Do not infer the cause without evidence.

Create the evidence request log

Prefill one row for every relevant checkpoint before the visit.

ID	Process or claim	Neutral observation	Evidence requested	Verification method	Status	Owner	Due date	Follow-up
FC-01			Current governing document and selected completed record		Pending
FC-02					Pending
FC-03					Pending

Use stable request identifiers so that later files, notes, photographs, screen reviews, and factory responses can be connected to the correct log entry.

Practical Verification Checklist

Use this checklist during and after the walkthrough

Checkpoint	What to observe	Evidence to request	Verification action	Record in the evidence log
Task scope	Products, processes, areas, and records included in the visit	Agreed scope and relevant process map or production flow	Confirm that the route covers the processes relevant to the sourcing decision	Exclusions, access limits, and unanswered areas
Product requirements	Specifications or criteria available at points of use	Current specification, drawings, approved criteria, or controlled instructions	Compare versions in use with the identified current version	Version, status, discrepancy, and affected process
Document control	Instructions identifiable by revision or status and available to personnel	Document-control procedure and selected revision history	Check whether current instructions are accessible where work occurs	Obsolete, missing, unofficial, or uncontrolled material
Incoming materials	Identification, segregation, inspection status, and storage conditions	Receiving records, incoming-inspection criteria, completed inspection records, and status records	Select a defined receipt and compare its identity, status, and inspection record	Component, receipt reference, and evidence result
Supplier or component controls	How externally supplied items are specified and reviewed	Purchase requirements, supplier-control criteria, and selected review records	Compare purchased requirements with incoming checks and production needs	Unsupported claim or requirement gap
Material traceability	Lot, batch, date, or other identifiers maintained through storage and production	Traceability procedure and records connecting selected materials to production	Perform a backward or forward trace using a defined item	Trace start, trace end, breaks, and unresolved links
Production instructions	Operators using current instructions and acceptance criteria	Work instruction, process specification, setup sheet, or approved reference	Compare observed activity with the documented sequence and criteria	Conformity, variation, or undocumented practice
Process controls	Important settings or checks recorded where required	Process-control plan and selected completed records	Compare recorded values or statuses with stated limits	Missing entries, changes, and review status
In-process inspection	Inspection points, status markings, hold points, and reactions to failure	Inspection instruction, acceptance criteria, and completed records	Match a selected record to the product or lot observed	Inspection identity, result, disposition, and traceability
Test and measurement equipment	Equipment identity, status, suitability, and operator use	Equipment list, relevant status or verification records, and use instructions	Match floor equipment identifiers to supporting records	Unknown or expired status and identifier mismatches
Nonconforming material or product	Identification, segregation, access control, and disposition	Nonconformance procedure and selected completed records	Trace one recorded nonconformance from detection to disposition	Authority, status, rework, and unresolved disposition
Corrective action	How repeated or significant problems are investigated and addressed	Corrective-action procedure and selected open or closed records	Connect the issue, action, responsibility, and effectiveness review	Open actions, missing evidence, and recurrence concerns
Finished-product release	Separation of completed, inspected, held, and released goods	Release criteria, final inspection or test records, and release authorization	Match a selected lot’s status to its release evidence	Lot identity, release status, approver role, and exceptions
Product-safety controls	Safety-related requirements incorporated into manufacturing and review	Product-safety procedures, risk-related controls, test criteria, and records	Connect identified safety requirements to production and release controls	Requirements not linked to a control or record
Packaging and labeling	Correct materials, warnings, identifiers, labels, and packing instructions	Current packaging and labeling specifications plus completed checks	Compare an observed pack with controlled requirements and check records	Wrong revision, missing check, or traceability gap
Record retention	Records retrievable for the relevant product, process, and period	Retention procedure and selected retrievable records	Request a defined record and check whether it can be located and linked	Retrieval result, format, limitation, or missing link
Issue response	Handling of defects, complaints, and safety concerns	Escalation, investigation, and response procedures with selected records where appropriate	Check whether responsibilities, records, and follow-up steps are defined	Missing escalation route or incomplete closure evidence
Lot sampling	Clearly identified inspection lot and defined inspection characteristics	Sampling plan, lot definition, acceptance criteria, sample records, and results	Confirm that plan inputs are established before samples are drawn	Lot identity, plan inputs, result, and deviations
Walkthrough closeout	Open requests and conflicting evidence reviewed with the factory	Completed evidence request log and list of unavailable items	Confirm wording, ownership, permitted format, and due date	Supported, partly supported, not supported, or pending

The product-safety, testing, traceability, record-retention, and issue-response checkpoints should be adapted to the applicable product and risk context. The CPSC manufacturing best practices provide guidance for framing these manufacturing and product-safety requests, but product-specific legal requirements must be identified separately.

Apply a consistent finding scale

Use one finding scale throughout the log:

• Supported: Relevant observations and records align with the defined criterion.
• Partly supported: Evidence exists, but its coverage, traceability, currency, or implementation is incomplete.
• Not supported: Requested evidence is absent or conflicts materially with the observed practice.
• Not yet verified: Access, timing, confidentiality, or missing information prevents a conclusion.

Do not convert “not yet verified” into approval or an allegation. Preserve the distinction between a missing record, a control that was not observed, and a confirmed failure against a defined requirement.

Produce the sourcing decision input

Summarize:

• Controls supported by evidence.
• Open evidence requests.
• Material inconsistencies.
• Sampling decisions still requiring defined inputs.
• Scope exclusions and access limitations.
• Records that could not be copied but were reviewed on screen or referenced.
• Issues requiring escalation against pre-established sourcing criteria.

Use the summary to support one of four pre-sourcing actions:

1. Continue research.
2. Request specified additional evidence.
3. Require resolution of defined gaps before further evaluation.
4. Remove the factory from consideration when sourcing criteria are not met.

A walkthrough should not be presented as a guarantee of future production, legal compliance, or product conformity.

Scope and limits

• This method supports a pre-sourcing Factory checks verification task. It is not a complete management-system audit, certification assessment, regulatory determination, or finished-product inspection.
• ISO 19011 provides auditing guidance; using it does not establish that a factory is certified or compliant.
• ISO 2859-1 provides acceptance-sampling procedures for inspection by attributes. Application requires defined lot, inspection, and sampling-plan inputs; this article does not prescribe sample sizes or invent those inputs.
• CPSC manufacturing best practices are used here to guide product-safety-oriented evidence requests. Applicable legal and product-specific requirements must be established separately.
• Walkthrough evidence is limited by visit timing, areas accessed, records made available, and products or lots selected.
• A visually orderly area, document template, or single conforming sample does not demonstrate consistent control by itself.
• Record factual observations and evidence gaps without unsupported allegations.
• Protect confidential information and obtain permission before photographing, copying, or retaining factory records.

Image credit

Selected image: “a bunch of wires that are on a rack”

Editorial context: General factory imagery only. The image does not depict a verified supplier, audit finding, or identified manufacturing practice.

Photo by Homa Appliances on Unsplash, used under the Unsplash License.

Sources

• ISO 2859-1 — Sampling procedures for inspection by attributes
  Use when planning defined lot-sampling activities and documenting sampling-plan inputs.

• ISO 19011 — Guidelines for auditing management systems
  Use to organize verification objectives, scope, criteria, evidence collection, findings, and reporting.

• U.S. Consumer Product Safety Commission — Manufacturing Best Practices
  Use to frame product-safety, manufacturing-control, testing, traceability, record-retention, and issue-response evidence requests.

Final next move

Create the evidence request log before scheduling the walkthrough. Prefill one row for every relevant checkpoint, then leave the factory with each open request assigned a status, responsible role, acceptable evidence format, and follow-up date.