How to create a claims and defenses evidence matrix for Business Fraud Disputes

Create a claims and defenses evidence matrix by selecting the governing law, separating each fraud element and asserted defense, and linking each issue to supporting evidence, adverse evidence, witnesses, and unresolved proof questions. For every disputed representation, distinguish what was communicated from what the speaker knew, what the recipient relied on, and what loss allegedly followed. The deliverable is a source-linked working table that identifies supported positions, competing explanations, missing evidence, and assigned follow-up—not a conclusion that fraud or a defense has been established.

When to use this workflow

Use this workflow when litigation counsel or an in-house team must assess a business fraud complaint, answer, document production, or settlement position. It is particularly useful when sales materials, diligence disclosures, contractual representations, and internal financial records tell different stories.

The task is evidence analysis, not a complete discovery plan or damages model. Start with identified statements or omissions and test both the claim and the response against the reviewed record. Set a review cutoff so readers can distinguish current assessments from unresolved collection gaps.

This guide uses a US orientation. Federal procedural references concern federal district-court litigation; they do not automatically govern state proceedings or arbitration. Select governing substantive law, applicable evidence rules, local requirements, and case orders before adapting the matrix. Contractual arguments require analysis of actual wording, governing law, and transaction facts.

What you need

Assemble a defined review set:

• Positions and authorities: operative pleadings, asserted defenses, relevant orders, and verified authorities identifying elements, burdens, and the relevant procedural standard.
• Transaction communications: pitch decks, emails, messages, diligence questions, data-room disclosures, attachments, recipient lists, and version histories.
• Executed documents: agreements, incorporated schedules, amendments, and integration, nonreliance, exclusive-remedy, and fraud-carveout provisions.
• Knowledge and reliance records: forecasts, CRM histories, board materials, approval memoranda, decisionmaker communications, and witness accounts.
• Loss and provenance records: payment records, ledgers, valuation inputs, custodians, source systems, collection information, and production references.

Identify unavailable sources and collection limitations. A missing attachment is a gap in the reviewed record, not proof that its contents never existed. Keep legal assessments in counsel’s designated working environment and assess protection separately rather than assuming the matrix’s label resolves privilege questions.

Use the template

The companion template is Business Fraud Disputes — Claims and defenses matrix. Copy this table into your working document or spreadsheet. Use one row per element or defense issue; split rows when statements, transactions, or decisionmakers require different proof.

In Element or defense, identify the party advancing the position and link the relevant legal proposition. Record the applicable burden in that authority note. An element challenge is not necessarily an affirmative defense; label the issue accurately.

Evidence cells need document IDs and clause, page, paragraph, message, or spreadsheet-cell references. Describe what the source establishes separately from counsel’s inference. Witness / foundation identifies the person with relevant knowledge and the proposed authentication route. Gap / assessment records uncertainty and competing explanations.

Assign an identifiable owner and a concrete task. Use statuses such as “supported by reviewed evidence,” “conflicting evidence,” or “not located in reviewed set,” rather than an unexplained confidence score. Stable row IDs allow later productions to change an assessment without breaking references elsewhere.

Step by step

1. Establish the legal framework and disputed propositions

Identify the claim, selected law, procedural posture, and authority for each element. In Connaughton, the New York Court of Appeals described fraud in terms of a false representation or material omission, knowledge of falsity, inducement, justifiable reliance, and injury. It affirmed dismissal for failure to allege compensable damages. This is a New York pleading-stage example, not a nationwide fraud checklist. See Connaughton, opinion pages 6–9. (nycourts.gov)

Separate affirmative defenses, element challenges, and contractual arguments. For an omission theory, assign the asserted disclosure-duty question for legal analysis instead of presuming silence is actionable. Keep legal sufficiency distinct from whether the reviewed evidence supports the allegation.

Record: separate issue rows, linked authorities, applicable burdens, and assigned governing-law questions.

2. Identify each statement and its transaction context

Assign a statement ID and link a statement note containing exact wording, speaker, recipient, medium, date, and relevant commitment or payment. For omissions, identify the missing information and the communication or decision context in which disclosure was allegedly required.

