How to create a claims and defenses evidence matrix for Breach-of-Contract Disputes

Create a claims and defenses evidence matrix by separating contractual obligations from governing-law elements, then linking each proposition to supporting evidence, adverse evidence, witnesses, and unresolved proof questions. Start with the operative agreement and verified legal framework, not the complaint’s narrative. The deliverable is a source-linked working table showing what counsel can presently support, what the opposing party can challenge, and which targeted investigation would most improve the assessment of liability, defenses, or damages. Keep factual findings, legal interpretations, and missing proof distinct.

When to use this workflow

Use this workflow when counsel must assess a demand, answer a complaint, evaluate a production, or prepare a focused merits review. It is particularly useful when parties disagree about which contract version controls, whether performance satisfied specifications, or whether notice and cure requirements were met.

Outside counsel and in-house teams can share the matrix while assigning different research, document, and witness tasks. Its scope is evidence analysis, not a complete discovery plan or legal memorandum.

This guide uses a US practice orientation. Verify substantive contract law separately; the cited federal rules do not supply contract elements or automatically govern state litigation or arbitration. See the scope provisions in the Federal Rules of Civil Procedure, Rule 1 and Federal Rules of Evidence, Rule 1101. Analyze rights against the actual language, applicable law, facts, and transaction context.

What you need

Assemble a bounded source set before evaluating proof:

• Executed agreements, amendments, incorporated specifications, schedules, purchase orders, and documents addressing conflicting terms.
• Pleadings or demands identifying claims, defenses, admissions, and disputed allegations.
• Delivery, acceptance, inspection, change-request, notice, cure, invoice, and payment records.
• Loss calculations with underlying accounting records, replacement transactions, credits, and assumptions.
• Witness information identifying roles, knowledge sources, and involvement in disputed performance.
• Counsel’s research identifying applicable elements, defenses, burdens, and unresolved governing-law questions.

Give documents stable IDs and retain pinpoint references. Identify covered repositories, custodians, and collection periods. “Not found in the reviewed production” describes a limitation; “does not exist” requires different support. Retain complete document families so attachments and incorporated terms remain available.

Use the template

Use the Breach-of-Contract Disputes — Claims and defenses matrix below. You can copy this table into your working document or spreadsheet. Maintain one row per element or defense proposition; split compound propositions when evidence or burdens differ.

Proposition / burden states what must be established and who bears the relevant burden, once researched. Distinguish allegations, legal elements, and contractual requirements. For defense rows, specify whose defense the supporting proof supports.

Contract / authority identifies the operative clause and relevant legal authority. Use document IDs with section or page references and authority pinpoints. Evidence cells should explain what a source shows, not merely list files. Cross-reference related issue IDs rather than duplicating analysis.

Witness / foundation identifies who can explain or authenticate material and any unresolved evidentiary question. Gap / status distinguishes “supported,” “contested,” “not yet supported,” and “legal research pending.” These are working assessments, not admissibility rulings. Assign actions to a person or team role. Place the assessment date and collection scope above the table.

Step by step

1. Fix the dispute boundaries and source coverage

Identify the parties, agreements, challenged conduct, requested relief, and assessment date. State whether the matrix addresses pleaded claims, anticipated claims, counterclaims, or all three. Keep each party’s position separate even when the same document concerns both.

Check amendment history and incorporated materials. If a purchase order allegedly changes delivery requirements, flag the competing documents rather than assuming priority. Identify missing schedules before interpreting specifications.

Record: stable issue IDs, relevant contract versions, and a coverage note identifying missing agreements, custodians, or production segments. Put document-specific limitations in the affected row’s gap field.

2. Convert the legal framework into testable propositions

Have counsel verify governing-law elements and asserted defenses. Do not substitute a generic formation–performance–breach–damages checklist for that analysis. Those categories organize investigation but do not establish the applicable legal test.

