A quality dispute can generate hundreds of photos and still have almost no usable evidence.

The problem is usually not volume. It is linkage.

A photo of a cracked part matters more when you know its lot number, the contract specification, when the photo was taken, how the item was stored, who handled it and whether a retained sample still exists. A laboratory report matters more when the tested sample can be traced to the disputed shipment.

The evidence file should help a new reviewer answer four questions quickly:

  1. What did the seller promise?
  2. What was actually delivered?
  3. What happened to the goods after delivery?
  4. Which evidence supports the proposed cause and remedy?

The following 11 records are the backbone of that file.

1. The contract-and-specification hierarchy

Do not store only the “latest PDF.”

Preserve the chain:

  • signed agreement;
  • PO;
  • order acknowledgment;
  • drawing revisions;
  • technical specification;
  • quality appendix;
  • packaging standard;
  • approved deviations;
  • later change orders.

Create a small register:

Document Version/date Issued by Accepted how? Supersedes

Why it matters: many disputes are not about whether a measurement is right, but which requirement controlled.

2. Approved sample and reference-standard records

If the deal used a golden sample, swatch, master part or reference image, document:

  • sample ID;
  • approval date;
  • who approved it;
  • purpose of approval;
  • tolerances;
  • storage location;
  • photographs;
  • whether it was consumed or altered.

A “sample” can mean color reference, dimensional master or general appearance. Its role must be defined.

3. Production and lot traceability

Preserve records that connect disputed goods to:

  • production date/time;
  • line/machine;
  • raw-material lot;
  • operator;
  • tooling;
  • process parameters;
  • inspection batch;
  • rework history.

The goal is not to dump a factory database on counsel. It is to make it possible to ask whether the problem clusters around one production variable.

4. Pre-shipment quality records

Keep original inspection records, not just the final “PASS” certificate.

Useful material can include:

  • sampling plan;
  • measured values;
  • instrument IDs;
  • calibration status;
  • photos;
  • nonconformance notes;
  • disposition;
  • inspector identity;
  • inspection date.

A pass/fail label without underlying values may be hard to evaluate later.

5. Packing, loading and transit condition

For suspected handling or moisture damage, preserve:

  • packing list;
  • packaging photos;
  • pallet layout;
  • container stuffing photos;
  • container/seal number;
  • carrier receipt;
  • bill of lading or transport document;
  • shock/tilt/moisture indicators;
  • arrival and unloading photos.

Incoterms® 2020 may allocate defined delivery, cost and risk responsibilities if incorporated, but they do not decide every cause or quality remedy. The physical record still matters.

6. Receiving and first-inspection record

The first condition report after delivery can become one of the most valuable documents.

Record:

  • date/time;
  • location;
  • person receiving;
  • seal/carton condition;
  • visible damage;
  • count;
  • photos;
  • immediate quarantine;
  • first test result.

Avoid reconstructing this two weeks later from memory.

7. Complaint and notice timeline

Create a single chronology:

Date Event Who Source Confidence
3 Apr goods received buyer warehouse receiving log documented
5 Apr first abnormal unit seen QC operator QC note documented
6 Apr seller notified buyer QA email documented
9 Apr broader lot concern raised buyer manager meeting note direct recollection

If the CISG applies, timing and specificity of notice of nonconformity can matter. The exact legal effect is jurisdiction- and transaction-specific, so preserve facts without trying to rewrite the chronology to fit a legal theory.

8. Sample chain of custody

Every sample sent to a lab should have an identity.

Record:

  • sample code;
  • lot;
  • who selected it;
  • selection method;
  • photographs;
  • seal;
  • transfer date;
  • courier;
  • lab receipt;
  • storage conditions;
  • condition on arrival;
  • remaining retained samples.

If the sample cannot be traced to the disputed goods, the technical result may be much less persuasive.

9. Test protocol and raw data

Do not keep only the conclusion page.

Preserve:

  • test standard/version;
  • instrument;
  • calibration;
  • environmental conditions;
  • sample preparation;
  • raw readings;
  • uncertainty where relevant;
  • calculation;
  • photographs/video;
  • analyst notes;
  • final report.

This helps separate “the product failed” from “the test setup differed.”

10. Downstream impact and mitigation record

Quality disputes often expand because damages are described in one large number.

Separate:

  • sorting cost;
  • rework;
  • replacement;
  • expedited freight;
  • line downtime;
  • customer credits;
  • scrap;
  • third-party claims;
  • internal labor;
  • projected future losses.

For each item, show:

amount / date / supporting document / causation note / mitigation step.

A forecast belongs in a different column from a paid invoice.

11. Disposition and communication log

Track what happened to every affected group of goods:

  • used;
  • quarantined;
  • reworked;
  • scrapped;
  • returned;
  • resold;
  • destroyed;
  • still held.

Also log material communications:

  • inspection invitations;
  • seller response;
  • proposed cure;
  • testing agreement;
  • credit proposal;
  • rights-reservation notice.

This prevents a later argument where neither side can explain what happened to the goods that supposedly formed the claim.

The three-way classification that saves time

Once the records are assembled, classify each observed problem into one of three working buckets.

A. Product nonconformity

