How to create a claims and defenses evidence matrix for Product Liability Matters

Create a claims and defenses evidence matrix by translating jurisdiction-verified legal theories into discrete factual propositions, then linking each proposition to supporting records, contrary evidence, witnesses, and unresolved gaps. Separate product identification, manufacturing defect, design defect, warnings, causation, damages, and asserted defenses rather than treating “defect” as one issue. The deliverable is a source-linked working table showing what the reviewed record supports, what remains disputed, and which targeted evidence task should come next—not a substitute for legal analysis, technical assessment, or admissible proof.

When to use this workflow

Use this workflow to assess pleadings against an initial production, reconcile engineering records with incident accounts, or identify proof gaps before expert assessment, depositions, or a dispositive motion. It suits plaintiff, manufacturer, distributor, and insurer-appointed teams. The represented party changes the questions and priorities, not the need to preserve adverse evidence.

Keep the scope bounded: identify the operative pleadings, reviewed document set, and assessment date. This is an evidence-analysis workflow, not a complete discovery plan.

The procedural discussion uses a US federal district-court baseline. Verify substantive elements and defenses under the applicable governing law; check state-court or arbitral requirements separately. Federal procedural rules do not establish substantive product-liability elements. Federal Rules of Civil Procedure, Rule 1

What you need

Assemble sources with stable identifiers:

• Legal framework: operative complaint and answer, asserted defenses, relevant orders, and counsel’s verified element-and-defense analysis, including burdens where relevant.
• Product identity: model, serial or lot information, purchase records, photographs, manufacture date, configuration, and incident-unit custody records.
• Technical records: specifications, drawings, bills of materials, supplier revisions, quality records, test protocols, raw results, and available engineering explanations.
• Warnings and use: artwork, manuals, packaging versions, distribution records, incident accounts, and repair or modification history.
• Causation and damages: inspections, witness accounts, relevant medical or property records, loss calculations, and available expert materials.

Identify collection limits. Final test reports without raw data may leave technical questions unanswered. Record missing custodians or repositories rather than treating the production as complete. Apply the team’s access and circulation controls to counsel’s analysis; do not assume every matrix version belongs in an external evidence package.

Use the template

The companion template is Product Liability Matters — Claims and defenses matrix. You can copy this table into your working document or spreadsheet.

Use one row per factual proposition, not one row per document. Assign stable IDs such as PL-014 so references survive sorting. In Law / burden, cite verified authority and a pinpoint, or the section of counsel’s legal memorandum addressing that proposition. Mark unresolved law as a research question.

Evidence cells need a document ID, precise locator, and explanation of relevance. Distinguish direct observations, reported statements, and counsel’s inferences. Contrary / limits accommodates both opposing evidence and limitations that do not themselves disprove the proposition.

Identify a potential foundation witness without implying that the person has already supplied testimony. Describe gaps specifically: “incident lot unidentified” is better than “weak.” Put status, review date, and source-set reference in the assessment cell or a linked row note. Assign an owner and the decision each action will inform.

Step by step

1. Define the claims, defenses, and disputed propositions

Read the operative allegations and defenses alongside counsel’s governing-law analysis. Create separate sections for the pleaded defect theories, product identification, causation, damages, and asserted defenses. These are organizational categories, not universal elements.

Break each element into propositions that evidence can support or contradict. For a manufacturing allegation, distinguish the applicable specification from evidence that the incident unit departed from it. For a warning allegation, distinguish warning content, delivery, use circumstances, and any required causal connection.

Analyze defenses independently. Do not label every alternative explanation “misuse”; determine whether it concerns a disputed claim element, an affirmative defense, or both under the governing law.

Record: row ID, proposition, legal reference, applicable burden, and any assigned legal research question.

2. Match each record to the relevant product configuration

Connect records to the incident unit through model, lot, component revision, manufacture date, and alterations. A same-family product test may involve a different component or operating condition.

Separate event dates from document creation dates. For design and warning revisions, trace approval, implementation, manufacture, and distribution. Approval does not establish which units received the change. For manufacturing issues, connect inspection measurements to the correct specification revision and production lot.