Separate deck creation from delivery, data-room availability from access, and access from discussion. Mark disputed or inferred dates. Retain original time zones when the sequence matters.

Federal Rule 9(b) requires particularity for circumstances constituting fraud while allowing knowledge and intent to be alleged generally. That pleading rule does not replace evidence analysis or establish the trial-proof standard. See Federal Rule of Civil Procedure 9(b). (uscourts.gov)

Record: statement-linked rows, pinpoint references, transaction timing, and unresolved communication facts.

3. Map supporting and adverse evidence together

Read complete threads and attachments. Link each source to the proposition it actually supports: authorship, falsity, knowledge, inducement, reliance, or loss. Do not copy a damaging email into every element row without explaining the connection.

Add adverse evidence during the same pass. A diligence warning may challenge reliance; a revised forecast may qualify a knowledge inference; an approval memorandum may disclose an independent reason for proceeding. Preserve competing interpretations rather than burying them in a status label.

Distinguish firsthand observations from inference and secondhand reports. Identify when apparently corroborating records repeat the same underlying account. Describe contradictions without rewriting uncertain witness recollections into categorical facts.

Record: pinpoint support, pinpoint contradiction, and a brief explanation of each source’s significance.

4. Test reliance and claimed loss against actual decisions

Identify who authorized the transaction, when they acted, and what information reached them beforehand. Compare the alleged representation with diligence findings, warnings, pricing discussions, and approval conditions. Record whether a witness actually recalls using the statement or whether reliance is inferred from contemporaneous records.

Trace claimed loss to payment and financial evidence. Separate expenditure, alleged value shortfall, subsequent underperformance, and alternative causes. Connaughton applied New York’s out-of-pocket approach and rejected speculative lost opportunities as a basis for compensable fraud damages; do not export that holding to another jurisdiction. See Connaughton, opinion pages 7–9. (nycourts.gov)

Record: decisionmaker, decision date, source-backed loss theory, competing causes, and required financial or legal review.

5. Analyze contractual responses without treating clauses as conclusions

Read the signed agreement and incorporated schedules, not a negotiation draft alone. Capture the scope of integration, nonreliance, exclusive-remedy, and fraud-carveout wording. Identify which statements, parties, and conduct each provision addresses.

Connect each clause to a specific allegation. A provision addressing projections should not silently become a response to an allegation about existing customer cancellation notices. Compare any carveout with the provision invoked and assign governing-law analysis before describing its effect.

Keep contractual responses separate from challenges to actual reliance. They may involve overlapping evidence but require different reasoning.

Record: executed-document citation, statement IDs, precise argument, contrary wording, and unresolved interpretation. Distinguish “clause located” from “defense established.”

6. Assess provenance and evidentiary readiness

For each important item, identify its custodian, source system, completeness, and available foundation witness. Flag screenshots lacking surrounding messages and spreadsheets lacking formulas or version context. Record whether the proposed witness knows the record’s creation, receipt, maintenance, or only its later discovery.

Federal Evidence Rule 901(a) requires evidence sufficient to support a finding that an item is what its proponent claims. Authentication does not resolve hearsay or other admissibility issues, and a Bates number is not itself an authentication route. See Federal Rule of Evidence 901(a). (uscourts.gov)

Record: proposed foundation, missing source material, and separate evidentiary questions. Avoid an unqualified “admissible” status.

7. Convert gaps into proportionate actions and reassess

Prioritize gaps capable of changing an element assessment, undermining a contractual response, or materially affecting loss analysis. Seek the missing disclosure version before proposing review of the entire customer relationship.

Federal discovery concerns nonprivileged matter relevant to claims or defenses and proportional to the case; information need not be admissible to be discoverable. Apply that boundary when converting gaps into proposed requests. See Federal Rule of Civil Procedure 26(b)(1). (uscourts.gov)

Choose the appropriate action: source retrieval, witness interview, targeted discovery, or legal research. When new evidence arrives, update both favorable and adverse columns and preserve the reason for the changed assessment.

