How to prepare a document collection checklist for Partnership Disputes

Prepare a partnership-dispute document collection checklist by mapping each contested governance or financial event to the operative agreement, relevant records, custodians, and collection sources. Separate what counsel needs from what the client can access, and distinguish missing evidence from sources not yet searched. The deliverable should define collection scope, identify preservation and privilege-review concerns, and assign an accountable next action for each gap. It should also let another lawyer trace received material to its origin without treating collection as a decision to produce it.

When to use this workflow

Use this workflow when a partner alleges diverted distributions, unauthorized borrowing, exclusion from management, an improper capital call, or a disputed withdrawal valuation. It serves litigation counsel and in-house teams coordinating records held by partners, finance personnel, administrators, and external accountants.

Confirm entity classification first: a business described as a partnership may be an LLC or limited partnership. Establish governing law, forum, agreement history, and applicable orders. Delaware Chapter 15 provides the illustrative general-partnership framework here, not a nationwide rule or a substitute for other entity statutes.

In federal district-court discovery, Rule 26(b)(1) limits scope to nonprivileged matter relevant to claims or defenses and proportional to the case’s needs. State litigation and arbitration require separate procedural analysis. Federal Rule of Civil Procedure 26(b)(1)

What you need

Assemble these inputs before assigning searches:

• Matter definition: entity type, client identity, partner status, governing law, forum, disputed events, relevant periods, and requests or orders.
• Agreement history: executed agreements, schedules, amendments, side letters, admission records, withdrawal notices, and evidence supporting alleged oral modifications.
• Governance records: notices, meeting materials, minutes, written consents, voting records, delegated authority, and approval communications.
• Financial records: capital calls, contribution schedules, bank statements, transaction detail, ledgers, distributions, partner loans, reimbursements, tax records, and valuation materials.
• Source inventory: custodians, business and personal accounts used for partnership affairs, messaging applications, shared drives, accounting systems, devices, and external advisers.
• Constraints: retention settings, access restrictions, departed personnel, preservation instructions, prior collections, and potentially protected repositories.

Delaware Chapter 15 recognizes written, oral, and implied partnership agreements, including amendments; agreements generally govern internal relations subject to statutory limits. Collecting only the signed agreement may therefore miss evidence of the arrangement alleged. That does not establish a modification’s existence or enforceability. Delaware Code §§ 15-101(15), 15-103

Use the template

The Partnership Disputes — Document collection checklist is counsel’s working control document. Copy this table into your working document or spreadsheet. Use one row for each issue, record category, and source combination; split rows when owners, access conditions, or status differ.

Assign stable row IDs for collection correspondence. Specify the event window and record category: “capital records” is less useful than “cash-call notices, payment evidence, and posting detail for the disputed contribution.”

Use Evidence / pinpoint for received document IDs and clause, page, worksheet, or cell references. Before receipt, identify the basis for expecting a record without presenting that expectation as evidence.

Distinguish requested, received, partially collected, inaccessible, and not located after a defined search. Keep collection status separate from review status. Record access and deletion concerns, then name an owner and next action. Include a follow-up date; identify the authority separately if it reflects a procedural deadline rather than an internal target.

Step by step

1. Define disputed events and collection boundaries

Translate allegations into identifiable events: a capital call, loan approval, distribution, removal of management access, or withdrawal notice. Identify whose conduct and financial interest are disputed and why each category bears on the issue.

Choose a period covering preparation, decision, implementation, and any alleged correction or ratification. Record why surrounding communications matter instead of defaulting to an unlimited search.

Checklist output: issue, targeted records, period, and unresolved scope questions. Distinguish material needed for counsel’s investigation from material targeted by a particular discovery request.

2. Reconstruct the operative agreement and partner roster

Request potentially operative versions, signature pages, schedules, side letters, and amendments. Align admission, transfer, withdrawal, and expulsion records with disputed event dates. Obtain evidence supporting competing accounts of partner status or voting entitlement.

Map each disputed decision to the asserted notice, consent, authority, contribution, distribution, or valuation provision. Separate execution dates from claimed effective dates. An unsigned draft may explain negotiations without proving adoption; missing written consent does not itself establish that consent never occurred.

Checklist output: document IDs, clause references, asserted effective periods, version conflicts, and an owner for execution or adoption evidence.

3. Map custodians, systems, and preservation concerns

Interview the managing partner, finance lead, and relevant administrators about actual record locations. Ask about accounting audit trails, personal email used for partnership business, messaging, shared folders, and departing partners’ devices.

Identify who controls each source and whether deletion or overwrite settings require prompt counsel review. Do not wait for the entire checklist before escalating an identified loss risk. Do not direct access to another partner’s personal account without resolving authority and collection method.

Checklist output: custodian, source, access limitation, retention setting, and preservation action or question. Mark unconfirmed technical details explicitly; link any separate source inventory by row ID.

4. Specify financial and governance records that test competing accounts

For contributions, request the obligation, payment instruction, bank movement, ledger posting, and later adjustment. Separate capital, loans, reimbursements, distributions, and allocations. For governance, collect notices, circulated materials, attendance evidence, votes, delegation, and alleged ratification.

Delaware § 15-401 provides defaults concerning partner accounts, advances, and decision-making, subject to the agreement and § 15-103. Those defaults do not resolve a disputed payment’s classification. Collect records supporting both competing explanations. Delaware Code § 15-401

Checklist output: requested category, issue connection, expected source, and dependency. Identify bank or accountant records that are needed but unavailable, and assign counsel to determine the access route.

5. Collect with source context intact

