How to create a claims and defenses evidence matrix for Partnership Disputes

Create a partnership-dispute evidence matrix by breaking each claim, defense, and requested remedy into propositions counsel must establish or rebut. Link each proposition to the operative agreement, supporting and adverse evidence, witness knowledge, and unresolved proof. Separate governance questions from financial classifications: a bank transfer does not establish a capital contribution, and missing minutes do not establish lack of consent. The deliverable is a source-linked working table identifying the alleged injury, competing explanations, evidentiary weaknesses, and the next action needed to test each position.

When to use this workflow

Use this workflow when pleadings, an investigation, or a threatened partner exit presents competing accounts of authority, contributions, distributions, record access, or financial loss. Outside counsel and in-house teams can use it to assess proof before selecting discovery priorities, evaluating settlement positions, or preparing witnesses.

First establish the entity type, governing law, and forum. A business informally called a partnership may require a different statutory framework. Delaware Chapter 15 is illustrative here, not a substitute for limited-partnership or LLC legislation. Federal procedural references concern U.S. district-court litigation; state proceedings and arbitration require their own rules and orders. See the Delaware partnership framework and Federal Civil Rules. (delcode.delaware.gov)

Keep the matrix focused on proof and uncertainty. It is neither a pleading nor an admissibility determination. This is general professional workflow guidance; actual rights depend on the agreement, governing law, facts, and forum.

What you need

Collect the operative pleadings or demand, requested relief, and counsel’s current list of disputed propositions. Add the partnership agreement, amendments, side letters, admission and withdrawal records, and evidence of alleged oral or implied changes.

Build the evidence set around the contested events:

• Governance: notices, minutes, consents, delegations, voting information, and conflict disclosures.
• Finances: contribution commitments, capital calls, bank statements, ledgers, audit trails, distribution schedules, tax records, and valuations.
• Communications: partner email, messages, attachments, and relevant personal-account communications within the authorized collection scope.
• Witnesses: dated accounts distinguishing firsthand knowledge, secondhand information, and document-refreshed recollection.

Assign stable document IDs and preserve clause, page, transaction, and spreadsheet-cell references. Record custodians, collection dates, missing attachments, and unavailable accounting periods separately. Otherwise, an incomplete collection can look like proof that an event never occurred.

Use the template

The Partnership Disputes — Claims and defenses matrix is a working table you can copy into your working document or spreadsheet. Use one row per element, defense proposition, remedy component, or material disputed fact. Give related rows an issue prefix without collapsing distinct proof questions.

Label the row as a claim, defense, or remedy proposition. “Proposition / injury” identifies whose alleged loss is at issue; it does not decide who may recover. “Rule / agreement” records verified authority and the provision effective at the relevant time. Cite evidence precisely: FIN-014, Transactions!D18:F18, not “financial records.”

Use “not located in reviewed set,” “contradicted,” or “requires legal analysis” deliberately: they describe different problems. The foundation field identifies a witness or other authentication route, not a presumed admissibility finding. Every unresolved row needs a defined action and responsible owner. Use restricted references where underlying material requires controlled access.

Step by step

1. Fix the legal and contractual frame

Record entity classification, governing law, forum, and agreement versions before building substantive rows. Under Delaware Chapter 15, the agreement generally governs interpartner and partnership-partner relations, subject to statutory limits and gap-fillers. The statutory definition recognizes written, oral, and implied agreements, including amendments. Version control and alleged modifications therefore present substantive evidence questions. See 6 Del. C. §§ 15-101(15), 15-103. (delcode.delaware.gov)

For a disputed oral change, record its alleged content, participants, timing, supporting conduct, and contrary evidence. Do not silently substitute it for signed language. Identify any amendment requirements and refer enforceability questions to counsel.

Output: agreement and authority references in the template, with unresolved classification or modification questions assigned.

2. Decompose claims and defenses into testable propositions

Translate “misappropriation of partnership funds” into questions: who authorized the payment, who received it, how it was classified, what obligation it satisfied, and whose loss is alleged?

