How to create a claims and defenses evidence matrix for Bankruptcy Adversary Proceedings

Create the matrix by separating each pleaded claim and defense into propositions counsel must establish or contest, then linking each proposition to supporting evidence, adverse evidence, witnesses, and unresolved gaps. Verify governing authority and burdens separately from the factual record. In a bankruptcy adversary proceeding, preserve distinctions between debtor and counterparty records, transaction dates, and competing accounts of payment or performance. The deliverable is a source-linked working table showing what the record supports, what remains uncertain, and which evidence task should come next.

When to use this workflow

Use this workflow to evaluate a complaint and answer against the available record, prioritize discovery, prepare witness examinations, or assess evidentiary support for a proposed motion. It is particularly useful when debtor accounting records, counterparty records, and bank activity describe the same transaction differently.

The scope is US federal bankruptcy adversary proceedings. Bankruptcy Rules 7026, 7030, and 7033–7037 incorporate corresponding Civil Rules governing discovery. Contested matters require separate treatment under Rule 9014, including its exceptions concerning disclosure and conference provisions. Check local rules and case-specific orders separately. See Bankruptcy Rules 7026–7037 and 9014. (uscourts.gov)

The matrix organizes analysis; it does not supply substantive elements. Keep preference, fraudulent-transfer, discharge, and contract theories separate, with authority appropriate to the claim, governing law, and procedural posture.

What you need

Assemble a defined review set:

• Operative pleadings and orders: complaint, amendments, answer, asserted defenses, and orders narrowing the issues.
• Verified legal analysis: authority for each element, defense proposition, and burden, identifying controlling jurisdiction and procedural posture.
• Transaction records: contracts, amendments, invoices, delivery records, bank statements, remittances, ledger exports, reversals, and refunds.
• Bankruptcy context: petition information and relevant docket materials, with docket and page references.
• Witness and discovery materials: interviews, declarations, transcripts, written responses, production indexes, and collection limitations.
• Review controls: stable document IDs, an entity list, access restrictions, and designated reviewers for legal and evidentiary questions.

Preserve accounting exports with their original files, tab names, date coverage, and export settings. A cell reference must identify a retrievable version. Identify missing periods before interpreting silence as evidence that an event did not occur.

Use the template

The companion template is Bankruptcy Adversary Proceedings — Claims and defenses matrix. Copy this table into your working document or spreadsheet. Use one row per element or defense proposition, splitting rows when distinct factual questions require different proof.

Assign stable identifiers such as C1-E2 or D2-P1. Include a precise authority citation and counsel’s verified legal proposition—not merely a statute name. Identify unresolved legal questions explicitly.

Source cells should contain document IDs and pages, transcript lines, or workbook versions and cell ranges. Distinguish allegations from evidence. Use descriptive statuses such as “supported but contradicted” or “insufficient record,” rather than unexplained confidence scores.

The witness field should distinguish factual knowledge from record foundation. The same person may not supply both. Keep absent corroboration in the gap field: an unsigned delivery ticket is not, without more, affirmative evidence of nondelivery. Assign each material gap an action and owner.

Step by step

1. Define the issues and initial source set

Read the operative pleadings alongside orders affecting scope. Assign identifiers to each claim and defense, preserving distinctions between parties, transactions, and requested relief. Cross-reference supporting transaction schedules rather than compressing multiple payments into an unexplained total.

Create a dated source index separating debtor, counterparty, third-party, and counsel-created materials. Record missing collections and unreviewed productions. Preserve entity distinctions: similar names do not establish that an affiliate received the challenged payment.

Record in the template: theory identifier, pleading paragraph, affected transaction or entity, initial status, and missing source categories.

2. Verify the proposition and burden

For each row, identify the legal proposition being tested. Have counsel verify the applicable authority, burden allocation, and procedural posture before evaluating evidentiary sufficiency. Distinguish a claimant’s required showing from a defendant’s denial and an affirmative defense.

Where authority is unresolved, assign a research question rather than inserting an assumed rule. Payment initiation, bank clearing, and ledger posting should remain separate events until counsel determines their legal significance. A completed factual review cannot compensate for an incorrect statement of the element.

Record in the template: precise authority, burden, and verified proposition—or an assigned legal question. Keep legal uncertainty distinct from factual uncertainty.

3. Map favorable and unfavorable evidence

Enter the strongest supporting source and strongest contradiction before adding cumulative records. Describe what each source actually shows. An invoice records billing information; do not treat it alone as proof of delivery or receipt of payment.

For payment disputes, reconcile identifiers across bank activity, debtor ledgers, remittances, and invoice applications. Preserve reversals and refunds. Distinguish the contracting party, invoice issuer, payee, intermediary, and alleged beneficiary. Where no adverse evidence was found, state that conclusion only for the defined review set.

Record in the template: exact supporting and adverse citations, identifying direct records, witness accounts, and counsel inferences separately.

4. Test witnesses and evidentiary foundations

Identify who can explain the transaction and who can establish the record’s foundation. Separate personal recollection from interview notes, declarations, and deposition testimony. Organizational testimony under Civil Rule 30(b)(6) concerns information known or reasonably available to the organization, not only the designee’s personal memory. See Civil Rule 30(b)(6). (uscourts.gov)

Bankruptcy Rule 9017 applies the Federal Rules of Evidence. Authentication under Evidence Rule 901(a) and the business-records exception under Rule 803(6) require separate analysis; indexing a ledger establishes neither. See Bankruptcy Rule 9017 and Evidence Rules 901(a) and 803(6). (uscourts.gov)