Break each element into factual propositions evidence could support or contradict. Separately identify contract-dependent questions, such as whether notice and a cure opportunity were required. Determine whether an assertion is a defense, denial of an element, or another issue under applicable law. Record unresolved burdens rather than guessing.

Record: the proposition, burden research, authority pinpoint, and interpretation dependency. Mark provisional rows as research pending and link factual subrows to their parent element.

3. Map the obligation to the alleged departure

Read the operative provision with definitions, exceptions, incorporated specifications, and amendments. Identify the obligated party, triggering event, required act, contractual timing, and alleged departure.

For defective goods, distinguish late delivery, technical nonconformity, disputed acceptance, and unsuccessful repair. For services, distinguish an express deliverable from an expectation absent from the reviewed agreement. Separate the factual event from counsel’s conclusion about its contractual significance.

Record: clause citations and distinct propositions for the obligation and challenged conduct. Add notice, cure, or remedy provisions where they could change the assessment; cross-reference rather than combining unrelated breaches.

4. Link evidence on both sides

Read the complete relevant document or conversation, including attachments. An email acknowledging delivery may reserve objections; a quality report may cover only a sample. State limitations beside citations. A receipt date does not necessarily establish the inspection or defect-discovery date.

Record pleading allegations as positions, not substitutes for underlying proof. Flag potentially significant admissions for counsel’s separate analysis. Distinguish firsthand knowledge from document-assisted recollection and secondhand accounts. Preserve contradictions rather than rewriting them into one narrative.

Record: supporting and adverse document IDs, pages or message locations, relevance explanations, and witness sources. Label inferences explicitly and identify what would confirm or contradict them.

5. Test foundation and identify missing proof

Ask how each important item could be identified and explained. In proceedings governed by the Federal Rules of Evidence, Rule 901(a) requires evidence sufficient to support a finding that an item is what its proponent claims. Knowledgeable-witness testimony is one nonexclusive example. Authentication does not itself resolve every admissibility issue. See Federal Rules of Evidence, Rule 901. (uscourts.gov)

Turn gaps into narrow tasks: obtain underlying inspection readings, identify the notice recipient, or interview the employee who approved a change. Federal civil discovery reaches nonprivileged information relevant to claims or defenses and proportional to the case’s needs under Rule 26(b)(1). (uscourts.gov)

Record: foundation questions, source limitations, targeted actions, and owners. Refer preservation questions promptly to responsible counsel; do not broaden collection indiscriminately to fill every blank.

6. Connect loss and defenses to the same record

For each claimed loss, identify the alleged breach, causal explanation, calculation, source records, and explanatory witness. Separate incurred costs from forecasts. Check credits, avoided costs, replacement purchases, duplication, and contractual remedy language without assuming their legal effect. Treat payment status as a factual question, not an automatic recoverability test.

Connect defenses to the propositions they challenge. A notice objection may raise different issues from a challenge to replacement-cost allocation.

Federal Rule 26(a)(1)(A)(iii) generally requires damages computations by category and availability of supporting nonprotected material, subject to applicable exceptions, stipulations, and orders. See Federal Rules of Civil Procedure, Rule 26. (uscourts.gov)

Record: damages-schedule references, documented amounts, disputed assumptions, and linked defense IDs. Distinguish a billed amount from a verified recoverable loss.

7. Review the matrix as a decision document

Conduct an opposing-position review: what is the strongest supported response to each proposition? Prioritize gaps by their potential to change the merits assessment, not document volume. A controlling amendment may matter more than additional repetitive complaints.

Separate missing evidence from unresolved interpretation. Assign legal research to counsel and factual investigation to the appropriate reviewer. After supplemental productions, update affected rows and preserve revision history.

Record: current status, decisive uncertainty, next action, and owner. Identify whether the remaining gap prevents a conclusion or merely limits confidence. Carry material unresolved issues into the review agenda.

Worked example