Counsel should verify the applicable elements and defenses. The matrix organizes them; it should not supply an unverified cause of action. Separate liability from remedy and give the opponent’s explanation its own row where it requires independent proof. For example, an asserted loan repayment needs evidence of the original advance, repayment obligation, and amount outstanding.

Distinguish a factual rebuttal from an affirmative defense; do not use the matrix label to assume pleading requirements or proof burdens. Track those questions in the authority field.

Output: individually testable claim, defense, and remedy rows with the relevant legal question identified.

3. Match each governance event to its authority

For each disputed decision, identify the then-operative provision, notice evidence, eligible decision-makers, voting denominator, threshold, delegated authority, and claimed later approval. Distinguish execution, effective, transmission, and event dates.

Delaware’s defaults distinguish majority resolution of ordinary-course differences from unanimous consent for outside-ordinary-course acts, but must be read with the agreement and § 15-103. Transaction size alone should not determine the classification. See 6 Del. C. § 15-401(j). (delcode.delaware.gov)

Record both asserted authority and contrary evidence. If the approval clause concerns loans, first flag whether the disputed transaction was a loan. An incomplete minutes collection establishes a collection gap, not necessarily missing approval.

Output: governance rows showing the claimed authority, competing account, and unresolved predicate facts.

4. Reconcile money without assuming its classification

Trace each amount from the alleged obligation through incoming funds, outgoing payment, ledger posting, and later adjustments. Separate agreed capital, advances, loans, reimbursements, distributions, and allocations. Preserve competing calculations rather than overwriting one.

Section 15-401 supplies default account credits and charges and addresses advances beyond agreed capital. These provisions do not independently classify a particular transfer or establish its tax treatment. Read them with the agreement. See 6 Del. C. § 15-401(a), (d)–(e). (delcode.delaware.gov)

Cite reconciliation cells and identify duplicate postings, reversals, noncash valuations, liabilities, and missing bank periods. If a repayment satisfied a genuine debt, the payment amount alone does not answer the alleged-loss question.

Output: financial rows separating verified cash movement, disputed characterization, and competing loss calculations.

5. Attach adverse evidence and test foundation

Identify the strongest supporting and contrary items for each material assertion. Separate contemporaneous records from later explanations and firsthand knowledge from information learned from others. Retain dated witness-account versions when recollections change.

In federal proceedings, Evidence Rule 901(a) requires sufficient evidence that an item is what its proponent claims. Authentication does not resolve hearsay or other objections. Rule 1006 addresses evidentiary summaries of voluminous admissible materials that cannot conveniently be examined in court and requires access to underlying originals or duplicates. A counsel-created reconciliation is not automatically admissible. See Federal Evidence Rules 901 and 1006. (uscourts.gov)

Identify who can explain the accounting export, email attachment, or calculation methodology. Avoid treating a witness’s confidence as a substitute for knowledge.

Output: foundation sources, contrary evidence, and specific evidentiary questions recorded for material rows.

6. Turn proof gaps into bounded investigation tasks

Specify what would change the assessment: a missing consent attachment, accounting audit trail, bank confirmation, or explanation of a posting. Assign a custodian and owner rather than writing “more discovery.” Prioritize gaps that could defeat a theory or materially alter exposure.

Federal Rule 26(b)(1) limits discovery to nonprivileged matter relevant to claims or defenses and proportional to the case’s needs; discoverable information need not itself be admissible. Link proposed requests to matrix rows and explain their expected contribution. See Federal Civil Rule 26(b)(1). (uscourts.gov)

Keep partner information-access routes distinct from litigation discovery. For Delaware § 15-403, separately assess partner status, purpose, agreement restrictions, demand requirements, and necessary-and-essential limits. See 6 Del. C. § 15-403. (delcode.delaware.gov)

Output: prioritized, issue-specific tasks with owners and expected proof value—not a complete discovery plan.

7. Review protection and circulate a controlled version

Before circulation, review entries reproducing legal advice, interview analysis, or sensitive partner information. Identify the client, participant roles, communication purpose, and forwarding history rather than assuming all partnership communications have the same protection status.

Federal Evidence Rule 501 applies state privilege law concerning civil claims or defenses for which state law supplies the rule of decision. A confidentiality label does not itself establish privilege. See Federal Evidence Rule 501. (uscourts.gov)