Preserve potentially relevant records when identity is uncertain, but qualify the connection rather than selecting the most convenient revision.

Record: identifiers beside evidence citations, configuration uncertainty in the assessment, and the task needed to establish the missing link.

3. Link supporting evidence to narrow factual statements

Read the underlying source, not only a summary. Capture the page, drawing region, test-run identifier, photograph number, or transcript lines supporting the proposition. Explain the inferential step: a laboratory failure may establish a result under specified conditions without establishing the incident mechanism.

For damages, separate evidence of an incurred expense from evidence connecting it to the claimed injury. For witnesses, distinguish personal observations from information received from others. Link duplicates to a canonical record while preserving different attachments, annotations, or versions.

Record: what each source supports, who may explain it, and the limits of its significance. Avoid measuring support by document counts.

4. Test contrary evidence and defense propositions

Ask what would undermine each proposition: a different configuration, intervening repair, inconsistent use account, test deviation, alternative injury mechanism, or unsupported loss component. Treat these as questions to investigate, not established facts or automatically available defenses.

Build affirmative rows for asserted defenses rather than leaving them only in a claim row’s contrary-evidence cell. Cross-reference shared sources so the team can see whether the same record challenges causation and supports a separately verified defense.

Compare other incidents by model, configuration, conditions, failure mode, and source quality. Preserve conflicting accounts rather than replacing earlier statements with later testimony.

Record: opposing evidence, its precise effect, relevant defense-row references, and unresolved comparability. “None located in the reviewed set” does not mean none exists.

5. Separate discovery relevance from proposed evidentiary use

In federal district-court litigation, Rule 26(b)(1) permits discovery of nonprivileged matter relevant to claims or defenses and proportional to the case; information within that scope need not be admissible. Use this distinction when prioritizing gaps. Federal Rule of Civil Procedure 26(b)(1)

Rule 901 requires sufficient evidence to support finding that an item is what its proponent claims. Authentication does not independently resolve hearsay or other admissibility issues. Identify foundation questions for photographs, spreadsheets, inspection results, and messages. Federal Rule of Evidence 901

For subsequent remedial measures, record timing and proposed purpose. Rule 407 excludes their use to prove negligence, culpable conduct, product or design defect, or need for warnings or instructions. Other purposes may qualify, including impeachment or, if disputed, ownership, control, or feasibility. The rule addresses admissibility, not a blanket discovery prohibition. Federal Rule of Evidence 407

Record: the specific evidentiary concern and reviewer; avoid labeling an entire factual issue “inadmissible.”

6. Turn material gaps into targeted evidence tasks

Prioritize tasks by their effect on important disputed propositions and the practical route to an answer. Identifying the incident revision may matter more than collecting another batch of loosely comparable complaints.

Specify the needed evidence: “obtain inspection measurements and disposition records for the incident lot,” not “get quality documents.” Identify whether records, a fact witness, inspection, or expert analysis should answer the question. Do not ask a custodian to supply an unsupported technical conclusion.

Record: task, owner, expected source, priority, and decision affected. Explain any deliberate deferral; keep broader discovery scheduling in the team’s separate tracker.

7. Reassess the matrix and preserve material changes

Have counsel test the strongest and weakest rows against their sources and legal references. Assess claim and defense rows together without collapsing their distinct burdens.

Use reasoned statuses such as “supported on current record,” “conflicted,” or “unresolved.” A technical result can be supported while its incident applicability remains unresolved. Avoid numerical liability scores that conceal a missing causal or identification link.

Update affected rows when evidence arrives, retaining a short history of material changes.

Record: revised assessment, reason, source-set boundary, review date, and open owner assignments. Preserve a dated version for the next case assessment.

Worked example

Fictional scenario: Counsel represents fictional manufacturer Alder Kettle Works in a burn-injury action concerning an AK-4 electric kettle. The complaint alleges a shutoff-system design defect and inadequate warning. The answer disputes causation. All parties, products, documents, and facts below are fictional; the rows are factual subpropositions, not statements of governing law.