Record: concrete task, owner, priority, review date, and assessment history.

Worked example

Fictional scenario: Alder Quay Analytics buys a software business from Beacon Ridge Systems for $9.4 million. Counsel is evaluating a New York-law fraud theory, subject to separate governing-law verification. All parties, documents, amounts, and clause wording are fictional.

A September 2, 2026 sales deck, BR-020 p. 4, states: “No major subscription customer has given cancellation notice.” A delivery email, BR-021 p. 1, shows Beacon’s finance lead sent that deck to Alder’s acquisition director on September 3. The acquisition closed September 18.

An August 28 internal email discusses a cancellation request, but the customer’s original notice is missing. A disclosure workbook mentions renewal risk; the reviewed set does not establish which version Alder accessed before signing. The executed agreement addresses nonreliance on forecasts and contains a fraud carveout. These facts require distinct knowledge, reliance, contractual, and loss inquiries.

The following three entries are an excerpt, not the complete element analysis.

The matrix changes the next decision. Knowledge warrants targeted follow-up, but the cancellation request’s meaning remains contested. Reliance requires delivery and decision evidence, not merely a disclosure file’s existence. Separate contractual rows should analyze AQ-031 §8.4’s forecast wording and §8.7’s fraud carveout; neither resolves the existing-notice allegation without further analysis. The ledger proves payment, not the amount of fraud-related loss.

Common mistakes

• One row for “fraud.” Separate elements and responses so a strong knowledge inference does not conceal missing reliance or loss proof.
• Treating available disclosures as received. Track version, delivery, access, and decision timing; flag absent logs.
• Using hindsight as knowledge evidence. Explain how later records bear on earlier awareness and examine intervening events.
• Treating nonreliance wording as dispositive. Map executed language and carveouts to individual statements, then assign governing-law analysis.
• Equating purchase price with damages. Identify the loss theory, valuation support, and alternative causes instead of copying the payment total.

Final quality check

Before circulating the matrix, confirm:

• Every element and asserted defense has an accurately labeled row.
• Authorities match the jurisdiction, burden, and procedural posture.
• Material assertions have checked pinpoint source references.
• Complete threads, attachments, and disclosure versions are checked or flagged.
• Evidence and counsel’s inferences remain distinguishable.
• Key records have proposed foundation routes and separate evidentiary questions.
• Material gaps are resolved or assigned to identifiable owners with review dates.
• The review cutoff, limitations, and reasons for changed assessments are visible.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, and chronology capabilities can support examination of the records underlying this matrix. Use the chronology viewer to support timing analysis and trial preparation capabilities where they fit the assignment. The matrix remains counsel’s work product: lawyers verify sources, assess contradictions, and determine legal significance. To discuss this evidence-analysis workflow, book a demo.

Frequently asked questions

Should every representation have its own matrix?

Usually, statement IDs within one matrix are sufficient. Split rows when different speakers, recipients, or commitment dates would otherwise obscure proof. Link each row to the exact statement note.

How should we record an alleged omission?

Identify the missing information, relevant communication or decision, and asserted basis for a disclosure obligation. Separate that legal question from evidence that someone possessed the information.

Can we mark an element unsupported before discovery ends?

Yes, if the status expressly means unsupported in the reviewed record at the stated cutoff. Identify unreviewed sources and distinguish “not located” from affirmative contradictory evidence.

Can the matrix become a trial exhibit?

Do not assume so. Federal Rule 1006 permits summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not the underlying materials are introduced. Originals or duplicates must be available to other parties at a reasonable time and place. Assess a proposed exhibit separately under Federal Rule of Evidence 1006; an advocacy matrix is not automatically a qualifying summary. (uscourts.gov)

Sources

• Federal Rules of Civil Procedure, Rules 9(b) and 26(b)(1).
• Federal Rules of Evidence, Rules 901(a) and 1006.
• Connaughton v. Chipotle Mexican Grill, Inc., New York Court of Appeals, May 2, 2017, opinion pages 6–9.

Scope: General professional workflow guidance using the supplied research through October 13, 2026; not advice for a particular dispute.

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.