Record in the template: potential witness, basis of knowledge, foundation question, and unresolved evidentiary concern.

5. Turn gaps into proportionate evidence tasks

Prioritize missing information that could change the assessment. Determine whether existing production, a focused request, an interview, or another discovery method is the best next source. Specify the question to answer rather than assigning “more discovery.”

Civil Rule 26(b)(1), applicable through Bankruptcy Rule 7026, addresses nonprivileged information relevant to claims or defenses and proportional to case needs. Discoverability does not require admissibility. Keep useful investigative leads distinct from evidence ready for the proposed use. See Civil Rule 26(b)(1). (uscourts.gov)

Record in the template: missing fact, proposed source, owner, and priority rationale. Cross-reference a discovery tracker rather than calculating deadlines in the matrix.

6. Reassess the row and preserve alternatives

After new evidence arrives, reconsider both sides. A matching bank debit may strengthen payment identification while leaving recipient ownership unresolved. An accounting explanation may resolve a posting discrepancy without establishing the legally relevant date.

Use a second reviewer for decisive rows. Ask for the strongest competing explanation and the evidence needed to distinguish it. Preserve prior assessments in version history. Classify remaining issues as resolved, awaiting evidence, awaiting legal analysis, or accepted uncertainty for a specified decision.

Record in the template: revised status, review date, alternative explanation, and next action. Completion requires resolution or an explicit disposition of uncertainty—not merely filled cells.

Worked example

Fictional scenario: Counsel represents Cedar Quay Components LLC in an adversary proceeding brought by the trustee of fictional debtor Harbor Lantern Manufacturing Inc. A preference count challenges a $96,000 payment. Cedar Quay disputes the alleged recipient and asserts a subsequent-new-value defense involving a later shipment. These fictional allegations do not establish the claim’s or defense’s legal requirements.

The initial records include a debtor ledger, bank statement, remittance notice, invoice register, and unsigned delivery ticket. Counsel has not completed verification of burdens, transfer-date law, or the later shipment’s legal significance. The three entries below are preliminary factual subissues, not a complete elements matrix.

The matrix changes the immediate decision. Counsel should not treat the posting date and debit date as interchangeable, assume CQ Processing is Cedar Quay, or credit $24,000 as an established defense amount. The unsigned ticket creates a corroboration gap, not proof of nondelivery. The next tasks are payment tracing, recipient identification, receipt verification, and legal analysis; unresolved elements must then receive additional rows.

Common mistakes

• One row for an entire avoidance count. Split propositions so evidence of payment does not conceal a missing recipient or other required issue.
• Treating a ledger entry as the transaction. Compare bank and counterparty records; preserve distinct event dates.
• Confusing missing corroboration with contradiction. Put absent receipt evidence in the gap field; reserve adverse-source cells for contrary material.
• Treating a witness name as a foundation. Identify what that witness can establish and which recordkeeping questions remain.
• Assuming a full table is a complete case analysis. Check every pleaded theory against verified elements, including rows still awaiting evidence.
• Calling the matrix a Rule 1006 exhibit. That rule addresses summaries of voluminous admissible materials and access to underlying originals or duplicates. An internal analysis table does not automatically qualify. See Evidence Rule 1006. (uscourts.gov)

Final quality check

Before relying on the matrix, confirm:

• Every operative claim and defense has identifiable proposition-level rows.
• Elements, burdens, and authorities are verified or expressly assigned.
• Decisive source references open to the correct passages or cells.
• Favorable evidence, contradictions, and missing corroboration remain distinct.
• Entities, payment events, and competing date theories are not conflated.
• Witness knowledge, authentication, and hearsay questions are separately assessed.
• Restricted materials remain within the matter’s access protocol.
• Every open issue has an owner, action, and stated decision consequence.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Use its document review, privilege and confidentiality analysis, chronology, evidence analysis, and deposition preparation capabilities to support source review while maintaining the matrix as counsel’s work product. The Chronology Viewer is relevant to competing event sequences; trial preparation supports related witness preparation. Counsel retains responsibility for authority, burdens, and evidentiary conclusions. To discuss this workflow, book a demo.

Frequently asked questions

Should each payment have its own row?

Use proposition-level rows linked to a transaction schedule. Split rows when recipients, defenses, evidence, or date questions differ materially; do not let aggregation obscure transaction-specific gaps.

Can one document support both sides?

Yes. Cite the relevant passage in each row and explain the competing inferences. A remittance can support payment identification while raising recipient uncertainty. Avoid one global favorable or adverse label.

How should privileged interview material appear?

Keep protected analysis within matter-specific access controls. Distinguish interview notes from independently available records. For broader working versions, use restricted-source references rather than copying sensitive analysis into accessible cells.

When is a row ready for a motion or examination?

Readiness depends on use. Counsel should be able to explain the proposition, authority, burden, supporting and adverse evidence, and foundation issues. A row may support deposition questions without supporting a factual assertion in a motion.

Sources

• Federal Rules of Bankruptcy Procedure: Rules 7026–7037, 9014, and 9017.
• Federal Rules of Civil Procedure: Rules 26(b)(1) and 30(b)(6).
• Federal Rules of Evidence: Rules 803(6), 901(a), and 1006.

Scope: General professional workflow guidance as of October 13, 2026; substantive claims and defenses require matter-specific verification.

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.