The reviewed set contains a laboratory report, incident photographs, and warning artwork. The incident serial label is unreadable. Fictional legal memorandum LM-01 addresses the governing theories, but the reviewed evidence does not establish the unit’s component revision or supplied manual. The report describes contacts remaining closed, leaving power energized—not an open circuit that would interrupt power.

This assessment changes the next decision. Counsel cannot connect the test result to the incident mechanism without addressing configuration and comparability. The unreadable label leaves a proof gap; it is not affirmative proof that a different revision caused the injury. Similarly, pre-purchase artwork approval does not establish warning delivery or resolve warning adequacy and causation.

The next tasks target identity, test comparability, and packaging implementation. No missing serial record, raw result, or distribution record is assumed to exist.

Common mistakes

• One row labeled “defective product.” Separate manufacturing, design, and warning propositions; connect manufacturing measurements to the applicable specification.
• Defenses appear only as adverse notes. Create rows for their verified factual requirements and cross-reference overlapping claim evidence.
• Complaint volume substitutes for comparability. Record model, conditions, configuration, mechanism, and unresolved differences before grouping incidents.
• Document silence proves absence. Identify the reviewed repositories and seek the expected record or explanation for its absence.
• Revision approval proves implementation. Trace release, manufacture, distribution, and incident timing independently.
• The matrix becomes advocacy. Preserve adverse sources and qualify technical inferences instead of converting them into findings.

Final quality check

• Each element and defense has verified governing-law support or an assigned research question.
• Every source citation opens to the stated passage, image, or data location.
• Product identity, specification revision, and configuration differences are explicit.
• Observations, reported accounts, and inferences are distinguishable.
• Supporting evidence, contrary evidence, and source limitations remain visible.
• Foundation, evidentiary-purpose, and technical questions have appropriate reviewers.
• Every material gap is resolved, assigned, or deferred with reasons.
• The version identifies its assessment date, source set, and permitted circulation.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its evidence analysis, document review, chronology, and deposition-preparation capabilities can support examination of the records underlying counsel’s matrix. Use its trial-preparation capabilities to support source-based analysis, while lawyers retain responsibility for legal elements, technical inferences, and unresolved gaps. The matrix remains the team’s work product, not a promised dedicated module. Book a demo to discuss this product-liability evidence workflow.

Frequently asked questions

Should manufacturing and design allegations share a row?

Usually not. Even when both rely on an inspection, separate departure-from-specification questions from design-related propositions and verify their respective legal requirements. Cross-reference the shared inspection rather than treating it as interchangeable proof.

How should we handle an unavailable incident product?

Mark identification and inspection limitations. Map photographs, purchase records, service history, and witness accounts to the narrower facts they support. Assign counsel and technical reviewers to assess unanswered questions without inventing inspection findings or presuming the consequences of unavailability.

Can a test result establish causation?

Do not assume it does. Record the tested configuration, protocol, conditions, deviations, and observed result separately from the proposed incident mechanism. Assign the comparability and causal questions for appropriate technical assessment, alongside factual evidence of actual use.

Can we offer the matrix itself as a trial summary?

Not automatically. Rule 1006 permits evidentiary summaries of voluminous admissible materials that cannot conveniently be examined in court, with underlying originals or duplicates available to other parties. A matrix containing legal analysis and unresolved inferences requires separate assessment; a chart functioning only as an illustrative aid falls under Rule 107. Federal Rule of Evidence 1006

Sources

• Federal Rules of Civil Procedure, Rules 1 and 26(b)(1); compilation amended through December 1, 2025.
• Federal Rules of Evidence, Rules 407, 901, and 1006; compilation amended through December 1, 2025.

Scope: General professional workflow guidance for the October 13, 2026 assignment cutoff, not a determination of liability in a particular matter.

This guide is general information about legal workflows, not legal advice for any matter. It was drafted and reviewed with AI assistance. The worked example is fictional. Contract rights and procedure depend on the governing law, the actual wording, and the facts, so check the cited sources and the rules that apply in your jurisdiction before relying on it.