Product
Analyze
Review
Produce
Draft
Solutions
Litigation
- Early Case Assessment
- Investigations & Subpoenas
- Trial Preparation
- Enterprise eDiscovery
- Cloud eDiscovery
Transactional
Who it’s for
Resources
Learn
Customers
Events & CLE
Organize witness evidence around disputed propositions, not witness names alone. For each proposition, identify who can address it, distinguish personal recollection from organizational knowledge or document-based inference, and link supporting and adverse records to exact citations. Record contradictions, missing sources, foundation questions, and assigned follow-up in a witness evidence matrix. The resulting work product should connect an allegation or defense to its testimony and documents, while preserving uncertainty and avoiding assumptions that an interview note is sworn evidence or an accounting date determines the legally operative transfer date.
When to use this workflow
Use this workflow when counsel has pleadings, witness accounts, and transaction records but cannot yet explain consistently who knows what and which documents support each account. Triggers include preparing a former controller’s examination, reconciling a vendor’s testimony with debtor payment records, or assessing conflicting accounts before settlement discussions. It also helps in-house teams organize counterparty records for litigation counsel.
The scope is US federal bankruptcy adversary proceedings. Bankruptcy Rules 7026 and 7030 incorporate Civil Rules 26 and 30. Contested matters differ: Rule 9014(c) excludes specified Rule 26 disclosure and conference provisions unless ordered otherwise. Check local rules and case-specific orders separately. See Bankruptcy Rules 7026, 7030, and 9014.
This is an evidence-organization workflow, not a determination of avoidance elements, discharge standards, burdens, or controlling precedent. Counsel must supply the governing issue framework.
What you need
Assemble a bounded review set and identify its coverage before populating rows:
- Issue framework: operative complaint, answer, counterclaims, and counsel-verified elements, defenses, burdens, and authorities. Keep preference, fraudulent-transfer, discharge, and contract theories separate.
- Witness sources: dated interview notes, declarations, deposition transcripts and errata, relevant correspondence, and organizational deposition topics where applicable.
- Transaction records: debtor and counterparty ledgers, bank records, invoice applications, remittance notices, contracts, amendments, and transaction communications.
- Source inventory: stable document IDs, Bates ranges where available, custodians, preserved versions, collection dates, and known coverage gaps.
- Review constraints: scheduling and discovery orders, confidentiality restrictions, privilege decisions, and responsibility for unresolved questions.
Retain source files separately from analytical annotations. Include surrounding material needed to test each statement: an email attachment, the preceding deposition question, or the bank entry corresponding to a ledger posting may change its meaning.
Use the template
The companion template is Bankruptcy Adversary Proceedings — Witness evidence matrix. You can copy this table into your working document or spreadsheet. Assign stable row IDs so sorting does not break references in examination outlines.
| Row / issue | Proposition / burden | Witness / capacity | Statement citation | Document references | Conflict / gap | Foundation / status | Action / owner |
|---|---|---|---|---|---|---|---|
Use Row / issue to connect a factual proposition to a claim or defense and its authority in counsel’s issue framework. Record the verified burden or an explicit assignment to resolve it; witness affiliation does not determine the burden.
In Statement citation, identify source type and exact location: interview-note paragraph, declaration paragraph, or deposition page and lines. Include the statement date. In Document references, distinguish supporting, contrary, and contextual material. For spreadsheets, record the preserved version, worksheet, and cell range; for PDFs, use document ID and page or Bates reference.
Use Foundation / status for evidentiary questions, circulation restrictions, and verification status—not a blanket admissibility conclusion. Action / owner should name a responsible person and specific next step. Record an internal target date if useful; verify any court or discovery deadline separately.
Step by step
1. Define the propositions the evidence must address
Start with the operative pleadings and counsel’s issue framework. Break broad allegations into questions witnesses and documents can address: who authorized a payment, which entity received funds, or what delivery records existed when an invoice was approved.
Use one row per disputed proposition within an element or defense. Split rows involving different transactions or materially different knowledge sources. A witness’s account of authorization should not silently become proof of receipt, ownership, or a defense.
Record the issue reference, proposition, and verified burden. If the legal framework remains unsettled, assign that question rather than presenting it as a factual gap.
2. Establish stable source references
Create an index connecting each document ID to its preserved version and location. Distinguish debtor records from counterparty records, and contracting entities from invoice issuers, payees, and intermediaries. Similar names alone do not justify consolidating entities.
For bank and accounting evidence, distinguish payment initiation, clearing, invoice application, and ledger posting dates. Record the petition date separately where relevant. These categories describe source events; counsel must determine their legal significance under the applicable claim and authority.
Enter exact references in the matrix. Identify missing attachments, unavailable exports, and incomplete periods. Preserve the original spreadsheet and record the reviewed version so later sorting or filtering does not make cell references misleading.
3. Classify each witness account by its actual basis
Identify the witness’s role during the relevant period, employing entity, and involvement in the transaction. Separate personal recollection, information learned from others, review of contemporaneous records, and counsel’s inference.
Do not turn “I normally approved those payments” into “I approved this payment.” An interview note is the interviewer’s record of an account, not interchangeable with a declaration or transcript. Preserve attribution, qualifications, and uncertainty.
Organizational testimony requires separate treatment. Civil Rule 30(b)(6) requires designees to testify about information known or reasonably available to the organization, not only their personal recollection. See Civil Rule 30(b)(6). Record capacity and knowledge basis; employment alone does not make a witness an organizational designee.
4. Pair each proposition with supporting and adverse records
Read each cited passage in context before summarizing it. Match transaction identifiers, amounts, entities, and dates across accounts and records. A ledger description may suggest a relationship without resolving it.
List material supporting and contrary references together. Describe apparent inconsistencies neutrally: “Witness recalls approval before transmission; email requests confirmation after the recorded initiation time.” Determine whether the email concerns initial approval, later documentation, or another transaction before calling it a contradiction.
Record whether the dispute concerns sequence, identity, amount, knowledge, or interpretation. Label counsel’s proposed explanation as an inference. This classification helps determine whether the next action is an interview, record request, or legal analysis.
5. Separate evidentiary questions from factual confidence
A persuasive factual account can still present evidentiary problems. Bankruptcy Rule 9017 applies the Federal Rules of Evidence. Evidence Rule 901(a) addresses authentication; Rule 803(6) separately sets conditions for qualifying regularly conducted activity records, including foundation and trustworthiness. Indexing a ledger satisfies neither inquiry by itself. See Bankruptcy Rule 9017 and Evidence Rules 901(a) and 803(6).
Identify potential foundation witnesses, unexplained record-generation details, and hearsay questions, including statements embedded within records. Keep factual confidence separate from evidentiary readiness.
Screen notes and linked communications before wider circulation. Record restrictions without copying potentially protected substance into an unrestricted matrix. Assign privilege questions rather than assuming every witness interview or analytical table is protected.
6. Convert gaps into targeted follow-up
Replace “need more evidence” with an action: obtain a missing bank page, identify who maintained the application ledger, or locate an approval email’s attachment. State which proposition the action will test.
Prioritize gaps that could change the factual theory or examination plan. Civil Rule 26(b)(1), applicable through Bankruptcy Rule 7026, permits discovery of relevant, nonprivileged information proportional to the case’s needs; discoverability does not require admissibility. See Civil Rule 26(b)(1).
Record an owner, intended decision, and status. Distinguish voluntary interviews, party discovery, and potential nonparty collection. Keep procedural tracking separate, but reference the relevant request or assignment so the matrix does not lose unresolved evidence needs.
7. Verify the matrix before using it for examination
Have a second reviewer open each material citation and test whether it supports the proposition as written. Check negative assertions carefully: “not found in the reviewed set” does not establish “never existed.” Confirm transcript citations against any errata without silently replacing the original testimony.
Build examination questions from verified rows, beginning with knowledge and foundation before inconsistencies. Preserve unresolved alternatives instead of scripting the preferred answer.
Record reviewer, verification date, and open assignments in Foundation / status and Action / owner. Freeze a dated examination version. When later testimony changes a row, retain the earlier source and explain the revision rather than erasing the conflict.
Worked example
Fictional scenario: All parties, people, documents, amounts, and record descriptions below are fictional. Counsel represents Harbor Loom Components LLC in an adversary proceeding brought by the trustee of Briar Millworks Inc., seeking recovery of an $84,000 payment. Counsel’s separate issue sheet identifies the applicable legal questions; the matrix tests facts without deciding liability or burdens.
Former controller Elena Vale recalls that payment followed delivery confirmation. Receivables manager Marcus Chen says Harbor applied the receipt to two older invoices. The reviewed records include interview notes dated September 15–16, 2026, an email requesting delivery confirmation, a partial bank statement, remittance instructions, and ledger exports. The referenced delivery attachment and bank transaction detail are absent.
| Row / issue | Proposition / burden | Witness / capacity | Statement citation | Document references | Conflict / gap | Foundation / status | Action / owner |
|---|---|---|---|---|---|---|---|
| W01 / authorization | Confirmation preceded authorization; legal relevance and burden unresolved in I-2 | Vale / former controller | INT-01, Sept. 15, 2026, ¶¶ 8–10; interview notes | Context: EMAIL-07 p. 1 requests confirmation Aug. 7; LED-02 v1, Payments!F18 lists Aug. 6 initiation | Apparent sequence conflict; confirmation attachment absent; authorization time unknown | Vale’s observation unclear; email and export meanings unverified | Associate Reed: locate attachment and ask what Vale personally observed; counsel to resolve I-2 |
| W02 / payment sequence | Entries may describe initiation and later clearing; legal significance reserved in I-2 | Vale / former controller | INT-01 ¶ 12; undefined “payment date” | LED-02 v1, Payments!F18: Aug. 6, 2026; BANK-04 p. 2: Aug. 8 debit, $84,000 | Same amount, but missing bank detail prevents conclusive matching | Candidate match only; bank reference and ledger field need verification | Analyst Park: obtain transaction detail and test linkage before reconciliation |
| W03 / invoice application | Harbor’s recorded application differs from remittance instructions; burden unresolved in I-3 | Chen / receivables manager | INT-02, Sept. 16, 2026, ¶¶ 4–6; ledger-based account | Support: HLED-03 v1, Applications!B22:E23; contrary instructions: REM-05 p. 1 identifies another invoice | Instructions and application may differ without contradicting Chen; invoices incomplete | Record-maintenance role unconfirmed; application basis unexplained | Counsel Moss: obtain invoices, ask about overrides, and resolve I-3 |
The matrix changes the examination plan. Vale should explain what she personally observed and whether the August 7 request sought first confirmation or later documentation. The email does not yet disprove her recollection.
Chen should explain application practices and the difference between instructions and actual allocation. Bank detail remains necessary to connect the ledger and debit reliably. Counsel therefore has three targeted inquiries, not a supposedly complete payment narrative.
Common mistakes
- Organizing only by witness: This hides overlapping accounts. Group by disputed proposition, then filter by witness for preparation.
- Flattening statement types: Label interview notes, declarations, and testimony separately; preserve qualifications and exact citations.
- Selecting one “payment date”: Retain initiation, clearing, and posting separately. Refer legal significance to counsel’s issue framework.
- Treating every mismatch as contradiction: Test whether records describe different stages, instructions, or actual events before characterizing the conflict.
- Calling missing material nonexistent: Identify the reviewed set and its coverage; assign collection or verification before making broader assertions.
Final quality check
- Every material proposition maps to a defined claim or defense.
- Burdens and authorities are verified or explicitly assigned for resolution.
- Statement citations identify date, source type, and exact location.
- Document references open the preserved version and supporting passage.
- Supporting, adverse, and contextual evidence are accurately distinguished.
- Entity identities and transaction dates remain separate where unresolved.
- Foundation and circulation restrictions have responsible reviewers.
- Open issues have concrete actions; verified rows identify reviewer and date.
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 source comparison and witness preparation. Explore trial preparation or the chronology viewer for related workflows. Counsel retains responsibility for source verification, evidentiary judgments, and follow-up decisions. Book a demo to discuss applying these capabilities to your review set.
Frequently asked questions
Should the matrix be organized by witness or claim?
Use claims and defenses as the primary structure, with disputed propositions underneath. Witness-based views help preparation but should retain links to competing accounts and shared records.
How should counsel record an interview that conflicts with a deposition?
Preserve both citations and state the precise difference. Check question wording, context, errata, and knowledge basis. Assign clarification rather than overwriting either account or prematurely labeling the difference impeachment material.
Can a ledger replace a witness who does not remember the payment?
Do not use the matrix to manufacture personal knowledge. Record what the ledger shows, the witness’s lack of recollection, and available foundation sources. Counsel must assess the proposed evidentiary route separately.
Can the completed matrix become a trial summary?
Not automatically. Rule 1006 concerns summaries of voluminous admissible materials that cannot conveniently be examined in court, whether or not introduced. Originals or duplicates must be available to other parties at a reasonable time and place. Assess those prerequisites separately; an analytical matrix is not automatically evidence. See Evidence Rule 1006.
Sources
- Federal Rules of Bankruptcy Procedure: Rules 7026, 7030, 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; apply governing substantive law, local rules, and case-specific orders separately.
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.