Fictional scenario: All parties, documents, amounts, and contractual terms below are invented. Alder Packaging buys 120 custom conveyor motors from Beacon Motion for $240,000. Agreement D001 requires delivery by September 10 under §3, Schedule A compliance under §4, and written defect notice to a designated address with a ten-business-day repair opportunity under §8. Section 11 excludes specified lost-profit claims; counsel has not assessed its application.

Alder alleges 30 failures and claims $36,000 in replacement costs plus $80,000 in projected production losses. The reviewed set contains a receiving log, partial tests, an operational email, and a replacement invoice. It lacks complete testing data, designated-address transmission evidence, and payment records. Governing-law research remains pending. These are representative factual subissues, not verified claim elements or an exhaustive matrix.

The matrix changes the assessment. Tests document 12 recorded failures, not 30 established failures. The receiving log concerns visible condition and does not resolve technical compliance. Notice requires transmission and repair evidence; an operational email alone establishes neither compliance nor noncompliance with §8.

The invoice documents a bill but leaves causation, allocation, and payment unresolved. Unexplained freight challenges allocation, not necessarily the entire replacement claim. Projected production losses need a separate row testing assumptions and §11. Counsel should not label the full $116,000 claim supported or reject it solely because payment records are absent.

Common mistakes

• One row for the entire claim. Separate obligations, elements, and loss categories so strong delivery evidence cannot conceal weak defect proof.
• Reliance on an unsigned draft. Verify execution, amendments, and incorporated schedules before mapping obligations.
• Silence treated as proof. Describe collection coverage and investigate before concluding notice or payment never occurred.
• Adverse passages omitted. Include reservations, concessions, repair offers, and conflicting accounts with pinpoints.
• Legal effects assigned to labels. Preserve facts behind “accepted,” “waived,” or “consequential,” and assign the legal question.
• Unclear defense direction. Specify whose proposition each evidence cell supports; cross-reference the challenged claim row.

Final quality check

• Each element and defense has verified authority or an assigned research issue.
• Contract citations identify operative versions and incorporated materials.
• Factual assessments trace to document pinpoints or identified witness sources.
• Supporting and adverse evidence remain distinct, with inferences labeled.
• Dates distinguish delivery, inspection, notice, and repair events.
• Damages rows identify calculations, source records, and disputed assumptions.
• Foundation questions and collection limitations remain visible.
• Material open issues have owners; revised links work and superseded assessments remain traceable.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, privilege and confidentiality analysis, chronology, and deposition-preparation capabilities can support the review behind this matrix. Use chronology analysis to examine disputed sequences and trial preparation to develop witness questions from proof gaps. The matrix is the team’s working document; lawyers verify sources, authorities, and conclusions. To discuss this workflow, book a demo.

Frequently asked questions

Should each defense have its own row?

Yes. Split distinct propositions when evidence or burdens differ. Identify the asserting party, cross-reference challenged claim rows, and research whether the issue is a defense or a denial of an element.

How should competing contract interpretations appear?

State each reading, cite supporting language, and identify facts that matter under each. Keep interpretation separate from performance evidence. Mark the legal question unresolved until counsel completes the analysis.

Can the matrix establish that no notice was sent?

Not merely because reviewed files lack notice. Record searched mailboxes, custodians, and periods. Distinguish limited collection results from affirmative testimony, and investigate sending and receipt separately.

Is the completed matrix ready to offer in evidence?

No, not automatically. Treat it as an internal analytical document; do not assume its label establishes privilege or protection. Federal Rule 1006 addresses qualifying summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not introduced. Underlying originals or duplicates must be available to other parties at a reasonable time and place. Counsel must assess any proposed evidentiary use separately. See Federal Rules of Evidence, Rule 1006. (uscourts.gov)

Sources

• Federal Rules of Civil Procedure: Rules 1, 26(b)(1), and 26(a)(1)(A)(iii).
• Federal Rules of Evidence: Rules 901, 1006, and 1101.

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.