Maintain a dated version and evidence cutoff. Distinguish observed facts, counsel’s inferences, and unresolved legal questions. Have a second reviewer test decisive rows against underlying documents and confirm the intended recipients.

Output: a controlled matrix with verified citations, review status, and expressly assigned open issues.

Worked example

Entirely fictional scenario: Alder Quay Design Partnership has three partners: Mira, Owen, and Tess. Mira challenges an $84,000 payment to Owen. Owen says it repaid an advance and all partners approved it.

The fictional agreement’s § 6.2 requires all three partners’ written approval for partner-loan repayments above $50,000. Section 4.1 identifies scheduled capital commitments; § 8.3 conditions distributions on reserves. Counsel has the signed agreement, an outgoing-payment bank statement, a partial ledger, selected emails, and Mira’s calculation. The incoming-funding records, complete audit trail, and referenced approval attachment have not been collected. These terms are illustrative, not market standards.

The matrix changes the immediate decision. Counsel should not treat the ledger label as conclusive or present Mira’s calculation as verified entitlement. A genuine advance could change both classification and loss analysis, while leaving an approval issue unresolved. Conversely, a capital classification could make § 6.2 the wrong approval provision. The missing attachment could affect authority, but its contents cannot be assumed. Each possibility calls for different proof, not merely more documents.

Common mistakes

• One row for the whole claim. Separate authority, classification, injury, and amount so weaknesses remain visible.
• Treating cash, capital, and profit allocation as interchangeable. Trace the transaction and test the agreement-based classification.
• Applying the latest agreement retrospectively. Cite the version operative at the event and record disputed modifications separately.
• Recording defenses only as adverse documents. Give independently testable defense propositions their own rows without assuming proof burdens.
• Calling missing approval proven misconduct. State collection limits and identify the missing record or witness.
• Converting an ownership fraction into damages. Separate arithmetic from entitlement, actual injury, and the effect of satisfying an existing obligation.

Final quality check

• Entity type, governing law, forum, and evidence cutoff are explicit.
• Claims, defenses, and remedies are separated into testable propositions.
• Agreement versions and legal propositions have verified source references.
• Material facts have document IDs and usable pinpoints.
• Supporting and adverse evidence have both been assessed.
• Financial amounts trace to underlying records, with assumptions identified.
• Foundation, protection, and circulation questions have been reviewed.
• Every open issue is resolved or assigned a responsible owner and defined action.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its document review, evidence analysis, privilege and confidentiality analysis, and chronology capabilities can support source review. Use the chronology viewer to examine event sequencing and connect unresolved witness questions to deposition preparation. The matrix remains counsel’s work product; legal theories, source verification, and evidentiary judgments remain with the legal team. Book a demo to discuss support for this evidence-analysis workflow.

Frequently asked questions

Should each partner have a separate matrix?

Usually begin with one issue structure and identify the relevant partner and alleged injury in each row. Separate controlled versions may be appropriate where representation, access, or protection concerns differ. Resolve those concerns before sharing.

How should an alleged oral amendment appear?

Use distinct rows for alleged terms, participants, timing, conduct, and contrary records. Identify relevant amendment provisions. Do not treat either signed language or a witness’s assertion as automatically resolving the modification question.

Can the matrix establish damages?

It can expose calculations and supporting evidence, not establish entitlement. Separate verified amounts, classification assumptions, injury, and recovery questions. In particular, test whether the challenged payment satisfied a real partnership obligation before equating the payment with loss.

When should counsel update the matrix?

Update affected rows after material productions, interviews, depositions, or revised calculations. Preserve the earlier assessment and explain what changed. Revisit connected defense and remedy rows when new evidence changes a liability proposition.

Sources

• Delaware Code, Title 6, Chapter 15, Subchapter I — agreement definition and governing framework.
• Delaware Code, Title 6, Chapter 15, Subchapter IV — partner accounts, decision-making, and information access.
• Federal Rules of Civil Procedure — federal discovery scope.
• Federal Rules of Evidence — privilege, authentication, and evidentiary summaries.

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.