Factory quality information can arrive as audit reports, inspection releases, batch data, photographs and shipment records. A project team needs to know what each file describes before relying on it in a handover pack. The first indexing question is therefore scope: which product, production period, unit, lot or shipment does this record actually cover?

Capture provenance at receipt

Record the issuing organisation, received date, document title, identifier, revision and source communication. If the file was provided through a portal, retain an appropriate reference to that submission. Keep the received original unchanged, including annexes that define the sample, production line or limitations.

Do not infer coverage from a filename alone. An inspection summary may relate to a sample rather than every unit, while an audit report may describe a management or production process rather than acceptance of a particular shipment. Put questions about the meaning or sufficiency of the evidence to the project's technical reviewer.

Build a coverage map

Useful cross-reference fields include product model, factory, production line where stated, lot or batch, serial range, pallet, container, shipment and project equipment reference. Populate only the fields supported by the supplied records. An empty or uncertain field is more useful than a confident-looking connection inferred from sequence or proximity.

Keep audit findings and their responses distinguishable from product inspection results. If a report is revised, connect the issues and retain the reason for revision where supplied. Use a separate action list for unresolved traceability questions and requests for missing annexes.

Hypothetical example

A module inspection report names production Lot F08, while shipping records use Shipment S04. The coordinator asks the supplier for the mapping between those references and records the source of the answer. Until that relationship is supplied and reviewed, the index should not state that the inspection report covers the full shipment.

Prepare a reviewable package

Group files by the reviewer's intended question: production process, product inspection, corrective action or shipment traceability. Provide a contents index and a short coverage note based on the issuer's stated scope. Make clear which relationships are confirmed and which remain queries.

A well-organised factory record library improves navigation; it does not validate the testing method, sampling plan, defect classification or product acceptance. Avoid adding assurances, conclusions or signatures that the original issuer did not provide. The technical reviewer must decide whether the evidence meets the project's requirements.