Skip to main content
Skip to guide content

File · 04 Editorial guide

Incident evidence file

The product and the complaint log are the file. Do not wait for a theory of defect.

First job Preserve the product and the complaint record before arguments about defect.

Start here

Decision railsafety → product identity → incident → custody and condition → supply chain → testing and loss
See routing facts

Start here

Key considerations

The first questions are about urgency, governance and preservation — before collection expands or interviews begin.

  1. Is the product still available?
  2. Which batch or serial facts exist?
  3. What complaints already came in?

Direct answer

What this page decides

Owner
02

A product-incident file should preserve the product, packaging, labels, instructions, serial or batch identifiers and purchase record before testing, repair or disposal changes the evidence. Record the incident, custody, use, maintenance, warnings, injury or property damage and every supply-chain participant. Keep observed facts separate from a proposed defect theory. This page prepares the evidence record; it does not determine defect, causation, responsibility or compensation.

At a glance

Which fact changes the next route

Use the fact that changes ownership or urgency to decide the next move.

Facts that change the next investigation route
QuestionWhy it mattersNext route
Is the product still available?Condition, components and identifiers may be central to later inspection.Secure it safely and document custody without destructive testing.
Which exact unit and batch are involved?Model families and packaging may change over time.Photograph identifiers and preserve purchase and distribution records.
How was it used and maintained?Installation, modification, environment and maintenance affect the factual analysis.Build a sourced use and service chronology.
Who handled it after the incident?Movement, repair or testing can alter condition and provenance.Create a signed custody and access log.

Scope

What this page owns — and what it does not

This page covers product identity, scene and condition evidence, custody, instructions, use, maintenance, supply chain, testing preparation and loss records.
Recall, food safety, personal injury, consumer remedies and insurance should remain coordinated but distinct workstreams.
Not decided heredefect type, warning adequacy, causation, responsible party, admissibility, recall duty or damages.

Practical workflow

Action, evidence, legal gate, output

Practical workflow
ActionDocuments / evidenceLegal gateOutput
Protect people and productSafety response, scene media, product and packagingDo not delay care or alter evidenceInitial preservation record
Fix identity and custodySerial, batch, receipt, shipping and access recordsReconcile the exact unit and handlersIdentity and custody log
Reconstruct use and incidentInstructions, installation, maintenance, witnesses and device dataSeparate observation from theorySourced incident chronology
Plan inspection and claimsTesting protocol, supply chain, injuries, damage and noticesCoordinate access and preserve originalsInspection and claim brief

Documents

What to gather before the next call

These items help clarify the file; they are not a legal requirement list.

Documents to gather before instructing counsel
ItemWhy neededWho holds itRisk if missing
Product, packaging and identifiersFixes the item and its conditionCustodian and partiesThe wrong model or an altered item is examined
Use, maintenance and incident recordShows the operating contextUser, installer, servicer and witnessesA defect theory replaces the factual chronology
Supply-chain and custody fileIdentifies actors and preserves provenanceSeller, distributor, manufacturer and custodianResponsibility or admissibility cannot be assessed

Common failure points

Where files usually break

  1. Discarding packaging or sending the product for repair before preservation.

  2. Allowing destructive testing without an agreed protocol and documentation.

  3. Publishing a defect conclusion before identity, condition and use are verified.

Decision map

Keep the question bounded.

  1. Hold the unitIf safe, do not destroy it.
  2. Hold the paperInstructions, warnings, QC, complaints.
  3. Map the chainWho made, imported, and sold it.

Curated resources

Open the asset that matches this job.

Helpful to prepare

Facts that make the next conversation clearer.

These items are orientation aids, not a legal requirement list.

Whether the unit is preservedOwner of the complaint logWhether a regulator already has a file

Evidence file

Preserve the record before the forum is chosen.

This is a preparation prompt, not a finding that any item is admissible or required.

  1. Product sample or photos
  2. Batch / serial / listing identity
  3. Instructions and warnings as sold
  4. Complaint and incident chronology
  5. Supply-chain parties at a high level

Counsel hand-off

What to bring when you instruct

Bring the preserved product and packaging, original media, purchase and shipping records, serial and batch details, instructions and warnings, installation and maintenance history, incident and medical records, witness details, custody log, supply-chain identities, complaints or recalls, insurance notices and loss evidence.

Local context

Add the city when market-supervision practice changes.

SAMR, sampling and court practice can differ after the national defect or recall question is identified.

Open city and province guides

Counsel hand-off

Need product-liability counsel?

This hub organises defect, injury, recall and channel questions. It does not decide defect, run a recall or settle a claim on your facts.

Find product-liability counsel

Submit an initial enquiry

Need qualified counsel?

Move carefully. Move with a record.

Use the portal to identify counsel for this practice and related China-side issues.