The goods themselves appear not to meet the relevant contractual requirement.

Examples:

  • dimension outside tolerance;
  • wrong material grade;
  • performance below agreed threshold.

B. Specification drift

The parties are using different requirement versions or expectations.

Examples:

  • buyer tests to Rev D while seller manufactured to Rev C;
  • a sample change was approved verbally but not reflected in PO;
  • a customer expectation was never incorporated into the supplier contract.

C. Handling or post-delivery damage

The item may have left production conforming but changed later.

Examples:

  • forklift impact;
  • moisture;
  • improper storage;
  • installation damage;
  • contamination.

These are investigative buckets, not legal conclusions.

A real case can involve more than one.

What not to do with evidence

Do not:

  • overwrite original photos with annotations;
  • rename files so aggressively that original identifiers disappear;
  • throw away packaging before cause is understood;
  • destroy every sample in the first lab test;
  • send counsel only a slideshow;
  • delete inconvenient QC data;
  • backfill dates from memory without marking them estimated;
  • edit a supplier email before saving it.

Create working copies, but preserve originals.

Preserve provenance for digital records too

For important spreadsheets, machine logs, photographs and exported quality data, keep the original export and record when it was created. Where the dispute is substantial, a cryptographic hash can help show that a preserved file has not changed after collection.

A hash does not prove the underlying information is true. It simply helps demonstrate file integrity. Pair it with ordinary provenance: who exported the record, from which system, for which date range and where the authoritative source remains.

Avoid turning a convenience copy into the only copy.

A simple file structure

Use:

00_CASE_MAP
01_CONTRACT_SPEC
02_SAMPLES_REFERENCE
03_PRODUCTION_TRACE
04_PRE_SHIPMENT_QC
05_PACKING_TRANSIT
06_RECEIVING
07_NOTICE_TIMELINE
08_SAMPLE_CUSTODY
09_LAB_TESTING
10_COSTS_MITIGATION
11_DISPOSITION_COMMUNICATION

At the top level, maintain a document register with file ID, date, owner, original location and hash for important digital records where appropriate.

Why regulatory files belong in a separate subfolder

If the dispute includes claims about certification, market access or mandatory standards, preserve:

  • regulation/standard citation;
  • applicable version/date;
  • certificate;
  • test report;
  • declaration;
  • importer information;
  • destination market.

WTO Technical Barriers to Trade materials are useful background for understanding technical regulations, standards and conformity assessment in trade. They are not a substitute for identifying the actual local regulation governing the product.

Legal boundaries to preserve

The CISG may be relevant to conformity and notice in qualifying international sales, but its application must be established. The UK Sale of Goods Act 1979 offers a national example of sales-by-description, quality/fitness and sample concepts; it is not a global sales code. Incoterms® can address defined delivery and risk functions when incorporated but do not answer every defect question.

That is why the evidence file should remain factual first.

Let the legal theory follow the records.

A five-minute handoff test

Give the index—not your explanation—to a colleague unfamiliar with the dispute.

Ask whether they can identify within five minutes:

  • controlling specification;
  • affected lot;
  • first discovery date;
  • first notice date;
  • current goods location;
  • retained samples;
  • test method;
  • claimed amount;
  • next deadline.

If not, the file is still an archive rather than a case-management tool.

Bottom line

The strongest quality-dispute file is not the one with the most photographs.

It is the one where every important conclusion can travel backward through a clean chain:

claim → measurement → sample → lot → shipment → specification → contract.

That chain helps both sides distinguish a genuine product defect from specification drift, transit damage or an unproven assumption—and makes settlement, technical review or formal proceedings much more efficient.

General educational information only, not legal advice, evidence advice for a particular proceeding or technical certification. Preservation, disclosure, inspection, testing and admissibility rules vary by jurisdiction and forum.

Primary sources checked

  • UNCITRAL — United Nations Convention on Contracts for the International Sale of Goods (Vienna, 1980) (CISG)
    https://uncitral.un.org/en/texts/salegoods/conventions/sale_of_goods/cisg
    Checked: 2026-10-03. Boundary: Applies only when its scope and connecting rules are satisfied; parties may exclude or vary its application subject to applicable law. It does not create a universal sales law for every cross-border transaction.
  • legislation.gov.uk — Sale of Goods Act 1979
    https://www.legislation.gov.uk/ukpga/1979/54
    Checked: 2026-10-03. Boundary: UK statute used only as a concrete national-law example. Scope, amendments and contract type must be checked locally.
  • International Chamber of Commerce — Incoterms® 2020
    https://2go.iccwbo.org/explore-our-products/books/incoterms/incoterms-2020-eng-config.html
    Checked: 2026-10-03. Boundary: Contractual trade rules allocating defined delivery, cost and risk responsibilities when incorporated; they do not replace the entire sales contract or decide product quality law.
  • World Trade Organization — Technical Barriers to Trade
    https://www.wto.org/english/tratop_e/tbt_e/tbt_e.htm
    Checked: 2026-10-03. Boundary: Intergovernmental trade-law framework concerning technical regulations, standards and conformity-assessment procedures. It does not decide a private buyer-seller quality claim by itself.

Related Reading