Ask for records that match the product and order.

Build a project claims ledger

Before publishing or relying on a claim, record the exact wording, evidence source, holder, applicable product or facility, time period, owner and next review date. A certificate held by one facility should not be presented as if it automatically applies to every supplier, product or order.

Evidence should answer: what does this prove, for which product or facility, and for what period?

Development evidence

Useful records can include the buyer brief, tech pack revision, bill of materials, measurement specification, sample comments, fit photos, approved color reference and sample approval. The aim is traceability between the decision and the approved version.

Material and testing evidence

Record supplier-submitted material information and requested test reports with the material reference, color, applicable standard, laboratory, date and scope. Check whether the report covers the actual material and whether the target market requires additional testing.

Do not add price, performance, sustainability or compliance claims to structured data unless the supporting evidence is approved for public use.

Production and inspection evidence

Production evidence may include approved pre-production records, inline check notes, quantity and color breakdowns, packaging instructions and final inspection results. Inspection scope, sampling method and acceptance criteria should be aligned before the inspection occurs.

Evidence request map

Buyer questions

Does a factory certificate prove every product is compliant?

No. Check the certificate holder, facility, scope, validity period and whether product-specific testing is also required.

When should inspection scope be agreed?

Before production or inspection begins, so the method, sample size, checkpoints and acceptance criteria are understood.