Assign collection identifiers and record who supplied material, its source, receipt date, and collection method. Preserve received files separately from working copies. Where feasible, retain spreadsheet formulas, worksheets, attachments, message context, and accounting detail alongside readable reports.

Compare requests with deliveries. A distribution summary does not replace transfer evidence; a PDF ledger may omit adjustment history. Test date coverage and unexplained breaks before closing the source.

Source documentation supports later authentication analysis: Evidence Rule 901(a) requires sufficient evidence that an item is what its proponent claims. Authentication does not resolve other admissibility objections. Federal Rule of Evidence 901(a)

Checklist output: receipt IDs, pinpoints, linked collection details, and coverage gaps.

6. Separate collection from privilege and disclosure decisions

Route potentially protected material to counsel rather than having collectors silently omit it. Identify the client, participants’ roles, legal versus business purpose, forwarding history, and attachments. Escalate joint-representation and former-partner access questions.

Evidence Rule 501 directs application of state privilege law to civil claims or defenses for which state law supplies the rule of decision; analyze mixed claims separately. Federal Rule of Evidence 501

Federal withholding on privilege or trial-preparation grounds requires an express claim and a description enabling assessment without revealing protected information. The checklist does not replace that process. Federal Rule of Civil Procedure 26(b)(5)(A)

Checklist output: review routing, unresolved protection questions, and responsible lawyer—not an untested privilege conclusion.

7. Validate gaps and assign the next collection decision

Ask whether missing records exist elsewhere, were never created, or survive only as summaries. Specify which sources were searched, by whom, for what period, and with what limitations. Preserve conflicting explanations rather than silently choosing one.

For federal Rule 34 requests, connect gaps to response commitments. Objections must be specific and disclose whether responsive material is withheld. Production in lieu of inspection must finish by the requested inspection time or another reasonable time specified in the response. Check orders and stipulations separately. Federal Rule of Civil Procedure 34(b)(2)

Checklist output: next search, access decision, scope decision, or documented stopping point, with an owner and relevant response reference.

Worked example

Fictional scenario: Harbor Lantern Design Partnership is a Delaware general partnership. Partner Mira Chen disputes a $240,000 payment to partner Owen Reed, recorded as repayment of an advance, and a subsequent capital call. Counsel has a signed agreement, ledger export, and selected emails, but no bank transfer evidence or complete messaging collection. Every party, amount, document, and provision in this example is fictional.

The fictional agreement’s § 6.2 requires written approval by both partners before the partnership accepts a partner advance. An email refers to a later “revised approval arrangement,” but supplies neither its terms nor adoption evidence. Counsel must investigate without assuming the original provision or an alleged change resolves the dispute.

The immediate priorities are message preservation and bank access, with agreement history pursued in parallel. Original funding evidence could distinguish a genuine advance from an unsupported ledger characterization; approval evidence could change the authority analysis. The email justifies another search, not acceptance of an amendment. None of these rows is complete.

Common mistakes

• Collecting only formal files. Include operational communications and evidence of alleged oral or implied arrangements without treating allegations as proof.
• Treating every partner payment as capital. Obtain transfer evidence, posting history, loan records, and reimbursement support before classification.
• Ignoring departing partners’ sources. Identify devices, account changes, and retention risks early; resolve collection authority first.
• Equating “not supplied” with “nonexistent.” Record completed searches and unsearched sources separately.
• Assuming unrestricted partner access. Delaware § 15-403 addresses purpose, written demands, counsel’s written authorization, and contractual variation of information rights. Analyze those conditions separately from discovery. Delaware Code § 15-403

Final quality check

• Entity classification, client identity, governing law, forum, and purpose are recorded.
• Agreement versions and partner-status records cover disputed events.
• Financial rows distinguish obligations, transfers, postings, and adjustments.
• Messaging, personal accounts, audit trails, and departing custodians have been considered.
• Evidence IDs and pinpoints have been checked against received sources.
• Collection, privilege review, and production statuses remain distinct.
• Every gap has an owner and action or a documented scope decision.

Complete the workflow with DecoverAI

DecoverAI is the Legal Intelligence Platform for litigation and transactions. Its litigation capabilities include document review, privilege and confidentiality analysis, chronology, and evidence analysis. Use the chronology viewer to support examination of disputed events while maintaining this checklist as counsel’s separate work product. Lawyers retain responsibility for source verification, collection scope, and legal decisions. To discuss the collection-to-review workflow, book a demo.

Frequently asked questions

Should personal email and text messages appear in the checklist?

Include them when they may contain relevant partnership business. Identify custodians, periods, and access constraints. Listing a source does not authorize access; counsel must determine the collection method.

How much financial history should counsel request?

Start with enough history to trace the disputed obligation, funding, posting, and disposition. Expand for material opening balances, prior advances, reversals, or competing explanations. Record why each expansion is needed.

Can a partner’s spreadsheet replace accounting-system records?

Treat it as evidence and an explanation, not an automatic substitute. Seek underlying transactions, formulas, and adjustment history. Record reconciliation to ledger and bank records and identify unexplained differences.

When can a collection row close?

Close it when defined sources and periods are addressed, received records are identified, and remaining gaps have a documented disposition. Assigned follow-up should remain visibly open. A completed search does not prove that missing evidence never existed.

Sources

• Federal Rules of Civil Procedure: Rules 26 and 34.
• Federal Rules of Evidence: Rules 501 and 901.
• Delaware Code, Chapter 15, Subchapter I: agreement definitions and statutory framework.
• Delaware Code, Chapter 15, Subchapter IV: accounts, governance, and information access.

Scope: General US legal-workflow guidance, not advice for a particular matter. Rights depend on the operative agreement, applicable law, and facts.

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.