Factory audit vs inspection compares two distinct source records. An audit report may state facility, process, infrastructure/equipment, systems/procedures, training/record fields, documentation, and audit scope/date. A product inspection report may state product/order/lot, requirements, observations, measurements, stated test/equipment field, packaging/labels, defects, attachments, outcome, and report scope/date. Neither record establishes the other’s facts or recommends a universal sequence.
The title asks which one comes first, but a source record cannot answer that for every project. It can show what a named audit or inspection report states, what it does not state, and where an open question remains. The records should stay separate from later commercial decisions.
Key takeaways
- An audit report and a product inspection report address different stated subjects and scopes.
- Read the audit source/date and its stated facility/process/system fields before drawing any conclusion from it.
- Read the inspection report source/date, product/order/lot reference, requirements, observations, attachments, outcome, and scope before drawing any conclusion from it.
- Do not use an audit record as proof of a particular product or order result.
- Do not use a product inspection report as proof of facility capability, management systems, legal status, or a future order result.
Contents
- Factory audit vs inspection at a glance
- What an audit report may state
- What a product inspection report may state
- Keep audit and inspection sources separate
- Use the scope comparison table
- Read report limits before comparing documents
- Why there is no universal answer to first
- Message template for source clarification
- Practical source-scope checklist
- FAQ
Factory audit vs inspection at a glance
Factory audit vs inspection compares two distinct source records. An audit report can identify stated information about a named facility or supplier context. A product inspection report can identify stated information about a named product/order/lot context. The source, date, product/facility reference, and stated scope decide how each record should be read.
Public guides distinguish audit records concerning stated supplier or facility information, production/process systems, documentation, and related records from product inspection reports concerning stated product specifications, components, assembly, appearance, labels, packaging, measurements, defect records, and attachments. [1] [2] [3]
These categories do not turn either document into a universal answer. A report field only says what its source states within the document’s scope. It does not prove a fact that the source does not cover.
What an audit report may state
An audit report may state its source/date, facility reference, audit scope, and audit fields concerning general facility information, infrastructure/equipment, process records, stated systems/procedures, material/document-control records, training/record fields, or management documentation. The HQTS audit comparison guide and HQTS factory-audit guide describe these broad categories.
Keep the report’s exact title, source/date, facility reference, stated scope, and wording with the audit record. A stated facility/process/system field is not proof that every product met a requirement. A listed document or procedure is not proof that it applied to a particular order, product version, report date, or later production.
A factory-audit checklist record can help organise source fields. A factory versus trading-company guide can help keep business-identity sources separate from manufacturing or product records. Neither source selects a supplier or establishes a future order result.
What a product inspection report may state
A product inspection report may state source/date, product version if stated, order/lot reference, stated scope, requirement source, observations, measurements, stated test/equipment fields, packaging/label records, defect records, photo or attachment references, and a stated outcome field. The QualityInspection.org report guide discusses report categories including product specifications, components, assembly, appearance, labels, packaging, stated tests/measurements, presented quantity, defects, and photo appendices.
A product report field needs its own product/order/lot reference and stated scope. An observation does not become an underlying requirement source. A measurement record does not establish a method that the source does not identify. A stated outcome does not become a commercial decision or a conclusion about every unit, later product, supplier system, or delivery.
The product inspection report guide describes how to keep product scope, requirement source, observed information, attachments, report outcome, and unknowns separate. The quality inspection checklist guide helps retain the underlying product/source records without treating them as guarantees.
Keep audit and inspection sources separate
Audit source/date, facility/process/system record, product/order/lot reference, requirement source, observed information, report outcome, report scope, and unknowns must remain distinct records. An audit scope is not a product/order/lot scope. A product observation is not an audit field. A report outcome is not a facility capability record. An unknown is not a quality result.
If an audit report refers to a product, retain the audit source/date and stated scope. If an inspection report refers to a facility, retain the inspection source/date and stated scope. Do not merge the two documents into one conclusion about a supplier, every unit, compliance, a shipment, or delivery.
Use the scope comparison table
This table helps compare the stated scope of two documents. It does not select an order, timing, provider, inspector, standard, requirement, test, threshold, action, or commercial decision.
| Source record | May state within its source/scope | Does not establish | Source/date/scope question |
|---|---|---|---|
| Audit report identity | Audit title/reference, source/date, facility reference, and stated audit scope | That every facility fact applies outside the named scope | Which facility, source date, and audit scope does the report name? |
| Facility/infrastructure record | Stated facility, infrastructure, equipment, or layout information | Product quality or a particular order outcome | What does the audit source actually state? |
| Process/system record | Stated procedure, process, management, documentation, training, or record field | That a particular product/order/lot followed the stated field | Which product/order/lot, if any, does the audit source identify? |
| Product inspection report identity | Report title/reference, source/date, product/order/lot reference, and scope | That every product or later order is covered | Which product/order/lot and report scope are stated? |
| Requirement source | Specification, sample, checklist, or named document reference | That an observation matched a requirement unless the relevant source says so | Which document version defines the named item? |
| Product observation or measurement | Reported observation/measurement wording within report scope | Facility capability, management system, legal status, or future order outcome | What source/date and product scope apply to the record? |
| Packaging, label, or defect record | Stated report field and attachment reference if supplied | A product-wide or future shipment conclusion | What does the report not state or cover? |
| Report attachment or outcome | Attachment/outcome wording as stated in report source | Commercial decision, audit result, or facility conclusion | What report source and scope limit the field? |
| Unknown or missing field | Open question and requested audit/inspection source | A quality, capability, or commercial conclusion | Which source record is still needed? |
Read report limits before comparing documents
An audit record does not prove product quality or a particular order outcome, and an inspection report does not prove facility capability, management system, legal status, or a future order outcome. Each source can be useful within its stated scope. Neither one fills the other’s missing fields.
A factory audit report and a product inspection report are not quality guarantees and do not prove or guarantee product quality, compliance, supplier capability, schedule, shipment, or delivery. The record may identify a source statement. It cannot guarantee what a source does not cover.
Why there is no universal answer to first
A project can list its own source questions: facility reference, product version, order/lot scope, requirement sources, observations, reports, attachments, and unknowns. The documents that exist, their stated dates/scopes, and the fields that remain unknown are part of the project record.
This article does not select which comes first, timing, provider, inspector, standard, requirement, tolerance, test, equipment, sample size, AQL, defect classification, pass/fail threshold, compliance action, corrective action, production action, payment action, shipment action, supplier decision, or contract approach. It provides a way to separate the documents before the reader makes any decision.
The supplier quality control plan guide can help organise plan sources separately from audit and product inspection report sources.
Message template for source clarification
Use a request that asks for the named audit and inspection records.
Hello [supplier contact],
We are organising the current facility audit and product inspection source records for [facility reference, product version, and order or lot reference]. Please identify the audit report source/date, facility reference, stated audit scope, facility/process/system record fields, and any related documents.
Please also identify the product inspection report source/date, product/order/lot reference, stated scope, requirement sources, observations, measurements, packaging/label records, attachment references, and stated outcome field.
If a field is not stated or cannot be linked to a written source, please say so in writing.
Thank you.
This request asks for documentation. It does not select which comes first, timing, provider, inspector, standard, requirement, tolerance, test, equipment, sample size, AQL, defect classification, pass/fail threshold, compliance action, corrective action, production action, payment action, shipment action, supplier decision, or contract approach.
Practical source-scope checklist
- Have you retained the source/date, facility reference, and stated scope of the audit record?
- Have you retained the source/date, product/order/lot reference, and stated scope of the inspection report?
- Are audit source/date, facility/process/system record, product/order/lot reference, requirement source, observed information, report outcome, report scope, and unknowns kept as separate fields?
- Have you separated a stated facility/process/system field from a conclusion about a particular product/order/lot?
- Have you separated a stated product observation/outcome from a conclusion about facility capability, management systems, legal status, or later orders?
- An audit record does not prove product quality or a particular order outcome, and an inspection report does not prove facility capability, management system, legal status, or a future order outcome.
- This article does not select which comes first, timing, provider, inspector, standard, requirement, tolerance, test, equipment, sample size, AQL, defect classification, pass/fail threshold, compliance action, corrective action, production action, payment action, shipment action, supplier decision, or contract approach and an audit report and inspection report are not quality guarantees and do not prove or guarantee product quality, compliance, supplier capability, schedule, shipment, or delivery.
FAQ
What is the difference between a factory audit and product inspection?
A factory audit and product inspection are different source records. An audit report may state facility/process/system information within its audit scope/date. A product inspection report may state product/order/lot requirements, observations, measurements, packaging/label fields, defects, attachments, outcome, and report scope/date. Neither source establishes the other’s facts.
Does a factory audit prove product quality?
No. An audit record does not prove product quality or a particular order outcome. A factory audit report is not a quality guarantee and does not prove or guarantee product quality, compliance, supplier capability, schedule, shipment, or delivery.
Does a product inspection report prove factory capability?
No. An inspection report does not prove facility capability, management system, legal status, or a future order outcome. A product inspection report is not a quality guarantee and does not prove or guarantee product quality, compliance, supplier capability, schedule, shipment, or delivery.
References
- HQTS, “Audits or Quality Inspections in China”
- HQTS, “China Factory Audit”
- QualityInspection.org, “How to prepare your QC inspection report template”
Next step
If you need help organising factory-audit and product-inspection source records, share the audit report, inspection report, named facility/product/order/lot references, requirement sources, stated scopes, and attachments with Yes Supplier. The review can help structure clarification questions. An audit report and inspection report are not quality guarantees and do not prove or guarantee product quality, compliance, supplier capability, schedule, shipment, or delivery.