Published: · Updated:
This guide covers what every factory inspection report needs, why each section matters, and the gaps that create disputes after shipment.
What an inspection report is actually for
An inspection report documents what was checked, what was found, and what the result means. It is the official record that tells the buyer whether the goods match what was ordered and whether the lot meets the agreed quality threshold.
A complete report protects both sides. The factory has documented proof of what was verified. The buyer has evidence to act on. When a dispute arises (and in manufacturing, disputes do arise) the report is the first document both sides reach for.
Order and product information
The report must open with the reference data that ties it to a specific shipment:
- Order number or purchase order reference
- Product name and style or SKU
- Customer name
- Inspection date and time
- Factory name and location
- Inspector name
Without this header block, the report is a free-floating document. It cannot be linked to a specific order in a dispute, referenced in a supplier review, or filed against the correct production record.
Sample size and inspection level
State the lot size, agreed general or special inspection level, inspection mode, standard and actual sample size. Record Ac and Re so the reader can check the plan and decision.
Record the AQL values and any separate zero-acceptance rule. State whether the plan counts nonconforming units or nonconformities. A sampling pass does not replace other required tests or shipment authorization.
Defect log with photos
This is the core of the report. Every defect found during the inspection gets its own entry:
- Defect description: what was wrong and where on the product
- Severity classification: critical, major, or minor
- Quantity affected: how many units showed this defect in the sample
- Photos: at least one clear image per defect type
Use photos to show visible defects and their location. For a dimensional or functional failure, record the measured or tested result, method and failed requirement. Photos support the evidence but do not guarantee agreement or replace a test result.
Group defects by severity to make the summary table straightforward to read.
Measurement results
If the product has dimensional specifications (garment measurements, carton dimensions, weight, or product tolerances) record the actual measurements against the spec sheet values.
Include the number of units measured, the measurements taken, and whether each measurement passed or failed. Measurement failures are documented separately from visual defects and often carry their own pass/fail threshold.
The pass/fail decision
State the overall result clearly (Pass, Hold, or Fail) with the defect summary that leads to it:
- Critical findings compared with the agreed critical-defect rule
- Major counts compared with Ac and Re using the agreed counting basis
- Minor counts compared with Ac and Re using the agreed counting basis
Put the decision at the top of the report and repeat it at the bottom. A reader who needs to act quickly should not have to scan through the defect log to find the result.
If the decision is Hold, specify exactly what re-inspection or sorting action is required and by when.
Record the inspection result separately from the shipment approval. Identify missing checks, the person authorized to release the lot, and any conditions. Keep the original report when a later reinspection is completed.
Inspector sign-off and timestamp
The report must be signed and timestamped by the inspector. The timestamp confirms when the inspection was completed, not when the report was compiled or sent.
If the inspection requires factory sign-off (common for in-house QC teams), record the factory representative's name and signature as well. Both signatures confirm the findings were reviewed and acknowledged on site.
What makes a report defensible in a dispute
Reports that hold up in post-shipment disputes share the same characteristics:
- Tied to a specific order: order number on every page
- Timestamped and signed on the day of inspection, not a day later
- Photos for visible defects and measured or tested results for failures that a photo cannot demonstrate
- AQL parameters recorded, so the decision basis is auditable
- Pass/fail stated clearly, not implied or qualified with 'mostly acceptable'
A report written in this format is self-contained. Either side can read it cold and understand exactly what happened and what was decided. That is what turns a document into proof.
Key takeaways
- Every report must be tied to a specific order number, product, and inspection date.
- Document the sample size and the AQL levels used: the decision is only valid against those parameters.
- Record the failed requirement with suitable photos, measurements or test results.
- State the pass/fail decision clearly at the top and again at the bottom of the report.
- Keep the inspector sign-off, completion time and approval record with the report.
Sources and related guides
Put this into practice with KaizenQ
KaizenQ gives your team a structured digital inspection workflow: defects logged with photos on the floor, a live report ready to share as soon as inspection is complete. No manual compilation. No end-of-day rework.